[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 20:33:58 +0200, Frank Lichtenheld <djpig@debian.org> said: 

> On Sun, Oct 07, 2007 at 10:49:48AM -0500, Manoj Srivastava wrote:
>> OK, commenting on this with my "I use arch" hat on. If I understand
>> correctly, we are proposing shipping a working directory in the .deb;
>> and not shipping an orig.tar.gz nor a diff.gz file. I like

> You probably mean source package here and not .deb. Also the original
> proposal just means shipping the repository data, since most DVCS can
> easily create a working directory from that.

        Hmm. The repository data, as far as I can tell, means the name
 of the archive, and the location.  Do you really mean we are not
 shipping any, say, foo.c file in the sources, just a locatio where you
 can get the foo.c file from, at a particular version?

> The whole idea of the proposal is to NOT create an export.

        If we are not creating and export, and we are only shipping the
 repository data,  how come there  needs to be a check for uncommitted
 files? If the changes are uncommitted, that means the repo does not
 know about it; and if we only ship  the repository data, we are not
 shipping stuff not in the repo.

        What am I missing?

>> for each tree_root and nested; do run $TLA CHANGES map {
>> $list{${NESTED_PATH}/$_} => 1; } join ",", `$TLA inventory -s` done
>> For all files in exclude list, go and set values in %list to 0 (or
>> delete the key)
>> ** I have no idea what the prune and shallow copy commands do, or the
>> arch equivalent **

> git gc --prune deletes old data that isn't needed anymore. This is
> needed since all other git commands never change or overwrite data
> (file data, this is obviously not true for meta data), they only add
> some.

        I am unsure what this means in term of arch.

>> sub post_unpack_tar make sure we have an ./{arch} directory.Look for
>> nested submodules: $tree_root=$($TLA tree-root); @nested=`$TLA
>> inventory -t --nested "$tree_root"`;
>> ** arch hooks are per user, not per repo -- iirc **
>> ** what does git-config do? or bzr checkout? **

> git-config is just an cli interface to the .git/config file.  Since we
> only ship the repository we need to create the working tree. This is
> what git/bzr checkout do.

        Well, I do not see how this is done in arch. If you are not
 shipping the working tree; all I can see shipping for arch is the URI
 of the repo. I am pretty sure this is not what you mean, since then any
 arch based source would be three lines or so, and would need network
 access to unpack the source tree.

>> Actually, at this point I am beginning to question my understanding
>> of the proposal.  If we are shipping a working tree, what is this
>> step doing?
>> Is this an svn update equivalent?

> No, that would be git fetch/pull (and probably something similar named
> in bzr)

        I don't think I know what this means when you are using arch.


Earn cash in your spare time -- blackmail your friends.
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: