Hi all, I committed a modification to UseFlags yesterday/this morning to enable same-named flags for every installed program by default. The program names are normalised to valid flag form (lowercase alphanumeric plus underscore; - transforms to _, every other character is stripped[1]). These flags are enabled after the system flags (in Scripts/Data), but before the site flags in /S/S/UseFlags.conf, so you can disable them in the usual fashion.
This means that installing a program will generally enable support for it everywhere, including places that don't autodetect correctly. It also means that many users won't ever need to know that the flags exist, and things will "just work". There will still be manually-enabled flags for hardware, generics, and other behaviour that isn't tied to a specific single dependency, and you can still control all the flags manually either by disabling the ones you don't want or with "-*" at the top of UseFlags.conf. For recipe authors, everything is much the same as it's always been, but you can rely on having +progname on when compiling against a particular dependency, for the cases where autodetection goes awry. Comments, anybody? I discussed this with Jonas, and we think it's a reasonable default behaviour, but does anybody else have any thoughts? This is with a Scripts release in mind sometime in the not-too-distant future. -Michael _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
