Summary: | Gentoolkit features: equery basedir and equery which --exclude-masked | ||
---|---|---|---|
Product: | Portage Development | Reporter: | ferret <ferret-bgo> |
Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | tom.gl |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
equery basedir
equery which --exclude-masked support combined --exclude-masked and --base-directory patch for 'equery which' |
Description
ferret
2005-05-06 18:54:57 UTC
Created attachment 58232 [details, diff]
equery basedir
Created attachment 58233 [details, diff]
equery which --exclude-masked support
Sorry, there's no man page diff. I don't know about the man page format yet. :( Imho your "basedir" command could be simply an option ("--basedir") for the "which" command. I mean, it has a similar purpose (find location of the best ebuild matching a pkgspec), and only the output differs a bit, no? Created attachment 58264 [details, diff]
combined --exclude-masked and --base-directory patch for 'equery which'
That seems a reasonable idea, here's a patch combining the two features into
'equery which'. Either way suits me, really.
Forgot to mention, in that last attachment I completely ignored any issues that might arise with specifying both -m and -b. It works, ond if for example all the packages in the main portage tree are masked but your ebuild in the overlay isn't masked it correctly returns the overlay base dir. I really can't think why anyone would specify both but I decided there was no need to enforce mutual exclusivity. Please feel free to suggest an alternative way of handling this. No interest in this feature. Not necessary. |