Re: [Slackbuilds-users] What is the best way to add a tag to the version of a program?

Le 11/01/2018 à 00:12, Daniel Prosser a écrit : > 2. That said, sbotools should check the BUILD as well as the VERSION > when determining whether a package should be upgraded. I agree, and think that pretty much every tools do (or should do) the same, considering that a "well formed" Slackware

Re: [Slackbuilds-users] What is the best way to add a tag to the version of a program?

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

Re: [Slackbuilds-users] What is the best way to add a tag to the version of a program?

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

Re: [Slackbuilds-users] What is the best way to add a tag to the version of a program?

On 10/01/18 18:44, Fellype do Nascimento wrote: Hi all! At the moment I am the maintainer of sayonara-player.SlackBuild [1]. The version numbering structure of Sayonara Player (SP) is: x.y.z-gitX-MMDD where x=major release, y=minor release, z=bugfix release and gitX-MMDD = "small

[Slackbuilds-users] What is the best way to add a tag to the version of a program?

Hi all! At the moment I am the maintainer of sayonara-player.SlackBuild [1]. The version numbering structure of Sayonara Player (SP) is: x.y.z-gitX-MMDD where x=major release, y=minor release, z=bugfix release and gitX-MMDD = "small adjustments" release. Sometimes the SP developers

[Slackbuilds-users] Updates - 20180110.1

Hi We pushed this update sooner than the usual update schedule, mainly because of the whole Spectre/Meltdown issue and new intel-microcode is now included in this batch so please update as soon as possible. libupnp update seems to broke vlc but it got fixed in this batch as well. As in my

Re: [Slackbuilds-users] How best to contact Slackware devs?

On Tue, 9 Jan 2018, Jeremy Hansen wrote: I was able to build it after commenting out the patch in the SlackBuild and then switching the SSLTYPE from unix to unix.pwd Here's a patch for the 14.2 SlackBuild. You'll need to rename your alpine download to: alpine-f2246f7.tar.xz Jeremy, Thank

Re: [Slackbuilds-users] qemu-guest-agent not in pending nor ready queue

>> Hi, >> >> On 08/01/2018 I sent update for qemu-guest-agent. >> But as of now, it's not in pending nor ready queue. >> >> Has someone forgotten to push it further? ;-) >> > > https://git.slackbuilds.org/slackbuilds/commit/?id=684732b86 > > Thanks :-) Hi Andrzej, yes that was me, I forgot to

Re: [Slackbuilds-users] qemu-guest-agent not in pending nor ready queue

On 10/01/18 07:40, Andrzej Telszewski wrote: Hi, On 08/01/2018 I sent update for qemu-guest-agent. But as of now, it's not in pending nor ready queue. Has someone forgotten to push it further? ;-) https://git.slackbuilds.org/slackbuilds/commit/?id=684732b86 Thanks :-) -- Best regards,

Re: [Slackbuilds-users] vlc & libupnp (was: libass ABI changes)

On 07/01/18 03:22, Matteo Bernardini wrote: > 2018-01-06 18:15 GMT+01:00 Willy Sudiarto Raharjo : [snip] >> >>> vlc >> >> It failed to build, but i guess it's caused by newer libupnp >> https://pastebin.com/dq8CKh1n > > thanks Willy! > > I found that support for the