public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeffrey Forman <jforman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] emerge -U getting removed?
Date: Mon, 20 Sep 2004 09:25:00 -0400	[thread overview]
Message-ID: <1095686699.2347.12.camel@sixthstreet.formanonline.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Just this morning (afternoon/evening) on #-dev I got to talking to some
people about the usefulness of "emerge -U." I was wondering if someone
had any clue as to why its being removed? I frequently mix packages in
~x86 to test, or just to use newer revisions which are more stable and
with -U going away, I wont be able to update my machine without
downgrading a <insert explitive> load of packages.

Yes I know about editing package.keywords, but how much of a PITA is
that to have to add an entry for every package you emerge that is masked
for one reason or another.

Any thoughts, comments, or ideas of how you want to burn me at the
stake?

-Jeffrey
-- 


--------------------
Jeffrey Forman
Gentoo Infrastructure
Gentoo Release Engin.
jforman@gentoo.org
--------------------

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-09-20 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 13:25 Jeffrey Forman [this message]
2004-09-20 13:55 ` [gentoo-dev] emerge -U getting removed? Ciaran McCreesh
2004-09-20 16:24   ` Luke-Jr
2004-09-20 16:37     ` Ciaran McCreesh
2004-09-21  1:29     ` Mike Frysinger
2004-09-21 21:08       ` Doug Goldstein
2004-09-21 22:00         ` Mike Frysinger
2004-09-21 22:01           ` Ciaran McCreesh
2004-09-22 17:51 ` Robert Moss
2004-09-22 21:01   ` Philippe Trottier

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=1095686699.2347.12.camel@sixthstreet.formanonline.com \
    --to=jforman@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