From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Changelogs
Date: Wed, 27 Jul 2005 23:58:00 +0900 [thread overview]
Message-ID: <200507272358.02749.jstubbs@gentoo.org> (raw)
In-Reply-To: <42E789CB.1050602@egr.msu.edu>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
On Wednesday 27 July 2005 22:19, Alec Joseph Warner wrote:
> Gentoo is a distribution and there is some responsibility to provide users
> upgrade paths when packages switch versions. Gentoo isn't just portage,
> IMHO.
Perhaps the first thing you've ever said that I've agreed with right off
the bat. ;)
The average system would probably have about five new updatable packages
every single day. Shouldn't users expect that upgrading them is not going to
break things? Isn't that the whole point of ~arch? Excluding the cases where
breakage is due to not updating config files, any breakage that may happen
from upgrading that can't be dealt with within the limits of an ebuild really
must be disseminated(sp?) to the users.
--
Jason Stubbs
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-27 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 2:05 [gentoo-dev] Changelogs Alec Warner
2005-07-27 2:22 ` Georgi Georgiev
2005-07-27 4:16 ` [gentoo-dev] Changelogs Duncan
2005-07-27 11:40 ` Michael Cummings
2005-07-27 12:13 ` Simon Stelling
2005-07-27 12:38 ` Michael Cummings
2005-07-27 12:52 ` Alin Nastac
2005-07-27 13:19 ` Alec Joseph Warner
2005-07-27 13:38 ` Simon Stelling
2005-07-27 14:00 ` Alec Joseph Warner
2005-07-27 15:37 ` Georgi Georgiev
2005-07-27 14:58 ` Jason Stubbs [this message]
2005-07-27 14:50 ` [gentoo-dev] Changelogs Jason Stubbs
2005-07-28 0:02 ` Alec Warner
2005-07-28 13:58 ` Jason Stubbs
2005-07-27 16:59 ` Maurice van der Pot
2005-07-27 18:23 ` Alec Joseph Warner
2005-07-27 18:29 ` Donnie Berkholz
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=200507272358.02749.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-dev@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