On 28/08/16 06:57, Fernando Lopez wrote:
had no issues making the package... had no issues running iperf 3.1.3 on
my slack current x64.
Thank you Fernando. I have one more problem with this package. The
developers keep on referring to the software on their project page as
iPerf3 (but in place
had no issues making the package... had no issues running iperf 3.1.3 on my
slack current x64.
On Sat, Aug 27, 2016 at 11:50 PM, Fernando Lopez wrote:
> lol i was on an android phone... didnt see the attachment... just got
> home... testing it... =)
>
> On Sat, Aug 27, 2016 at 8:45 PM, Willy Sud
lol i was on an android phone... didnt see the attachment... just got
home... testing it... =)
On Sat, Aug 27, 2016 at 8:45 PM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:
> > send them. ill test.
>
> >> Could I ask some kind souls here to test the iPerf3 scripts I've
> created,
> >
> send them. ill test.
>> Could I ask some kind souls here to test the iPerf3 scripts I've created,
> before uploading them to SBo, please.
I think what Sebastian meant was *before* he submit to SBo :)
he attached his SlackBuild script in his original email
--
Willy Sudiarto Raharjo
signatur
> Could admins please remove the following obsolete build scripts?
>
> network/node (replaced by development/nodejs)
It's now removed in my branch along with some scripts updated to reflect
this change.
If anyone have any objection, please let us soon before next public update.
--
Willy Sudia
It's been another busy week -- thanks to everybody who contributed!
Sat Aug 27 23:37:49 UTC 2016
academic/mendeleydesktop: Updated for version 1.16.2.
academic/scipy3: Added (python library).
academic/scipy: Updated for version 0.18.0.
academic/veusz: Updated for version 1.24.
accessibility/unclut
On 28.08.2016 00:53, Doogster wrote:
I would have suggested adding a KEEPASS_VERSION option to the plugin's
SlackBuild.
OK, but I don't see how this would solve the problem?
Short example:
Keepass v.2.30
Plugin: KeePassHttp v. 1.8.4.1
How would you name the compiled plugin p
On 27.08.2016 09:39, B Watson wrote:
On 8/26/16, Thomas Szteliga wrote:
they should be placed in:
/usr/lib/KeePass-${VERSION}/
And we can't really determine the version of Keepass
a user has installed in an extension SlackBuild, can we?
Never used KeePass, but to play the devil's advoc
On 27/08/16 04:20, Thomas Szteliga wrote:
My suggestion is to install KeePass in
/usr/lib/KeePass/
I would vote for this solution, which seems to be the rather standard
way here on SBo. So why brake it?
The user itself has to know that he might need to rebuild the plugins
after upgrad
I would have suggested adding a KEEPASS_VERSION option to the plugin's
SlackBuild.
On Sat, Aug 27, 2016 at 12:39 AM, B Watson wrote:
> On 8/26/16, Thomas Szteliga wrote:
>
>> they should be placed in:
>>
>> /usr/lib/KeePass-${VERSION}/
>>
>>
>> And we can't really determine the version of
Hi,
I've been trying to reach Nikos Giotis, the maintainer of qbs
SlackBuild, without success. (Well, I sent him an e-mail on Friday, but
the other one I sent him when we were switching from 14.1 to 14.2).
If you know that he's no longer active, I would happily take over the
maintenance of q
send them. ill test.
On Aug 27, 2016 12:20 PM, "Sebastian Arcus" wrote:
>
> Could I ask some kind souls here to test the iPerf3 scripts I've created,
before uploading them to SBo, please.
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slac
Could I ask some kind souls here to test the iPerf3 scripts I've
created, before uploading them to SBo, please.
iperf.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org
On 8/26/16, Thomas Szteliga wrote:
> they should be placed in:
>
> /usr/lib/KeePass-${VERSION}/
>
>
> And we can't really determine the version of Keepass
> a user has installed in an extension SlackBuild, can we?
Never used KeePass, but to play the devil's advocate...
Why not? There's su
14 matches
Mail list logo
