| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ciaran McCreesh wrote: |
| 5 |
> On Tue, 1 Nov 2005 14:32:47 +0100 Jakub Moc <jakub@g.o> wrote: |
| 6 |
> | What do you mean "they aren't tied to ebuilds"? I don't really |
| 7 |
> | understand what this feature should do then, it seems. Once again, |
| 8 |
> | what's wrong with reusing emerge --changelog mechanism for displaying |
| 9 |
> | this kind of information? |
| 10 |
> |
| 11 |
> We make changes that have scope other than ebuilds. |
| 12 |
> |
| 13 |
> | I'm not particularly happy with idea of emerge as a newsreader |
| 14 |
> | really, IMHO we should display relevant, vital upgrading information |
| 15 |
> | *when relevant*, not to inform users about upgrades that they are not |
| 16 |
> | interested in in the least. |
| 17 |
> |
| 18 |
> Which is what my proposed GLEP does, at least as far as we can |
| 19 |
> determine automatically. Yes, occasionally this will mean giving, say, |
| 20 |
> mysql 4.1 upgrade instructions to people who plan to use only mysql |
| 21 |
> 4.0, but then, if we didn't give them the news, most of them wouldn't |
| 22 |
> know that they don't want to upgrade. |
| 23 |
> |
| 24 |
> And it doesn't turn emerge into a news reader. All portage does is |
| 25 |
> deliver the news. How said news is read is a different issue. |
| 26 |
> |
| 27 |
> | And please, keep the thing simple so that I can be done in reasonable |
| 28 |
> | amount of time and does not follow the destiny of einfo/ewarn logging |
| 29 |
> | (3 years and counting). |
| 30 |
> |
| 31 |
> Of course. Hence why I'm proposing something easy and workable, and not |
| 32 |
> suggesting some magic new framework that will solve all existing |
| 33 |
> problems (including world peace). |
| 34 |
> |
| 35 |
|
| 36 |
Just keep in mind that portage is supposed to be non-interactive and |
| 37 |
most users like it that way. (Although the countdown when cleaning out |
| 38 |
old packages kinda breaks that idea, but I digress.) |
| 39 |
|
| 40 |
So just make sure that the scheme doesn't involve forcing the user to |
| 41 |
notice anything during a 'normal' non-interactive emerge in order for it |
| 42 |
to be effective. Thats why I keep pushing having a nice GuideXML version |
| 43 |
in a central location like http://errata.g.o/ and just having emerge |
| 44 |
output a summary and a link (however/at what point/with what mechanism |
| 45 |
you decide to actually have portage output it). |
| 46 |
-----BEGIN PGP SIGNATURE----- |
| 47 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 48 |
|
| 49 |
iD8DBQFDaq8U2QTTR4CNEQARAm6kAJ948WBp0elnZvxoHLMXvNfaBZvxsgCdEdAO |
| 50 |
gO6VPobgKHfqcKpjAQ1II6U= |
| 51 |
=iNoA |
| 52 |
-----END PGP SIGNATURE----- |
| 53 |
-- |
| 54 |
gentoo-dev@g.o mailing list |
Archives