From: Myk Taylor <myk@ucla.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] what's new with all those new packages?
Date: Mon, 11 Jul 2005 09:20:28 -0700 [thread overview]
Message-ID: <42D29C4C.409@ucla.edu> (raw)
In-Reply-To: <20050711123427.GA2457@daniel>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think if you're using Gentoo, there is an assumption that "if it's new
(and acceptably stable), I want it". I agree that a comprehensive list
of fixed bugs and new features would be nice for each updated package,
but I imagine that it would be unwelcome extra work for the port
maintainers.
Especially handy would be if I were updating from version x to version y
of a particular package and emerge would tell me the functional delta
between those two versions.
If there's a package I'm particularly interested in (or dubious about),
I'll venture over to its homepage to check out the changelist when it
gets updated, but I usually defer to the wisdom of the portage and
package maintainers.
- --myk
danielhf@21cn.com wrote:
> portage reminds me of updating packages frequently,
> i have to decide what to update, and if it's worth downloading?
>
> is there a easy way to see "what's new" of those packages to be
> updated? the ChangeLog within /usr/portage/xxx-xxx/ make no sense to me.
>
> thanks.
>
> regards
> daniel..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC0pxMBOPsJyAQkeARAsvEAJ9RWQ9LBWOdXJpBsesgfJP2wOBtBgCbBU0m
7LtGA+VdldKj/sxxrjlMtzg=
=NhMW
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-11 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 12:34 [gentoo-user] what's new with all those new packages? danielhf
2005-07-11 13:10 ` Philip Webb
2005-07-11 16:20 ` Myk Taylor [this message]
2005-07-11 16:40 ` Mark Knecht
2005-07-11 17:03 ` Dave Nebinger
2005-07-12 6:33 ` Ow Mun Heng
2005-07-11 16:42 ` Roy Wright
2005-07-11 17:08 ` Holly Bostick
2005-07-12 10:35 ` Martin S
2005-07-12 10:45 ` Jason Stubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42D29C4C.409@ucla.edu \
--to=myk@ucla.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox