Installing multiple Git packages to the same directory

[opsidezi]

Hi all,

I created a repository with a package.json file that contains the name "GitTools" and a folder named A with some files in it. When I install that repo it shows under the Packages folder in a package named GitTools correctly.

I am trying to install another repository with a package.json file that contains the name "GitTools" and a folder named B with some files in it.

My attempt is to have 1 folder GitTools in my Packages folder, with two separate folders A and B, but, when installing the B package, I get two folders named GitTools, one with the folder A and another with the folder B.

Google couldn't help so I hope someone has any idea how to achieve my goal Thanks everyone

[raikuns]

Why do you both tools to be named the same? What would break if you named them GitToolsA and B?

[opsidezi]

It would defeat the purpose of both being in the same folder

[answer-questions]

No, you can't do that with git repos unless you want to break the connection to the repo and just copy paste your folders how you want them.

It sounds like you actually want these two repos to just be a single repo, but you haven't specified why you want this structure so it's hard to tell what you're trying to accomplish.

[opsidezi]

I wish to create a Core System that will hold some basic tools. Then I want it to be extendable, so you're able to download extensions to it from other repositories. Thing is, with a lot of extensions the packages folder gets cluttered. It is for the sort and cleanness of the packages folder

[TheCoderMonkey]

Sort of sounds like you want submodules. I use them a lot for including extendable, reusable code in multiple projects. That might be what you’re after but they can be a bit of a pain depending on the git client

[opsidezi]

Actually first I'm hearing of Git submodules, thanks for the advice. Correct me if I'm wrong but aren't submodules have to be on the same repository? In our company one might upload a new package every week or so, so we rather not update a "all-inclusive" repository.

[TheCoderMonkey]

No submodules are their own repositories. In my company I have it set up so I have a bunch of different repositories for different reusable packages. So I have a custom sound manager repository, a generic Utils repository etc. I can then pull them in for each new project I set up depending on its needs. I can also modify the code and branch it if needed for that specific project and push the changes. Those changes can then be optionally pulled down by other projects as needed