On 09/05/18 00:12, Christoph Willing wrote:
In my case, I use git branches to accommodate the different SlackBuild
versions I want to maintain. Apart from the branches connected with
SlackBuilds for which I am the maintainer (therefore conforming strictly
to SBo conventions), I have a separate
On 08/05/18 05:53, or...@fredslev.dk wrote:
[snip]
> It would really mean a lot to me
> if this was applied to qt5 too so I that I didn't constantly have to
> edit the SlackBuild every time I update or rebuild qt5. Something which
> I routinely forget to do until the build fails...
>
Many
No problem. Thank you for testing. I will test on my VM and see if I can
replicate.
Thank you,
GenoBob
On Mon, May 7, 2018 at 7:08 PM, Daniel Prosser wrote:
> Bob,
>
> Thank you for helping me try to sort this out. I was able to use the
> upgrade dbs in
That assumption is irrelevant and if a maintainer is not willing to
respond to bug reports then it should be possible to implement fixes
without the maintainer.
The bottom line is that this patch would make the qt5.SlackBuild more
fail proof and the only reason to not accept it is to spite people
2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
> That assumption is irrelevant and if a maintainer is not willing to
> respond to bug reports then it should be possible to implement fixes
> without the maintainer.
>
> The bottom line is that this patch would make the