[Kde-scm-interest] Package splitting

[Chani]

On January 27, 2010 01:45:09 Thiago Macieira wrote:
> Em Quarta-feira 27 Janeiro 2010, às 09:35:21, Chani escreveu:
> > > You don't want to track. The point is to remember, when you go back in
> > > time, which revision is known to work. More importantly, when you tag,
> > > you know exactly what you released.
> > 
> > what's the downside of having a repository composed of thousands of
> > "update subrepo foo" commits? we're past a million svn commits now,
> > that's a lot of committing - but now that I think about it I'm having
> > trouble coming up wth an actual problem with that. apart from the
> > potential cpu and network load for the update bot, which could be tiny
> > for all I know.
> 
> You don't update the supermodule unless you want to say something.
> 
> For example, when we're about to tag, tag all repositories, then the
> supermodule.
> 
> Other than that, there's no need to change the supermodule at all.
> 

what? but then when someone downloads the kdegames supermodule, thinking that 
they're getting all hte latest kdegames code, they'd actually get... what? the 
code from the last tag, possibly weeks ago?

and then to get the actual latest kdegames code you'd have to do some git 
command in each individual game repo?

then we're back at square one.

the problem I was trying to solve here was the "I want all of games and edu 
without running over a dozen commands", not just the question of "what counts 
as part of kdegames?"

in order to do that with submdules, *something* has to be continually updating 
the supermodule to point to the latest revisions of everything.

-- 
This message brought to you by eevil bananas and the number 3.
www.chani3.com
-------------- 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/20100127/e2a4ce91/attachment.sig