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

Re: Need to reach a decision on how to handle the git repository



On Fri, Jun 6, 2008 at 11:04 AM, Miriam Ruiz <miriam@debian.org> wrote:
> 2008/6/6 Robin Cornelius <robin.cornelius@gmail.com>:
>
>> I also like the idea of using git, pristine-tar etc (as per option 2)
>> but also with the option of using a patch system such as quilt. I
>> currently have dpatch and have refrained from converting my package to
>> quilt patches until this discussion was resolved. I have the following
>> concerns :-
>
> My question then would be, if we used quilt and only changed stuff in
> debian/, what's the advantage of having the whole source code in git,
> instead of just debian/ as we do in SVN? The disadvantage is huge if
> you need to download many packages at once, while with just debian/
> it's quite quick. Upstream's source code won't be modified directly in
> this layout, so why not just keep having a tarball out of the
> versioning system as we do with SVN?
>

I can see your point and looking at what others do i have not seen a
satisfactory solution either that fits all situations.

Actually, the disadvantage should not be as great as you say. If
upstream branch has not changed the cost to update in any situation
should be small, either layout. Just the actual delta. The only
expensive bit is the initial cloning, but, with SVN you would have to
checkout then download the tarballs to have a working build so the
cost here is similar initially too.

A possible idea, upstream and pristine-tar type branches could be
remote tracking and ONLY pulled if explicitly requested by someone
cloning and pulling the remote branches (i think this is possible or i
miss understand how git actually works). This is more in common with
the svn approach but i don't think it takes away from git as much as
some other options, any one who wants everything gets it. If for some
reason you just want to download all the packaging it is very low
cost. Now git-build package does not support this. This was something
i tried when i first started playing as it seemed like a sensible
thing to do. To me i expected that i could have an unstable/ branch
with just debian/ and a upstream branch with pristine source and
git-buildpackage would just do the right thing, but i was clearly
wrong about what i should be doing, but i still think its not a bad
idea, i might however be very very wrong ;-0

Robin


Reply to: