Re: [oll-user] Call for initial feedback

[Urs L. <ul...@op...>]

Am 28.03.2013 13:19, schrieb Joseph Rushton Wakeling:
> On 03/20/2013 04:50 PM, Janek Warchoł wrote:
>>> If that would be possible, we could have one SourceForge project only,
>>> which would be less confusing probably.
>> I like tinkering with git and i think i could learn how to merge
>> repositories.  However, maybe git submodules would be a correct answer?  A
>> submodule is just a repository inside another repository, so that we could
>> have a big repo containing all projects, while all of them would remain to
>> be separate repos.
>> I don't know how well that plays with SourceForge, however.
> Sorry to come to this late in the day, but I don't see the point in having
> one-repo-to-rule-them-all _unless_ done via submodules -- the separation into 3
> different projects is quite correct IMO, as each part is clearly independently
> useful (or at least, such dependencies as exist are one-way only).
Hm, I'm not really sure.
If I'm not completely mistaken (and your linked examples doesn't 
indicate so) then a submodule is kind of a link to another git 
repository. So you have
- a 'toplevel' repository
- one or more accompanying repositories
- one or more submodules in the main repository
   that have the accompanying repos as their remote(s)

I'm somewhat reluctant to this overhead to keep everything in sync.
But I have to admit I don't have any practical experience with that.
And I haven't found a way so far (for myself) to cope with the growing 
number of repos that have to be kept in sync every day.

The dependencies between the parts is there only for contributors, but: 
Everybody who wants to contribute is responsible to contribute the 
relevant documentation for the contribution. And to compile the manuals 
one needs everything: The basic LaTeX stuff, musicexamples, and 
lilyglyphs. So if I want to contribute, I'd have to clone the repos, 
have to take care of not breaking anything with the remotes of the 
submodules. Maybe I'm wrong with that, but it somehow looks scary to me.
Users who only want to _use_ one or more of the parts will get archived 
'releases' anyway.

I'm commenting on the structure and relation of the parts in your other 
email.

Best
Urs
>
> If you want a nice example of submodules, you can see it here with LDC (a
> compiler for the D programming language based on the LLVM backend).  This
> project has the language runtime, standard library (Phobos) and test suite each
> as separate submodules.
> https://github.com/ldc-developers/ldc
>
> Since OLL is moving back to GitHub, that shouldn't be a problem.
>
> ------------------------------------------------------------------------------
> Own the Future-Intel® Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest.
> Compete for recognition, cash, and the chance to get your game
> on Steam. $5K grand prize plus 10 genre and skill prizes.
> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
> _______________________________________________
> openlilylib-user mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlilylib-user