On Sat, 28 Feb 2009, Michael Biebl wrote: >>> >>> 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) > > Pretty simple: It's less work for me and Rainer and more flexible. > Say I (for Debian) start adding the files upstream, so does Fedora, BSD, > etc... > Now when Rainer wants to make a new release to not have any stale > packaging files, he would have to ping all package maintainer first to > update the build files and push those changes. That simply doesn't > scale. > Packaging and upstream software releases should be decoupled. > > If you are really interested in the Debian Packaging, you can grab the > git repository from [1] and either work from there or at it as a > "remote" to the rsyslog git repo and merge the debian specific bits.
it's not that I'm interested in debian packaging, it's that I need to install the stuff that you haven't decided to ship in debian yet on my debian system in such a way that I keep the package manager happy (and don't have it overwriting what I've compiled with an update of an obsolete version) it's not that the upstream version of the files need to be perfect, but they should be good enough to avoid the need for users to have to fight the packaging system and duplicate your efforts. I hate to have to pull in some stuff from your tree and combine it with stuff from the upstream tree because I don't know enough to be sure that I'm both pulling everything I need and not pulling something that will cause grief. you've made your decision, count this as one voice disagreeing with that decision. David Lang _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
