----- Original Message -----
From: "Pavel Valena" <pvalena(a)redhat.com>
To: "Vít Ondruch" <vondruch(a)redhat.com>
Cc: "Ruby SIG mailing list" <ruby-sig(a)lists.fedoraproject.org>
Sent: Tuesday, December 6, 2016 1:12:05 PM
Subject: Re: Packaging pre-release version
> ----- Original Message -----
> > From: "Vít Ondruch" <vondruch(a)redhat.com>
> > To: "Ruby SIG mailing list" <ruby-sig(a)lists.fedoraproject.org>
> > Sent: Tuesday, December 6, 2016 10:45:01 AM
> > Subject: Packaging pre-release version
> >
> > Hi all,
> >
> > I am working on rubygem-asciidoctor-mallard review [1] and since there
> > was not released stable version yet, the pre-release version (actually
> > git snapshot) needs to be packaged. And now I realized it is more PITA
> > then it should be.
> >
> > The main issue is with the way, how pre-release packages are versioned.
> > E.g. in rubygem-asciidoctor-mallard case, the upstream version is
> > "0.1.0.dev" which transforms in Fedora into "0.1.0-0.1.dev"
and
> > subsequently, no standard macro works.
I wonder what would happen when you try to `dnf update` from 0.1.0.dev to
0.1.0? Will it behave correctly?
Additionally, like you said, the correct version in fedora is
'0.1.0-0.1.dev'[1], to which you will not conform to, or is there something
that I missed?
Sorry, please disregard the questions, as I have after an offline inquiry realized that
only macros for rubygems are to be changed, and not the package version itself.
Pavel Valena
Associate Software Engineer
Brno, Czech Republic
RED HAT | TRIED. TESTED. TRUSTED.
All of the airlines in the Fortune Global 500 rely on Red Hat.
Find out why at Trusted | Red Hat
<
http://www.redhat.com/en/about/trusted>