[TYPO3-dev] local git mirror og TYPO3 core & submodules

[Adrien Crivelli]

Hi,

Doing something completely different I cam across "url.<base>.insteadOf"
git option. It seems it alows you to rewrite URL on the fly for push/pull.
It can be set globally for git, so it's easier to set up. Have a look at
the man page:
http://www.kernel.org/pub/software/scm/git/docs/git-config.html

It's actually used in the "how to contribute to
TYPO3<http://wiki.typo3.org/Contribution_Walkthrough_with_CommandLine>"
guide.

Again, good luck :)


On 9 August 2012 20:32, Lieuwe Hummel <l.hummel at drecomm.nl> wrote:

> Hi Adrien,
>
> Thanks for the clarification, but I think I stick to my workaround for
> now. It will work, but this is typically a thing forgotten very easily when
> introducing a new collegue / deploying a new test site / ...
> It can be scripted, but that still requires a trigger somehow, somewhere.
> Anyway, my solution is not perfect either :) Thanks for your thoughts
>
> Regards,
> Lieuwe
>
>
> On 09-08-2012 12:08, Adrien Crivelli wrote:
>
>> Hi,
>>
>> I feel I should emphasis that what i suggested, modifying .git/config (not
>> .gitmodules) will never be versionned. It is not a fork. It is a *local
>> configuration* which override suggested submodule URL found in
>> .gitmodules.
>> So you still have a *100% identical mirrors*. But the setup of your local
>> websites is more complex because you need to edit that file for
>> every website. I guess you could use some script to automate that. That
>> would probably be easy to do with *find* and *sed* commands.
>>
>> I am not saying that's a perfect solution (far from it), but it's
>> different
>> than directly modifying .gitmodules.
>>
>> Good luck anyway :)
>>
>> Adrien
>>
>>
>> On 9 August 2012 18:33, Lieuwe Hummel <l.hummel at drecomm.nl> wrote:
>>
>>  Hi Ernesto, Adrien,
>>>
>>> Thanks for your replies and information. I made a quick analysis of the
>>> proposed solution to change the .gitmodules. My thoughts are to change
>>> the
>>> .gitmodules file to reflect the repository location to our server, commit
>>> the change and to retreive the community changes with git pull --rebase.
>>> It does not feel right for me for a few reasons:
>>>   - first of all, it's not a 100% clone anymore
>>>   - we checkout a tag, which points to a commit without the change in
>>>     the .gitmodules file. It will not help us.
>>>   - We could merge the community changes, but that will definitely give
>>>     us conflicts somewhere in the future.
>>>
>>> Unless I'm missing something, I think it is not easy to set it up for
>>> many
>>> websites. For now, I'm thinking to mirror the TYPO3v4/Core.git repository
>>> and leave the core submodules pointing to git.typo3.org
>>> My main decission point is gained advantage <-> ease to use and maintain.
>>>
>>> Regards,
>>> Lieuwe
>>>
>> ______________________________**_________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-dev<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev>
>