| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Paul de Vrieze wrote: |
| 5 |
> On Friday 04 November 2005 14:38, Nathan L. Adams wrote: |
| 6 |
> |
| 7 |
>>Paul de Vrieze wrote: |
| 8 |
>> |
| 9 |
>>>What is worse is that some |
| 10 |
>>>users might not update for a prolongued time (6 months). At that time |
| 11 |
>>>they will not find the information in the erata list anymore. But |
| 12 |
>>>they will get the RELEVANT news delivered by emerge/enews. |
| 13 |
>> |
| 14 |
>>Why would a "SomeSQL 1.0 to 1.1" guide ever need to dissappear? Surely |
| 15 |
>>errata.g.o would have archiving/searching. But I do see your point |
| 16 |
>>about emerge filtering out the unwanted stuff. |
| 17 |
> |
| 18 |
> |
| 19 |
> It would be hidden in the forrest. Even if I did a search on SomeSQL, it |
| 20 |
> might return a number of news items on SomeSQL. That is besides the fact |
| 21 |
> that I have 737 packages installed. I'm not going to search news on all |
| 22 |
> of them. Archiving would of course be provided, but searching is not |
| 23 |
> usefull for updating. |
| 24 |
|
| 25 |
You update all 737 packages with each emerge? I don't see any validity |
| 26 |
in your point; a nice http://errata.g.o/ site with archived guides and |
| 27 |
search wouldn't preclude 'emerge --news' in any way. |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFDa4R12QTTR4CNEQARApTFAKCL3rZ88STZtuu1EZUw/iSFf8NJMACfXtHu |
| 32 |
UyKLcgsYF4+nC+ezKSC4Of8= |
| 33 |
=a4Ki |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives