1 |
On Tue, 29 Aug 2006 18:56:05 +0200 Simon Stelling <blubb@g.o> |
2 |
wrote: |
3 |
| Ciaran McCreesh wrote: |
4 |
| > For those who aren't aware of how Paludis handles this... File sets |
5 |
| > are a text file that live in repodir/sets/ or confdir/sets/ and are |
6 |
| > named setname.conf. Lines can be in the form *atom , which means |
7 |
| > "include atom in the set", or ?atom , which means "include atom in |
8 |
| > the set only if the package represented by atom is already |
9 |
| > installed". |
10 |
| |
11 |
| That paragraph sounds like if it came from Duncan. No offense to |
12 |
| anyone, just couldn't resist *g*. |
13 |
|
14 |
Naah, it was only one paragraph. |
15 |
|
16 |
| > The big difference between paludis --install setname and paludis |
17 |
| > --install $(< setfile), aside from the *? support, is that the |
18 |
| > former won't reinstall packages that don't need upgrading, and the |
19 |
| > latter will. It's the same as emerge world vs emerge $(< |
20 |
| > worldfile), the latter being similar to emerge -e world... |
21 |
| |
22 |
| So it's the same as 'emerge -n $(< worldfile)'? |
23 |
|
24 |
It behaves like emerge -n works, yes (and not the way emerge --help |
25 |
says that -n works, which implies that emerge -n foo won't upgrade foo |
26 |
if foo is already installed at a lower version). |
27 |
|
28 |
-- |
29 |
Ciaran McCreesh |
30 |
Mail : ciaranm at ciaranm.org |
31 |
|
32 |
-- |
33 |
gentoo-dev@g.o mailing list |