[Slackbuilds-users] What happened to libssh2?

[Duncan Roe]

xen lists libssh2 as an optional dependency, but I can't find it at SBo.

It was there on Nov 10  2016, that's when I last built it.

Did I miss an announcement?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] What happened to libssh2?

[Willy Sudiarto Raharjo]

> xen lists libssh2 as an optional dependency, but I can't find it at SBo.
> 
> It was there on Nov 10  2016, that's when I last built it.
> 
> Did I miss an announcement?

https://git.slackbuilds.org/slackbuilds/commit/?id=12dde3a325d5441a27dcd7ec48349d07af1073b0


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] What happened to libssh2?

[Duncan Roe]

xen lists libssh2 as an optional dependency, but I can't find it at SBo.

It was there on Nov 10  2016, that's when I last built it.

Did I miss an announcement?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170603.1

[David Spencer]

> Maybe it would make sense to have the git hook to extract the version from
> *.info?
>
> Then the whole "Updated for version X.X.X." message could be determined and
> generated automatically?

my own review script already generates the message and author this
way. But it generates the same message for build bumps where the
version hasn't changed, and unfortunately I don't always remember to
amend the message. Willy has saved me from this error multiple times
:)

The git hook could check the version in the message, also it would be
nice to check the category and prgnam, and check that no files outside
that directory are in the commit. Does anybody want to look at doing
that? plase :)

Thanks
-D.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170603.1

[Andrzej Telszewski]

On 03/06/17 19:58, Willy Sudiarto Raharjo wrote:

system/krusader: Updated for version 3.0.1.

Some error must have occurred ;-)
There's no krusader 3.0.1 yet ;-)

Yep, my bad
it was supposed to be system/image-analyzer


Maybe it would make sense to have the git hook to extract the version 
from *.info?


Then the whole "Updated for version X.X.X." message could be determined 
and generated automatically?


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] question about libjvm.so symlinks

[Sebastien BALLET]

Hello,

I know why this symlink is in place. However, there's no documentation
which
specifies this symlink is a *requirement*. There's no serious softwares
which requires
it, and there's no other linux distribution which has a jdk with that
symlink.

Therefore, there's no reason to have this symlink installed by default. It
would be better
and cleaner to add a note about the possible need for this link, or, to add
the line below
in openjdk.sh / jdk.sh (and to update openjdk.csh / jdk.csh the same way) :

  export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$JAVA_HOME/jre/lib/$LIB_
ARCH/server/libjvm.so"

-- 
SeB

2017-06-04 8:16 GMT+02:00 Harald Achitz :

> for that other programs can find libjvm.so in the library search path
> ./$PRGNAM/jre/lib/${LIB_ARCH}/server/
> is just some path only the program self knows
>
> $PKG/usr/lib${LIBDIRSUFFIX}
> is a path all other programs also know
>
> /Harald
>
>
>
>
> 2017-06-02 18:41 GMT+02:00 Sebastien BALLET :
>
>> Hello,
>>
>> I would like to know if there is any (documented) reasons why the
>> slackbuilds for (open)jdk create the symlinks below.
>>
>> jdk.SlackBuild:
>> cd $PKG/usr/lib${LIBDIRSUFFIX}
>> ln -sf ./java/jre/lib/${LIB_ARCH}/server/libjvm.so .
>>
>> openjdk.SlackBuild:
>> cd $PKG/usr/lib${LIBDIRSUFFIX}
>>  ln -sf ./$PRGNAM/jre/lib/${LIB_ARCH}/server/libjvm.so .
>>
>> I've search the web and didn't find anything conclusive about that. In
>> fact, it seems that symlink is not needed and is more a hack used to fix
>> some specific issues.
>>
>>
>> Thanks.
>>
>> --
>> SeB
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[David O'Shaughnessy]

On 06/04/2017 06:06 PM, Harald Achitz wrote:
> Thanks for the explanation, even if it makes me sad to hear that, in
> case of Qt, stability and predictability is not the primary concern of
> SBo.

I actually drew the opposite conclusion from Willy's post. For what it's
worth, I have not noticed any stability problems with the Qt 5 apps that
I run on Slack 14.2 (with Qt from SBo).

--
Dave
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[Willy Sudiarto Raharjo]

> what do you want to tell me?
> Ok, I was wrong, there was for some weeks a stable version of Qt on SBo,
> did not notice it because at this time I had already to use my own builds,
> why?
> the update to 5.6 was a half year late, and than instead of staying on the
> stable LTS version the jump to the next developer version was done.
> And instead of having a 3 years supporter Qt version in SBo, what would
> reduce the amount of work, now there is a version that is basically already
> eof .
> Calling this info bogus is as ignorant as putting some URLs up and ignore
> the info I provide and do so as everything is wonderful
> So what's the point in showing me the URLs and the version history of Qt in
> SBo, it just shows that it is totally wrong. Have self a look at it and
> understand why

Hi Harald,

Let me clarify a bit about the version history from GIT:

Qt 5.6 got released on March 2016 and 5.6.1 got released on June 2016.
During this period we had a submission freeze for SBo and we were
focused on testing all scripts in the repository. For a library such as
Qt which is used by many other projects, we prefer to wait until it
reached it's first point release (.1) because major release normally
breaks many things (removal of QWebKit in 5.6). That's why you see i
bumped Qt to 5.6.1 in June, 19 2016, 2 weeks after first point release.

Qt 5.7 was released in June, 16 2016, but as usual, we prefer to wait
for first point release, which was released in December 2016, so Larry
bumped to 5.7.1 in January (roughly 3 weeks from it's release date,
because we had to test other scripts first for about 1 week)

Now, the reason why Larry insist on staying at 5.7.x is because another
script (PyQt5) can't be bumped to higher version unless sip package in
Slackware got updated (which is not at this moment and it won't happen
in -stable since it will affect many other packages as well). I believe
it's reasonable and i can understand his opinion on this one. He is
willing to support newer Qt, but that is for next development cycle.

Bumping to 5.9 will surely break some scripts and some others may have
to be removed due to incompatibility with Qt 5.9. Not to mention the
efforts to make sure all scripts are compatible with the just-released
Qt 5.9. I would consider that (or Qt 5.10) for next development cycle :)

As for LTS, i can understand the benefit of a long term support, but
other than that, it's basically just a regular release. This is my
personal opinion, it doesn't reflect other admins opinions.

AlienBOB is *probably* looking at Qt 5.9 for his future KDE 5 / Plasma
releases.


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[Harald Achitz]

what do you want to tell me?
Ok, I was wrong, there was for some weeks a stable version of Qt on SBo,
did not notice it because at this time I had already to use my own builds,
why?
the update to 5.6 was a half year late, and than instead of staying on the
stable LTS version the jump to the next developer version was done.
And instead of having a 3 years supporter Qt version in SBo, what would
reduce the amount of work, now there is a version that is basically already
eof .
Calling this info bogus is as ignorant as putting some URLs up and ignore
the info I provide and do so as everything is wonderful
So what's the point in showing me the URLs and the version history of Qt in
SBo, it just shows that it is totally wrong. Have self a look at it and
understand why


2017-06-04 8:40 GMT+02:00 Didier Spaier :

> Le 04/06/2017 à 08:26, Matteo Bernardini a écrit :
> > 2017-06-04 8:13 GMT+02:00 Harald Achitz :
> >> thanks Larry that you self delivered the reason why the SBo version
> should
> >> have been, and should be, on the LTS Version 5.6x and not on some
> >> intermediate development release. The 5.6 never mad it into SBo, right?
> you
> >> missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
> >> expert version strategy!
> >> Of course, not understanding such small, but important features, like
> LTS
> >> support and the difference between LTS and the intermediate versions
> makes
> >> it easy to call information people provide to you bogus, but I
> understand
> >> that it helps to be ignorant when a certain knowledge is missing.
> >> Have a nice weekend!
> >
> > https://git.slackbuilds.org/slackbuilds/log/?qt=grep=libraries%2Fqt5
>
> See also:
> http://slackware.uk/salix/x86_64/14.2/source/l/qt5/
>
> Didier
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[Harald Achitz]

thanks, so there was for 3 month, until the ignored update to 5.6.2,  a not
outdated stable version available.
If you think that does make Qt from SBo more usable, I have to disagree.

2017-06-04 8:26 GMT+02:00 Matteo Bernardini :

> 2017-06-04 8:13 GMT+02:00 Harald Achitz :
> > thanks Larry that you self delivered the reason why the SBo version
> should
> > have been, and should be, on the LTS Version 5.6x and not on some
> > intermediate development release. The 5.6 never mad it into SBo, right?
> you
> > missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
> > expert version strategy!
> > Of course, not understanding such small, but important features, like LTS
> > support and the difference between LTS and the intermediate versions
> makes
> > it easy to call information people provide to you bogus, but I understand
> > that it helps to be ignorant when a certain knowledge is missing.
> > Have a nice weekend!
>
> https://git.slackbuilds.org/slackbuilds/log/?qt=grep=libraries%2Fqt5
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[Didier Spaier]

Le 04/06/2017 à 08:26, Matteo Bernardini a écrit :
> 2017-06-04 8:13 GMT+02:00 Harald Achitz :
>> thanks Larry that you self delivered the reason why the SBo version should
>> have been, and should be, on the LTS Version 5.6x and not on some
>> intermediate development release. The 5.6 never mad it into SBo, right? you
>> missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
>> expert version strategy!
>> Of course, not understanding such small, but important features, like LTS
>> support and the difference between LTS and the intermediate versions makes
>> it easy to call information people provide to you bogus, but I understand
>> that it helps to be ignorant when a certain knowledge is missing.
>> Have a nice weekend!
> 
> https://git.slackbuilds.org/slackbuilds/log/?qt=grep=libraries%2Fqt5

See also:
http://slackware.uk/salix/x86_64/14.2/source/l/qt5/

Didier


0x60C03EEA.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] question about libjvm.so symlinks

[Harald Achitz]

for that other programs can find libjvm.so in the library search path
./$PRGNAM/jre/lib/${LIB_ARCH}/server/
is just some path only the program self knows

$PKG/usr/lib${LIBDIRSUFFIX}
is a path all other programs also know

/Harald




2017-06-02 18:41 GMT+02:00 Sebastien BALLET :

> Hello,
>
> I would like to know if there is any (documented) reasons why the
> slackbuilds for (open)jdk create the symlinks below.
>
> jdk.SlackBuild:
> cd $PKG/usr/lib${LIBDIRSUFFIX}
> ln -sf ./java/jre/lib/${LIB_ARCH}/server/libjvm.so .
>
> openjdk.SlackBuild:
> cd $PKG/usr/lib${LIBDIRSUFFIX}
>  ln -sf ./$PRGNAM/jre/lib/${LIB_ARCH}/server/libjvm.so .
>
> I've search the web and didn't find anything conclusive about that. In
> fact, it seems that symlink is not needed and is more a hack used to fix
> some specific issues.
>
>
> Thanks.
>
> --
> SeB
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[Harald Achitz]

thanks Larry that you self delivered the reason why the SBo version should
have been, and should be, on the LTS Version 5.6x and not on some
intermediate development release. The 5.6 never mad it into SBo, right? you
missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
expert version strategy!
Of course, not understanding such small, but important features, like LTS
support and the difference between LTS and the intermediate versions makes
it easy to call information people provide to you bogus, but I understand
that it helps to be ignorant when a certain knowledge is missing.
Have a nice weekend!



2017-06-04 5:24 GMT+02:00 Larry Hajali :

>
> unfortunately I am not optimistic that soon for Qt, sbo will run a sane
 version politic,
 The current maintainer showed more or less that he/she does not care to
 much and/or does not understand why a LTS version strategy is the right
 thing for a distribution like Slackware.

>>> All I'll say about this is that the above is a bogus statement!
>
>
>> That will have to be decided by qt5 maintainer (Larry)
>>> My suggestion (suppose we bump to 5.9) is to place them on -review
>>> branch first and see if other scripts are working fine with it. If it
>>> turns out to be OK, we can then merge it into master and 14.2.
>>>
>> I don't plan on upgrading Qt5 past the 5.7.X branch for Slackware 14.2.
> I like to keep PyQt5 around the same version as Qt5.  Unfortunately, PyQt5
> 5.7.1 requires sip 4.19 or above.  I can look at upgrading for -current but
> I don't see it happening for 14.2.
>
>
>> based on rough count, we have more than 60 other scripts depending on
>>> qt5 for hard dep and probably more with optional dep. That will take
>>> some time to test.
>>>
>> This is true.  It takes a while to go through all the builds that depend
> on Qt5.
>
> --Larry
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/