| View previous topic :: View next topic |
| Author |
Message |
Herodot
Guru
Joined: 29 Jul 2002
Posts: 429
Location: Professor Xavier's school for gifted youngsters
|
 Posted: Sat Nov 30, 2002 8:13 pm Post subject: Masked packages not in package.mask |
 |
|
Hello world,
this may be a stupid question, but: Howcome "emerge -s freenet" says it's masked, when /usr/portage/profiles/package.mask doesn't mention it at all? I can use "~x86", but I'd like to know why it's masked, and package.mask usually explains it.
Herodot |
|
| Back to top |
|
 |
BlackPhoenix
Tux's lil' helper
Joined: 01 Oct 2002
Posts: 124
|
| Posted: Sat Nov 30, 2002 9:59 pm Post subject: |
|
|
| I had the same problem with Mozilla 1.2_beta... I wanted to try it out, but I cannot find it in packages.mask, and I have the ~x86 keyword...still masked... Thats kindda...weird. Did they add a THIRD place to mask stuff? |
|
| Back to top |
|
|
zhenlin
Veteran
Joined: 09 Nov 2002
Posts: 1361
|
| Posted: Sun Dec 01, 2002 2:35 am Post subject: |
|
|
| Code: |
# <phoenix@gentoo.org> (21 Nov 2002)
# The huge nsplugins mask. These plugins use
# the new layout (/usr/lib/nsbrowser/plugins)
# and should work in both mozilla and phoenix.
=app-text/acroread-5.06-r2
=net-www/netscape-flash-6.0b-r1
=net-www/netscape-plugger-4.0-r2
--
# moz (also for galeon-1.2.6)
# worksforme // Spider
# need this out to get 1.2 in tree. <azarah@gentoo.org>
#>=net-www/mozilla-1.0.2
# <raker@gentoo.org> (25 Sep 2002)
# version bump. ssl and other fixes
--
# <cardoe@genoo.org> (25 Jul 2002)
# Moz 1.1beta (don't kill me Azarah for putting this here!)
# need this outta here to get 1.2 in. <azarah@gentoo.org>
#>=net-www/mozilla-1.1
# <azarah@gentoo.org> (25 Jul 2002)
# gawk is very flexible and can be used instead
--
# as it uses less RAM during compile
# but shouldn't be unmasked just for this
# only changes the buildprocess
=net-www/mozilla-1.0-r4
# <azarah@gentoo.org> (29 Jul 2002)
# I have major formatting problems with this one .. even
|
Ahem... |
|
| Back to top |
|
|
Herodot
Guru
Joined: 29 Jul 2002
Posts: 429
Location: Professor Xavier's school for gifted youngsters
|
| Posted: Sun Dec 01, 2002 4:10 am Post subject: |
|
|
You can ahem all you like zhenlin - the code you show doesn't mention 1.2b.
Anyway, shouldn't | Code: | | grep -i <progname> /usr/portage/profiles/package.mask |
reveal when a package is masked?
- Herodot |
|
| Back to top |
|
|
zhenlin
Veteran
Joined: 09 Nov 2002
Posts: 1361
|
| Posted: Sun Dec 01, 2002 4:20 am Post subject: |
|
|
Oops, Didn't see comment
However,
| Code: |
# env ACCEPT_KEYWORDS=\~x86 emerge -p mozilla
These are the packages that I would merge, in order.
Calculating dependencies ...done!
[ebuild N ] x11-misc/xloadimage-4.1
[ebuild U ] app-crypt/gnupg-1.2.1
[ebuild U ] net-www/mozilla-1.2
|
and
| Code: |
# env ACCEPT_KEYWORDS=~x86 emerge -p freenet
These are the packages that I would merge, in order.
Calculating dependencies ...done!
[ebuild N ] net-p2p/freenet-0.5.0.5
|
indicates that they are both masked via ~x86. Perhaps a emerge rsync would help? |
|
| Back to top |
|
|
Herodot
Guru
Joined: 29 Jul 2002
Posts: 429
Location: Professor Xavier's school for gifted youngsters
|
| Posted: Sun Dec 01, 2002 4:38 pm Post subject: |
|
|
Yes, I know about ACCEPT_KEYWORDS="~x86", I even said so.
Still, there's no mention of freenet in package.mask. So my question stands: Where is it masked?
The same goes for Mozilla: We saw that package.mask doesn't mention 1.2, but you can emerge it with the above keyword.
So, my question in the general case: How does this work?
- Herodot |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sun Dec 01, 2002 6:17 pm Post subject: |
|
|
| Herodot wrote: | | So, my question in the general case: How does this work? |
Every ebuild now defines a KEYWORDS variable. If it doesn't, it will be masked on all architectures. In that KEYWORDS variable, for each architecture, three values are possible: - arch, in which case it is considered stable on that architecture and will install normally
- ~arch, in which case it is considered unstable on that architecture, and will install only if ACCEPT_KEYWORDS="~arch" is defined
- -arch, in which case it is considered unusable on that architecture, and will not install unless you try to force it by passing emerge a full path to an ebuild. It will usually not work, however, and may not even compile.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
MoonWalker
Guru
Joined: 04 Jul 2002
Posts: 510
|
| Posted: Fri Dec 06, 2002 3:20 pm Post subject: |
|
|
So KEYWORDS now have replaced package.mask or? I kinda wonder as I like to use the ~arch to be a bit in the frontline, but there is some packages I don't want to have. Like apache 2.0 , to change it to -arch in the ebuild file will it be equal to as if it were in package.mask?
I tried to pin apache 1.3 in the world file but it don't seam to work when making use of ~arch (aka ~x86) in make.conf
_________________
/Joakim
Living on earth is expensive, but it includes a free trip around the sun
every year. |
|
| Back to top |
|
|
lx
Veteran
Joined: 28 May 2002
Posts: 1012
Location: Netherlands
|
| Posted: Fri Dec 06, 2002 4:25 pm Post subject: |
|
|
Keywords are replacing the mask file, but you could still use it, if you want to exclude packages you could add these to the package.mask file (probably write a simple scripts that does emerge rsync so this is done automatically), you could also use PORTDIR_OVERLAY for the specific ebuilds and as you described put KEYWORDS="-x86" you need to do this for every new packages that comes out.... So I would opt for putting <net-www/apache-2.0 ad end of package.mask file
Cya lX.
_________________
"Remember there's a big difference between kneeling down and bending over.", Frank Zappa |
|
| Back to top |
|
|
MoonWalker
Guru
Joined: 04 Jul 2002
Posts: 510
|
| Posted: Sat Dec 07, 2002 12:19 pm Post subject: |
|
|
| lx wrote: | | Keywords are replacing the mask file, but you could still use it, if you want to exclude packages you could add these to the package.mask file |
This could have been useful if it wasn't that the package.mask was overwritten when doing a emerge rsync. If the mask file will be replaced (it obviously are not yet) by a -arch parameter in the keyword directive, then it could be usefull to have a permanent mask file (not automaticly overwritten) for personal use. Right now we seam to be in a "paradigm shift", but I guess this will be cleared before 1.4 are official.
_________________
/Joakim
Living on earth is expensive, but it includes a free trip around the sun
every year. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sat Dec 07, 2002 12:25 pm Post subject: |
|
|
Warning: rampant speculation ahead, not backed up by any official word from anybody.
I think sticky variables are coming to Portage. I have seen carpaski mention the concept. I interpret it to mean "Portage will remember the state of USE, CFLAGS, ACCEPT_KEYWORDS, and whatever else is deemed to be important, at the time of most recent emerge of package X, and will apply these variables by default whenever that package is referenced".
This belief is my current Portage Holy Grail, as I think it will solve lots of people's complaints about stable/unstable, masked packages, and hopefully it will give the power to the people that gsfgf is stumping for in her .sig, without having to resort to the kludge of "emerge --masked", which does not really appeal to me aesthetically.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
MoonWalker
Guru
Joined: 04 Jul 2002
Posts: 510
|
| Posted: Sat Dec 07, 2002 12:42 pm Post subject: |
|
|
Ok that sounds interesting. However not sure what happened now. I emerge rsync'ed, it overwrite my mask file, and reset the changes to keyword parameter I did in apache2. So a new emerge -up world OR emerge -up apache should show apache-2.0.43,but it don't...
_________________
/Joakim
Living on earth is expensive, but it includes a free trip around the sun
every year. |
|
| Back to top |
|
|
lx
Veteran
Joined: 28 May 2002
Posts: 1012
Location: Netherlands
|
| Posted: Sat Dec 07, 2002 1:15 pm Post subject: |
|
|
| MoonWalker wrote: | | Ok that sounds interesting. However not sure what happened now. I emerge rsync'ed, it overwrite my mask file, and reset the changes to keyword parameter I did in apache2. So a new emerge -up world OR emerge -up apache should show apache-2.0.43,but it don't... |
If you make changes to ebuilds you should use PORTDIR_OVERLAY in /etc/make.conf and make a directory with the same structure as /usr/portage, rsync syncs your /usr/portage with the one from ibiblio c.q. mirror, so all changes are reverted back. Your overlay packages have priority over the same packages in /usr/portage, therefor your changes won't get lost.
The package.mask files is in /usr/portage and thus overwritten by rsync, you should instead make a simple script that calls emerge rsync and then doesn echo ">=app-..../dsfhjskf-2" or something or make a patch, so you can reaply it, well running masked files is a bit of a hassle, but ain't recommended, besides I think future versions of portage will probably make it easier to use custom USE flags for specific packages and install certain unstable packages, at least I hope so,.....
Cya lX.
_________________
"Remember there's a big difference between kneeling down and bending over.", Frank Zappa |
|
| Back to top |
|
|
MoonWalker
Guru
Joined: 04 Jul 2002
Posts: 510
|
| Posted: Sat Dec 07, 2002 1:30 pm Post subject: |
|
|
| lx wrote: | | If you make changes to ebuilds you should use PORTDIR_OVERLAY in /etc/make.conf and make a directory with the same structure as /usr/portage, rsync syncs your /usr/portage with the one from ibiblio c.q. mirror, so all changes are reverted back. Your overlay packages have priority over the same packages in /usr/portage, therefor your changes won't get lost. |
Ok I can follow that, but now it happens like I wanted my changes to be reverted back and although package.mask was replaced and so was the apache-2.0.43 and mod_perl-1.99 ebuilds I changed ~x86 to -x86 in, but portage somehow don't seam to understand this as it still mask them out? I have ALLOWED_KEYWORDS="~x86" in make.conf
_________________
/Joakim
Living on earth is expensive, but it includes a free trip around the sun
every year. |
|
| Back to top |
|
|
zhenlin
Veteran
Joined: 09 Nov 2002
Posts: 1361
|
| Posted: Sat Dec 07, 2002 2:09 pm Post subject: |
|
|
| -x86 means DOES NOT WORK ON x86, ALWAYS MASK! |
|
| Back to top |
|
|
MoonWalker
Guru
Joined: 04 Jul 2002
Posts: 510
|
| Posted: Sat Dec 07, 2002 2:20 pm Post subject: |
|
|
| zhenlin wrote: | | -x86 means DOES NOT WORK ON x86, ALWAYS MASK! |
I know that, but I tested it before as way to mask apache2 while still have the rest of packages with ~x86 in Keyword. But problem is now it mysteriously still remains masked after #emerge rsync
I think I better make a new treed of this as it really don't have anything to do with the original topic.
_________________
/Joakim
Living on earth is expensive, but it includes a free trip around the sun
every year. |
|
| Back to top |
|
|
|
Portage & Programming
