[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] proposed v3 source format using .git.tar.gz

On Sun, 7 Oct 2007 15:44:47 +0000, Colin Watson <cjwatson@debian.org> said: 

> On Sun, Oct 07, 2007 at 10:05:32AM -0500, Manoj Srivastava wrote:
>> On Fri, 5 Oct 2007 19:16:13 -0400, Joey Hess <joeyh@debian.org> said:
>> > 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.
>> > My implementation adds a new 3.0 version source format. A 3.0
>> > format debian source package can consist of any files allowed by
>> > formats 1 and 2, but may also contain .$VCS.tar.gz files. To build
>> > a version 3 source package, a new field is needed in
>> > debian/control:
>> I do not yet grok git, so could someoe tell me what this means in
>> terms of, say, CVS or arch? What is a $CVS.tar.gz file contain when
>> the we are using CVS?

> I think this only really makes sense for distributed revision control
> systems. For arch, the .arch.tar.gz would contain the {arch}
> directory, perhaps with a few adjustments similar to those being made
> in the git and bzr modules.

        Hmm. If I have just the ./{arch} directory, and none of the
 files, then arch thinks the files have just been deleted; and you can't
 just check out stuff, since the tree is up to date.  Ah. Baz undo
 restores all the files, cool.

        The problem here is that the repository in question _has_ to be
 registered by the user running this; so all the users would have to
 register the arch repository in question before unpacking the source
 tarball in order to tell baz/tla how to get access to the repo. Is this
 going to be an issue?

        I would prefer to instead ship a grab file for arch instead of
 the {arch} directory, since the latter really buys us nothing over the
 grab file (since we are requiring the distributed source dir and
 network access to unpack source packages).

	Consider this grab file:
--8<---------------cut here---------------start------------->8---
Archive-Name: srivasta@debian.org--lenny
Archive-Location: http://arch.debian.org/arch/private/srivasta
Target-Revision: packages--debian--1.0
Target-Directory: manoj-packages
Target-Config: configs/ucf/debian/ucf-3.003
--8<---------------cut here---------------end--------------->8---

tla register-archive --present-ok $values-of-Archive-Location-field
tla grab <path/to/the/grab-file>
cd $value-of-field-Target-Directory/<package-name>/*

(room for standardization here)


--8<---------------cut here---------------start------------->8---
__> baz status
* looking for srivasta@debian.org--lenny/ucf--devel--3.0--patch-1 to compare with
* comparing to srivasta@debian.org--lenny/ucf--devel--3.0--patch-1

D   .arch-ids
D   examples
D   examples/.arch-ids
D   t
D   t/.arch-ids
D   .arch-ids/COPYING.id
D   .arch-ids/ChangeLog.id
D   .arch-ids/Makefile.id
D   .arch-ids/lcf.1.id
D   .arch-ids/lcf.id
D   .arch-ids/ucf.1.id
D   .arch-ids/ucf.conf.5.id
D   .arch-ids/ucf.conf.id
D   .arch-ids/ucf.id
D   .arch-ids/ucfq.1.id
D   .arch-ids/ucfq.id
D   .arch-ids/ucfr.1.id
D   .arch-ids/ucfr.id
D   ChangeLog
D   Makefile
D   examples/.arch-ids/=id
D   examples/.arch-ids/ChangeLog.id
D   examples/.arch-ids/postinst.id
D   examples/.arch-ids/postrm.id
D   examples/ChangeLog
D   examples/postinst
D   examples/postrm
D   lcf
D   lcf.1
D   t/.arch-ids/=id
D   ucf
D   ucf.1
D   ucf.conf
D   ucf.conf.5
D   ucfq
D   ucfq.1
D   ucfr
D   ucfr.1
__> baz update
* tree is already up to date
--8<---------------cut here---------------end--------------->8---

"Time is money and money can't buy you love and I love your outfit"
T.H.U.N.D.E.R. #1
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: