[GH-ISSUE #570] How to specify variants (language, architecture, etc.) #1281

New Issue

GiteaMirror · 2026-04-16T10:39:10-05:00

GiteaMirror commented

2026-04-16 10:39:10 -05:00

Originally created by @thomedes on GitHub (Jun 2, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/570

It would be nice if there was a standard way to specify variants of the same thing.

Example, having:

FOO-spanish-i386 X.Y.Z
FOO-french-arm X.Y.Z

I'd like to be able to incorporate the different variants in the versioning string in a standard way.

Originally created by @thomedes on GitHub (Jun 2, 2020). Original GitHub issue: https://github.com/semver/semver/issues/570 It would be nice if there was a standard way to specify variants of the same thing. Example, having: - FOO-spanish-i386 X.Y.Z - FOO-french-arm X.Y.Z I'd like to be able to incorporate the different variants in the versioning string in a standard way.

GiteaMirror closed this issue

2026-04-16 10:39:11 -05:00

GiteaMirror commented

2026-04-16 10:39:12 -05:00

@ljharb commented on GitHub (Jun 2, 2020):

Different package names, or as a prerelease?

@ljharb commented on GitHub (Jun 2, 2020): Different package names, or as a prerelease?

GiteaMirror commented

2026-04-16 10:39:13 -05:00

@thomedes commented on GitHub (Jun 2, 2020):

Different package names. Now I see my mistake, I actually typed faster than I thought.

If you effectively make different variants of the same product, each having a set of keys/values that identifies them (like { "arch": "i386", "lang": "en_UK" } Then the version is just one more value to save in the set, like { "arch": "i386", "lang": "en_UK", "version": "X.Y.Z" }.

I would be wrong to store all that info in the version string.

It would be a different project to create a semantic product identifier string allowing a set of key/values to be specified in a formal way. Probably better to close this Issue.

@thomedes commented on GitHub (Jun 2, 2020): Different package names. Now I see my mistake, I actually typed faster than I thought. If you effectively make different variants of the same product, each having a set of keys/values that identifies them (like `{ "arch": "i386", "lang": "en_UK" }` Then the version is just one more value to save in the set, like `{ "arch": "i386", "lang": "en_UK", "version": "X.Y.Z" }`. I would be wrong to store all that info in the version string. It would be a different project to create a semantic product identifier string allowing a set of key/values to be specified in a formal way. Probably better to close this Issue.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#1281