[Kde-scm-interest] Layout of Git repositories for KDE

[Riccardo Iaconelli]

On Thursday 01 November 2007 12:08:52 Thiago Macieira wrote:
> Em Thursday 01 November 2007 11:34:54 Riccardo Iaconelli escreveu:
> > I'm a bit concerned about how we will treat svn:externals, especially
> > when they are in different modules. Think for example of libplasma being
> > embedded in amarok. How are we going to treat this?
>
> If the external refers to something that is a repository in entirety, then
> it's ok to keep it as a git-submodule link.
>
> If it's referring to something inside a repository, git submodule cannot
> represent it. Therefore, options are:
>
> 1) request the feature from git (this includes a partial-tree checkout too)
> or

Sounds like the saner idea, altough I presume it will probably take quite some 
time to be implemented, if it will ever be. When do we want, roughly 
estimating, do the switch to git?

> 2) make the target *be* a repository on its own and use submodules in both
> places or

Sounds a bit complicated, you would make kdebase/workspace/libs/plasma/ a 
submodule? Doesn't this all risk to get incredibly messy?

> 3) drop the link entirely

If we end up proposing with point 3 as a solution, I think we won't convince 
anyone in KDE to switch to git. ;-)
What I use right now (for svn externals in the same module, with git-svn) is a 
symbolic link (inserted in .gitignore), but that's very ugly, and it breaks 
anyways for links between different modules.

Bye,
-Riccardo
-- 
GPG key:
3D0F6376
When encrypting, please encrypt also for this subkey:
9EBD7FE1
-----
Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平
Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch
Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화