Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Universal Package Versioning
-
I like the setup of Universal Packages, however, the vendor installer packages I deal with (spread across .zip, .iso, .exe, and .msi) do not have friendly version names - certainly not semantic versioning.
Their software is typically in the format of this: 2024 SP3 R2 P1, where the base version would be something like 2024, and then as the software is changed, but no major version is released, the service pack, revision, and patch numbers increase. I could account for this if the semantic versioning allowed 4 segments, but it only allows two. Is there a better way to store their files than using Universal packages (I could use the Asset feed, but the Universal looked cleaner)?
I do like the Universal packages because I was going to bundle the PDFs with the installers.
-
hi @tyler_5201,
For a case like this, I'd recommend using a custom metadata field like
_vendorVersionor something like that? Of course, that's going to be relatively easy.The hart part is to "map" the vendor numbers to a SemVer. I would look at the data, and decide how you want to "pack" them into three segments.
2024.3.201might work, assuming there are less than 100 revisions per service pack. Or maybe2024.302.1. The number is really just for you, so whatever makes sense to you :)Cheers,
Alana
