On Mon, Oct 18, 2010 at 11:24:32AM -0400, Michael K. Johnson wrote: > I expect because uvcvideo-kernel is not in the groups in your > search path.
i suspected something like that. > "conary rq" searches the repository, not the current search path in > your model. The model does not fall back to the installLabelPath > (we considered that, but decided that it made models insufficiently > portable), so if you want your installLabelPath to be available in > the model, you need to add search lines for those labels. Something > like this: > > search group-world=foresight.rpath....@fl:2-devel/someversion > search foresight.rpath....@fl:2-devel > search foresight.rpath....@fl:2-kernel-devel > ... > > Does that make sense? the question is, which behaviour do we want for foresight? do we want to add the installLabelPath to a default foresight install? if not then i think we would want "conary rq" to not search the installLabelPath either. the issue here is not whether installLabelPath is in the system-model but rather how helpful or confusing it is that conary rq and conary update/install do different kind of searches. in my eyes, the point of conary rq is to tell me what is available for install, unless you want to introduce another verb here: 'conary search' for example. greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix searching contract jobs: debugging, programming, training and administration -- pike programmer working in china community.gotpike.org foresight developer (open-steam|caudium).org foresightlinux.org unix sysadmin iaeste.at realss.com Martin Bähr http://www.iaeste.at/~mbaehr/ is.schon.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
