On Wed, 8 Apr 2009, Ciaran McCreesh wrote:
> On Wed, 8 Apr 2009 17:29:04 -0400 (EDT)
> "Benjamin R. Haskell" <[email protected]> wrote:
>
> > Question 1: why doesn't '*/* -*' as the final line of keywords.conf
> > keyword-mask everything?
>
> 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.)
How is specificity calculated anyway? In particular, I'd be interested to
know the ordering on the following things:
== group one: categories, wildcards, and repos ==
*/*::repo
cat/*
cat/*::repo
== group two: versions, ranges, and repos ==
cat/pack::repo
>=cat/pack-1.1
>=cat/pack-1.1::repo
=cat/pack-1.1
=cat/pack-1.1::repo
> > Question 2: Why is the default for --dl-override-masks 'tilde-keyword
> > and license', rather than 'none'?
> >
> > Either I'm misinterpreting the intent, or 'license' in particular
> > completely flies in the face of having a list of licenses the user
> > wants to accept. (e.g. if something is MIT-licensed, and the user
> > doesn't want MIT-licensed things, will paludis slip it in anyway?)
>
> It won't slip it in. It will show an error, and tell you which keywords
> and licences are not accepted. Override masks only overrides them for
> resolution purposes, and only where necessary; if a mask occurs, Paludis
> won't proceed with an install until you explicitly unmask it. If you use
> 'none' instead, once it hits a mask it won't continue.
Ah, I see the intent now. Thanks.
> > Is there some other, more-obvious way that I'm missing where you can
> > mask all-but-a-few packages from a particular repository? I also
> > tried adding '*/*::java-overlay' to package_mask.conf, and adding
> > particular packages to package_unmask.conf, but that didn't get me
> > any further than my attempts above with keywords.conf.
>
> package_mask.conf everything, and package_unmask.conf the bits you want.
Done. Arrgh #2: that was easy. I swear I tried it before... I guess I
must have forgotten to remove something from keywords.conf when I did.
> > 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.
> > I added '--log-level debug', but the 183,555 lines of output doesn't
> > contain any of { "keyword", "~", "x86", "tilde" }. How would one use
> > paludis to obtain something like (this is very over-simplified, and
> > fictionalized, but shows what *types* of events I'd like to see):
> >
> > Trying to install dev-util/eclipse-sdk
> > Trying to install dev-util/eclipse-sdk-3.4.1::java-overlay
> > Added build dependency '>=virtual/jdk-1.5'
> > Satisfied '>=virtual/jdk-1.5' with 'virtual/jdk-1.6::installed'
> > Trying to satisfy build dependency 'dev-java/cldc-api:1.1'
> > Adding 'dev-java/cldc-api-1.1.0' to install list
> > Keywords mask 'dev-java/cldc-api-1.1.0' (KEYWORDS: ~amd64 ~x86)
> > Cannot install 'dev-java/cldc-api'
> > Cannot satisfy 'dev-java/cldc-api:1.1'
>
> Paludis doesn't really do anything like what you're wanting to see, so
> you can't see that kind of thing.
Alright. Thanks again for the help.
Best,
Ben
_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user
