On Wed, Jan 09, 2013 at 04:25:08PM -0200, Thiago Franco Moraes wrote:
> I was very busy working in InVesalius source code and solving other
> problems, so I wasn't working in packaging InVesalius. Now I'm on
> vacation and I think I can take some time to work in packaging :)
:-)
> On Mon, Dec 17, 2012 at 2:13 PM, Andreas Tille <andreas@an3as.eu> wrote:
> >> > Please also note that `dpkg --compare-versions` does consider 3.0.0.b3-1
> >> > larger than 3.0.0-1 - so uscan might fail identifying your real release
> >> > as a higher version than your beta release.
> >>
> >> I was reading [1] about this issue with version. So I'll need to use
> >> something like this as version to InVesalius: 2.99+3.0b3-0tfmoraes1?
> >> And I'll need to create a git tag with that version?
> >
> > Yes, this would be a possible solution. You could also simplify it by
> > using
> >
> > 3.0~b3-1
>
> As the name of invesalius repository is invesalius3, when I tag a
> version as "3.0~b3-1", the tarball created will be named
> invesalius3-3.0~b3-1. So I think I'll need to create manually a
> tarball named invesalius-3.0~b3-1, isn't it? Or there is a way to
> workaround it in github or in the watch file?
Well, you download the upstream tarball invesalius-<whatever_version>.tgz.
You rename it
mv invesalius-<whatever_version>.tgz invesalius3-3.0~b3-1
and you be done. Usually uscan even does the renaming (or symlinking)
for you.
> > which is also considered smaller than 3.0-1. This is a bit more
> > handsome for reading but finally it does not matter much as long as the
> > relation of the version numbers is correct. Whatever you decide you
> > need to use versionmangling in debian/watch file. Just tell me what
> > kind of version numbering you prefer and whether you need help in
> > adapting debian/watch (which is sometimes a bit tricky and some
> > experience is helpful in the beginning).
>
> I'll try by myself. Any help I need I write here.
Good luck
Andreas.
--
http://fam-tille.de