On Wed, Nov 11, 2020 at 4:30 PM Bruno Wolff III <br...@wolff.to> wrote:
>
> I looked at
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/
> and didn't see dashes specifically covered.
>
> In my case, squashfs-tools has a new upstream release tagged 4.4-git.1 .
> I'm guessing that using 4.4-git.1 as the version would be at least
> confusing and might be prohibitted. Should I do that?
>
> If not, should I replace the - with a . in the version or should I move
> git.1 into the release. This is the first tag using this naming pattern, so
> I don't know the next tag will sort properly if I keep it in the version.
Dashes are invalid in both Version and Release tags. RPM will not even
parse your .spec file if either of them contains one.
I would say the way to deal with this depends on what upstream wants
to convey with this confusing versioning scheme:
- the -git.1 is information that is irrelevant to end-users (and there
won't be -git.2, -git.3 releases): drop it from Version and Release
entirely
- this is a 4.4 pre-release (expecting that a there will be 4.4 at
some point): then use something like Version: 4.4, Release:
0.git.1%{?dist}, which will make "proper" 4.4 releases sort higher
than this one
- this is a 4.4 stable release with a weird name: then use something
like Version 4.4.git.1, Release: 1%{?dist}, which will also preserve
ordering for eventual git.2, git.3, etc. updates
Fabio
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
