[gentoo-user] maintaining package.keywords

[gentoo-user] maintaining package.keywords

[Alex Schuster]

Hi there!

Is there an automatism to inform me that a package has become stable, so I 
can remove it from package.keywords?

I often need to add a package there, tvbrowser for example needed 24 more 
masked packages. But after a while they become stable (tvbrowser now only 
needs 5 unstable packages), and a world update would give me the next 
unstabe version. What do you do about it?

	Alex
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] maintaining package.keywords

[Ken]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Schuster wrote:
> Hi there!
> 
> Is there an automatism to inform me that a package has become stable, so I 
> can remove it from package.keywords?
> 
> I often need to add a package there, tvbrowser for example needed 24 more 
> masked packages. But after a while they become stable (tvbrowser now only 
> needs 5 unstable packages), and a world update would give me the next 
> unstabe version. What do you do about it?
> 
> 	Alex

Running eix -T may help.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGbap50PM4px2/kjgRAhzmAJwMUT5AMiK37//Xg0OzadhKwYiU2ACfQsOv
ZXf1O3Jxcn0qCIWdbi2nAAk=
=ALMY
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] maintaining package.keywords

[Albert Hopkins]

On Mon, 2007-06-11 at 21:53 +0200, Alex Schuster wrote:
> Is there an automatism to inform me that a package has become stable,
> so I 
> can remove it from package.keywords?
> 
> I often need to add a package there, tvbrowser for example needed 24
> more 
> masked packages. But after a while they become stable (tvbrowser now
> only 
> needs 5 unstable packages), and a world update would give me the next 
> unstabe version. What do you do about it? 

Alex,

I believe, per the man page, that you can specify any DEPEND atom, so
you could include versions e.g:

        <=media-tv/tvbrowser-2.5.0 ~x86

Have you tried something like that and it didn't work?


--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] maintaining package.keywords

[Alex Schuster]

Albert Hopkins writes:

> I believe, per the man page, that you can specify any DEPEND atom, so
> you could include versions e.g:
>
>         <=media-tv/tvbrowser-2.5.0 ~x86
>
> Have you tried something like that and it didn't work?

I thought I had some while ago, but obviously I did something wrong, 
because this seems to work quite well. Thanks!

	Alex
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] maintaining package.keywords

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]

On Monday 11 June 2007 21:53:49 Alex Schuster wrote:
> Is there an automatism to inform me that a package has become stable, so I
> can remove it from package.keywords?
>
> I often need to add a package there, tvbrowser for example needed 24 more
> masked packages. But after a while they become stable (tvbrowser now only
> needs 5 unstable packages), and a world update would give me the next
> unstabe version. What do you do about it?

Personally I use Paludis [1]. This gives me access to gimme.rb [2] to unmask
packages. It also gives me access to config-decruft [3] (another ruby script
which can tell me of redundancy or unneeded entries in my config files. E.g.:

virtual/c++-tr1-memory: slot 0: virtual/c++-tr1-memory-0::installed installed, virtual/c++-tr1-memory-0::gentoo available with keywords amd64
virtual/c++-tr1-type-traits: slot 0: virtual/c++-tr1-type-traits-0::installed installed, virtual/c++-tr1-type-traits-0::gentoo available with keywords amd64
virtual/c++-tr1-functional: slot 0: virtual/c++-tr1-functional-0::installed installed, virtual/c++-tr1-functional-0::gentoo available with keywords amd64

[1] http://paludis.pioto.org/
[2] http://planet.gentoo.org/developers/rbrown/2007/04/11/give_me_all_your_loving
[3] http://paludis.pioto.org/trac/browser/scratch/scripts/config-decruft

With Portage versioned atoms and eix-test-obsolete is your best bet.

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]