Re: dpkg-source's future and relation with VCS

2008-02-24 Thread Guillem Jover
Hi, On Mon, 2008-02-11 at 14:46:33 +0100, Raphael Hertzog wrote: On Mon, 11 Feb 2008, Frank Lichtenheld wrote: For me this sentence is the essence of your mail: That you dislike Joey's idea since it includes the VCS in the source package itself and would prefer that we worked on creating a

Re: dpkg-source's future and relation with VCS

2008-02-24 Thread Anthony Towns
On Sun, Feb 24, 2008 at 11:48:44AM +0200, Guillem Jover wrote: So I don't quite like Joey's idea in its current form, for the reasons other people have stated on the thread: *sigh* So dpkg isn't going to support it then? Cheers, aj signature.asc Description: Digital signature

Re: dpkg-source's future and relation with VCS

2008-02-12 Thread Raphael Hertzog
On Wed, 13 Feb 2008, Anthony Towns wrote: On Mon, Feb 11, 2008 at 02:46:33PM +0100, Raphael Hertzog wrote: However I'm also convinced that: - a source package should be unpackable without a VCS. This means that somehow it should contain a checkout that can be extracted with basic

Re: dpkg-source's future and relation with VCS

2008-02-12 Thread Russ Allbery
Raphael Hertzog [EMAIL PROTECTED] writes: On Tue, 12 Feb 2008, Russ Allbery wrote: Basically, the way to do this is to do the dbs thing, I think. The structure of the .tar.gz file would be: - All content in the .tar.gz file is in a debian subdirectory as packed. - debian/patches contains

Re: dpkg-source's future and relation with VCS

2008-02-12 Thread Anthony Towns
On Tue, Feb 12, 2008 at 12:51:12AM -0800, Russ Allbery wrote: Anthony Towns [EMAIL PROTECTED] writes: My point is precisely that it's *NOT* useful now. No software is useful until it is implemented. wigpen is far from unique in that regard. Right, but the git/bzr stuff _is_ implemented...

Re: dpkg-source's future and relation with VCS

2008-02-12 Thread Anthony Towns
On Mon, Feb 11, 2008 at 02:46:33PM +0100, Raphael Hertzog wrote: However I'm also convinced that: - a source package should be unpackable without a VCS. This means that somehow it should contain a checkout that can be extracted with basic tools. [1] I don't think it's feasible to require

Re: dpkg-source's future and relation with VCS

2008-02-11 Thread Russ Allbery
Anthony Towns [EMAIL PROTECTED] writes: I think it's a mistake to separate those -- our source package format is a VCS system; if wigpen happens to be a more suitable VCS, that's fine, but it's not inherently superior or inferior to any other VCS, just because it happens to be

Re: dpkg-source's future and relation with VCS

2008-02-11 Thread Russ Allbery
Anthony Towns [EMAIL PROTECTED] writes: A VCS is a system for controlling (managing, distributing) versions of a repository. A Debian source package is a repository. It's a changeset or a set of changesets. This is not a repository any more than a collection of objects is a balanced

Re: dpkg-source's future and relation with VCS

2008-02-11 Thread Joey Hess
Russ Allbery wrote: (it's not yet clear to me that Git can usefully represent changesets via feature branches, but that's another argument that is already ongoing elsewhere). People are arguing about that because bikeshedding and random discussion of lattices, is, apparently, fun. apt-cache

Re: dpkg-source's future and relation with VCS

2008-02-11 Thread Raphael Hertzog
Hi, On Mon, 11 Feb 2008, Frank Lichtenheld wrote: For me this sentence is the essence of your mail: That you dislike Joey's idea since it includes the VCS in the source package itself and would prefer that we worked on creating a solution on top of wigpen instead. Do I understand that