I saw this posting in a few sources and read through most of it. It sounded appealing but now after reading this article, it falls short of what I was hoping for.
I really just want a way that I (as an upstream) can get my package to users ASAP after I do a release and without the semi-random collection of patches that tend to get added.
Posted Sep 6, 2012 13:57 UTC (Thu) by stefanor (subscriber, #32895)
[Link]
I don't think that's an entirely solvable problem. Packaging an application very often involves making some changes. The upstream developers don't usually think too much about how it'll eventually be deployed.
Improving Ubuntu's application upload process
Posted Sep 7, 2012 3:01 UTC (Fri) by pabs (subscriber, #43278)
[Link]
You can avoid some of those random changes by being distribution-friendly and running various static analysis tools, here are a couple of links for Debian:
As an upstream developer I always run whohas before every release to find out what distro patches/bugs I may have missed and then merge or fix those when there is time.
It sounds like what you want is one of these, that way you get to do the packaging instead of distributions and you can target all distros instead of just Ubuntu.
Posted Sep 10, 2012 21:49 UTC (Mon) by mathstuf (subscriber, #69389)
[Link]
> As an upstream developer I always run whohas before every release to find out what distro patches/bugs I may have missed and then merge or fix those when there is time.
Wow, never knew about whohas. *Adds to personal packaging tools comps file* Thanks!