| 1 |
On Fri, 2006-27-10 at 18:17 +0200, Johannes Weiner wrote: |
| 2 |
> Hi there, |
| 3 |
> |
| 4 |
> I wrote a stabilization detector (in Python) that is able to realize |
| 5 |
> when a package was installed as unstable version but became stable |
| 6 |
> through a more recent ebuild. |
| 7 |
> |
| 8 |
> There is a project website [1] and a corresponding bug-report [2] for |
| 9 |
> enhancement. |
| 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 |
> Regards, |
| 17 |
> Johannes Weiner |
| 18 |
> |
| 19 |
> |
| 20 |
> [1]: http://saeurebad.de/~hannes/estab.html |
| 21 |
> [2]: http://bugs.gentoo.org/show_bug.cgi?id=143880 |
| 22 |
|
| 23 |
I don't know about the portage devs, but I am interested in it for |
| 24 |
porthole. I have been wanting to add something like this to porthole |
| 25 |
for a while. The latest changes I made to the ebuild table dipslay adds |
| 26 |
the "Overlay" column (Y/N) and path (as a tooltip), also whether an |
| 27 |
installed version is no longer supported (ebuild is no longer in the |
| 28 |
tree). Detecting now stabilized packages would add more info available |
| 29 |
to maintainers. |
| 30 |
|
| 31 |
I have been wanting to add some code to check the tree for dupes of an |
| 32 |
overlay that are newer than the overlay's ebuild. Also to help |
| 33 |
keep /etc/portage files up to date by detecting stabilized packages like |
| 34 |
your routines. |
| 35 |
|
| 36 |
I'll check it out in the next few days. If it is included in portage |
| 37 |
then it will be easily accessible to porthole. |
| 38 |
-- |
| 39 |
Brian <dol-sen@×××××.net> |
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-portage-dev@g.o mailing list |
Archives