Since I see that @github.com is here (hi!), I'm going to ask a question about something that really bugs me about repositories and releases: Why isn't there a proper way to manage releases of multiple products that live under the same repository? (or if there is, why isn't that easily disvoerable?) - ThreadSky

About ThreadSky

konamiman.com • 79 days ago

Since I see that @github.com is here (hi!), I'm going to ask a question about something that really bugs me about repositories and releases:

Why isn't there a proper way to manage releases of multiple products that live under the same repository? (or if there is, why isn't that easily disvoerable?)

Comments

konamiman.com•79 days ago

Case in point: Nextor, my OS for MSX computers (https://github.com/Konamiman/Nextor). It has multiple components that can be summarized in:

- Kernel ROM files
- NEXTOR.SYS file
- Command line tools

I usually update only the kernel, being the others unchanged. But a new release is "all or nothing"...

konamiman.com•79 days ago

...so I either include the unchanged files in the release (ugly/confusing), or leave them out (unpractical). My workaround is to include "this release updates only the kernel, for the latest NEXTOR.SYS go to (link to past release)" as part of the release description. But this, again, is ugly.

konamiman.com•79 days ago

Splitting the code into different repositories wouldn't be practical either. All the components are heavily entwined, even if they end up in different binaries.

My suggestion is to offer multiple product releases in the same repository, e.g. as in this crude mockup:

konamiman.com•79 days ago

Lastly, another similar example: Nestor80, my Z80 assembler (https://github.com/Konamiman/Nestor80), which consists of three standalone tools: assembler, linker, and library manager.

And that's it. Thanks for listening!

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply