[Kde-scm-interest] [Proposal] Package splitting with thin meta-repos

[Daniel Johnson]

On Friday 29 January 2010 13:12:27 Pau Garcia i Quiles wrote:
> 2010/1/29 ComputerDruid <computerdruid at gmail.com>:
> > So basically I'm missing what action you need to do across the whole of
> > KDE that isn't a "get everything" or "update everything".
> 
> You need no new code. There's 'repo' for that case. But I'm not sure
> we want to go that path. I certainly dislike it.
I'd really like to know why you don't like it, especially since I perceive it 
to be incredibly flexible.

I like the idea of using our own scripts if we were able to keep them 
incredibly simple, because then they could hopefully be very transparent (eg 
show the developer exactly what is going on during the clone operation).

> As I said before, IMHO the need for something like 'svn externals'
> should be fulfilled in git (i. e. adding a new subcommand to the git
> suite, not creating our own command). I already pointed to a thread
> where this was being discussed. Submodules only work for a very
> specific case.
But these type of external modules seems restrictive, since you're basically 
forced to get everything in that case.

But even if you don't care about having to get everything, why is this better 
than a couple of quick scripts that setup everything before setting you free 
with a bunch of git modules?

> Oh, and regarding 'git clone --recursive', well, '--recursive' should
> be the default, not the option. IMHO it should be exactly the
> opposite: 'git clone --no-recursive' should be the option.

This really is a minor detail. You only ever have to clone once, so it's not 
like it's a command you're going to be using every day.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100129/378f9535/attachment-0001.sig