Re: [Slackbuilds-users] Package as a whole or in different parts

2018-01-30 Thread Jeremy Hansen 
On Tue, Jan 30, 2018, 1:43 PM B Watson  wrote:

> On 1/30/18, Xavier Maillard  wrote:
>
> > As I do not want to go the wrong way and I want to stick with the
> > KISS philosophy, I am just asking here: how would you package this
> > ? As a whole sat SBo build script, as 2 SBo (one for the backend
> > and one for the frontends), as many different SBo scripts (one for
> > the backend and one per frontend) ?
>
> Does the source for all of the above come as a single tarball?
>
> If so, I might do a single SlackBuild, that builds the backend and
> all the frontends by default, with environment variables to disable
> parts of it.
>
> Example: the transmission SlackBuild. I maintain that one, though I
> didn't write it from scratch (took it over from previous maintainer a
> while back).
>
> If the sources ship separately, it makes more sense to do separate builds
> for the different parts.
>

I do a similar thing for mediainfo. It is the same source for both the CLI
and GUI versions, so I have the CLI enabled by default (but can be disabled
if desired) and the GUI optional by passing GUI=yes.

Jeremy

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

Re: [Slackbuilds-users] Package as a whole or in different parts

2018-01-30 Thread B Watson 
On 1/30/18, Xavier Maillard  wrote:

> As I do not want to go the wrong way and I want to stick with the
> KISS philosophy, I am just asking here: how would you package this
> ? As a whole sat SBo build script, as 2 SBo (one for the backend
> and one for the frontends), as many different SBo scripts (one for
> the backend and one per frontend) ?

Does the source for all of the above come as a single tarball?

If so, I might do a single SlackBuild, that builds the backend and
all the frontends by default, with environment variables to disable
parts of it.

Example: the transmission SlackBuild. I maintain that one, though I
didn't write it from scratch (took it over from previous maintainer a
while back).

If the sources ship separately, it makes more sense to do separate builds
for the different parts.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Package as a whole or in different parts

2018-01-30 Thread Xavier Maillard 

Hello,

I am willing to submit a new SBo for a project I am supporting and 
I have a few questions.

The project is SaT -i.e. Salut a Toi, an XMPP client.

It comes with a daemon, sat (the backend) and a few frontend 
clients (primitivus, jp, etc.)


As I do not want to go the wrong way and I want to stick with the 
KISS philosophy, I am just asking here: how would you package this 
? As a whole sat SBo build script, as 2 SBo (one for the backend 
and one for the frontends), as many different SBo scripts (one for 
the backend and one per frontend) ?


What's your opinion on this ?

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

[Slackbuilds-users] Fwd: Rstudio 0.98 no longer runs/compiles on Slackware current

2018-01-30 Thread rob van nues 


- Forwarded Message -
From: "rob van nues" 
To: "michael stewart" 
Sent: Saturday, 6 May, 2017 12:34:45 PM
Subject: Rstudio 0.98 no longer runs/compiles on Slackware current

Hi Michael,

Since the recent upgrade of boost, Rstudio 0.98 on SBo won't run:

"bash-4.4$ rstudio
rstudio: error while loading shared libraries: libboost_date_time.so.1.61.0: 
cannot open shared object file: No such file or directory
"

nor compile. Maybe the latter is due to gcc 7 or other dependencies (please see 
below remarks on LQ)

https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page38.html#post5706804

I myself am not using R or R-studio at the moment (but have had some tutorials 
in the past on R and still keep it in case I'll need to use it again).

Cheers,


Rob

- Forwarded Message -
From: "LinuxQuestions.org" 
To: rvn...@tesco.net
Sent: Saturday, 6 May, 2017 10:19:20 AM
Subject: Reply to thread 'SBo scripts not building on current (read 1st post, 
pls)'

Dear brobr,

ponce has just replied to a thread you have subscribed to entitled - SBo 
scripts not building on current (read 1st post, pls) - in the Slackware forum 
of LinuxQuestions.org.

This thread is located at:
http://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999-new/

Here is the message that has just been posted:
***
rstudio-desktop script will need a little refactoring to work with the new 
1.0.143 version (there will also be additional dependencies, like qt5-webki
***


There may also be other replies, but you will not receive any more 
notifications until you visit the forum again.

All the best,
LinuxQuestions.org

~
Unsubscription information:

To unsubscribe from this thread, please visit this page:
http://www.linuxquestions.org/questions/subscription.php?do=removesubscription=thread=2475606=3b499537cfbf333cb6c497c27cd53a3f

To unsubscribe from ALL threads, please visit this page:
http://www.linuxquestions.org/questions/subscription.php?do=viewsubscription=all
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Postfx version 3.2.5 is available

2018-01-30 Thread Konrad J Hambrick 
Mario --

Saw on LQ that postfix version 3.2.5 is now available.

Builds and installs and runs fine on Slackware64 14.2 with 'the usual'
changes.

new DOWNLOAD="
http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.2.5.tar.gz
"

new MD5SUM="d32f51b7178b12a87f2ac249e376ad38"

MD5SUM was set after checking Weitse's PGP Key at:
http://cdn.postfix.johnriley.me/mirrors/postfix-release/wietse.pgp

Thanks for the SlackBuild !

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

[Slackbuilds-users] DOWNLOAD= in Several Flask-* SlackBuilds

2018-01-30 Thread Konrad J Hambrick 
Mikos --

I stumbled over the DOWNLOAD= Lines in the following SlackBuilds when I
tried to `wget` the quoted URLs:


   python/Flask-Principal/Flask-Principal.info
   python/Flask-WTF/Flask-WTF.info
   python/Flask-Mail/Flask-Mail.info
   python/Flask-HTMLmin/Flask-HTMLmin.info

Note that each of the URL's includes a trailing '#md5=' string inside
the double-quoted DOWNLOAD= Value.

Also note that I only downloaded what I needed to build pgadmin4 so I
didn't look at all of the Flask-* SlackBuilds.

Maybe this is OK ?

Thanks for all the SlackBuilds and all your effort !

-- kjh

attached: diff -Naur listing createc vis:

# for i in `find python -type f -iname "*~01*"`; do j="$(echo $i |sed -e
's/~01//')"; diff -Naur $i $j; done
--- python/Flask-Principal/Flask-Principal~01.info  2017-03-04 
23:29:58.636277473 -0600
+++ python/Flask-Principal/Flask-Principal.info 2018-01-29 10:57:56.054321426 
-0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-Principal"
 VERSION="0.4.0"
 HOMEPAGE="http://packages.python.org/Flask-Principal/;
-DOWNLOAD="https://pypi.python.org/packages/14/c7/2531aca6ab7baa3774fde2dfc9c9dd6d5a42576a1013a93701bfdc402fdd/Flask-Principal-0.4.0.tar.gz#md5=462d1345c9ddaddbec33a743e5821e2c;
+DOWNLOAD="https://pypi.python.org/packages/14/c7/2531aca6ab7baa3774fde2dfc9c9dd6d5a42576a1013a93701bfdc402fdd/Flask-Principal-0.4.0.tar.gz;
 MD5SUM="462d1345c9ddaddbec33a743e5821e2c"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
--- python/Flask-WTF/Flask-WTF~01.info  2017-03-04 23:29:58.636277473 -0600
+++ python/Flask-WTF/Flask-WTF.info 2018-01-29 11:03:22.375303924 -0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-WTF"
 VERSION="0.14.2"
 HOMEPAGE="https://github.com/lepture/flask-wtf;
-DOWNLOAD="https://pypi.python.org/packages/ba/15/00a9693180f214225a2c0b1bb9077f3b0b21f2e86522cbba22e8ad6e570c/Flask-WTF-0.14.2.tar.gz#md5=586f50f233926cade42e3d744aca3e8f;
+DOWNLOAD="https://pypi.python.org/packages/ba/15/00a9693180f214225a2c0b1bb9077f3b0b21f2e86522cbba22e8ad6e570c/Flask-WTF-0.14.2.tar.gz;
 MD5SUM="586f50f233926cade42e3d744aca3e8f"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
--- python/Flask-Mail/Flask-Mail~01.info2017-03-04 23:29:58.636277473 
-0600
+++ python/Flask-Mail/Flask-Mail.info   2018-01-29 10:49:45.490347738 -0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-Mail"
 VERSION="0.9.1"
 HOMEPAGE="https://github.com/rduplain/flask-mail;
-DOWNLOAD="https://pypi.python.org/packages/05/2f/6a545452040c2556559779db87148d2a85e78a26f90326647b51dc5e81e9/Flask-Mail-0.9.1.tar.gz#md5=04b35a42a44ec7aa724ec8ce55e2e08e;
+DOWNLOAD="https://pypi.python.org/packages/05/2f/6a545452040c2556559779db87148d2a85e78a26f90326647b51dc5e81e9/Flask-Mail-0.9.1.tar.gz;
 MD5SUM="04b35a42a44ec7aa724ec8ce55e2e08e"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
--- python/Flask-HTMLmin/Flask-HTMLmin~01.info  2017-03-10 18:54:50.378873556 
-0600
+++ python/Flask-HTMLmin/Flask-HTMLmin.info 2018-01-29 13:25:19.773847082 
-0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-HTMLmin"
 VERSION="1.2"
 HOMEPAGE="https://github.com/hamidfzm/Flask-HTMLmin;
-DOWNLOAD="https://pypi.python.org/packages/dd/2e/9f2d797d2ac59549fb3f493ab4716f2dbe538802d2c172fcc6f39eb079bf/Flask-HTMLmin-1.2.tar.gz#md5=c50ea7b1fcb6eae4b44e96d00671e2ea;
+DOWNLOAD="https://pypi.python.org/packages/dd/2e/9f2d797d2ac59549fb3f493ab4716f2dbe538802d2c172fcc6f39eb079bf/Flask-HTMLmin-1.2.tar.gz;
 MD5SUM="c50ea7b1fcb6eae4b44e96d00671e2ea"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] KeePass-2.38 installed in wrong directory

2018-01-30 Thread Shrivats 
Heh, I thought that was fixed a while ago. Anyway, I'll take a look at it
tonight

Thanks for letting be know!

On Jan 30, 2018 11:31, "Thomas Szteliga"  wrote:

> Hello,
>
> is there a real reason why KeePass-2.38 is being installed
> in /usr/lib/KeePass-2.38  and not in /usr/lib/KeePass?
>
> AFAIR few months ago I've submitted a patch and this was corrected,
> but now I see KeePass is again installed in /usr/lib/KeePass-${VERSION}.
>
> IMHO this is wrong, because this makes it harder to create packages
> for KeePass plugins, like KeePassHttp, every time KeePass gets an update,
> the plugin Slackbuilds need to be upgraded too, even if the plugin
> was not changed. Plugins are compatible from one version to another,
> and they are "recompiled" (by KeePass) at runtime.
>
> I don't see any other program in /usr/lib/ which is installed
> to /usr/lib/${PRGNAM}-${VERSION}, all go to /usr/lib/${PRGNAM}.
>
>
> Can we maybe fix this once and for all? ;-)
>
>
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/20
> 16-August/016939.html
>
>
> --
> Thomas Szteliga
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://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
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] KeePass-2.38 installed in wrong directory

2018-01-30 Thread Thomas Szteliga 

Hello,

is there a real reason why KeePass-2.38 is being installed
in /usr/lib/KeePass-2.38  and not in /usr/lib/KeePass?

AFAIR few months ago I've submitted a patch and this was corrected,
but now I see KeePass is again installed in /usr/lib/KeePass-${VERSION}.

IMHO this is wrong, because this makes it harder to create packages
for KeePass plugins, like KeePassHttp, every time KeePass gets an update,
the plugin Slackbuilds need to be upgraded too, even if the plugin
was not changed. Plugins are compatible from one version to another,
and they are "recompiled" (by KeePass) at runtime.

I don't see any other program in /usr/lib/ which is installed
to /usr/lib/${PRGNAM}-${VERSION}, all go to /usr/lib/${PRGNAM}.


Can we maybe fix this once and for all? ;-)


https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-August/016939.html


--
Thomas Szteliga

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