On Fri, 05 May 2006 11:05:47 +0200
Hanno Fietz <hanno.fietz@...> wrote:

> Here's a suggestion for two portage features that I would appreciate.
> Please tell me if this is the wrong list.
> 
> I would like to have a system where ebuilds are classified such that
> when updating a package, I can tell whether this is a security patch
> or critical bugfix or new feature release or whatever. Thus, I could
> set up automatic updates that check only for critical patches and do
> not install every tiny new fancy thing.

Short version: needs modular dep resolver first (or some new fancy
type of visiblity filter), no chance otherwise. And even then I don't
think it's possible to note these things in ebuilds as the ebuild
doesn't know the upgrade path.

> Also, a system would be nice, where authors of a package or the ebuild
> maintainers could supply a message to the user along with the ebuild,
> for example to warn them of massive numbers of reverse dependencies
> that are going to be broken by the update (-> libexpat! I would have
> chosen a different time for the update if I had known what I had to
> update after that).

elog and/or glep 42.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.