1 |
On Tue, 29 Aug 2006 07:57:43 -0400 Alec Warner <antarus@g.o> |
2 |
wrote: |
3 |
| So I have implemented merging of sets (more or less) in a local |
4 |
| portage branch. |
5 |
|
6 |
Aah, good to see that you're picking up one of the more useful Paludis |
7 |
features. |
8 |
|
9 |
For those who aren't aware of how Paludis handles this... File sets are |
10 |
a text file that live in repodir/sets/ or confdir/sets/ and are named |
11 |
setname.conf. Lines can be in the form *atom , which means "include |
12 |
atom in the set", or ?atom , which means "include atom in the set only |
13 |
if the package represented by atom is already installed". |
14 |
|
15 |
The big difference between paludis --install setname and paludis |
16 |
--install $(< setfile), aside from the *? support, is that the former |
17 |
won't reinstall packages that don't need upgrading, and the latter |
18 |
will. It's the same as emerge world vs emerge $(< worldfile), the |
19 |
latter being similar to emerge -e world... |
20 |
|
21 |
-- |
22 |
Ciaran McCreesh |
23 |
Mail : ciaranm at ciaranm.org |