[Slackbuilds-users] aris: new maintainer

Dear admins After an email exchange with Juan M. Lasca, I agree to give the maintainership of the aris Slackbuild back to him. As you can see, he is the original author of the script. Thanks Philip ___ SlackBuilds-users mailing list

[Slackbuilds-users] Dropping system/srm ?

Hi I'm currently the maintainer of the system/srm SlackBuild. I wonder if dropping it from the 15.0 repo altogether might be a good idea. It doesn't support most journaled file systems, for example, and is unmaintained since 2015. What do you suggest? Anyone still using it? Cheers, Philip

[Slackbuilds-users] patch: coriander

der/coriander.SlackBuild 2022-02-06 18:08:52.0 +0100 +++ b/multimedia/coriander/coriander.SlackBuild 2022-02-07 13:31:01.879304969 +0100 @@ -2,7 +2,7 @@ # Slackware build script for coriander -# Copyright 2015-2021 Philip Lacroix +# Copyright 2015-2022 Philip Lacroix # All rig

Re: [Slackbuilds-users] Unmaintained builds - want any of these?

Am 11.02.2020 15:50 schrieb mab974: Selon B Watson : These 2 belong to Petar Petrov: desktop/xfce4-cpufreq-plugin I will take this one if it is stille available. Petar is the new maintainer. Philip ___ SlackBuilds-users mailing list

Re: [Slackbuilds-users] Unmaintained builds - want any of these?

I'd take these as well: graphics/entangle graphics/plotutils MAINTAINER="Philip Lacroix" EMAIL="slackph at posteo dot de" Philip ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.

Re: [Slackbuilds-users] Unmaintained builds - want any of these?

Hi Robby, I'd be glad to take these, if they are still available: academic/aris academic/geomview MAINTAINER="Philip Lacroix" EMAIL="slackph at posteo dot de" Thanks, Philip Am 02.01.2020 09:41 schrieb Robby Workman: Hello all, TL;DR version: if you would like to se

Re: [Slackbuilds-users] Bottle slackbuild

Hi All A few days ago I received an e-mail (off list) with the above title, but I inadvertently deleted it along with spam before reading it. Whoever wrote the original e-mail is invited to send it to me once again. Sorry for the inconvenience. Cheers Philip

Re: [Slackbuilds-users] templates and guidelines

Am 29.05.2017 19:28 schrieb Petar Petrov: How about guidelines about package file install locations? (...) for example: - when is it advisable to install things to /opt Am 30.05.2017 18:56 schrieb B Watson: Guidelines about file locations: I'd say you should only use /opt when your build is

Re: [Slackbuilds-users] zyGrib source code link

Am 30.05.2017 02:47 schrieb Willy Sudiarto Raharjo: Done Thanks, Willy! ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives -

[Slackbuilds-users] zyGrib source code link

Greetings I'm updating the SlackBuild for zyGrib, which is now at release 8.0.1. The PHP script on the official website doesn't seem to be allowing automated downloads (as with wget), hence I was considering to point the .info file to one of the Gentoo mirrors: they do provide a completely

Re: [Slackbuilds-users] Only 68 builds left!

Am 24.03.2017 20:09 schrieb Ryan P.C. McQuen: B. Watson was nice enough to compile this list of my builds that are remaining with their subsequent READMEs and dependencies (REQUIRES): http://urchlay.naptime.net/~urchlay/src/ryanbuilds.txt Hi Ryan Thanks for your great contribution to SBo.

Re: [Slackbuilds-users] Scripts For Grab

Am 15.02.2017 02:20 schrieb Willy Sudiarto Raharjo: gis/routino I'll take routino, if no one else wants it. Thanks Philip ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] Glances 2.8

Am 21.01.2017 19:09 schrieb Nicolas Kovacs: Hi everybody, In the wake of the discussion about package updates, I thought I might give you a little heads-up. SBo is currently providing Glances 2.5.1. Version 2.8 has just been released by Nicolas Hennion. I gave it a spin, and it builds fine

Re: [Slackbuilds-users] DOWNLOAD advice for github

Am 14.05.2016 18:35 schrieb David Spencer: So, here's the new advice: Heinz has worked out that if we use (for example) DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz; then the archive will *always* be named clyrics-0.04.tar.gz, even if we use wget or curl, and

Re: [Slackbuilds-users] package for grab: sage

more tests): #---# #!/bin/sh # Slackware build script for sage # Originally written by Jack Maddox <j...@auburn.edu> # Currently maintained by Willy Sudiarto Raharjo <will...@slackbuilds.org> # # (03.2016) Reviewed and updated by Philip Lacroix <s

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

A short follow-up. A non-invasive python3-pillow Slackbuild is now available as a complement to python-pillow. Thanks to all who answered to my post for your valuable input. Philip ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

ust work" after 14.2 is released, unless Patrick is suddenly going to move 14.2 to python3 and change his python-pillow. -D. On 15 December 2015 at 13:12, Philip Lacroix <slac...@posteo.de> wrote: Am 14.12.2015 23:19 schrieb B Watson: What happens if someone needs both python 2 and 3

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

Am 15.12.2015 18:29 schrieb Brenton Earl: The only problem I see with adding support for both 2 and 3 is that your python3-pillow will conflict with the official Slackware package when 14.2 is released. It would conflict anyway, even if it included support for Python 3 only, because of files

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

Am 14.12.2015 23:19 schrieb B Watson: What happens if someone needs both python 2 and 3 support? Does the python3 stuff actually conflict with the python2 stuff? If not, maybe it'd be good to allow building both instead of choosing only one or the other. Removed redundant assignments in the

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

Thanks, --Larry On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix <slac...@posteo.de> wrote: Greetings I wonder if something like the following test could be added to python-pillow.SlackBuild, in order to automatically add support for Python3 if the latter is installed: python setu

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

Am 14.12.2015 21:37 schrieb Brent Earl: I think that package duplication is unnecessary. An if else statment in the SlackBuild would be the solution I think. Where I live there is a large snow storm that knocked out my internet connection. It may not be until tomorrow or the next day that

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

Am 14.12.2015 23:19 schrieb B Watson: On 12/14/15, Philip Lacroix <slac...@posteo.de> wrote: Am 14.12.2015 21:37 schrieb Brent Earl: I think that package duplication is unnecessary. An if else statment in the SlackBuild would be the solution I think. Thanks. I'll either e

[Slackbuilds-users] Support for Python 3 in python-pillow?

Greetings I wonder if something like the following test could be added to python-pillow.SlackBuild, in order to automatically add support for Python3 if the latter is installed: python setup.py install --root=$PKG + if $(python3 -c 'import sys' 2>/dev/null); then + python3 setup.py

Re: [Slackbuilds-users] Support for Python 3 in python-pillow?

r python slackbuilds that support python3 to avoid file conflicts. Thanks, --Larry On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix <slac...@posteo.de> wrote: Greetings I wonder if something like the following test could be added to python-pillow.SlackBuild, in order to automaticall

Re: [Slackbuilds-users] Marco Boneti's Packages

Am 02.11.2015 16:34 schrieb Willy Sudiarto Raharjo: I contacted Marco and he no longer maintain his packages, so feel free to grab and send updates to the following packages I can take system/xar as well, of course if nobody else is interested. The original project at Google Code has been

Re: [Slackbuilds-users] two blender packages?

Am 05.11.2015 23:49 schrieb Christoph Willing: On 06/11/15 08:20, Philip Lacroix wrote: The content of the source archives (source code or binary) can be inferred from the names (and a quick look at the scripts), but perhaps a short note at the end of both READMEs would help to remove any

Re: [Slackbuilds-users] two blender packages?

Am 05.11.2015 22:46 schrieb Ryan P.C. McQuen: On Thu, Nov 5, 2015 at 1:31 PM Andrew wrote: Better rename it to "blender-bin", please. We followed the same naming scheme as arduino/Arduino: (...) So this does have some precedence. The content of the source archives (source

Re: [Slackbuilds-users] Marco Boneti's Packages

Am 02.11.2015 16:34 schrieb Willy Sudiarto Raharjo: Hi I contacted Marco and he no longer maintain his packages, so feel free to grab and send updates to the following packages Hi Willy I can pick system/srm, unless someone else is interested. Thanks Philip

Re: [Slackbuilds-users] SBo source archive

Am 26.10.2015 19:34 schrieb B Watson: Been working on this for a couple of weeks, it's now to the point where it's ready to be announced to the world, so here we go: There's a huge public archive of the sources linked to by SBo .info files: http://slackware.org.uk/sbosrcarch/ Something like

Re: [Slackbuilds-users] Offer: Dia SlackBuild ownership

Hi Doogster Am 18.09.2015 23:04 schrieb Doogster: I'd like to offer ownership of the Dia SlackBuild to anyone who wants it. If I get no takers, I'll continue to maintain it as best I can. If no one else is interested I'd be glad to maintain it. Cheers Philip

Re: [Slackbuilds-users] Github file name issue

Am 25.05.2015 16:52 schrieb Ryan P.C. McQuen: I use: if [ -e $CWD/$VERSION.tar.gz ]; then tar xvf $CWD/$VERSION.tar.gz else tar xvf $CWD/$PRGNAM-$VERSION.tar.gz fi So that a 'no such file or directory' warning won't get displayed. Yeah, that's exactly what I've been doing in my scripts

Re: [Slackbuilds-users] Some thoughts about WinFF: source vs. binary

Am 22.04.2015 10:24 schrieb Niki Kovacs: Le 17/04/2015 01:07, Philip Lacroix a écrit : Did you contact the maintainer? You should ask him: if he agrees that you take on the maintainership of his package then I guess that the SBo admins will be ok as well (of course I cannot speak for them

Re: [Slackbuilds-users] Some thoughts about WinFF: source vs. binary

Am 17.04.2015 00:36 schrieb Niki Kovacs: I don't know if the author has abandoned WinFF, but if everybody's OK with it, I'd like to jump in and submit my own SlackBuild for it, since it builds the application from source. Did you contact the maintainer? You should ask him: if he agrees that

Re: [Slackbuilds-users] unicap

Hi Robby Am 08.03.2015 21:29 schrieb Robby Workman: On Fri, 06 Mar 2015 21:37:54 +0100 Philip Lacroix phi...@posteo.de wrote: Could you please do the same with libucil, libunicapgtk and UCView? If needed I still have the following, original upstream source packages, which I downloaded about

Re: [Slackbuilds-users] unicap

Hi Klaatu All, Unicap's author and maintainer has accounts on GitHub and Launchpad as well, where the full code is (still) available: https://github.com/unicap https://launchpad.net/~arne-datafloater/+archive/ubuntu/unicap He is (or used to be) the chief firmware developer for The Imaging

Re: [Slackbuilds-users] unicap

Am 06.03.2015 07:17 schrieb Robby Workman: http://harrier.slackbuilds.org/misc/libunicap-0.9.12.tar.gz http://harrier.slackbuilds.org/misc/libunicap-0.9.12.tar.gz.sign Note: The .sign is from *me* rather than upstream - that's just to certify that I uploaded the code from a presumably trusted

Re: [Slackbuilds-users] Fossil 1.31 update

The removal form only works if the package is still in the pending list. Your package, however, was already accepted by Willy for the next update: http://slackbuilds.org/cgit/slackbuilds/commit/?id=27b08c9fd So either you wait for next week's update in order to submit the modified version,

Re: [Slackbuilds-users] New e-mail address

Am 24.03.2014 21:03 schrieb Rob McGee: No problem at all. I *want* feedback on our spam controls. (...) So [this addressed to all], please keep it coming. I want to hear from anyone who tries to post to these lists and gets rejected. Perhaps you'll have to use a different address to reach me,

Re: [Slackbuilds-users] New e-mail address

Hello Rob, thanks a lot for your reply. I didn't intend to criticize anyone or anything, but perhaps my message sounded a bit like that (I'm not a native speaker), and in that case I'm sorry: I appreciate the work you guys are doing, and by list manager I intended the automatic filtering

[Slackbuilds-users] New e-mail address

list). Please keep this form: me at foo dot bar. Thanks! Best wishes, Philip Lacroix ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http

Re: [Slackbuilds-users] New e-mail address

Am 21.03.2014 18:22 schrieb Willy Sudiarto Raharjo: done Great, thank you very much, PL ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives -