On Fri, Oct 05, 2007 at 07:16:13PM -0400, Joey Hess wrote:
> I've been working on making dpkg-source support a new source package format
> based upon git.
Oh, one question that comes to mind: how does this affect checking for
non-free stuff in past revisions? If 3.1-4 had some non-free files that
On Sat, Oct 06, 2007 at 10:37:48PM +, Colin Watson wrote:
> The second possibility seems to me to be more flexible, though, and
> probably not all that hard to implement: build both a .tar.gz
> (containing the working tree) and a .$VCS.tar.gz, and teach 'dpkg-source
> -x' to unpack the tree giv
On Sat, Oct 06, 2007 at 11:19:43AM -0400, Joey Hess wrote:
> Anthony Towns wrote:
> > Changes in repository formats will presumably result in versioned
> > dependencies too.
> I don't think that dpkg should add vcs formats that we don't have a good
> expectation of remaining supported by newer vers
Frank Lichtenheld wrote:
> I guess if we use Joey's idea at all we will not be able to avoid
> shipping such a module for each distributed VCS, and I didn't get
> the impression that Joey thought otherwise.
I do think otherwise. If the distributed (or other) VCS does not meet
our criteria for secu
Colin Watson wrote:
> So, I can't stand git's user interface. I generally try to avoid making
> a huge issue of this since it seems to be massively political on places
> like Planet at the moment, there seems to be a certain amount of
> confusion of people's personal opinions with that of their emp
Frank Lichtenheld wrote:
> I think there is a mechanism in git to disallow replacing old pack
> files (i.e. forcing to create additional ones with only new objects),
> however, I haven't used that myself, yet.
The packs in the diff package would be basically the same packs that
git-send-pack gener
On Sat, Oct 06, 2007 at 11:09:21PM +0200, Frank Lichtenheld wrote:
> Use .orig.tar.(bz2|lzma) if they are available
> and no .gz can be found. Also let the user specify
> via -C(gz|bz2|lzma) how files that need to be
> generated should be compressed.
Hmm, I just noticed that dpkg-genchanges alread
On Sat, Oct 06, 2007 at 10:37:48PM +, Colin Watson wrote:
> On Fri, Oct 05, 2007 at 07:16:13PM -0400, Joey Hess wrote:
> > I've been working on making dpkg-source support a new source package
> > format based upon git. The idea is that a source package has only a
> > .dsc and a .git.tar.gz, whi
On Sat, Oct 06, 2007 at 11:17:58PM +0200, Frank Lichtenheld wrote:
> On Sat, Oct 06, 2007 at 05:27:04PM +1000, Anthony Towns wrote:
> > This means you can't build the package by hand with standard unix tools
> > -- at the very least you need git installed, and if other VC systems
> > are to be supp
On Fri, Oct 05, 2007 at 07:16:13PM -0400, Joey Hess wrote:
> I've been working on making dpkg-source support a new source package
> format based upon git. The idea is that a source package has only a
> .dsc and a .git.tar.gz, which is just a git repo.
So, I can't stand git's user interface. I gene
On Sat, Oct 06, 2007 at 11:19:43AM -0400, Joey Hess wrote:
> Anthony Towns wrote:
> > Is a .gitdiff.tar.gz possible, so the archive doesn't need to have the
> > full git repo replaced by each upload? ie, something like
> >
> > Files:
> > foo_1.0-1.git.tar.gz
> > foo_1.0-2.g
On Sat, Oct 06, 2007 at 05:27:04PM +1000, Anthony Towns wrote:
> On Fri, Oct 05, 2007 at 07:16:13PM -0400, Joey Hess wrote:
> This means you can't build the package by hand with standard unix tools
> -- at the very least you need git installed, and if other VC systems
> are to be supported, you nee
Use .orig.tar.(bz2|lzma) if they are available
and no .gz can be found. Also let the user specify
via -C(gz|bz2|lzma) how files that need to be
generated should be compressed.
I think this is about the maximum support for wig&pen we can add in
dpkg-source -b without big code changes. But it might
Joey Hess wrote:
> > Bonus points: rather than "debian/rules clean, create a diff, build",
> > have dpkg do "debian/rules clean, commit any uncommitted changes with the
> > commit message being the changes from the changelog, create a .git.tgz,
> > build" for git-source-format packages.
>
> I have
Joey Hess wrote:
> > Maybe providing a feature on packages.debian.org (or similar) to download
> > sources in simple, non-VC, tarball format would make this a complete
> > non-issue though?
>
> pristine-tar could be used for this, it would just need source packages
> to put the delta somewhere sta
On Fri, Sep 28, 2007 at 05:42:41PM +0100, Ian Jackson wrote:
> Raphael Hertzog writes ("Accepted dpkg 1.14.7~newshlib (source i386
> all)"):
> > [stuff]
>
> I'm very pleased to see all of this work being done on the Perl
> scripts - I'm hoping for big compatibility improvements from Raphael's
> sh
I was looking for a way to really close #373003 (dpkg-dev: deb-control.5
old rule for Version hyphenation). In the end it lead me to the
conclusion that Dpkg should contain a full description of its Version
format, which in turn lead to completly copying the section from Policy
since this is probab
Anthony Towns wrote:
> Is a .gitdiff.tar.gz possible, so the archive doesn't need to have the
> full git repo replaced by each upload? ie, something like
>
> Files:
> foo_1.0-1.git.tar.gz
> foo_1.0-2.gitdiff.tar.gz
>
> so that a small patch only adds a small file to
On Fri, Oct 05, 2007 at 07:16:13PM -0400, Joey Hess wrote:
> I've been working on making dpkg-source support a new source package format
> based upon git. The idea is that a source package has only a .dsc and a
> .git.tar.gz, which is just a git repo.
Is a .gitdiff.tar.gz possible, so the archive
19 matches
Mail list logo
