On Tue, 29 Aug 2006 18:56:05 +0200 Simon Stelling <[EMAIL PROTECTED]> wrote: | Ciaran McCreesh wrote: | > 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". | | That paragraph sounds like if it came from Duncan. No offense to | anyone, just couldn't resist *g*.
Naah, it was only one paragraph. | > 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... | | So it's the same as 'emerge -n $(< worldfile)'? It behaves like emerge -n works, yes (and not the way emerge --help says that -n works, which implies that emerge -n foo won't upgrade foo if foo is already installed at a lower version). -- Ciaran McCreesh Mail : ciaranm at ciaranm.org -- [email protected] mailing list
