I am creating an application that will work in two separate versions of the same software. These frameworks will have completely different modules with a common dependency on the JavaScript framework I created.
Let's say
dave/version1 dave/version2
What proportion depends on dependence with
dave/framework
I want to support this structure ( dave / framework ) in one repository, which may be required for both parent modules. However, the location where these frame files should be located differs slightly between the two modules, as well as slightly different requirements for the composer.json files so that everything moves correctly (the two versions of this software implement the composer differently).
With my limited knowledge of composer and Git, I formulated a couple of solutions:
Create three repositories, two wrapper repositories with specific composer.json files to support every other version of the software. With another dependency on the third repository, which contains the actual structure. I am not sure that this will work beyond theory. In addition, it eventually becomes a little dirty.
Use some form of smart labeling and have version 1 and version2, depending on individual versions of the framework, which, in turn, will have a slightly different make-up. The composer will then struggle with pulling out the latest version of the module, since we will be launching two very slightly different code bases in strange versions.
However, both of them seem to be a potentially erratic and incorrect way of structuring what I am trying to achieve.
Is there a good way to achieve this? or is it better for me to maintain two separate repositories for the framework?
source share