Closed pauldotknopf closed 4 years ago
I think there is some harm in having downstream packaging files in upstream project repos. Except in the case where the project owner is also the primary responsible party for downstream packaging, they are almost never in sync. Basically downstream(s) need to keep that info in a repository of their own anyway and the upstream stuff is just a template to get started that may or may not be followed exactly. For example in the case of Debian the changelog must be edited for every rebuild which includes tweaking what distro targets it builds for, rebuilding for reasons unrelated to the upstream, etc. It is unreasonable to think that those updates will all make it back into this repo, and even if they did there would be conflicts between Debian, Ubuntu, and other packagers that use the same meta data but not the same build infrastructure. Inevitably this ends up being stale.
Also I don't think you'd want the clutter of including packaging templates for all distros! A PKGBUILD for Arch and a Ruby formula for Homebrew and a ...
Yeah, you are right. If nothing else, it's now known that it exists in this fork if anyone needs it.
I'm not sure if you'd even want them, but I see no harm in trying to put them upstream :)