Hi Joey, Thanks again for your constructive feedback.
Joey Hess <jo...@debian.org> writes: > That's not what I was trying to say. I like debhelper commands to be > thin wrappers around programs that handle the heavy lifting and the > domain-specific knowledge. This is why debhelper has a per-command LOC > limit. > > If that were moved out to a serparate program, which would look perhaps > something like [1], dh_systemd would be a lot shorter, and then > we could perhaps make a better decision about whether or not it belongs > inside dh_installinit. AFAICT, there are no such binaries shipped with debhelper itself. Does that imply that we should ship such a tool in e.g. systemd-dev built from the systemd source package? Is that what you’re suggesting? > Oh yeah, something else I don't like doing in debhelper is encoding the > current location in PATH of commands. Similar autoscripts use which This sentence looks cut-off. Could you clarify what you meant? I’ll look into your suggestions over the course of the next few days. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
