threads / discuss / 39700

Dependency Management

Subject: Dependency Management

## tl;dr

4 messages between Jun 23, 2015 and Jun 25, 2015.

replies: 3people: 4as markdown or json

Jean Audibert· Jun 23, 2015, 08:52 UTC · lore

Hi,

Sorry to bother you with this question but I can't find any "official" answer or "strong opinion" from Git community.

In my company we recently started to use Git and we wonder how to share code and manage dependencies with Git? Use case: in project P we need to include lib-a and lib-b (libraries shared by several projects)

In your opinion, what is the "future proof" solution?
* Use submodule
* Use subtree

We know there is lot of PRO/CONS but I feel that subtree is "behind" in the race and the latest version of submodule work fine

Suggestions are very welcome. Thanks in advance,

Jean Audibert

_________________________________________________________________

This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of Euronext N.V. or any of its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

Stefan Beller· Jun 23, 2015, 17:34 UTC · re: Jean Audibert · lore

Re: Dependency Management

On Tue, Jun 23, 2015 at 1:52 AM, Jean Audibert <jaudibert@euronext.com> wrote:

Show 12 quoted lines

> Hi,
>
> Sorry to bother you with this question but I can't find any "official" answer or "strong opinion" from Git community.
>
> In my company we recently started to use Git and we wonder how to share code and manage dependencies with Git?
> Use case: in project P we need to include lib-a and lib-b (libraries shared by several projects)
>
> In your opinion, what is the "future proof" solution?
> * Use submodule
> * Use subtree
>
> We know there is lot of PRO/CONS but I feel that subtree is "behind" in the race and the latest version of submodule work fine

Use whatever works fine for your use case.

My personal opinion/expectation is to see submodules improving/advancing more than subtrees advancing in the near future. Though this is neither the official nor a strong opinion.

Stefan

Show 15 quoted lines

>
> Suggestions are very welcome.
> Thanks in advance,
>
> Jean Audibert
>
>
> _________________________________________________________________
>
> This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of Euronext N.V. or any of its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Josh Hagins· Jun 23, 2015, 18:49 UTC · re: Stefan Beller · lore

Re: Dependency Management

If neither git-submodule nor git-subtree is palatable to you, here are a couple of alternatives you might try:

  * https://github.com/ingydotnet/git-subrepo
  * https://github.com/tdd/git-stree

On Tue, Jun 23, 2015 at 1:36 PM Stefan Beller <sbeller@google.com> wrote:

Show 42 quoted lines

>
> On Tue, Jun 23, 2015 at 1:52 AM, Jean Audibert <jaudibert@euronext.com> wrote:
> > Hi,
> >
> > Sorry to bother you with this question but I can't find any "official" answer or "strong opinion" from Git community.
> >
> > In my company we recently started to use Git and we wonder how to share code and manage dependencies with Git?
> > Use case: in project P we need to include lib-a and lib-b (libraries shared by several projects)
> >
> > In your opinion, what is the "future proof" solution?
> > * Use submodule
> > * Use subtree
> >
> > We know there is lot of PRO/CONS but I feel that subtree is "behind" in the race and the latest version of submodule work fine
>
> Use whatever works fine for your use case.
>
> My personal opinion/expectation is to see submodules
> improving/advancing more than subtrees advancing in the near future.
> Though this is neither the official nor a strong opinion.
>
> Stefan
>
> >
> > Suggestions are very welcome.
> > Thanks in advance,
> >
> > Jean Audibert
> >
> >
> > _________________________________________________________________
> >
> > This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of Euronext N.V. or any of its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe git" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Luke Diamand· Jun 25, 2015, 09:00 UTC · re: Josh Hagins · lore

Re: Dependency Management

On 23/06/15 19:49, Josh Hagins wrote:

Show 5 quoted lines

> If neither git-submodule nor git-subtree is palatable to you, here are
> a couple of alternatives you might try:
>
>    * https://github.com/ingydotnet/git-subrepo
>    * https://github.com/tdd/git-stree

You could also use Android's "repo" tool:

https://code.google.com/p/git-repo/

Luke

Show 31 quoted lines

>
> On Tue, Jun 23, 2015 at 1:36 PM Stefan Beller <sbeller@google.com> wrote:
>>
>> On Tue, Jun 23, 2015 at 1:52 AM, Jean Audibert <jaudibert@euronext.com> wrote:
>>> Hi,
>>>
>>> Sorry to bother you with this question but I can't find any "official" answer or "strong opinion" from Git community.
>>>
>>> In my company we recently started to use Git and we wonder how to share code and manage dependencies with Git?
>>> Use case: in project P we need to include lib-a and lib-b (libraries shared by several projects)
>>>
>>> In your opinion, what is the "future proof" solution?
>>> * Use submodule
>>> * Use subtree
>>>
>>> We know there is lot of PRO/CONS but I feel that subtree is "behind" in the race and the latest version of submodule work fine
>>
>> Use whatever works fine for your use case.
>>
>> My personal opinion/expectation is to see submodules
>> improving/advancing more than subtrees advancing in the near future.
>> Though this is neither the official nor a strong opinion.
>>
>> Stefan
>>
>>>
>>> Suggestions are very welcome.
>>> Thanks in advance,
>>>
>>> Jean Audibert
>>>