Unable to emerge php-5.0

[bking]

I'm going crazy here trying to get php5 installed... Not sure why my change to /etc/portage/package.unmask isn't unmasking the package.

Code: Select all

root@myth php # more /etc/portage/package.unmask
=sys-fs/e2fsprogs-1.37
>=dev-php/php-5.0
>=dev-php/mod_php-5.0
root@myth php # emerge --pretend php

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] dev-php/php-4.3.11
root@myth php # grep php /usr/portage/profiles/package.mask
=dev-php/PEAR-PEAR-1.3.5-r1
#=dev-php/mod_php-5*
=dev-php/PECL-imagick-0.9.11

What else do I have to do to unmask this package? I commented out the mod_php mask in[/code] /usr/portage/profiles, but it stays masked with or without it (not that the above output is an emerge of mod_php... but)

Trying to get a handle on portage, but it's just not behaving as I'd expect.... What am I missing?

[ndarlow]

Hi,

package.unmask is obsolete, use package.keywords instead e.g.:

dev-php/mod_php ~x86
dev-php/php ~x86

Substitute your architecture for ~x86.

Regards,
Neil Darlow

[allanw]

Hi,

package.unmask is obsolete, use package.keywords instead e.g.:

dev-php/mod_php ~x86
dev-php/php ~x86

Substitute your architecture for ~x86.

Regards,
Neil Darlow

Huh? package.unmask is still being used to unmask package.mask packages.

[Buzz]

Hi,

package.unmask is obsolete, use package.keywords instead e.g.:

Are you sure? Is it possible you are confusing:

/usr/portage/profiles/package.mask

and

/etc/portage/package.mask

Cheers,

Buzz


The following should allow mod_php 5.0.4 to be pulled in:
(note that this is just a reiteration of what's above)

echo "dev-php/mod_php ~x86" >> /etc/portage/package.keywords
echo "dev-php/php ~x86" >> /etc/portage/package.keywords
echo "=dev-php/mod_php-5.0.4" >> /etc/portage/package.unmask

(if this doesn't do it, sync again, and double check all the portage files for conflicting lines)...

[gwolf]

Hi,

package.unmask is obsolete, use package.keywords instead e.g.:

No, it is not, package.unmask and package.keywords just serve different purposes.
/etc/portage/package.unmask is to unmask hardmasked packages, i.e. the packages that are described in
/usr/portage/profiles/package.mask

/etc/portage/package.keywords is to set keywords (like ~arch or -~arch) package-wise, as opposed to putting them to /etc/make.conf where they apply to each package.

bking,
I still think that your problem will be solved as ndarlow described, since you are probably running a stable (arch not ~arch) system. My previous comment only means that the reasoning was not quite correct.

[bking]

Well that seemed to work. After complaining about being blocked by 4.99.99, and unmerging the 4.x fixed that...

So I tried to emerge php5, and complained about no mpm installed in apache, so I added an mpm to my apache, but that needed r5, which requird addng the ~x86 keyword to a few other modules..... and well I got a build running, but my question now is: How scared should I be of having 7 ~x86 packages? Just wait till the version updates and remove the keyword?

Not bitching, just curious

Thanks for the info, think the keyword/masking makes sense now.