On 12/08/14 09:57, David Lamparter wrote: > Now, for usage of the files bundled in Quagga: > > * .spec init systemd sysconf logrot. PAM > Alpine - custom - - - - > Arch - - custom - sed - > Debian - custom - - custom custom > Gentoo - custom - - used custom > Mageia custom - custom used used used > OpenSuSE custom custom - - used custom > Rawhide custom - patch used used - > Slackware - custom - - custom custom
Note that even for those that have a "custom" variant, there may well be someone downstream watching for diffs on the bundled files and manually reinterpreting those as changes to be applied to the customized version (or at least as a warning of important changes to note). I agree with Alexis Rosen's previous message. A "best effort" approach makes a lot of sense. Keep what's there. Either take a blind stab at applying changes in the rare case that they happen, or ignore the files because you don't understand them and let 'em rot; either's fine. Happily update if someone actually using that system contributes updates "real" fixes. A readme that says "we think this might have worked at one point, and we wish you the best of luck" should be sufficient. A principled stand would be to make a platform-agnostic programming interface. I.e., provide some sort of script or utility that can report which daemons need to run and with what arguments based on the supplied configuration, and then leave it up to a platform-supplied mechanism to determine what to do with that list (feed to shell, tell systemd or svccfg, or something else). But that's probably ETOOHARD. -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
