public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stephen P. Becker" <geoman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Cutting down on non-cascaded profiles
Date: Mon, 02 May 2005 12:33:24 -0400	[thread overview]
Message-ID: <42765654.3010404@gentoo.org> (raw)
In-Reply-To: <4276513D.5060200@flaska.net>

> What is bad about doing *only* `emerge --sync` and security updates?

Nothing, however if they have been doing security only updates, I think
that their install won't be *too* far behind the stable tree.  Besides,
at some point old ebuilds are completely removed from portage anyway,
and therefore there is no support for those versions if somebody tries
to submit a bug.  This is really getting into a whole different
discussion altogether about having a security update only tree, but
there has been talk of this a few times before...search the mailing list
archives.

> This is not my case so it's quite possible that no such users exist (so
> the gentoo-dev ml isn't probably the best place to ask if they exist,
> btw), but if you do something that will prevent *everyone* who is so
> "late with upgrades" from continuing, you'll introduce (IMHO dangerous)
> precedence about backward compatibility.

Removing old profiles will do nothing other than forcing them to set a
new profile.  Changing the profile won't stop people from doing security
only updates.

-Steve
-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-02 16:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 10:17 [gentoo-dev] Cutting down on non-cascaded profiles Donnie Berkholz
2005-05-01 10:35 ` Stuart Longland
2005-05-01 12:31   ` [gentoo-dev] " Duncan
2005-05-01 13:15     ` Ned Ludd
2005-05-02 14:55   ` [gentoo-dev] " Jan Kundrát
2005-05-02 15:53     ` Stephen P. Becker
2005-05-02 16:11       ` Jan Kundrát
2005-05-02 16:33         ` Stephen P. Becker [this message]
2005-05-02 16:40           ` Jan Kundrát
2005-05-02 23:55             ` Stuart Longland
2005-05-03  0:45               ` Alec Warner
2005-05-03  0:54                 ` Mike Frysinger
2005-05-03  1:31                   ` Alec Warner
2005-05-03  6:29               ` Jan Kundrát
2005-05-03  7:05                 ` Stuart Longland
2005-05-03 12:27                   ` Mike Frysinger
2005-05-03 15:21           ` [gentoo-dev] " Duncan
2005-05-03 16:10             ` Chris Gianelloni
2005-05-03 18:37               ` [gentoo-dev] " Duncan
2005-05-03 18:49               ` [gentoo-dev] " Mike Frysinger
2005-05-03 21:05                 ` Chris Gianelloni
2005-05-09 20:12                   ` Paul de Vrieze
2005-05-09 20:27                     ` Mike Frysinger
2005-05-10  9:15                       ` Paul de Vrieze
2005-05-10  9:31                         ` Georgi Georgiev
2005-05-09 22:23                     ` Brian Harring
2005-05-03 21:20                 ` Marius Mauch
2005-05-04  7:17               ` John Myers
2005-05-01 11:37 ` [gentoo-dev] " Ned Ludd
2005-05-01 17:11 ` Mike Frysinger
2005-05-02 13:47   ` Chris Gianelloni
2005-05-03  8:53 ` Aaron Walker
2005-05-03 12:43   ` Jason Stubbs
2005-05-03 13:19   ` Chris Gianelloni

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=42765654.3010404@gentoo.org \
    --to=geoman@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