| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
I think if you're using Gentoo, there is an assumption that "if it's new |
| 5 |
(and acceptably stable), I want it". I agree that a comprehensive list |
| 6 |
of fixed bugs and new features would be nice for each updated package, |
| 7 |
but I imagine that it would be unwelcome extra work for the port |
| 8 |
maintainers. |
| 9 |
|
| 10 |
Especially handy would be if I were updating from version x to version y |
| 11 |
of a particular package and emerge would tell me the functional delta |
| 12 |
between those two versions. |
| 13 |
|
| 14 |
If there's a package I'm particularly interested in (or dubious about), |
| 15 |
I'll venture over to its homepage to check out the changelist when it |
| 16 |
gets updated, but I usually defer to the wisdom of the portage and |
| 17 |
package maintainers. |
| 18 |
|
| 19 |
- --myk |
| 20 |
|
| 21 |
danielhf@××××.com wrote: |
| 22 |
> portage reminds me of updating packages frequently, |
| 23 |
> i have to decide what to update, and if it's worth downloading? |
| 24 |
> |
| 25 |
> is there a easy way to see "what's new" of those packages to be |
| 26 |
> updated? the ChangeLog within /usr/portage/xxx-xxx/ make no sense to me. |
| 27 |
> |
| 28 |
> thanks. |
| 29 |
> |
| 30 |
> regards |
| 31 |
> daniel.. |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 34 |
|
| 35 |
iD8DBQFC0pxMBOPsJyAQkeARAsvEAJ9RWQ9LBWOdXJpBsesgfJP2wOBtBgCbBU0m |
| 36 |
7LtGA+VdldKj/sxxrjlMtzg= |
| 37 |
=NhMW |
| 38 |
-----END PGP SIGNATURE----- |
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives