https://bugzilla.redhat.com/show_bug.cgi?id=1311752
--- Comment #10 from Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> --- Pffff, I'll try to use conjunctions that actually make sense > This is not a packaging issue, but an upstream issue. But vrpn already has a > config file, so it should simply read whatever options it need itself. Having > a second config file is just a workaround for a stupid deficiency in the > server. If you need to provide configuration options on the command-line, a > systemd unit drop-in override is probably a better option. This is not a packaging issue, but an upstream issue. Vrpn already has a config file, so it should simply read whatever options it need itself. Having a second config file is just a workaround for a stupid deficiency in the server. Nevertheless, if you need to provide configuration options on the command-line, a systemd unit drop-in override is probably a better option. (Also, the name /etc/default/something to *override* *defaults* is backwards ;)) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review
