On Wed, 8 Apr 2009 18:58:16 -0400 (EDT) "Benjamin R. Haskell" <[email protected]> wrote: > > The order of lines in your config file isn't relevant. The > > specificity is what matters. */* gets overridden by foo/bar. > > Arrgh. Damn. I thought I'd done a simple test to see if that was > the case. Is that true for all .conf-style files? I was going to > ask a couple weeks ago as to whether there was a fixed order for > foo.conf.d/*.conf files. That could still be important, I suppose, > for cases of identical specs. (e.g. a general use.conf that has */* > gtk, but a machine-specific use.conf.d/local.conf that has */* -gtk.)
In general, there's no fixed order you can rely upon. > How is specificity calculated anyway? Most specific: anything that mentions an explicit cat/pkg. Less specific: named sets. Least specific: wildcards. Relying upon anything beyond that is unwise, since it might get changed. > > > Question 5: What's the best way to see how paludis is resolving > > > dependencies? > > > > Uh, I wouldn't try to do that... You probably don't want to know > > what's going on there... > > I do want to know, actually. But, I'll leave it be for now. The way the current resolver works is a horrible hack... I strongly recommend waiting for the new resolver (or dying of old age, not sure which'll happen first) before digging deeper... -- Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
