As some of you might have noticed, I've been experimenting with submodules
for a few days. We looked briefly into this when we created Compiz Fusion,
but it was discarded because it only became available in git 1.5, and not
even 1.5.0. That is no longer an issue.

Submodules in git is just having a super-repository which links to a series
of other repositories. The obvious use case for Compiz Fusion is to have
one super repository which contains all of Compiz Fusion, and Compiz. I
have, in fact, set up a repository just like that [1]. 

Today, the closest thing to this that we have is plugins-main/extra, which
has some issues (Branching, being one significant one. Easy breakage being
an other).

The main advantage that I see is that we can unify the project. This will
make it easier to document the entire project, to keep track of the project
as a whole and to introduce new developers to the project. However, there
is some work needed to make it work well, mainly build system magic (or I
could script it, which isn't that bad either). Again, the advantage would
be to have ONE place for this. It would also make things like yags and
get-git redundant.

Before I start arguing technical details, I want to hear the opinions of
other developers. Thoughts, ideas, concerns, etc. I suggest that you
(the developers, however long you've been with the project) take at least a
brief look at the test repo I set up. It can obviously be organized
differently, but it should give you an idea of how it works. README has
some loose comments on Pros and Cons.

[1] http://cgit.compiz-fusion.org/~kristian/cf-master-test/

- Kristian

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Dev mailing list
[email protected]
http://lists.compiz-fusion.org/mailman/listinfo/dev

Reply via email to