Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
On Mon, 30 Oct 2006 21:56:23 -0600, Ryan Hill <[EMAIL PROTECTED]> wrote: > Caleb Cushing wrote: > > > maybe it would be a lot of work. to even develop the tools. but it > > would be nice if a global use flag could have a detailed option. > > this has been discussed a few times before. i think there's even a > bug for it (don't remember the #). > Maybe you're talking about #84884: https://bugs.gentoo.org/show_bug.cgi?id=84884 I still do quick and dirty syncs of the emerge patch for my own use. It adds 4 options (when in --pretend or --ask mode): * --use-desc-special prints descriptions of global flags overloaded in use.local.desc. I don't use this one since there is currently no such specific description, but it still works. * --use-desc-new prints descriptions of the new ones (yellow "flag%" on packages updates). I use this one when i update world. * --use-desc-local prints descriptions of local flags. I use this one when i'm about to install some new package. * --use-desc-all prints descriptions of all USE flags. I don't think it's much useful, but who knows... Sure, if some Portage dev want to have a look at it, i can clean it up and resubmit it once again. > i keep meaning to look at how other USE-type utils handle it. At least "equery uses pkg/foo" needs to be patched too (or it choose the global description when it finds one). Bug #84884 had a patch for that too, which is easy to sync. -- TGL. -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
Caleb Cushing wrote: > maybe it would be a lot of work. to even develop the tools. but it > would be nice if a global use flag could have a detailed option. this has been discussed a few times before. i think there's even a bug for it (don't remember the #). > example. > > euse -i mplayer [+ C ] mplayer - Enable mplayer support for playback > or encoding > > is what we currently get. > > add a -d option for --descriptive euse -id mplayer could show > something like [+ C ] mplayer - Enable mplayer support for playback > or encoding media-video/kmplayer - adds the ability to play back > media using the mplayer engine euse already does this actually. ;) $ grep "^doc" /usr/portage/gentoo-x86/profiles/use.desc doc - Adds extra documentation (API, Javadoc, etc) $ grep ":doc" /usr/portage/gentoo-x86/profiles/use.local.desc dummy-cat/fakepkg:doc - This is a package specific USE description. $ euse -i doc global use flags (searching: doc) [-] doc - Adds extra documentation (API, Javadoc, etc) local use flags (searching: doc) [-] doc (dummy-cat/fakepkg): This is a package specific USE description. i keep meaning to look at how other USE-type utils handle it. -- by design, by neglect [EMAIL PROTECTED]for a fact or just for effect 9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
On Sat, Oct 28, 2006 at 05:23:50PM +0200, arfrever wrote: > In connection with latest globalization of mplayer USE flag I would like to > ask for globalizing cairo, openexr and udev USE flags. These flags are used > by enough amount of packages. I vote for a 'libnotify' global USE flag. It is used now by 11 packages in use.local.desc and does the same thing in all of them - Allows popups via libnotify (or dbus+notification-daemon, which amounts to the same thing). -- Jim Ramsay Gentoo/Linux Developer (rox) pgppPbZjuRCvZ.pgp Description: PGP signature
Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
maillog: 29/10/2006-05:26:52(+0200): Mart Raudsepp types > > The main problem in my eyes here is that with certain USE flags, the > description doesn't really convey what the user will get. > Many are in the form of "adds support for this optional thing" instead > of "by using this optional dependency [named often the same as the USE > flag name] you will get this and that extra functionality". > > > Now what good wxGTK maintainer would I be, if I didn't pick wxwindows > USE flag as an example: > > "wxwindows - Adds support for wxWindows/wxGTK GUI toolkit" > > Lets see what the user really gets with this in the example of a few > packages that use this USE flag in IUSE: > > app-backup/bacula: a wxWidgets console, while there are other consoles > available, such as gnome2-console and having both USE flags will result > in two consoles. However all of these are dependent on bacule-console > local USE flag... > > app-emulation-bochs: Compile a wxWidgets based GUI (other are available) > media-gfx/zphoto: Use wxWidgets for GUI (to get ANY kind of GUI) > media-video/gpac: Build wxOsmo4 and V4Studio > media-video/mkvtoolnix: Build mmg and a GUI for mkvinfo > > All of these "support wxGTK" in the sense that they pull it in and build > a few things against it, but it doesn't articulate what does the user > exactly get from using that global USE flag for this particular package. > Sometimes she gets just some little extra GUI apps, sometimes a GUI in > the first place, sometimes an extra GUI interface in addition to others, > and so on. > Similar things can be observed with many other global USE flags (and > also some local flags) - examples on request (time consuming detail > gathering). > > And that's the problem - the user doesn't know what benefit will it > bring her to use or not use a global USE flag for this particular > package. That's why the descriptions in the linux kernel are great. They mention exactly what you get and also give advice about the value: "If you don't know what Access Control Lists are, say N" "If unsure, say N" "If unsure, say N. More documentation can be found at ..." Maybe something to consider when editing/adding descriptions. -- /\ Georgi Georgiev /\ You'd best be snoozin', 'cause you don't /\ \/[EMAIL PROTECTED]\/ be gettin' no work done at 5 a.m. anyway. \/ /\ http://www.gg3.net/ /\ -- From the wall of the Wurster Hall /\ \/ --- \/ stairwell \/ pgpQKtFVquwpe.pgp Description: PGP signature
Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
And that's the problem - the user doesn't know what benefit will it bring her to use or not use a global USE flag for this particular package. yeah and it would be really nice to know these. I just thought of another useful feature. a flag for emerge that assumes --verbose but defines what the use flag's do. maybe we could have one similar to lspci? where -vv is more verbose that just -v. thx Mart for giving a better example than me. because I couldn't come up with a good one at the time. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
On Sat, 2006-10-28 at 17:12 -0400, Alec Warner wrote: > Caleb Cushing wrote: > >> > >> cairo and openexr, good idea, AFAIK. udev has come up before but from > >> that discussion, the flag means slightly different things in some cases. > >> Keeping it local allows individual per-pkg descriptions, so where it > >> means > >> something different, the description can say so. In both meanings, udev > >> defaulting to on remained best, but with the slightly different > >> meanings... > >> There was some discussion about modifying things or changing the flag > >> where it meant something else, but I don't know what came of that. > >> > > > > maybe it would be a lot of work. to even develop the tools. but it > > would be nice if a global use flag could have a detailed option. > > > > example. > > > > euse -i mplayer > > [+ C ] mplayer - Enable mplayer support for playback or encoding > > > > is what we currently get. > > > > add a -d option for --descriptive > > euse -id mplayer could show something like > > [+ C ] mplayer - Enable mplayer support for playback or encoding > >media-video/kmplayer - adds the ability to play back media using > > the mplayer engine > > > > or maybe something better... > > I don't think any specification precludes having a more descriptive > per-package meaning. It would just be a matter of: > > a. having devs write them in use.local.desc when necessary > b. Having tools look in use.local.desc first. > > But the whole point of global flags is really to consolidate the > description functions and keep naming consistent. So I doubt (a) will > ever come to pass for the majority of flags. Luckily (a) isn't a hard > requirement, tools don't loose functionality by looking in > use.local.desc first. The main problem in my eyes here is that with certain USE flags, the description doesn't really convey what the user will get. Many are in the form of "adds support for this optional thing" instead of "by using this optional dependency [named often the same as the USE flag name] you will get this and that extra functionality". Now what good wxGTK maintainer would I be, if I didn't pick wxwindows USE flag as an example: "wxwindows - Adds support for wxWindows/wxGTK GUI toolkit" Lets see what the user really gets with this in the example of a few packages that use this USE flag in IUSE: app-backup/bacula: a wxWidgets console, while there are other consoles available, such as gnome2-console and having both USE flags will result in two consoles. However all of these are dependent on bacule-console local USE flag... app-emulation-bochs: Compile a wxWidgets based GUI (other are available) media-gfx/zphoto: Use wxWidgets for GUI (to get ANY kind of GUI) media-video/gpac: Build wxOsmo4 and V4Studio media-video/mkvtoolnix: Build mmg and a GUI for mkvinfo All of these "support wxGTK" in the sense that they pull it in and build a few things against it, but it doesn't articulate what does the user exactly get from using that global USE flag for this particular package. Sometimes she gets just some little extra GUI apps, sometimes a GUI in the first place, sometimes an extra GUI interface in addition to others, and so on. Similar things can be observed with many other global USE flags (and also some local flags) - examples on request (time consuming detail gathering). And that's the problem - the user doesn't know what benefit will it bring her to use or not use a global USE flag for this particular package. -- Mart Raudsepp Gentoo Developer Mail: [EMAIL PROTECTED] Weblog: http://planet.gentoo.org/developers/leio signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
Caleb Cushing wrote: cairo and openexr, good idea, AFAIK. udev has come up before but from that discussion, the flag means slightly different things in some cases. Keeping it local allows individual per-pkg descriptions, so where it means something different, the description can say so. In both meanings, udev defaulting to on remained best, but with the slightly different meanings... There was some discussion about modifying things or changing the flag where it meant something else, but I don't know what came of that. maybe it would be a lot of work. to even develop the tools. but it would be nice if a global use flag could have a detailed option. example. euse -i mplayer [+ C ] mplayer - Enable mplayer support for playback or encoding is what we currently get. add a -d option for --descriptive euse -id mplayer could show something like [+ C ] mplayer - Enable mplayer support for playback or encoding media-video/kmplayer - adds the ability to play back media using the mplayer engine or maybe something better... I don't think any specification precludes having a more descriptive per-package meaning. It would just be a matter of: a. having devs write them in use.local.desc when necessary b. Having tools look in use.local.desc first. But the whole point of global flags is really to consolidate the description functions and keep naming consistent. So I doubt (a) will ever come to pass for the majority of flags. Luckily (a) isn't a hard requirement, tools don't loose functionality by looking in use.local.desc first. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
cairo and openexr, good idea, AFAIK. udev has come up before but from that discussion, the flag means slightly different things in some cases. Keeping it local allows individual per-pkg descriptions, so where it means something different, the description can say so. In both meanings, udev defaulting to on remained best, but with the slightly different meanings... There was some discussion about modifying things or changing the flag where it meant something else, but I don't know what came of that. maybe it would be a lot of work. to even develop the tools. but it would be nice if a global use flag could have a detailed option. example. euse -i mplayer [+ C ] mplayer - Enable mplayer support for playback or encoding is what we currently get. add a -d option for --descriptive euse -id mplayer could show something like [+ C ] mplayer - Enable mplayer support for playback or encoding media-video/kmplayer - adds the ability to play back media using the mplayer engine or maybe something better... -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
arfrever <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 28 Oct 2006 17:23:50 +0200: > In connection with latest globalization of mplayer USE flag I would like > to ask for globalizing cairo, openexr and udev USE flags. These flags are > used by enough amount of packages. > > cairo - 11 packages > openexr - 10 packages > udev - 7 packages > Each of these USE flags is used by bigger amount of packages than mplayer > USE flag. cairo and openexr, good idea, AFAIK. udev has come up before but from that discussion, the flag means slightly different things in some cases. Keeping it local allows individual per-pkg descriptions, so where it means something different, the description can say so. In both meanings, udev defaulting to on remained best, but with the slightly different meanings... There was some discussion about modifying things or changing the flag where it meant something else, but I don't know what came of that. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Global USE flags (Was: mplayer global use flag)
In connection with latest globalization of mplayer USE flag I would like to ask for globalizing cairo, openexr and udev USE flags. These flags are used by enough amount of packages. cairo - 11 packages openexr - 10 packages udev - 7 packages Each of these USE flags is used by bigger amount of packages than mplayer USE flag. I hope that my proposal will be positively considered. Steve Dibb <[EMAIL PROTECTED]> 2006-10-26 napisaĆ: > If no one objects, I'd like to add an mplayer global USE flag to replace all > the > local ones. 5 ebuilds use it right now for all the same purpose, and I'm > going > to need one on mythvideo as well. -- Arfrever F. Taifersar A. -- gentoo-dev@gentoo.org mailing list