php53-devel

Hello,
I’m using SLES 11.2 and would like to install php53-devel. Where can I get this? I have downloaded the two SDK isos but can’t find it on there.

Cheers,

Nathan.

It’s in the SDK Updates Channel.

S | Name | Typ | Version | Arch | Repository
–±------------±------±-------------±-------±---------------------
| php53-devel | Paket | 5.3.8-0.33.2 | x86_64 | SLE11-SP2-SDK-Updates
| php53-devel | Paket | 5.3.8-0.27.1 | x86_64 | SLE11-SP2-SDK-Updates
| php53-devel | Paket | 5.3.8-0.23.1 | x86_64 | SLE11-SP2-SDK-Updates

So not on the DVDs.

On 07/25/2012 03:04 AM, nathanfriend08 wrote:[color=blue]

Hello,
I’m using SLES 11.2 and would like to install php53-devel. Where can I
get this? I have downloaded the two SDK isos but can’t find it on
there.[/color]

Just a side comment. I have some things running on the SLES11-SP2 php53… and
all it not so nice. A LOT of packages want just php… and not php53… so the
ability to use other repos, etc… is problematic. Things get really confused
easily. This was not done well. php53 is a hack (one off in time) at best.

IMHO, this could have been (maybe) better handled with an upgraded repos with
the newer version of php instead of a package rename.

I completely agree.

How do I add the SDK updates channel in YaST?

In the Novell Customer Center, select My Products → Mirror credentials. There, you have all the repositories listed. Get the url of SDK and SDK-Updates, and simply add it to your repos with
yast2 repositories or zypper add-repo

Hello Enovaklbank,
I’ve added the repos but I’m getting the following error:

There was an error in the repository initialization.
SLES-11-SP2-SDK-UPDATES’: [|] Valid metadata not found at specified URL(s)
History:

  • [|] Repository type can’t be determined.

Any ideas?

Cheers,

Nathan.

RESOLVED

Hi,
Thanks for your help. Got this resolved by Novell support. Had to add the ISOs to Add on products in Yast then re-register the system to get the online SDK-channels added. You can then remove the ISOs.

Cheers,

Nathan.

Btw, this is a REAL pain… just saying.

SUSE always says they’ve improved their patching etc… but it’s always
busted in some way or another. Design? Anyone?

Sigh… (not sure if anyone realizes what a struggle it is
to get SUSE into a company because of nonsense like this)

On 08/01/2012 04:14 AM, nathanfriend08 wrote:[color=blue]

RESOLVED

Hi,
Thanks for your help. Got this resolved by Novell support. Had to add
the ISOs to Add on products in Yast then re-register the system to get
the online SDK-channels added. You can then remove the ISOs.

Cheers,

Nathan.

[/color]