From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage Sets
Date: Tue, 29 Aug 2006 16:25:21 +0100 [thread overview]
Message-ID: <20060829162521.6105d3f4@snowdrop.home> (raw)
In-Reply-To: <44F42BB7.4010005@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Tue, 29 Aug 2006 07:57:43 -0400 Alec Warner <antarus@gentoo.org>
wrote:
| So I have implemented merging of sets (more or less) in a local
| portage branch.
Aah, good to see that you're picking up one of the more useful Paludis
features.
For those who aren't aware of how Paludis handles this... File sets are
a text file that live in repodir/sets/ or confdir/sets/ and are named
setname.conf. Lines can be in the form *atom , which means "include
atom in the set", or ?atom , which means "include atom in the set only
if the package represented by atom is already installed".
The big difference between paludis --install setname and paludis
--install $(< setfile), aside from the *? support, is that the former
won't reinstall packages that don't need upgrading, and the latter
will. It's the same as emerge world vs emerge $(< worldfile), the
latter being similar to emerge -e world...
--
Ciaran McCreesh
Mail : ciaranm at ciaranm.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-29 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 11:57 [gentoo-dev] Portage Sets Alec Warner
2006-08-29 14:22 ` Kevin F. Quinn
2006-08-29 14:37 ` Chris White
2006-08-29 14:44 ` Simon Stelling
2006-08-29 17:41 ` Mike Frysinger
2006-08-29 18:22 ` Wernfried Haas
2006-08-29 18:42 ` Mike Frysinger
2006-08-29 16:22 ` Alec Warner
2006-08-29 15:04 ` Chris White
2006-08-29 15:25 ` Ciaran McCreesh [this message]
[not found] ` <44F471A5.3020405@gentoo.org>
2006-08-29 17:20 ` Ciaran McCreesh
2006-08-29 17:45 ` Mike Frysinger
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=20060829162521.6105d3f4@snowdrop.home \
--to=ciaranm@ciaranm.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