Split addons into separate repos per project

[marmarek]

Reported by joanna on 5 Nov 2012 14:48 UTC
It is really inconvenient to trace the devel histroy of those (independent) components using one git repo...

Migrated-From: https://wiki.qubes-os.org/ticket/670

[marmarek]

Comment by marmarek on 8 Nov 2012 00:46 UTC
What name scheme choose? "addons-thunderbird-qubes" or plain "thunderbird-qubes"?

[marmarek]

Comment by marmarek on 8 Nov 2012 00:46 UTC
What name scheme choose? "addons-thunderbird-qubes" or plain "thunderbird-qubes"?

[marmarek]

Comment by joanna on 8 Nov 2012 10:51 UTC
I think without addons prefix.

But one more option to consider is to keep the addons repo, only move each addon project into a git submodule:

http://git-scm.com/book/en/Git-Tools-Submodules

This way can track individual devel history of each addon in a separate git submodule (so, not intermixed with other addon projects). But still we must commit the changes in each of the submodules into the main addons repo, at least something like "qubes-tor: vXXX".

So, perhaps we shall just have 3 separate repos?

[marmarek]

Comment by joanna on 8 Nov 2012 10:51 UTC
I think without addons prefix.

But one more option to consider is to keep the addons repo, only move each addon project into a git submodule:

http://git-scm.com/book/en/Git-Tools-Submodules

This way can track individual devel history of each addon in a separate git submodule (so, not intermixed with other addon projects). But still we must commit the changes in each of the submodules into the main addons repo, at least something like "qubes-tor: vXXX".

So, perhaps we shall just have 3 separate repos?

[marmarek]

Comment by marmarek on 9 Nov 2012 04:25 UTC
In current layout you can still get log for just one component:

cd gpg-split
git log .

But separate repos will be more obvious. Use of git submodule IMHO doesn't make sense here - it is designed to integrate external upstream into project - to track both upstream and local changes.

Will done it as separate repos.

[marmarek]

Comment by marmarek on 9 Nov 2012 04:25 UTC
In current layout you can still get log for just one component:

cd gpg-split
git log .

But separate repos will be more obvious. Use of git submodule IMHO doesn't make sense here - it is designed to integrate external upstream into project - to track both upstream and local changes.

Will done it as separate repos.

[marmarek]

Comment by marmarek on 9 Nov 2012 05:31 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/qubes-builder.git;a=commit;h=ae3949d8547a47956443d736eaedfb165b02946f

And new repositories: gpg-split, qubes-tor, thunderbird-qubes

[marmarek]

Comment by marmarek on 9 Nov 2012 05:31 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/qubes-builder.git;a=commit;h=ae3949d8547a47956443d736eaedfb165b02946f

And new repositories: gpg-split, qubes-tor, thunderbird-qubes