[Slackbuilds-users] What is the best way to add a tag to the version of a program?
Daniel Prosser
dpross1100 at msn.com
Wed Jan 10 23:12:54 UTC 2018
Fellype,
A couple comments here.
1. I agree with Andrzej that if you update your SlackBuild because of a
new version of the source code available, that should constitute a
change in the VERSION variable, not the BUILD. BUILD is more for
adjustments to the SlackBuild script itself (or other things unique to
SBo) for the same version of the source code. As Andrzej said, replacing
the dashes in the source version string with underscores is a typical
way to handle your situation.
2. That said, sbotools should check the BUILD as well as the VERSION
when determining whether a package should be upgraded. I recently went
through this with sboui, too. Perhaps an issue should be filed upstream
if sbotools does not do that.
Dan
On Wed, Jan 10, 2018 at 04:12:44PM -0200, Fellype do Nascimento wrote:
> On 01/10/2018 03:56 PM, Andrzej Telszewski wrote:
> >
> > I think your reasoning is not exactly correct, but the outcome result is
> > good ;-)
> >
> > What I mean is that BUILD should not mimic in any way the upstream
> > versioning schema.
> >
> > The only thing you have to change is that you cannot use "-" in version
> > string.
> > Common practice here is to replace it with "_" (underscore).
> > Then your SlackBuild should somehow deal with "_" is VERSION but with
> > "-" in source tarball name.
> >
> > Something like:
> > SRCVER=$(echo $VERSION | tr _ -)
> >
> >
> Hi Andrzej!
>
> Thank you for your tip. I got it.
>
> Best regards,
>
> Fellype
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
More information about the SlackBuilds-users
mailing list