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
> 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
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
> 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
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
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
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
> 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
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
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
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
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
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
13 matches
Mail list logo