5 ms·
How does it work if a single repository contains more than one independently usable library?
by howinteresting 4y ago
How does it work if a single repository contains more than one independently usable library?
- wnoise 4y agoWell, if they're actually independent, clearly those shouldn't be in the same repository...
- t0astbread 4y ago"Independently usable" does not have to mean "totally independent". The libraries could be related to the same product using the same infrastructure.
- howinteresting 4y agoThat doesn't follow. Why should they not be in the same repository? They may be related but independently usable.
- tricky777 4y agomono repo approach (or something to that direction)
- jrochkind1 4y agoDo people use a mono repo approach with different parts of the repo having different version numbers? The way I thought of it, the whole point of mono repo is not that.
- howinteresting 4y agoSometimes, yes. Monorepos use monolithic versioning internally, but they may use semantic versioning when publishing libraries.
- WorldMaker 4y agoTags in git allow just about the same naming options as branches, and "v" prefix is just a convention not a requirement. So rather than applying a tag v1.3.2 you could use a "folder structure" such as library1/v1.3.2 and library2/v3.1.2. Today I learned that you can use `git describe --match="library1/v*"` to get the version relative to just "library1" if you are versioning this way (in a monorepo, for instance).
- howinteresting 4y agoIt seems like what you describe is what golang supports: the folder structure in the tag name must match the folder structure in the repository. That's pretty cool.