DISQUS

Donnie Berkholz · 11 months ago

Woot! I use this all the time. It would be great to support metadata.xml USE flag descriptions.

dams · 10 months ago

Hi Donnie, could you explain me what you have in mind? What is missing from flagedit --list --desc ?

Donnie Berkholz · 10 months ago

Well, use.local.desc is generated now from the local flags in metadata.xml of each package. It would be nice if flagedit understood metadata.xml directly, because I'm assuming that the use.local.desc will go away at some point.

hrongyorgy · 10 months ago

Then it means euses'll go away too? Because - if I know well - it based on use.desc and use.local.desc files. But euses is a quick tool to investigate the feature of some uncommon use flags. If euses use metadata.xml then it must scan the complete tree - but it may make it slower.

I think a good way is generating use.local.desc at emerge --metadata - it's a good solution to make this available, and don't include it in rsync-ed tree.

Pavel · 11 months ago

features suggested:
- set/unset/(reset) hardmask on a package. rationale: to set a hardmask, you only need echo, unsetting it requires sed or something.
- clean obsolate package.keywords entries. if a package has an entry with a = or <= version specification and the current available/installed version is higher or equal, remove it.
Feel free to let me know about testing flagedit.

dams · 10 months ago

if you can have a go with flagedit-0.0.8, it should fix #241668

Milan · 11 months ago

Really good use flag editor, I didn't even know it exists. Too bad that I switched to paludis. What I would like to see is maybe support for paludis :) it has one file, use.conf with global and per app use flags. Just my wish, but if you don't use it I guess it is not going to happen :(

dams · 10 months ago

I'll stick to portage for now :)

Pawel Madej · 11 months ago

flagedit is great piece of software so I'll be surely happy to see it growing :)

Stefano Priore · 10 months ago

Why don't merge flagedit with profuse? A "--gui" option could be used to invoke it.

The rationale is that profuse is very usefulto quickly browse through the enormous list of USE flags and you can easily check if the flag is global or local.

More suggestions:

- A "check" mode for obsolete flags: if a flag is no more supported by the current version or the one specificated in package.keywords, a warning is displayed.
- A "proof" mode to warn if a global flag is applied to a single package or if a local flag is applied in make.conf.
- If profuse gets integrated: a way to filter the list of flags: only global, only local or by regexp