I think that's everything, and it's a bit of a mess as-is since some of these files are in slightly different formats even if the path is the same.
Systemd 197 released
Posted Jan 9, 2013 15:36 UTC (Wed) by Zack (guest, #37335)
[Link]
"Ah, no, it's very distribution-agnostic. It's just, you know, that some of these _other_ distributions are simply not agnostic enough to run the software on."
On the upside though, once package management gets integrated, we'll finally have an answer as to whether 'deb or rpm' constitutes the "one true way".
Systemd 197 released
Posted Jan 9, 2013 17:31 UTC (Wed) by james (subscriber, #1325)
[Link]
One thing you missed is this:
If downstream distributions want to maintain compatibility with their old configuration files, they are welcome to do so, but need to maintain this as patches downstream. The burden needs to be on the distributions to maintain differences here. Our suggestion however is to just convert the old configuration files on upgrade, as multiple distributions already do.
Systemd 197 released
Posted Jan 9, 2013 17:41 UTC (Wed) by sorpigal (subscriber, #36106)
[Link]
I wouldn't call that "missed" since it's essentially in the summary anyway:
We
recommend distributions to simply adopt the configuration
files everybody else uses now and convert the old
configuration from packaging scripts. Most distributions
already did that. If that's not possible or desirable,
distributions are welcome to forward port the specific
pieces of code locally from the git history.
I was listing specifics that weren't in the summary.
Systemd 197 released
Posted Jan 10, 2013 8:06 UTC (Thu) by nhippi (subscriber, #34640)
[Link]