On 04/06/2014 02:24, Tom Wijsman wrote: > There is no such thing as a non-systemd profile; a sub directory is a > specialization, that doesn't mean that it parents suddenly become the > opposite of that. No, the parents are just generalizations that aren't > as specific as the sub directory. > > Doing what you've suggested everywhere but in gnome/systemd and > kde/systemd is a recipe to upset everyone whom runs systemd on another > desktop environment than GNOME or KDE; so, that's not a way forward. > > Another option is to create no-systemd sub directories; but such > profiles will be highly controversial, besides helping the exponential > grow of the profiles directories as well as be a non-default profile. > > Mix-ins from Funtoo, anyone?
p.s. off-list :-) mix-ins? Awesome idea. We should do more of those. I don't understand why people are punting this idea of a non-systemd profile, I can see how that could ever work. Profiles *add* stuff or set some defaults, taking things away in a profile is really hard. The only thing it works for is globally setting stuff that can never be used eg, you need to remove all x86 cpu flags from arm Desktop profiles with and without systemd or KDE or Gnome or whatever looks exactly like an inherited class plus interfaces problem. Which is what mix-ins do :-) So once again - mixins, an awesome idea -- Alan McKinnon alan.mckin...@gmail.com
