| 1 |
> I wrote a stabilization detector (in Python) that is able to realize |
| 2 |
> when a package was installed as unstable version but became stable |
| 3 |
> through a more recent ebuild. |
| 4 |
> |
| 5 |
> There is a project website [1] and a corresponding bug-report [2] for |
| 6 |
> enhancement. |
| 7 |
|
| 8 |
Nice. I've been looking for something like this for a while. I |
| 9 |
obviously wasn't looking hard enough. |
| 10 |
|
| 11 |
> I'm writing to you, because I think that just an external program |
| 12 |
> checking for such stabilizations is not good enough and it would be |
| 13 |
> even better to let Portage itself handle this after a sync for |
| 14 |
> example. Now I'm interested in what you think about it. |
| 15 |
|
| 16 |
I for one would like to see this kind of functionality added to portage. |
| 17 |
I regularly use a mixture of stable and unstable packages on the same |
| 18 |
machine and it can become a real pain working out which entries are |
| 19 |
still required in package.keywords. |
| 20 |
|
| 21 |
I would like an option to automatically remove (or comment) lines like |
| 22 |
~cat/pkg-1.2 from package.keywords and package.unmask also - if a |
| 23 |
feature request isn't too cheeky. :-) |
| 24 |
|
| 25 |
NW |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-portage-dev@g.o mailing list |
Archives