if you consider that the package would need to be different for each different distro (and likely for different releases of the same distro), I don't know how any packaging tool could reach the point of 'run it and upload it to the distro repository'
for that matter, I would have assumed that the distros don't take binary uploads anyway. shouldn't they all be setup where you upload the source and a series of instructions and their build servers create the binary packages for each of their several target architectures?
there is not as much variation in distros that accept .deb packages, but if you look at all the distros that use .rpm packages, the number of things that would be different from one to the other seems like it would be very significant, and a lot of it would be things that a packaging tool would not know about (what the the correct version of gcc to use, etc)
Posted Sep 7, 2011 11:45 UTC (Wed) by robbe (guest, #16131)
[Link]
> if you consider that the package would need to be different for each different distro [...]
I can imagine a profile-based solution. But it'd probably be much maintenance work for little gain.
> for that matter, I would have assumed that the distros don't take binary uploads anyway.
Debian used to take source+binary uploads. There has been discussion to switch to source-only uploads, but the risk of maintainers not even compile-testing revisions that supposedly contained only trivial fixes was deemed too high. So the current regime, AFAIK, is to requier source+binary, but throw away the binary.