Splitting|joining repositories

Discussion corner for Developers of Serendipity.
Post Reply
LazyBadger
Regular
Posts: 176
Joined: Mon Aug 25, 2008 12:25 pm
Location: Russia
Contact:

Splitting|joining repositories

Post by LazyBadger » Sat May 17, 2014 6:43 am

From translator's POV, current repos structure is rather far from ideal: I have to fork 2 full repositories (Serendipity + additional_plugins) in order to update translations inside lang\UTF-8 for core and <plugin>\UTF8 for plugins

Maybe with Git's submodules|subtrees|whatever it will be possible to build from only needed nodes additional repo, which will include transparently only translation-related parts of existing repositories?
Just sample tree from my local repo

Code: Select all

lang/UTF-8/serendipity_lang_ru.inc.php
plugins/serendipity_event_assigncategories/UTF-8/lang_ru.inc.php
plugins/serendipity_event_bbcode/UTF-8/lang_ru.inc.php
plugins/serendipity_event_emoticate/UTF-8/lang_ru.inc.php
plugins/serendipity_event_entryproperties/UTF-8/lang_ru.inc.php
plugins/serendipity_event_freetag/UTF-8/lang_ru.inc.php
plugins/serendipity_event_gravatar/UTF-8/lang_ru.inc.php
plugins/serendipity_event_karma/UTF-8/lang_ru.inc.php
plugins/serendipity_event_nl2br/UTF-8/lang_ru.inc.php
plugins/serendipity_event_relatedlinks/UTF-8/lang_ru.inc.php
plugins/serendipity_event_s9ymarkup/UTF-8/lang_ru.inc.php
plugins/serendipity_event_spamblock/UTF-8/lang_ru.inc.php
plugins/serendipity_plugin_shoutbox/UTF-8/lang_ru.inc.php
lang_*.inc.php must be, obviously, for all supported languages
Quis custodiet ipsos custodes?

User avatar
yellowled
Regular
Posts: 7056
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany
Contact:

Re: Splitting|joining repositories

Post by yellowled » Sat May 17, 2014 9:25 am

LazyBadger wrote:Maybe with Git's submodules|subtrees|whatever it will be possible to build from only needed nodes additional repo, which will include transparently only translation-related parts of existing repositories?
As for submodules, I don't think that's feasible. Submodules are rather prone to errors since you have to init, pull and push them seperately. As for subtrees, I don't see how translators would benefit from that. I think you'd still have to pull the full repository. Both techniques to me seem to be meant to include external repositories, not (necessarily) to modularize an existing repository?

That being said, I'm far from being a git expert, so if anyone sees the suggested benefit here, please elaborate. I'm all for making translations easier in s9y.

YL
amazon Wishlist - Serendipity-Podcast (German only, sorry)

Post Reply