On Fri, 27 Feb 2009, Michael Biebl wrote: > 2009/2/26 <[email protected]>: >> even where rsyslog is included in a distro it's very handy to have a spec >> file (or debian equivalent) included with the source to allow a 'make rpm' >> or 'make deb' to properly make packages. >> >> I've been using checkinstall to create debian packages from the compiled >> source, and I don't know what it's doing wrong, but I've been tripped up a >> few times by it not replacing all the files that it should if rsyslog is >> already installed (the packages it creates work just fine if rsyslog isn't >> installed at all) > > > FWIW, I as Debian maintainer of rsyslog, explicitly asked Rainer to > remove the debian/ directory from the upstream source tree. Reason is > simple: Packaging is the task of the downstream distros and the files > shipped upstream were always out-of-date anyways. This not only caused > more work for me as Debian maintainer but also leads to bad user > experience if the rpm/debs created from the upstream spec/debian build > files are outdated and potentially create a half-way broken package. > > If the fedora bits are kept in an entirely separate upstream packaging > branch, then I don't really care. > But I wouldn't like to see them (or any debian related files) shipped > in a release tarball.
so how am I (a debian user) supposed to create debian compatible packages for versions that you don't yet deal with? why couldn't you push the debian related files upstream and maintain them there? (submitting patches, or git pull requests for updates) David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
