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

Ciaran McCreesh wrote:
> On Tue, 1 Nov 2005 14:32:47 +0100 Jakub Moc <[EMAIL PROTECTED]> wrote:
> | What do you mean "they aren't tied to ebuilds"? I don't really
> | understand what this feature should do then, it seems. Once again,
> | what's wrong with reusing emerge --changelog mechanism for displaying
> | this kind of information?
> 
> We make changes that have scope other than ebuilds.
> 
> | I'm not particularly happy with idea of emerge as a newsreader
> | really, IMHO we should display relevant, vital upgrading information
> | *when relevant*, not to inform users about upgrades that they are not
> | interested in in the least.
> 
> Which is what my proposed GLEP does, at least as far as we can
> determine automatically. Yes, occasionally this will mean giving, say,
> mysql 4.1 upgrade instructions to people who plan to use only mysql
> 4.0, but then, if we didn't give them the news, most of them wouldn't
> know that they don't want to upgrade.
> 
> And it doesn't turn emerge into a news reader. All portage does is
> deliver the news. How said news is read is a different issue.
> 
> | And please, keep the thing simple so that I can be done in reasonable
> | amount of time and does not follow the destiny of einfo/ewarn logging
> | (3 years and counting).
> 
> Of course. Hence why I'm proposing something easy and workable, and not
> suggesting some magic new framework that will solve all existing
> problems (including world peace).
> 

Just keep in mind that portage is supposed to be non-interactive and
most users like it that way. (Although the countdown when cleaning out
old packages kinda breaks that idea, but I digress.)

So just make sure that the scheme doesn't involve forcing the user to
notice anything during a 'normal' non-interactive emerge in order for it
to be effective. Thats why I keep pushing having a nice GuideXML version
in a central location like http://errata.g.o/ and just having emerge
output a summary and a link (however/at what point/with what mechanism
you decide to actually have portage output it).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDaq8U2QTTR4CNEQARAm6kAJ948WBp0elnZvxoHLMXvNfaBZvxsgCdEdAO
gO6VPobgKHfqcKpjAQ1II6U=
=iNoA
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Reply via email to