From: Marshall T. Vandegrift <vandem2@rpi.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] emerge -U world with mixed stable/unstable ebuilds
Date: Wed, 26 Mar 2003 09:04:35 -0500 [thread overview]
Message-ID: <873cla2pho.fsf@rpi.edu> (raw)
In-Reply-To: <200303261135.49930.C.J.Bainbridge@ed.ac.uk> (Chris Bainbridge's message of "Wed, 26 Mar 2003 11:35:49 +0000")
Trying again, after realizing that gento-dev dislikes attachments...
Chris Bainbridge <C.J.Bainbridge@ed.ac.uk> writes:
> I could modify my local portage tree after syncing to mark every
> ebuild I want stable, but is there an easier way? Preferably some
> way to update all stable ebuilds to the latest stable version and
> all unstable ones to the latest unstable...?
For a hideous hack that works right now (and is thus the solution I
use) check out the following shell scripts:
----- begin: stable-eup.sh -----
#! /bin/sh
NOCOLOR="true" emerge -up world \
| grep '^\[ebuild' \
| grep -v '^\[ebuild UD\]' \
| sed -re's/.*?\] (.*?)-[0-9
------ end: stable-eup.sh ------
---- begin: unstable-eup.sh ----
#! /bin/sh
NOCOLOR="true" emerge -up world \
| grep '^\[ebuild' \
| grep '^\[ebuild UD\]' \
| sed -re's/.*?\] (.*?)-[0-9].*/\1/' \
| NOCOLOR="true" ACCEPT_KEYWORDS="~x86" xargs emerge -p \
| grep '^\[ebuild' \
| grep -v '^\[ebuild R \]' \
| sed -re's/.*?\] (.*?)-[0-9].*/\1/' \
| ACCEPT_KEYWORDS="~x86" xargs emerge "$@"
----- end: unstable-eup.sh -----
--
Marshall T. Vandegrift <vandem2@rpi.edu>
Disciplined and calm, to await the appearance of
disorder and hubbub amongst the enemy:--this is the
art of retaining self-possession.
-- Sun Tzu (/The Art of War/, 7:30)
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-03-26 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 11:35 [gentoo-dev] emerge -U world with mixed stable/unstable ebuilds Chris Bainbridge
2003-03-26 14:04 ` Marshall T. Vandegrift [this message]
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=873cla2pho.fsf@rpi.edu \
--to=vandem2@rpi.edu \
--cc=gentoo-dev@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