Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 7, 2013 at 8:58 PM, Chris Rees utis...@gmail.com wrote: On 7 June 2013 18:49, Andrew W. Nosenko andrew.w.nose...@gmail.com wrote: On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees utis...@gmail.com wrote: I can see your point when talking about DOCS, but for NLS it's insanity *for general use*. Give me an example of where NLS non-globals are appropriate and I'll shut up. The GIMP in Russian locale. GNU Make in any non-English locale. I guess you mean the translations are bad? Chris Even good translations can be annoying if you're trying to use them together with resources in English. (For values of resources that can also include searching for the exact error string online...) -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, 7 Jun 2013 21:06:32 +0300 Andrew W. Nosenko andrew.w.nose...@gmail.com wrote: On Fri, Jun 7, 2013 at 8:23 PM, Michael Gmelin free...@grem.de wrote: I was mostly talking about DOCS, I (poorly) chose NLS as an additional example to show how multiple groups could work. Usually NLS is a true global option. NLS is global option only for people with en_* locale, who, therefore, just don't see the pain produced by it. DOCS are just a space on HDD. But localized names of image filters, tools Co in GIMP -- it's just a barrier to use books and other knowledge sources. And I don't say just about stupid eye-blow errors in translations, when results of automatic merge went in the release and the wild without even fast looking through by the someone, who has that language as native. Translations tend to be bad when there is no QA process. Ever been asked if you want to nearby the application? I usually disable NLS or use LANG=C/en_US.UTF-8 all the time for most development tools (gmake, gcc etc.) since the translations are just irritating, but explicitly switch to my native language for certain UI apps. That's fairly easy to do though, so in most cases messing with NLS on a ports level is unnecessary, e.g. export LANG=en_US.UTF-8 alias gimp=LANG=de_DE.UTF-8 gimp (for those who prefer using gimp in German) -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 7, 2013 at 9:58 PM, Chris Rees utis...@gmail.com wrote: On 7 June 2013 18:49, Andrew W. Nosenko andrew.w.nose...@gmail.com wrote: On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees utis...@gmail.com wrote: I can see your point when talking about DOCS, but for NLS it's insanity *for general use*. Give me an example of where NLS non-globals are appropriate and I'll shut up. The GIMP in Russian locale. GNU Make in any non-English locale. I guess you mean the translations are bad? Your guess is wrong. For some reason you are treating NLS as black and white thing. Either completely enable, or completely disable. Please, just belive that there are lot of grays in between. But I'm completely against: 1. Poor or confusing translations (when easiest way to understand something is to try to back-translate to English, or in some pathological cases, start application in the English locale and match UI elements by position); 2. Translations of tools, which are intended to or used to interact with other tools, as opposed to the end users (GNU make, GCC, Git, GnuPG are perfect examples) 3. Ports which do not provide the easy enough and consistent way to disable NLS. Just because it deprives me a way to workaround cases #1 and #2. And the #3 is the reason, why I stand up in this thread. I don't bother about popping-up dialogs. After all, I'm not in a business of rebuilding the whole ports tree from scratch every day. And even a machine will wait my answer the whole night -- not a problem. Summary time required to build plus wasted time is negligible in comparison to time spent in using application. Therefore, the first thing, which I optimize, is a comfort of using application, and other things are going only after that. -- Andrew W. Nosenko andrew.w.nose...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[HEADSUP] dialog4ports does not popup anymore only for global options
Hi, I have committed the code preventing config-conditional to popup the dialog only if some global options are defined (NLS, DOCS, EXAMPLES and IPV6 for now). This was a popular demand, hope that it fits the requirement. So from now please always define via OPTIONS_DEFINE those options if your ports are going to use them. regards, Bapt pgpYne1nED4Qc.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Baptiste Daroussin wrote: I have committed the code preventing config-conditional to popup the dialog only if some global options are defined (NLS, DOCS, EXAMPLES and IPV6 for now). This was a popular demand, hope that it fits the requirement. So from now please always define via OPTIONS_DEFINE those options if your ports are going to use them. Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 12:20:24PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: I have committed the code preventing config-conditional to popup the dialog only if some global options are defined (NLS, DOCS, EXAMPLES and IPV6 for now). This was a popular demand, hope that it fits the requirement. So from now please always define via OPTIONS_DEFINE those options if your ports are going to use them. Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. regards, Bapt pgpvH3KoZ7K2F.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. regards, Bapt pgprabnyKNIcR.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Baptiste Daroussin wrote: So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. Previously maintainers could decide to show dialog with only DOCS or not to show it. They didn't do it consistently, of course. Probably because no guidelines where established. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. We could provide 'OPTIONS_DEFINE_SILENT' for ports that don't want to spam the users with dialogs, but still want to provide the options. Or a separate flag, like 'OPTIONS_ARE_SILENT'. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? regards, Bapt pgpsIkuScXlSE.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
Le 07/06/2013 15:30, Tijl Coosemans a écrit : On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Like you said, every users have different opinion (as I have another than yours :-) ) and the only way I think can satisfy every one is a customizable behavior… -- Florent Peterschmitt | Please: flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail +33 (0)6 64 33 97 92 | * PDF for documents http://florent.peterschmitt.fr | Thank you :) signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt pgplEngOzunbX.pgp Description: PGP signature
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, 7 Jun 2013 15:42:44 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt I can feel your pain, Bapt :) Anyway, I think the problem with those options (especially DOCS) is that they are not really global in that you want to set them for all ports, but more like general as in well-known. So many ports provide them and the user has a good idea what they're supposed to mean, but ultimately you don't want to set them to the same value for all ports. Regardless of implementation details I would like to see something like the following at least for DOCS, either through config-recursive or - maybe more likely - through a tool like portmaster: After starting the build process and collecting dependencies, an ncurses dialog should be shown that says The following ports provide documentation and a check-box list showing all packages as well as a All and None options on top of the list. That way the user can easily select which port documentation to install and at the same time can easily set it for all affected ports, e.g. # portmaster shells/bash +-- Install documentation -+ + [ ] All + + [X] None + + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ I have no idea what it would take to implement this in a sane way within the current framework, but IMHO this would provide a pretty good user experience. Cheers, Michael p.s. - If you wanted to provide this for more than one general option, dialog4ports' section feature might become handy, e.g.: + General options -+ + [ ] All + + [X] None + + Documentation --+ + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + + Native Language Support + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On 7 Jun 2013 17:57, Michael Gmelin free...@grem.de wrote: On Fri, 7 Jun 2013 15:42:44 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt I can feel your pain, Bapt :) Anyway, I think the problem with those options (especially DOCS) is that they are not really global in that you want to set them for all ports, but more like general as in well-known. So many ports provide them and the user has a good idea what they're supposed to mean, but ultimately you don't want to set them to the same value for all ports. Regardless of implementation details I would like to see something like the following at least for DOCS, either through config-recursive or - maybe more likely - through a tool like portmaster: After starting the build process and collecting dependencies, an ncurses dialog should be shown that says The following ports provide documentation and a check-box list showing all packages as well as a All and None options on top of the list. That way the user can easily select which port documentation to install and at the same time can easily set it for all affected ports, e.g. # portmaster shells/bash +-- Install documentation -+ + [ ] All + + [X] None + + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ I have no idea what it would take to implement this in a sane way within the current framework, but IMHO this would provide a pretty good user experience. Cheers, Michael p.s. - If you wanted to provide this for more than one general option, dialog4ports' section feature might become handy, e.g.: + General options -+ + [ ] All + + [X] None + + Documentation --+ + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + + Native Language Support + + [ ] devel/gettext+ + [ ] shells/bash + I can see your point when talking about DOCS, but for
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, 7 Jun 2013 18:15:16 +0100 Chris Rees utis...@gmail.com wrote: On 7 Jun 2013 17:57, Michael Gmelin free...@grem.de wrote: On Fri, 7 Jun 2013 15:42:44 +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote: On 2013-06-07 13:40, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote: On 2013-06-07 12:17, Baptiste Daroussin wrote: On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote: Baptiste Daroussin wrote: Is it possible to still show the dialog if one of those options implies additional dependencies? If not, what should those of us who do not want them installed do? make config will always show those options so you can always tune them. just make config-conditional will not fireup a new dialog automatically if the defined options are only those from the global options. I see. As far as I can tell though, and correct me if I'm wrong, but 'make install' doesn't show those options. It also does not show those options for dependent ports. Neither does 'make config-recursive'. Tools like portmaster will now ignore those as well during install and reinstall. So, again, what are my options if I don't want dependencies to be pulled in silently? You have no options and you never had one in the ports tree sorry. If you have a way to implement that cleanly, I'll be happy to push such features in the ports but really I see a way to do what you ask for. How about only suppressing the dialog if the options have been explicitly set or unset in make.conf? That would be easy but is that a really desired feature? I can only speak for myself, but I don't see DOCS as a global option. For some ports I want documentation, for others I don't, so I want the dialog to show up even if DOCS is the only option. There doesn't seem to be a clear cut line between global and per port options and different users have different opinions about it. Can you make it such that config-conditional suppresses the dialog if all options have been explicitly set or unset either through command line, make.conf or optionsfile? Or in other words only show the dialog if one of the options falls back to a default value (e.g. when a new option has been added to a port and that option has not been set globally). I think that would allow anyone to set/unset any option globally and not be bothered by dialogs without enforcing that view on everybody else. You wouldn't need GLOBAL_OPTIONS any more then. Ok so I misunderstood at first. That looks not easy to do, and I'm a bit borred with hacking the options. If someone do something in that direction, I'll be happy to review and help, but honnestly I don't plan to do it myself. regads, Bapt I can feel your pain, Bapt :) Anyway, I think the problem with those options (especially DOCS) is that they are not really global in that you want to set them for all ports, but more like general as in well-known. So many ports provide them and the user has a good idea what they're supposed to mean, but ultimately you don't want to set them to the same value for all ports. Regardless of implementation details I would like to see something like the following at least for DOCS, either through config-recursive or - maybe more likely - through a tool like portmaster: After starting the build process and collecting dependencies, an ncurses dialog should be shown that says The following ports provide documentation and a check-box list showing all packages as well as a All and None options on top of the list. That way the user can easily select which port documentation to install and at the same time can easily set it for all affected ports, e.g. # portmaster shells/bash +-- Install documentation -+ + [ ] All + + [X] None + + [ ] converters/libiconv + + [ ] devel/gettext+ + [ ] shells/bash + +--+ + OK Cancel + +--+ I have no idea what it would take to implement this in a sane way within the current framework, but IMHO this would provide a pretty good user experience. Cheers, Michael p.s. - If you wanted to provide this for more than one general option, dialog4ports' section feature might become handy, e.g.: + General options -+ + [ ] All + + [X] None + + Documentation --+ + [ ] converters/libiconv + + [ ] devel/gettext
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees utis...@gmail.com wrote: I can see your point when talking about DOCS, but for NLS it's insanity *for general use*. Give me an example of where NLS non-globals are appropriate and I'll shut up. The GIMP in Russian locale. GNU Make in any non-English locale. -- Andrew W. Nosenko andrew.w.nose...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On Fri, Jun 7, 2013 at 8:23 PM, Michael Gmelin free...@grem.de wrote: I was mostly talking about DOCS, I (poorly) chose NLS as an additional example to show how multiple groups could work. Usually NLS is a true global option. NLS is global option only for people with en_* locale, who, therefore, just don't see the pain produced by it. DOCS are just a space on HDD. But localized names of image filters, tools Co in GIMP -- it's just a barrier to use books and other knowledge sources. And I don't say just about stupid eye-blow errors in translations, when results of automatic merge went in the release and the wild without even fast looking through by the someone, who has that language as native. -- Andrew W. Nosenko andrew.w.nose...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] dialog4ports does not popup anymore only for global options
On 7 June 2013 18:49, Andrew W. Nosenko andrew.w.nose...@gmail.com wrote: On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees utis...@gmail.com wrote: I can see your point when talking about DOCS, but for NLS it's insanity *for general use*. Give me an example of where NLS non-globals are appropriate and I'll shut up. The GIMP in Russian locale. GNU Make in any non-English locale. I guess you mean the translations are bad? Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
