Re: Behaviour of dpkg-source with "3.0 (quilt)" and VCS and automatic patches
- To: firstname.lastname@example.org
- Subject: Re: Behaviour of dpkg-source with "3.0 (quilt)" and VCS and automatic patches
- From: Ben Finney <email@example.com>
- Date: Wed, 01 Jun 2011 13:25:10 +1000
- Message-id: <[🔎] firstname.lastname@example.org>
- References: <20110529085303.GA17707@rivendell.home.ouaza.com> <20110529124544.GA9602@pcpool00.mathematik.uni-freiburg.de> <20110530144155.GD28898@rivendell.home.ouaza.com> <20110530180430.GA7355@pcpool00.mathematik.uni-freiburg.de> <email@example.com> <20110531124344.GL14793@bach.rivera.co.za>
Stefano Rivera <firstname.lastname@example.org> writes:
> Hi Scott (2011.05.31_12:58:05_+0200)
> > This fits my mental model of being a distribution developer. It
> > cleanly separates upstream code from packaging except when I choose
> > to entangle them by applying the patches.
> That's my model too, and I find v3 works well, combined with
> merge-mode VCS (i.e. containing only /debian).
Yes. I use this, too, and recommend this style to Scott since it does
exactly what he states above as a requirement in his mental model.
\ “It is well to remember that the entire universe, with one |
`\ trifling exception, is composed of others.” —John Andrew Holmes |