I'd like to weigh in here as one who has to build the Chromium source
package on an almost daily basis, rendering his computer almost unusable
during the build (~20 min).
Changes in debian/, i.e. those that doesn't touch the upstream
directories, shouldn't to require a new .orig unpack. I'm no
On Fri, Dec 11, 2009 at 02:08:36PM +0100, Raphael Hertzog wrote:
> On Fri, 11 Dec 2009, Mike Hommey wrote:
> > On Fri, Dec 11, 2009 at 01:40:34PM +0100, Raphael Hertzog wrote:
> > > On Fri, 11 Dec 2009, Mike Hommey wrote:
> > > > There are currently 2 problems with the way the .orig.tar.gz file is
On Fri, 11 Dec 2009, Mike Hommey wrote:
> On Fri, Dec 11, 2009 at 01:40:34PM +0100, Raphael Hertzog wrote:
> > On Fri, 11 Dec 2009, Mike Hommey wrote:
> > > There are currently 2 problems with the way the .orig.tar.gz file is
> > > extracted during dpkg-source -b:
> > > - When a package-ver.orig di
On Fri, Dec 11, 2009 at 01:40:34PM +0100, Raphael Hertzog wrote:
> On Fri, 11 Dec 2009, Mike Hommey wrote:
> > There are currently 2 problems with the way the .orig.tar.gz file is
> > extracted during dpkg-source -b:
> > - When a package-ver.orig directory pre-exists, it gets removed.
>
> With for
On Fri, 11 Dec 2009, Mike Hommey wrote:
> There are currently 2 problems with the way the .orig.tar.gz file is
> extracted during dpkg-source -b:
> - When a package-ver.orig directory pre-exists, it gets removed.
With format 1.0, there are many -s* options precisely to control this
(you may want t
Package: dpkg-dev
Version: 1.15.5.4
Severity: wishlist
File: /usr/bin/dpkg-source
There are currently 2 problems with the way the .orig.tar.gz file is
extracted during dpkg-source -b:
- When a package-ver.orig directory pre-exists, it gets removed.
- The orig tarball is unpacked just to be removed
6 matches
Mail list logo
