Is one package pr. repo an absolute requirement?
Per Olesen
I am trying to figure out if composer, or composer in combination with satis, can help me in my use case.
I have a couple of php projects, between which I would like to share code using composer. The code I want to share would be in a fairly fine-grained fashion, like 1-2 files/classes pr. library. Hence, I would end up with lots of small components/libs, that I would like to export.
Do I really need to create a vcs repo for each small library?
I have come to the conclusion, that I can only have one composer.json pr. library I want to publish. I know satis can help me publish them all in one composer repository, but I would still need to have one vcs repo for each library defined in satis config then.
I seem to be unable to have satis "scan" a repo for composer.json's - it will only look into the root of the tree. I have tried forcing satis, by explicitly defining them as type package with a source to the repo, but to no help.
And I am pretty sure I can't specify more than one library in one composer.json, right?
It also seems, that composer understands "everything in the repo" as the content of the library. So, a vcs repo, where thecomposer.json must reside in top-level dir, can also only contain code for the lib, because I will get all there when installing it.
Am I correct in my understanding of the above? Maybe it just doesn't support my use case here?