Marc Haber wrote: > On Sun, 17 Aug 2014 23:14:33 -0500, Josh Triplett <j...@joshtriplett.org> > wrote: > >Why a requirement to not improve upstream? Ideally, the Debian patches > >for a piece of software should trend to zero over time, as fixes make > >their way upstream. > > Imagine an upstream author having the cooperation level of the systemd > team.
Highly cooperative, responsive, understanding of distribution issues, and willing to work with multiple distributions to come up with a good cross-distro solution that works everywhere? > This will put the Debian maintainer between a rock and a hard place. When dealing with an upstream that *isn't* cooperative or helpful, sure, you might end up effectively creating a downstream fork. It's unfortunate when that happens in the Debian packages rather than in a separate repository that then gets packaged, but *shrug*. However, the original mail that started this thread didn't suggest that the upstream in this case was uncooperative or unreceptive to patches. - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819044821.GA1345@thin
