ebuild is only enabling by default (+) +firmware-loader and +kmod, but this is not coherent with flags tagged as defaults in http://wiki.gentoo.org/wiki/Systemd#Software Thanks for clarifying this :) Reproducible: Always
Feel free to update the wiki; keeping the ebuild and wiki 100% in-sync sounds like a pain though.
The default column shows, whether this USE flag is enabled by default in this package or by profile. See the "default" column description: http://wiki.gentoo.org/wiki/Template:USEflag/doc
From my point of view, wiki should list what USE flags are expected to be enabled by default, not simply what flags are finally enabled as a result of profiles combination (in that case it's simply informative, and not very useful)
The idea is to have a list of enabled/disabled USE flags like you see when you typ 'emerge systemd'. So you can - without running emerge - enable or disable USE flags in package.use in advance. Also you can see, that differences to the default list are caused by configuration on your side. For me this is more useful, than listing only the defaults of the ebuild.
In that case, I think we should simply drop that box and, instead, show what USE flags systemd team think should be enabled or disabled (as a recommendation)
I have dropped the box: people will need to review what flags will be enabled/disabled in their setups anyway as they will vary depending on the profile, make.conf and many different variables
(In reply to Pacho Ramos from comment #6) > I have dropped the box: people will need to review what flags will be > enabled/disabled in their setups anyway as they will vary depending on the > profile, make.conf and many different variables Arne, my idea would be to try to not make the guide grow with this info because, from my point of view: - A user migrating from openrc will look at the guide - He/She will expect to get configuration steps to migrate, while I see no gain in making the guide bigger (well, people tend to get scared if they see a really big guide to migrate). But, of course, we can still debate it :/ (it wasn't my intention to offend you in any way). Maybe one option would be to split the document: - A Systemd "software information" page -> that would include this box, information about upstream, what "systemd" is... - A page oriented to migration and configuration
(In reply to Pacho Ramos from comment #7) > Arne, my idea would be to try to not make the guide grow with this info > because, from my point of view: > - A user migrating from openrc will look at the guide > - He/She will expect to get configuration steps to migrate, while I see no > gain in making the guide bigger (well, people tend to get scared if they see > a really big guide to migrate). > > But, of course, we can still debate it :/ (it wasn't my intention to offend > you in any way). Maybe one option would be to split the document: > - A Systemd "software information" page -> that would include this box, > information about upstream, what "systemd" is... > - A page oriented to migration and configuration Everything alright, no offend here. Well, it's right, that a big guide is scary, but a big guide packed with good information is more useful than a small guide with not enough information. So I'm more in favor of splitting the guide then drop useful information. And yes, I still like the {{USEflag}} template and its information. It shows nearly all information about USE flags - available flags, descriptions, defaults - one needs in advance before installing the package. It's no full replacement for emerge -v, especially of the depends, but IMO for the package in questions its useful. To slim down the guide: A former version of the {{USEFlag}} template had a feature to collapse the table. See the sandbox examples at http://wiki.gentoo.org/wiki/Template:USEflag/testcases. The feature was removed, because of small visual bugs. I try to get it to work again. Then the table can be set to be collapsed by default.
