From klaatu at straightedgelinux.com Sun Nov 1 00:46:17 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Sun, 1 Nov 2015 13:46:17 +1300 Subject: [Slackbuilds-users] xdotool (3.20150503.1) In-Reply-To: <5634DFCB.3010009@slackbuilds.org> References: <20151031153242.GA29948@jdiamond-nb2> <5634DFCB.3010009@slackbuilds.org> Message-ID: <563560D9.20105@straightedgelinux.com> Willy or other-relevant admin: Could we add 'nvidia-cg-toolkit' to the REQUIRES of lightworks ? Sorry, I forgot to add it with my most recent update to 12.5 - klaatu On 11/01/2015 04:35 AM, Willy Sudiarto Raharjo wrote: >> it would seem xdotool (3.20150503.1) requires libxkbcommon, but that >> is not listed as a requirement. > > Fixed in my branch > > Thanks > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sun Nov 1 00:47:53 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 1 Nov 2015 07:47:53 +0700 Subject: [Slackbuilds-users] xdotool (3.20150503.1) In-Reply-To: <563560D9.20105@straightedgelinux.com> References: <20151031153242.GA29948@jdiamond-nb2> <5634DFCB.3010009@slackbuilds.org> <563560D9.20105@straightedgelinux.com> Message-ID: <56356139.2030506@slackbuilds.org> > Willy or other-relevant admin: > > Could we add 'nvidia-cg-toolkit' to the REQUIRES of lightworks ? > > Sorry, I forgot to add it with my most recent update to 12.5 Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From klaatu at straightedgelinux.com Sun Nov 1 04:34:43 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Sun, 1 Nov 2015 17:34:43 +1300 Subject: [Slackbuilds-users] xdotool (3.20150503.1) In-Reply-To: <56356139.2030506@slackbuilds.org> References: <20151031153242.GA29948@jdiamond-nb2> <5634DFCB.3010009@slackbuilds.org> <563560D9.20105@straightedgelinux.com> <56356139.2030506@slackbuilds.org> Message-ID: <56359663.9000306@straightedgelinux.com> On 11/01/2015 01:47 PM, Willy Sudiarto Raharjo wrote: >> Willy or other-relevant admin: >> >> Could we add 'nvidia-cg-toolkit' to the REQUIRES of lightworks ? >> >> Sorry, I forgot to add it with my most recent update to 12.5 > > Done > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > Geez, I also hijacked the xdotool thread. Sorry... -klaatu From willysr at slackbuilds.org Mon Nov 2 15:34:08 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 2 Nov 2015 22:34:08 +0700 Subject: [Slackbuilds-users] Marco Boneti's Packages Message-ID: <56378270.6090206@slackbuilds.org> Hi I contacted Marco and he no longer maintain his packages, so feel free to grab and send updates to the following packages desktop/pidgin-libnotify desktop/wmii development/bsdiff development/dpkg development/portaudio libraries/BeautifulSoup libraries/Impacket libraries/libixp libraries/libnids libraries/libvidcap libraries/libwhisker2 libraries/newt libraries/nltk libraries/tsocks multimedia/tvtime network/SocksiPy network/amap network/corkscrew network/deluge network/dsniff network/hping3 network/libdnet network/nikto network/packit network/periscope network/pidgin-sipe network/polipo network/reaver network/sqlmap network/sqlninja network/ttdnsd network/w3af perl/perl-Bit-Vector perl/perl-Carp-Clan perl/perl-Class-Gomor perl/perl-IO-Interface perl/perl-IO-Socket-INET6 perl/perl-Math-Base85 perl/perl-Net-IPv4Addr perl/perl-Net-IPv6Addr perl/perl-Net-LibIDN perl/perl-Net-Libdnet perl/perl-Net-Packet perl/perl-Net-Pcap perl/perl-Net-RawIP perl/perl-Net-Telnet perl/perl-Net-Write perl/perl-NetPacket perl/perl-Socket6 python/SOAPpy python/json-py python/pyPdf python/pycxx python/pysvn python/python-cluster system/apache-activemq system/byobu system/debootstrap system/ksplice system/srm system/wiimms-wbfs-tool system/xar -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From gerardo.zamudio at linux.com Mon Nov 2 15:55:53 2015 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 2 Nov 2015 09:55:53 -0600 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <56378789.6020801@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/02/2015 09:34 AM, Willy Sudiarto Raharjo wrote: > Hi > > I contacted Marco and he no longer maintain his packages, so feel > free to grab and send updates to the following packages > > desktop/pidgin-libnotify desktop/wmii development/bsdiff > development/dpkg development/portaudio libraries/BeautifulSoup > libraries/Impacket libraries/libixp libraries/libnids > libraries/libvidcap libraries/libwhisker2 libraries/newt > libraries/nltk libraries/tsocks multimedia/tvtime network/SocksiPy > network/amap network/corkscrew network/deluge network/dsniff > network/hping3 network/libdnet network/nikto network/packit > network/periscope network/pidgin-sipe network/polipo > network/reaver network/sqlmap network/sqlninja network/ttdnsd > network/w3af perl/perl-Bit-Vector perl/perl-Carp-Clan > perl/perl-Class-Gomor perl/perl-IO-Interface > perl/perl-IO-Socket-INET6 perl/perl-Math-Base85 > perl/perl-Net-IPv4Addr perl/perl-Net-IPv6Addr perl/perl-Net-LibIDN > perl/perl-Net-Libdnet perl/perl-Net-Packet perl/perl-Net-Pcap > perl/perl-Net-RawIP perl/perl-Net-Telnet perl/perl-Net-Write > perl/perl-NetPacket perl/perl-Socket6 python/SOAPpy python/json-py > python/pyPdf python/pycxx python/pysvn python/python-cluster > system/apache-activemq system/byobu system/debootstrap > system/ksplice system/srm system/wiimms-wbfs-tool system/xar > > > > > _______________________________________________ SlackBuilds-users > mailing list SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - > http://slackbuilds.org/faq/ > Hey Willy, I can take over network/deluge provided no one else wants it. - -- Gerardo Zamudio Linux System Administrator https://gerardozamudio.mx -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWN4eJAAoJEPbPpamee1lXdasQAKnXribqerFx1hpdSXWdt6GF krymQYYVgkBf2jQ8hgDNbRcWLbGqikETKQ1mWWeHSGE3rSMhVgKz3WPqe5MoSO2r bUUIim0sLfVV3tR6kiTjyq1NQEs7Tc3f+nSb3IiIuEo4WenNUGSYxco5VxbMsu1n IUlZs3mhXmkLrzignKtqimuSuNOlAJ2l1iYLZ6VJhpnV530bD2zYaF4P28QacdDY MVYDqqhwzc8KDEWylQo/95rPYzAClmiUcExXowRBXJ09eJrxjG2M7fB7Uq+8l/K0 LRnZ1uBcwxJCO3i3iU0TKVgawiI53I04OLYU+/rLwVrTMyU66Zmh3Rghi8YECq+T hUtywLmzDfTl1iqqvbH4MCt6fEpvq1Q9QtH26hhyB9xSniBV2zalND6zIWlRHsW/ EFkG+TBu4WQrPTJzmueqKAa++1N8x9C/6I9XLsDmcv2PIJ6kGcySKw2/YlYmbliZ eu1SHRxb2X9vQsK57dCJe3/YFPJl4ZsSVvdTbUovNw+vjHlryvZjPkTkFIabwG6d P7tb8n9gTnWoS43jXz5yAo/oZ79ajREGhEnE3MU5RsYW7E4CYKxmgU8Zt4IjO/yP 27yYo81e7pWO5OuuyTUHSa8YwlW7NmmtUwJOXDwrvf798X1HvRMFyt28pXl8g1Kv MNIUgkkcwTbk5aL3dD/r =0peX -----END PGP SIGNATURE----- From didier at slint.fr Mon Nov 2 16:02:01 2015 From: didier at slint.fr (Didier Spaier) Date: Mon, 2 Nov 2015 17:02:01 +0100 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <563788F9.1030304@slint.fr> On 02/11/2015 16:34, Willy Sudiarto Raharjo wrote: > Hi > > I contacted Marco and he no longer maintain his packages, so feel free > to grab and send updates to the following packages I volunteer for these: > libraries/newt > system/byobu I didn't check but if other packages also depend on newt I could adopt them as well. I plan to include the patch that links newt to fribidi discarded by Fedora but included by Debian so that their text installer can properly display Middle East languages. Didier From larryhaja at gmail.com Mon Nov 2 16:16:06 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Mon, 2 Nov 2015 08:16:06 -0800 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <563788F9.1030304@slint.fr> References: <56378270.6090206@slackbuilds.org> <563788F9.1030304@slint.fr> Message-ID: > libraries/BeautifulSoup I can take over BeautifulSoup. This is a dependency for one of my packages. --Larry On Mon, Nov 2, 2015 at 8:02 AM, Didier Spaier wrote: > On 02/11/2015 16:34, Willy Sudiarto Raharjo wrote: > > Hi > > > > I contacted Marco and he no longer maintain his packages, so feel free > > to grab and send updates to the following packages > > I volunteer for these: > > > libraries/newt > > system/byobu > > I didn't check but if other packages also depend on newt > I could adopt them as well. > > I plan to include the patch that links newt to fribidi > discarded by Fedora but included by Debian so that their > text installer can properly display Middle East languages. > > Didier > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.becker at gmail.com Mon Nov 2 16:29:57 2015 From: glenn.becker at gmail.com (Glenn Becker) Date: Mon, 2 Nov 2015 11:29:57 -0500 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: I will take wmii bsdiff dpkg debootstrap .... unless someone more skilled wants 'em. Glenn On Mon, Nov 2, 2015 at 10:34 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi > > I contacted Marco and he no longer maintain his packages, so feel free > to grab and send updates to the following packages > > desktop/pidgin-libnotify > desktop/wmii > development/bsdiff > development/dpkg > development/portaudio > libraries/BeautifulSoup > libraries/Impacket > libraries/libixp > libraries/libnids > libraries/libvidcap > libraries/libwhisker2 > libraries/newt > libraries/nltk > libraries/tsocks > multimedia/tvtime > network/SocksiPy > network/amap > network/corkscrew > network/deluge > network/dsniff > network/hping3 > network/libdnet > network/nikto > network/packit > network/periscope > network/pidgin-sipe > network/polipo > network/reaver > network/sqlmap > network/sqlninja > network/ttdnsd > network/w3af > perl/perl-Bit-Vector > perl/perl-Carp-Clan > perl/perl-Class-Gomor > perl/perl-IO-Interface > perl/perl-IO-Socket-INET6 > perl/perl-Math-Base85 > perl/perl-Net-IPv4Addr > perl/perl-Net-IPv6Addr > perl/perl-Net-LibIDN > perl/perl-Net-Libdnet > perl/perl-Net-Packet > perl/perl-Net-Pcap > perl/perl-Net-RawIP > perl/perl-Net-Telnet > perl/perl-Net-Write > perl/perl-NetPacket > perl/perl-Socket6 > python/SOAPpy > python/json-py > python/pyPdf > python/pycxx > python/pysvn > python/python-cluster > system/apache-activemq > system/byobu > system/debootstrap > system/ksplice > system/srm > system/wiimms-wbfs-tool > system/xar > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackph at posteo.de Mon Nov 2 16:38:36 2015 From: slackph at posteo.de (Philip Lacroix) Date: Mon, 02 Nov 2015 17:38:36 +0100 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: 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 From didier at slint.fr Mon Nov 2 17:48:38 2015 From: didier at slint.fr (Didier Spaier) Date: Mon, 2 Nov 2015 18:48:38 +0100 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: References: <56378270.6090206@slackbuilds.org> <563788F9.1030304@slint.fr> Message-ID: <5637A1F6.9000709@slint.fr> On 02/11/2015 17:16, Larry Hajali wrote: >> libraries/BeautifulSoup > > I can take over BeautifulSoup. This is a dependency for one of my packages. > > --Larry I never used it myself but out of curiosity: Larry, is it still necessary to have both BS3 and BS4 (maintained by Dimitris Zlatadadis)? I just noticed that only the latter has pysetuptools as dependency according to the README. In particular, would the package that you maintain work with BS4 (not BS3) installed? Again, just curious. Didier From marc at mos6581.de Mon Nov 2 18:05:01 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Mon, 2 Nov 2015 19:05:01 +0100 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <5637A5CD.4040501@mos6581.de> On 11/02/2015 04:34 PM, Willy Sudiarto Raharjo wrote: > development/portaudio I'll take it. -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Mon Nov 2 19:03:44 2015 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 2 Nov 2015 19:03:44 +0000 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: > I contacted Marco and he no longer maintain his packages, so feel free > to grab and send updates to the following packages He's done a great job for us, if you are still subscribed here Marco thank you very much! So I can offer to take these, unless someone else is interested? > python/json-py Need this for my day job :-) > network/reaver I've got an old update for that, if anyone cares? > system/ksplice I've got some experimental fixes for -current although I'm not sure it's useful any more? Best regards -D. From edps.mundognu at gmail.com Mon Nov 2 19:38:49 2015 From: edps.mundognu at gmail.com (edinaldo) Date: Mon, 02 Nov 2015 17:38:49 -0200 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: References: Message-ID: i'm interested in: /development/dpkg but @Glenn Becker already volunteered, so it's in good hands. I use dpkg-source for unpacking the files (* .dsc, .orig.tar.gz * and * .debian.tar.gz) for testing and for get patches for some SlackBuilds. From marc at mos6581.de Mon Nov 2 19:54:31 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Mon, 2 Nov 2015 20:54:31 +0100 Subject: [Slackbuilds-users] [profile-sync-daemon] Dropped support Message-ID: <5637BF77.1080906@mos6581.de> I drop support for profile-sync-daemon. Whilst it still works without the systemd clusterfuck, it requires `sudo` in user space. That's not the way I want to have it to work and patch orgies in future. If someone wants to takeover it anyway, feel free to grab bit. -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From artourter at gmail.com Mon Nov 2 19:58:12 2015 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 2 Nov 2015 19:58:12 +0000 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: References: Message-ID: I can pick up nltk if noone else wants it. Cheers Greg On 2 November 2015 at 19:38, edinaldo wrote: > i'm interested in: > > /development/dpkg > > but @Glenn Becker already volunteered, so it's in good hands. > > I use dpkg-source for unpacking the files (* .dsc, .orig.tar.gz * and * > .debian.tar.gz) > for testing and for get patches for some SlackBuilds. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From spaceman at antispaceman.com Mon Nov 2 20:19:33 2015 From: spaceman at antispaceman.com (spaceman) Date: Mon, 2 Nov 2015 20:19:33 +0000 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <20151102201933.GC7148@home.lan> Hi, I will take: > network/polipo if no one else wants it. Regards, spaceman >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - http://slackbuilds.org/faq/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From arkadiusz at drabczyk.org Mon Nov 2 21:02:12 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Mon, 2 Nov 2015 21:02:12 +0000 (UTC) Subject: [Slackbuilds-users] Marco Boneti's Packages References: <56378270.6090206@slackbuilds.org> Message-ID: On 2015-11-02, David Spencer wrote: >> system/ksplice > I've got some experimental fixes for -current although I'm not sure > it's useful any more? Do you use ksplice regularly, what do you think about it? Is it reliable? I can take over libraries/tsocks because I use it occasionally and it's a useful little program. There has been no upgrade since 2002 http://tsocks.sourceforge.net/ so there shouldn't be much to do here. -- Arkadiusz Drabczyk From miguel at thedeanda.com Tue Nov 3 05:59:29 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 2 Nov 2015 21:59:29 -0800 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: i'll take system/apache-activemq if nobody else wants it. On Mon, Nov 2, 2015 at 7:34 AM, Willy Sudiarto Raharjo wrote: > Hi > > I contacted Marco and he no longer maintain his packages, so feel free > to grab and send updates to the following packages > > desktop/pidgin-libnotify > desktop/wmii > development/bsdiff > development/dpkg > development/portaudio > libraries/BeautifulSoup > libraries/Impacket > libraries/libixp > libraries/libnids > libraries/libvidcap > libraries/libwhisker2 > libraries/newt > libraries/nltk > libraries/tsocks > multimedia/tvtime > network/SocksiPy > network/amap > network/corkscrew > network/deluge > network/dsniff > network/hping3 > network/libdnet > network/nikto > network/packit > network/periscope > network/pidgin-sipe > network/polipo > network/reaver > network/sqlmap > network/sqlninja > network/ttdnsd > network/w3af > perl/perl-Bit-Vector > perl/perl-Carp-Clan > perl/perl-Class-Gomor > perl/perl-IO-Interface > perl/perl-IO-Socket-INET6 > perl/perl-Math-Base85 > perl/perl-Net-IPv4Addr > perl/perl-Net-IPv6Addr > perl/perl-Net-LibIDN > perl/perl-Net-Libdnet > perl/perl-Net-Packet > perl/perl-Net-Pcap > perl/perl-Net-RawIP > perl/perl-Net-Telnet > perl/perl-Net-Write > perl/perl-NetPacket > perl/perl-Socket6 > python/SOAPpy > python/json-py > python/pyPdf > python/pycxx > python/pysvn > python/python-cluster > system/apache-activemq > system/byobu > system/debootstrap > system/ksplice > system/srm > system/wiimms-wbfs-tool > system/xar > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From kingbeowulf at gmail.com Tue Nov 3 06:11:04 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 2 Nov 2015 22:11:04 -0800 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: References: <56378270.6090206@slackbuilds.org> Message-ID: <56384FF8.90702@gmail.com> On 11/02/2015 11:03 AM, David Spencer wrote: >> system/ksplice > I've got some experimental fixes for -current although I'm not sure > it's useful any more? > Given that Oracle has sucked up ksplice and provides support for just a few kernels and distros that Oracle has "blessed', I'd say no; dump it. New 4.x kernels are now incorporating that functionality anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Tue Nov 3 14:01:16 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 3 Nov 2015 15:01:16 +0100 Subject: [Slackbuilds-users] Missing fonts in google-droid-fonts? Message-ID: <5638BE2C.20209@microlinux.fr> Hi, For the last three years or so, I've been using Google Droid Sans as my main system font for Xfce. Here's what it looks like: http://www.microlinux.fr/images/mled/mled_desktop.png The font is "Droid Sans" size 11. Here's the package source, initially taken from SBo and modified accordingly: http://www.microlinux.fr/microlinux/desktop-14.1-source/google-droid-fonts/ Around last year, I tried to upgrade the package, but curiously enough, more than half of the "Droid" variants were gone. So I've reverted to the old version of the package. Anybody knows what happened with "Droid Sans" in that package? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From rshepard at appl-ecosys.com Tue Nov 3 14:21:24 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 3 Nov 2015 06:21:24 -0800 (PST) Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 Message-ID: I've one application used daily that requires Python3 and others that require Python2. Installed here are PyQt-4.11.1-i486-1python2and3 and sip-4.16.8-i486-1_python2and3 but I do not have the source files and slackbuilds scripts for either one. I need to re-install the PyQt package to see if that fixes a sudden problem with the Python3-requiring application to not load and I have not found either source/script on SBo. Web searches also fail to find the sources. Please point me to the sources for these two packages so I have them here and can upgrade or re-install as necessary. Thanks in advance, Rich From ryan.q at linux.com Tue Nov 3 14:50:33 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Tue, 3 Nov 2015 06:50:33 -0800 Subject: [Slackbuilds-users] Missing fonts in google-droid-fonts? In-Reply-To: <5638BE2C.20209@microlinux.fr> References: <5638BE2C.20209@microlinux.fr> Message-ID: >Anybody knows what happened with "Droid Sans" in that package? The fonts are taken from here: https://github.com/android/platform_frameworks_base/tree/master/data/fonts Instead of here: http://www.droidfonts.com/droidfonts/ Per this request: http://lists.slackbuilds.org/pipermail/slackbuilds-users/2014-May/012525.html -- [ryanpcmcquen.org] -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Tue Nov 3 14:51:10 2015 From: didier at slint.fr (Didier Spaier) Date: Tue, 3 Nov 2015 15:51:10 +0100 Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 In-Reply-To: References: Message-ID: <5638C9DE.7020304@slint.fr> On 03/11/2015 15:21, Rich Shepard wrote: > I've one application used daily that requires Python3 and others that > require Python2. Installed here are PyQt-4.11.1-i486-1python2and3 and > sip-4.16.8-i486-1_python2and3 but I do not have the source files and > slackbuilds scripts for either one. > > I need to re-install the PyQt package to see if that fixes a sudden > problem with the Python3-requiring application to not load and I have not > found either source/script on SBo. Web searches also fail to find the > sources. > > Please point me to the sources for these two packages so I have them here > and can upgrade or re-install as necessary. Not sure I understand your request. If you are looking for the source /slackbuild for PyQt4 there is no reason that you find it in SBo as it's shipped in Slackware, Slackware 14.1 has the version 4.9.6 and Slackware-current the version 4.11.4 as shows the Slackware Pacakages Browser: http://packages.slackware.com/ But if you are after PyQt-4.11.1-i486-1python2and3 and/or sip-4.16.8-i486-1_python2and3 I am afraid this list be not the good place to ask. All I have found is this thread: https://groups.google.com/forum/#!topic/wxpython-users/n1NDoJKUqkM But I assume you opened so that won't help you. Didier From titopoquito at gmail.com Tue Nov 3 15:06:30 2015 From: titopoquito at gmail.com (Tito) Date: Tue, 3 Nov 2015 16:06:30 +0100 Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 In-Reply-To: References: Message-ID: I think I posted the SlackBuild in linuxquestions.org some time ago. If you look for my posts (user "titopoquito")... I don't post too often, so you will stumble upon it rather quickly. > Am 03.11.2015 um 15:21 schrieb Rich Shepard : > > I've one application used daily that requires Python3 and others that > require Python2. Installed here are PyQt-4.11.1-i486-1python2and3 and > sip-4.16.8-i486-1_python2and3 but I do not have the source files and > slackbuilds scripts for either one. > > I need to re-install the PyQt package to see if that fixes a sudden > problem with the Python3-requiring application to not load and I have not > found either source/script on SBo. Web searches also fail to find the > sources. > > Please point me to the sources for these two packages so I have them here > and can upgrade or re-install as necessary. > > Thanks in advance, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From didier at slint.fr Tue Nov 3 15:23:19 2015 From: didier at slint.fr (Didier Spaier) Date: Tue, 3 Nov 2015 16:23:19 +0100 Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 In-Reply-To: References: Message-ID: <5638D167.40300@slint.fr> On 03/11/2015 16:06, Tito wrote: > I think I posted the SlackBuild in linuxquestions.org some time ago. If you look for my posts (user "titopoquito")... I don't post too often, so you will stumble upon it rather quickly. Maybe you are speaking about this thread: http://www.linuxquestions.org/questions/slackware-14/pyqt-for-python3-4175497944/ From titopoquito at gmail.com Tue Nov 3 15:49:49 2015 From: titopoquito at gmail.com (titopoquito) Date: Tue, 3 Nov 2015 16:49:49 +0100 Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 In-Reply-To: <5638D167.40300@slint.fr> References: <5638D167.40300@slint.fr> Message-ID: <5638D79D.4040606@gmail.com> On 03.11.2015 16:23, Didier Spaier wrote: > On 03/11/2015 16:06, Tito wrote: >> I think I posted the SlackBuild in linuxquestions.org some time >> ago. If you look for my posts (user "titopoquito")... I don't post >> too often, so you will stumble upon it rather quickly. > > Maybe you are speaking about this thread: > http://www.linuxquestions.org/questions/slackware-14/pyqt-for-python3-4175497944/ Yes, that's it. Thanks a lot for searching and finding it, Didier :D From rshepard at appl-ecosys.com Tue Nov 3 17:08:58 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 3 Nov 2015 09:08:58 -0800 (PST) Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 [RESOLVED] In-Reply-To: <5638D79D.4040606@gmail.com> References: <5638D167.40300@slint.fr> <5638D79D.4040606@gmail.com> Message-ID: On Tue, 3 Nov 2015, titopoquito wrote: >> Maybe you are speaking about this thread: >> http://www.linuxquestions.org/questions/slackware-14/pyqt-for-python3-4175497944/ > > Yes, that's it. Thanks a lot for searching and finding it, Didier :D Thank you all. I was trying to find that thread with my Web searches but did not hit it. Now I'll save the information for the next time. Much appreciated, Rich From rshepard at appl-ecosys.com Tue Nov 3 21:17:36 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 3 Nov 2015 13:17:36 -0800 (PST) Subject: [Slackbuilds-users] PyQt4 and sip for Python2 and Python3 [RESOLVED] In-Reply-To: References: Message-ID: On Tue, 3 Nov 2015, Rich Shepard wrote: > Please point me to the sources for these two packages so I have them here > and can upgrade or re-install as necessary. Thanks to both of you I've fixed the problem. Reading that linuxquestions thread pointed me to the proper SBo subdirectories here for both PyQt4-2&3 and sip-2&3. I had to rebuild sip and reinstall it, then do the same with PyQt4. Now the application loads. Same versions of sip and PyQt4 as before. Strange. Much appreciated, Rich From lksj at yandex.ru Wed Nov 4 10:23:09 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Wed, 04 Nov 2015 13:23:09 +0300 Subject: [Slackbuilds-users] kdenlive build bug Message-ID: <3013781446632589@web5g.yandex.ru> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: locales.patch Type: text/x-diff Size: 14305 bytes Desc: not available URL: From michelino.chionchio at gmail.com Wed Nov 4 08:32:38 2015 From: michelino.chionchio at gmail.com (Michelino Chionchio) Date: Wed, 4 Nov 2015 09:32:38 +0100 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack Message-ID: <5639C2A6.4030805@gmail.com> Just to point out that hugin-2015.0.0 won't compile here without libmspack, and this package is not listed in "requires"(nor in the "requires" of dependencies AFAIK). Cheers Michelino From titopoquito at gmail.com Wed Nov 4 11:10:03 2015 From: titopoquito at gmail.com (titopoquito) Date: Wed, 4 Nov 2015 12:10:03 +0100 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack In-Reply-To: <5639C2A6.4030805@gmail.com> References: <5639C2A6.4030805@gmail.com> Message-ID: <5639E78B.1020301@gmail.com> On 04.11.2015 09:32, Michelino Chionchio wrote: > Just to point out that hugin-2015.0.0 won't compile here without > libmspack, and this package is not listed in "requires"(nor in the > "requires" of dependencies AFAIK). > Cheers Michelino I don't remember that I had to compile libmspack. Unfortunately I will be not able to check this before the weekend, but I will look into it. Tito From willysr at slackbuilds.org Thu Nov 5 01:49:58 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 5 Nov 2015 08:49:58 +0700 Subject: [Slackbuilds-users] kdenlive build bug In-Reply-To: <3013781446632589@web5g.yandex.ru> References: <3013781446632589@web5g.yandex.ru> Message-ID: <563AB5C6.4050102@slackbuilds.org> > Hello. > I found build bug in > http://slackbuilds.org/repository/14.1/multimedia/kdenlive/ > Any locale defined as "fr" > Patch attachend Applied in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Thu Nov 5 07:56:59 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 5 Nov 2015 08:56:59 +0100 Subject: [Slackbuilds-users] Missing fonts in google-droid-fonts? In-Reply-To: References: <5638BE2C.20209@microlinux.fr> Message-ID: <563B0BCB.8040100@microlinux.fr> Le 03/11/2015 15:50, Ryan P.C. McQuen a ?crit : > Instead of here: > > http://www.droidfonts.com/droidfonts/ > > Per this request: > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2014-May/012525.html > The curious thing is that the old package actually contains *more* fonts than the more recent one. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Thu Nov 5 09:36:31 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 5 Nov 2015 16:36:31 +0700 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack In-Reply-To: <5639E78B.1020301@gmail.com> References: <5639C2A6.4030805@gmail.com> <5639E78B.1020301@gmail.com> Message-ID: <563B231F.90902@slackbuilds.org> > On 04.11.2015 09:32, Michelino Chionchio wrote: >> Just to point out that hugin-2015.0.0 won't compile here without >> libmspack, and this package is not listed in "requires"(nor in the >> "requires" of dependencies AFAIK). >> Cheers Michelino > > I don't remember that I had to compile libmspack. Unfortunately I will > be not able to check this before the weekend, but I will look into it. Yep, you don't need libmspack wxPython: MD5SUM check for wxPython-src-2.8.12.1.tar.bz2 ... OK Building package wxPython-2.8.12.1-x86_64-2_SBo.tgz ... OK Installing package wxPython-2.8.12.1-x86_64-2_SBo.tgz ... OK tclap: MD5SUM check for tclap-1.2.1.tar.gz ... OK Building package tclap-1.2.1-x86_64-1_SBo.tgz ... OK Installing package tclap-1.2.1-x86_64-1_SBo.tgz ... OK libpano13: MD5SUM check for libpano13-2.9.19.tar.gz ... OK Building package libpano13-2.9.19-x86_64-1_SBo.tgz ... OK Installing package libpano13-2.9.19-x86_64-1_SBo.tgz ... OK exiftool: MD5SUM check for Image-ExifTool-10.00.tar.gz ... OK Building package exiftool-10.00-x86_64-1_SBo.tgz ... OK Installing package exiftool-10.00-x86_64-1_SBo.tgz ... OK vigra: MD5SUM check for vigra-1.10.0-src-with-docu.tar.gz ... OK Building package vigra-1.10.0-x86_64-2_SBo.tgz ... OK Installing package vigra-1.10.0-x86_64-2_SBo.tgz ... OK gsl: MD5SUM check for gsl-1.16.tar.gz ... OK Building package gsl-1.16-x86_64-1_SBo.tgz ... OK Installing package gsl-1.16-x86_64-1_SBo.tgz ... OK enblend-enfuse: MD5SUM check for enblend-enfuse-4.1.2.tar.gz ... OK Building package enblend-enfuse-4.1.2-x86_64-2_SBo.tgz ... OK Installing package enblend-enfuse-4.1.2-x86_64-2_SBo.tgz ... OK hugin: MD5SUM check for hugin-2015.0.0.tar.bz2 ... OK Building package hugin-2015.0.0-x86_64-1_SBo.tgz ... OK Installing package hugin-2015.0.0-x86_64-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From clansco at clansco.org Thu Nov 5 11:19:08 2015 From: clansco at clansco.org (clansco) Date: Thu, 5 Nov 2015 12:19:08 +0100 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack In-Reply-To: <5639C2A6.4030805@gmail.com> References: <5639C2A6.4030805@gmail.com> Message-ID: <20151105121908.d40a0b975584cdbcc335a7af@clansco.org> On Wed, 4 Nov 2015 09:32:38 +0100 Michelino Chionchio wrote: > Just to point out that hugin-2015.0.0 won't compile here without > libmspack, and this package is not listed in "requires"(nor in the > "requires" of dependencies AFAIK). > Cheers Michelino Hi, I can reproduce this : 1- build wxPython with libmspack 2- removepkg libmspack 3- try to build hugin yet not tested with wxPython whithout libmspack... comming soon ;) From falsetti at clansco.org Thu Nov 5 11:30:15 2015 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Thu, 5 Nov 2015 12:30:15 +0100 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack In-Reply-To: <5639C2A6.4030805@gmail.com> References: <5639C2A6.4030805@gmail.com> Message-ID: <20151105123015.3f51a936d46ad2c0cbabcc1e@clansco.org> On Wed, 4 Nov 2015 09:32:38 +0100 Michelino Chionchio wrote: > Just to point out that hugin-2015.0.0 won't compile here without > libmspack, and this package is not listed in "requires"(nor in the > "requires" of dependencies AFAIK). > Cheers Michelino Hi, I can reproduce this : 1- build wxPython with libmspack 2- removepkg libmspack 3- try to build hugin yet not tested with wxPython whithout libmspack... comming soon ;) From michelino.chionchio at gmail.com Thu Nov 5 11:45:06 2015 From: michelino.chionchio at gmail.com (Michelino Chionchio) Date: Thu, 5 Nov 2015 12:45:06 +0100 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack In-Reply-To: <20151105123015.3f51a936d46ad2c0cbabcc1e@clansco.org> References: <5639C2A6.4030805@gmail.com> <20151105123015.3f51a936d46ad2c0cbabcc1e@clansco.org> Message-ID: <563B4142.1010300@gmail.com> On 05/11/2015 12:30, Fr?d?ric Falsetti wrote: > On Wed, 4 Nov 2015 09:32:38 +0100 > Michelino Chionchio wrote: > >> Just to point out that hugin-2015.0.0 won't compile here without >> libmspack, and this package is not listed in "requires"(nor in the >> "requires" of dependencies AFAIK). >> Cheers Michelino > > Hi, > I can reproduce this : > 1- build wxPython with libmspack > 2- removepkg libmspack > 3- try to build hugin > > yet not tested with wxPython whithout libmspack... > comming soon ;) > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > You are right, it's my mistake. I've a wxPython package compiled against libmspack, so wxPython requires libmspack and huging building fails. Sorry for crying wolf! Michelino From falsetti at clansco.org Thu Nov 5 12:09:42 2015 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Thu, 5 Nov 2015 13:09:42 +0100 Subject: [Slackbuilds-users] Hugin-2015.0.0 and libmspack In-Reply-To: <563B4142.1010300@gmail.com> References: <5639C2A6.4030805@gmail.com> <20151105123015.3f51a936d46ad2c0cbabcc1e@clansco.org> <563B4142.1010300@gmail.com> Message-ID: <20151105130942.be37efb52258a680a0388106@clansco.org> On Thu, 5 Nov 2015 12:45:06 +0100 Michelino Chionchio wrote: > On 05/11/2015 12:30, Fr?d?ric Falsetti wrote: > > On Wed, 4 Nov 2015 09:32:38 +0100 > > Michelino Chionchio wrote: > > > >> Just to point out that hugin-2015.0.0 won't compile here without > >> libmspack, and this package is not listed in "requires"(nor in the > >> "requires" of dependencies AFAIK). > >> Cheers Michelino > > > > Hi, > > I can reproduce this : > > 1- build wxPython with libmspack > > 2- removepkg libmspack > > 3- try to build hugin > > > > yet not tested with wxPython whithout libmspack... > > comming soon ;) test: and if wxGTK is also build against libmspack: hugin-2015.0.0/src/hugin_script_interface: /usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/ld: warning: libmspack.so.0, needed by /usr/X11R6/lib/libwx_gtk2u_html-2.8.so, not found (try using -rpath or -rpath-link) I try to rebuild wxGTK without libmspack :) > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > You are right, it's my mistake. > I've a wxPython package compiled against libmspack, so wxPython requires > libmspack and huging building fails. > Sorry for crying wolf! > Michelino > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From ryan.q at linux.com Thu Nov 5 14:39:50 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 5 Nov 2015 06:39:50 -0800 Subject: [Slackbuilds-users] Missing fonts in google-droid-fonts? In-Reply-To: <563B0BCB.8040100@microlinux.fr> References: <5638BE2C.20209@microlinux.fr> <563B0BCB.8040100@microlinux.fr> Message-ID: >The curious thing is that the old package actually contains *more* fonts than the more recent one. This is where versioning systems come in handy: http://slackbuilds.org/cgit/slackbuilds/tree/system/google-droid-fonts?id=6ee5954f665977598e7ac6b57b57ae6ff7e26deb Although there is no 4.x tarball at the link in .info anymore, you can still find it here: http://sourceforge.net/projects/slackbuildsdirectlinks/files/google-droid-fonts/ -- [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From kenneth.t.chan at gmail.com Thu Nov 5 16:29:34 2015 From: kenneth.t.chan at gmail.com (Kenneth Chan) Date: Fri, 6 Nov 2015 00:29:34 +0800 Subject: [Slackbuilds-users] Outdated openconnect slackbuilds In-Reply-To: References: Message-ID: The openconnect on sbo is 5.03 which is a bit outdated. Any chance to update to 7.06 or so? Amongst the many Juniper SSLVPN support was added so it'll be nice to bump the version. Ken On 3 November 2015 at 15:11, Kenneth Chan wrote: > Hi Robby, > > The openconnect on sbo is 5.03 which is a bit outdated. Any chance to > update to 7.06 or so? Amongst the many Juniper SSLVPN support was added so > it'll be nice to bump the version. > > Ken > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Thu Nov 5 17:27:18 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 5 Nov 2015 18:27:18 +0100 Subject: [Slackbuilds-users] smptube OR smtube on ready queue Message-ID: <563B9176.9030909@gmail.com> Hi, I just noticed that ready queue has package named 'smptube' where it should be 'smtube'. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Thu Nov 5 17:27:46 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 6 Nov 2015 00:27:46 +0700 Subject: [Slackbuilds-users] smptube OR smtube on ready queue In-Reply-To: <563B9176.9030909@gmail.com> References: <563B9176.9030909@gmail.com> Message-ID: <563B9192.7010903@slackbuilds.org> > I just noticed that ready queue has package named 'smptube' where it > should be 'smtube'. Fixed :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Thu Nov 5 21:03:25 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 5 Nov 2015 14:03:25 -0700 Subject: [Slackbuilds-users] two blender packages? Message-ID: http://slackbuilds.org/repository/14.1/graphics/Blender/ http://slackbuilds.org/repository/14.1/graphics/blender/ why? -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Thu Nov 5 21:05:00 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 05 Nov 2015 21:05:00 +0000 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: References: Message-ID: http://slackbuilds.org/repository/14.1/graphics/Blender/ Built from source. http://slackbuilds.org/repository/14.1/graphics/blender/ Repackages binary version. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Thu Nov 5 21:08:31 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 5 Nov 2015 14:08:31 -0700 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: References: Message-ID: thanks. On Thu, Nov 5, 2015 at 2:05 PM, Ryan P.C. McQuen wrote: > http://slackbuilds.org/repository/14.1/graphics/Blender/ > > Built from source. > > http://slackbuilds.org/repository/14.1/graphics/blender/ > > Repackages binary version. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbernts at broadpark.no Thu Nov 5 21:13:11 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 05 Nov 2015 22:13:11 +0100 Subject: [Slackbuilds-users] luna-wallpapers error Message-ID: <20151105211311.GA1862@jostein> Installing luna-wallpapers now gives this error: ssing luna-wallpapers luna-wallpapers: Found luna-wallpapers.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for luna-wallpapers.tar.gz ... OK luna-wallpapers not found in /var/cache/sbopkg. --2015-11-05 22:12:06-- https://launchpad.net/~elementary-os/+archive/ubuntu/daily/+files/elementary-wallpapers_0.1.4-0%7E42%7Eubuntu0.3.1.tar.gz Resolving launchpad.net (launchpad.net)... 91.189.89.223, 91.189.89.222 Connecting to launchpad.net (launchpad.net)|91.189.89.223|:443... connected. HTTP foresp?rsel sendt, mottar topptekster... 404 Not Found 2015-11-05 22:12:06 FEIL 404: Not Found. Jostein From jbernts at broadpark.no Thu Nov 5 21:15:16 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 05 Nov 2015 22:15:16 +0100 Subject: [Slackbuilds-users] Libreoffice 5.0.2.2 error Message-ID: <20151105211516.GB1862@jostein> Installing Libreoffice 5.0.2.2 gives this error: LibreOffice_5.0.2.2_Linux_x86-64_rpm/install LibreOffice_5.0.2.2_Linux_x86-64_rpm/readmes/ LibreOffice_5.0.2.2_Linux_x86-64_rpm/readmes/README_en-US no package supplied cpio: premature end of archive libreoffice: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. Anything that needs to be checked here? Jostein From anddt at ukr.net Thu Nov 5 21:30:45 2015 From: anddt at ukr.net (Andrew) Date: Thu, 5 Nov 2015 23:30:45 +0200 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: References: Message-ID: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> On Thu, 05 Nov 2015 21:05:00 +0000 "Ryan P.C. McQuen" wrote: > http://slackbuilds.org/repository/14.1/graphics/blender/ > Repackages binary version. Better rename it to "blender-bin", please. -- WBR, Andrew From ryan.q at linux.com Thu Nov 5 21:46:39 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 05 Nov 2015 21:46:39 +0000 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> References: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> Message-ID: On Thu, Nov 5, 2015 at 1:31 PM Andrew wrote: > On Thu, 05 Nov 2015 21:05:00 +0000 > "Ryan P.C. McQuen" wrote: > > > http://slackbuilds.org/repository/14.1/graphics/blender/ > > Repackages binary version. > Better rename it to "blender-bin", please. > > We followed the same naming scheme as arduino/Arduino: http://slackbuilds.org/repository/14.1/development/arduino/ http://slackbuilds.org/repository/14.1/development/Arduino/ So this does have some precedence. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackph at posteo.de Thu Nov 5 22:20:26 2015 From: slackph at posteo.de (Philip Lacroix) Date: Thu, 05 Nov 2015 23:20:26 +0100 Subject: [Slackbuilds-users] =?utf-8?q?two_blender_packages=3F?= In-Reply-To: References: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> Message-ID: <5e399321980831f1e40c34020f1067c3@posteo.de> 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 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 ambiguities. Just my 2 ?. From chris.willing at iinet.net.au Thu Nov 5 22:49:33 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 6 Nov 2015 08:49:33 +1000 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: <5e399321980831f1e40c34020f1067c3@posteo.de> References: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> <5e399321980831f1e40c34020f1067c3@posteo.de> Message-ID: <563BDCFD.4080108@iinet.net.au> On 06/11/15 08:20, Philip Lacroix wrote: > 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 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 ambiguities. I included such a note in the README when I first submitted the SlackBuild for Blender (built from source code), since it was added some time after the blender SlackBuild (repackaged binary). However that section was cut from the version that was finally published - I guess because the additional notes contained a lot of extra stuff about how to build for maximum functionality (some of which impinged on some SlackBuilds). Perhaps I should update Blender's README with a minimal note about its difference from the blender SlackBuild; then some other file about build optimisations. chris From slackph at posteo.de Thu Nov 5 23:26:54 2015 From: slackph at posteo.de (Philip Lacroix) Date: Fri, 06 Nov 2015 00:26:54 +0100 Subject: [Slackbuilds-users] =?utf-8?q?two_blender_packages=3F?= In-Reply-To: <563BDCFD.4080108@iinet.net.au> References: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> <5e399321980831f1e40c34020f1067c3@posteo.de> <563BDCFD.4080108@iinet.net.au> Message-ID: 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 >> ambiguities. > > I included such a note in the README when I first submitted the > SlackBuild for Blender (built from source code), since it was added > some time after the blender SlackBuild (repackaged binary). However > that section was cut from the version that was finally published - I > guess because the additional notes contained a lot of extra stuff > about how to build for maximum functionality (some of which impinged > on some SlackBuilds). Perhaps I should update Blender's README with a > minimal note about its difference from the blender SlackBuild; then > some other file about build optimisations. Sounds good. I noticed that the packages for Arduino have something like that. The notes in both READMEs could also mention each other's SlackBuilds, in order to make users fully aware of the choice. Philip From chris.willing at iinet.net.au Thu Nov 5 23:51:32 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 6 Nov 2015 09:51:32 +1000 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: References: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> <5e399321980831f1e40c34020f1067c3@posteo.de> <563BDCFD.4080108@iinet.net.au> Message-ID: <563BEB84.90103@iinet.net.au> On 06/11/15 09:26, Philip Lacroix wrote: > 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 >>> ambiguities. >> >> I included such a note in the README when I first submitted the >> SlackBuild for Blender (built from source code), since it was added >> some time after the blender SlackBuild (repackaged binary). However >> that section was cut from the version that was finally published - I >> guess because the additional notes contained a lot of extra stuff >> about how to build for maximum functionality (some of which impinged >> on some SlackBuilds). Perhaps I should update Blender's README with a >> minimal note about its difference from the blender SlackBuild; then >> some other file about build optimisations. > > Sounds good. I noticed that the packages for Arduino have something like > that. The notes in both READMEs could also mention each other's > SlackBuilds, in order to make users fully aware of the choice. I just noticed that the extra info is already in Blender's README.Slackware chris From willysr at slackbuilds.org Fri Nov 6 00:03:56 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 6 Nov 2015 07:03:56 +0700 Subject: [Slackbuilds-users] Libreoffice 5.0.2.2 error In-Reply-To: <20151105211516.GB1862@jostein> References: <20151105211516.GB1862@jostein> Message-ID: > Installing Libreoffice 5.0.2.2 gives this error: > > LibreOffice_5.0.2.2_Linux_x86-64_rpm/install > LibreOffice_5.0.2.2_Linux_x86-64_rpm/readmes/ > LibreOffice_5.0.2.2_Linux_x86-64_rpm/readmes/README_en-US > no package supplied > cpio: premature end of archive > libreoffice: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. Normally that was caused by a corrupted source Try redownloading again Or even better, upgrade to 5.0.3 which was released already -- Willy Sudiarto Raharjo From mralk3 at exitstatusone.com Fri Nov 6 03:01:35 2015 From: mralk3 at exitstatusone.com (MrAlk3) Date: Thu, 05 Nov 2015 20:01:35 -0700 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <90427034.m36ymQkK3t@mothership> On Monday, November 02, 2015 10:34:08 PM Willy Sudiarto Raharjo wrote: > Hi > > I contacted Marco and he no longer maintain his packages, so feel free > to grab and send updates to the following packages > I will be happy to assume maintenance for all of the following. > libraries/Impacket > network/SocksiPy > network/amap > network/corkscrew > network/dsniff > network/hping3 > network/libdnet > network/nikto > network/packit > network/polipo > network/sqlmap > network/w3af > python/pyPdf It doesn't look like anyone has, but please let me know if someone else has already picked one of these up. Thanks, Brenton Earl From jbernts at broadpark.no Fri Nov 6 08:37:20 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Fri, 06 Nov 2015 09:37:20 +0100 Subject: [Slackbuilds-users] Libreoffice 5.0.2.2 error In-Reply-To: References: <20151105211516.GB1862@jostein> Message-ID: <20151106083720.GC1862@jostein> On 06.11.15,07:03, Willy Sudiarto Raharjo wrote: > > > Installing Libreoffice 5.0.2.2 gives this error: > > > > LibreOffice_5.0.2.2_Linux_x86-64_rpm/install > > LibreOffice_5.0.2.2_Linux_x86-64_rpm/readmes/ > > LibreOffice_5.0.2.2_Linux_x86-64_rpm/readmes/README_en-US > > no package supplied > > cpio: premature end of archive > > libreoffice: > > Would you like to continue processing the rest of the > > queue or would you like to abort? If this failed > > package is a dependency of another package in the queue > > then it may not make sense to continue. > > Normally that was caused by a corrupted source > Try redownloading again > Or even better, upgrade to 5.0.3 which was released already > I try to redownload, but gets the same error message. I have sync the repo, but it is still v. 5.0.2.2? Jostein From willysr at slackbuilds.org Fri Nov 6 09:53:33 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 6 Nov 2015 16:53:33 +0700 Subject: [Slackbuilds-users] Libreoffice 5.0.2.2 error In-Reply-To: <20151106083720.GC1862@jostein> References: <20151105211516.GB1862@jostein> <20151106083720.GC1862@jostein> Message-ID: <563C789D.2020605@slackbuilds.org> > I try to redownload, but gets the same error message. I have sync the repo, > but it is still v. 5.0.2.2? 5.0.3 is still in my branch will be part of the next public update -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryan.q at linux.com Fri Nov 6 15:25:46 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 06 Nov 2015 15:25:46 +0000 Subject: [Slackbuilds-users] two blender packages? In-Reply-To: <563BEB84.90103@iinet.net.au> References: <20151105233045.50153ef1bd51a5a08a4f765b@ukr.net> <5e399321980831f1e40c34020f1067c3@posteo.de> <563BDCFD.4080108@iinet.net.au> <563BEB84.90103@iinet.net.au> Message-ID: > Sounds good. I noticed that the packages for Arduino have something like > that. The notes in both READMEs could also mention each other's > SlackBuilds, in order to make users fully aware of the choice. Note added to 'blender'. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackph at posteo.de Fri Nov 6 16:21:49 2015 From: slackph at posteo.de (Philip Lacroix) Date: Fri, 06 Nov 2015 17:21:49 +0100 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <90510a026bd03abdb355070f4b4445cb@posteo.de> 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 idle since 2007 (1.5.2), but it was forked on GitHub and a small team has been continuing development: https://github.com/mackyle/xar Their latest release is xar-1.6.1 (2012), they made some bug fixes and enhancements, so I was thinking about updating the SlackBuild with this one. Looks good so far, at least from a user's point of view. Anyone looked at this fork? I'm interested in what you guys think about it. Philip From johannes.georgi at georgi-enterprises.eu Fri Nov 6 19:01:37 2015 From: johannes.georgi at georgi-enterprises.eu (Johannes Georgi) Date: Fri, 06 Nov 2015 20:01:37 +0100 Subject: [Slackbuilds-users] morituri - lsb_release Message-ID: Hello, I installed morituri today from SBo and it does not run > morituri.extern.deps.distro.DistroException: lsb_release binary not found is this an overlooked dependency? I there even a Slackware package providing lsb_release? Also the optional dependency in the readme should be "pycdio" not "pycdaudio". Greetings, Johannes From willysr at slackbuilds.org Fri Nov 6 19:09:56 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Nov 2015 02:09:56 +0700 Subject: [Slackbuilds-users] luna-wallpapers error In-Reply-To: <20151105211311.GA1862@jostein> References: <20151105211311.GA1862@jostein> Message-ID: <563CFB04.1040206@slackbuilds.org> > Installing luna-wallpapers now gives this error: > > ssing luna-wallpapers > luna-wallpapers: > Found luna-wallpapers.tar.gz in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for luna-wallpapers.tar.gz ... OK > luna-wallpapers not found in /var/cache/sbopkg. > --2015-11-05 22:12:06-- > https://launchpad.net/~elementary-os/+archive/ubuntu/daily/+files/elementary-wallpapers_0.1.4-0%7E42%7Eubuntu0.3.1.tar.gz > Resolving launchpad.net (launchpad.net)... 91.189.89.223, 91.189.89.222 > Connecting to launchpad.net (launchpad.net)|91.189.89.223|:443... connected. > HTTP foresp?rsel sendt, mottar topptekster... 404 Not Found > 2015-11-05 22:12:06 FEIL 404: Not Found. grab them here http://slackware.org.uk/microlinux/desktop-14.1-source/luna-wallpapers/elementary-wallpapers_0.1.4-0~42~ubuntu0.3.1.tar.gz -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mralk3 at exitstatusone.com Fri Nov 6 21:47:47 2015 From: mralk3 at exitstatusone.com (MrAlk3) Date: Fri, 06 Nov 2015 14:47:47 -0700 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <1796224.XMUu8KQTOj@mothership> On Monday, November 02, 2015 10:34:08 PM Willy Sudiarto Raharjo wrote: > Hi > > I contacted Marco and he no longer maintain his packages, so feel free > to grab and send updates to the following packages > I will also take: > libraries/libnids Let me know if anyone else has picked this one up already. Thanks, Brenton Earl From willysr at slackbuilds.org Sat Nov 7 03:46:24 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Nov 2015 10:46:24 +0700 Subject: [Slackbuilds-users] Updates - 20151107.1 Message-ID: <563D7410.3070007@slackbuilds.org> Sat Nov 7 03:34:36 UTC 2015 academic/gcompris: Updated for version 15.10. academic/wxmacmolplt: Update DOWNLOAD url. accessibility/xdotool: Update DEP. audio/tap_plugins: Updated for version 0.7.3, add desktop/setcap. audio/zita-ajbridge: Updated for version 0.6.0. desktop/luna-wallpapers: Update DOWNLOAD url. desktop/ssr: Updated for version 0.3.6. development/bas55: Updated for version 1.05. development/gnuradio: Updated for version 3.7.5.1. development/lazarus: Updated for version 1.4.4. development/monodevelop-database: Add patch. development/neovim: Updated for version 0.1.0. development/portaudio: Updated for version v19_20140130. development/qt-creator3: Updated for version 3.5.1. development/re2c: Updated for version 0.14.3. development/rust: Updated for version 1.4.0. development/vstudio: Updated for version 6.0.13. development/zed: Fix build issues. games/hedgewars: Updated for version 0.9.22. games/mgba: Updated for version 0.3.1. graphics/CairoSVG: Updated for version 1.0.19. graphics/blender: Add note about other Blender. graphics/tesseract: Updated for version 3.04.00. libraries/c++-gtk-utils: Updated for version 2.0.29. libraries/hdf5: Updated for version 1.8.15_patch1. libraries/libevhtp: Updated for version 1.2.11. libraries/libnids: New maintainer. libraries/libsodium: Updated for version 1.0.5. libraries/live555: Updated for version 2015.10.29. libraries/nltk: Updated for version 3.1 + new maintainer. libraries/reportlab: Updated for version 3.2.0. libraries/tcllib: Updated for version 1.17. multimedia/TeamSpeak3: Updated for version 3.0.18.2. multimedia/kdenlive: Fix locale. multimedia/lwks: Update DEP. multimedia/smplayer: Updated for version 15.9.0. multimedia/smtube: Updated for version 15.9.0. network/ClusterSSH: Updated for version 4.04. network/Electrum: Updated for version 2.5.2. network/SocksiPy: New maintainer. network/amap: New maintainer. network/bozohttpd: Update DOWNLOAD url and remove DEP. network/clipgrab: Updated for version 3.5.2. network/corkscrew: New maintainer. network/davmail: Added (Mail Gateway). network/deluge: Updated for version 1.3.12 + new maintainer. network/dsniff: New maintainer. network/google-cli: Update script. network/haproxy: Updated for version 1.6.1. network/iojs: Updated for version 4.2.2. network/jabberd2: Fix startup script. network/pentadactyl: Updated to work with Firefox 42. network/pyzor: Updated for version 1.0.0. network/skylable-sx: Updated for version 1.2. network/telegram: Updated for version 0.9.10. network/vivaldi: Updated for version 1.0.303.48_1. network/you-get: Updated for version 0.4.125. network/youtube-dl: Updated for version 2015.11.02. office/ProjectLibre: Updated for version 1.6.2. office/impressive: Update DEP. office/libreoffice-helppack: Updated for version 5.0.3. office/libreoffice-langpack: Updated for version 5.0.3. office/libreoffice: Updated for version 5.0.3. office/pdf2djvu: Updated for version 0.9.2. perl/Net-SSLeay: Updated for version 1.72 + new maintainer. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.023. perl/perl-IO-Socket-SSL: Updated for version 2.020 + new maintainer. perl/perl-NetAddr-IP: Updated for version 4.078. perl/perl-Sidef: Updated for version 2.10. perl/perl-tk: Updated for version 804.033. perl/perl-tree-dagnode: Updated for version 1.27. python/py3cairo: Fix building with the newer python. python/pyliblo: Updated for version 0.10.0. python/regex: Updated for version 2015.10.29. ruby/heroku-client: Updated for version 3.41.5. system/anything-sync-daemon: Updated for version 5.76. system/autojump: Updated for version 22.2.4. system/gnu-unifont: Updated for version 8.0.01. system/lxdm: Updated for version 0.5.2. system/pcsc-tools: Updated for version 1.4.24. system/srm: Updated for version 1.2.15 + new maintainer. system/swatch: Updated for version 3.2.4. system/unp: Updated for version 2.0~pre7+nmu1. system/uptimed: Updated for version 0.4.0. system/xar: Updated for version 1.6.1 + New maintainer. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From thedoogster at gmail.com Sat Nov 7 04:38:25 2015 From: thedoogster at gmail.com (Doogster) Date: Fri, 6 Nov 2015 20:38:25 -0800 Subject: [Slackbuilds-users] morituri - lsb_release In-Reply-To: References: Message-ID: "Overlooked dependency" sounds right, but I'm going to need your help to look into this.What is the command to make this happen, and what is the full console log? ( really hope it's more than just that one line!). I just tried to reproduce this in a chroot, and I couldn't do it. On Fri, Nov 6, 2015 at 11:01 AM, Johannes Georgi wrote: > Hello, > I installed morituri today from SBo and it does not run > >> morituri.extern.deps.distro.DistroException: lsb_release binary not found > > > is this an overlooked dependency? I there even a Slackware package providing > lsb_release? > > Also the optional dependency in the readme should be "pycdio" not > "pycdaudio". > > Greetings, Johannes > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From mralk3 at exitstatusone.com Sat Nov 7 04:50:41 2015 From: mralk3 at exitstatusone.com (MrAlk3) Date: Fri, 06 Nov 2015 21:50:41 -0700 Subject: [Slackbuilds-users] Marco Boneti's Packages In-Reply-To: <56378270.6090206@slackbuilds.org> References: <56378270.6090206@slackbuilds.org> Message-ID: <3306714.fgP4ula3CL@mothership> On Monday, November 02, 2015 10:34:08 PM Willy Sudiarto Raharjo wrote: > libraries/libwhisker2 I will assume maintenance of libwhisker2 as well since it's a dependency of nikto. Thanks, Brenton Earl From thedoogster at gmail.com Sat Nov 7 10:44:14 2015 From: thedoogster at gmail.com (Doogster) Date: Sat, 7 Nov 2015 02:44:14 -0800 Subject: [Slackbuilds-users] morituri - lsb_release In-Reply-To: References: Message-ID: On Sat, Nov 7, 2015 at 12:36 AM, Johannes Georgi wrote: > Hi Dugan, > I hope I gathered everything relevant... > > > $ ls /var/log/packages | grep ... > cdparanoia-III_10.2-x86_64-1 > gst-python-0.10.22-x86_64-2_SBo > libcdio-0.83-x86_64-1 > pycdio-0.20-x86_64-1_SBo > gstreamer-0.10.36-x86_64-2 > gstreamer-compat32-0.10.36-x86_64-2compat32 > phonon-gstreamer-4.6.3-x86_64-1 > cdrdao-1.2.3-x86_64-2 > > $ rip cd rip > WARNING: using default offset 0. > Install pycdio and run 'rip offset find' to detect your drive's offset. > Checking device /dev/sr0 > CDDB disc id: XXXXXXXXXXX > MusicBrainz disc idXXXXXXXXXXXXXXXXXXXx > MusicBrainz lookup URL XXXXXXXXXXXXXXXXXXXXXXX > Disc duration: 00:47:42.XXX, 15 audio tracks > Error: NotFoundException(ResponseError(),) > Continuing without metadata > Submit this disc to MusicBrainz at the above URL. > > Could not import python module 'CDDB' > This module is part of python-CDDB. > See http://cddb-py.sourceforge.net/ for more information. > > Traceback (most recent call last): > File "/usr/bin/rip", line 41, in > sys.exit(main.main(sys.argv[1:])) > File "/usr/lib/python2.7/site-packages/morituri/rip/main.py", line 50, in > main > h.handleImportError(e) > File "/usr/lib/python2.7/site-packages/morituri/extern/deps/deps.py", line > 128, in handleImportError > self.handleMissingDependency(dep) > File "/usr/lib/python2.7/site-packages/morituri/extern/deps/deps.py", line > 148, in handleMissingDependency > d = distro.getDistroFromRelease() > File "/usr/lib/python2.7/site-packages/morituri/extern/deps/distro.py", > line 74, in getDistroFromRelease > raise DistroException('lsb_release binary not found') > morituri.extern.deps.distro.DistroException: lsb_release binary not found > EOF > > distro.py from line 62: > def getDistroFromRelease(): > """ > Decide on the distro based on the presence of a distro-specific release > file. > > rtype: L{Distro} or None. > """ > # start with lsb_release > (status, output) = commands.getstatusoutput("lsb_release -i") > if os.WIFEXITED(status): > ret = os.WEXITSTATUS(status) > if ret == 127: > raise DistroException('lsb_release binary not found') > EOF > > if I can provide any more, mail me > THANK YOU > > PS: sorry for not setting the email header reference, I have the list on > digest. Replying to the list instead of directly to Johannes this time. The missing dependency looks like it might be cddb-py from SBo. Could you please try installing that and running "rip" again? From slackalaxy at gmail.com Sat Nov 7 16:38:15 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Sat, 7 Nov 2015 18:38:15 +0200 Subject: [Slackbuilds-users] place to host problematic sources? Message-ID: Hi to all. Some of my SlackBuilds have 'problematic' sources: unversioned (so MD5SUm changes), become unavailable from time to time or the site upstream is dead. What would you recommend? I started using Dropbox to host these, but is there a smarter solution? May be register at Sourceforge and host there, similarly to http://sourceforge.net/projects/slackbuildsdirectlinks/files/ ? I will appreciate any suggestions. bye Petar PS: it's great we now have the SBo sources archive! -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Sat Nov 7 17:13:18 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 07 Nov 2015 17:13:18 +0000 Subject: [Slackbuilds-users] place to host problematic sources? In-Reply-To: References: Message-ID: On Sat, Nov 7, 2015 at 9:07 AM Petar Petrov wrote: > Hi to all. > > > Some of my SlackBuilds have 'problematic' sources: unversioned (so MD5SUm > changes), become unavailable from time to time or the site upstream is dead. > > What would you recommend? I started using Dropbox to host these, but is > there a smarter solution? May be register at Sourceforge and host there, > similarly to http://sourceforge.net/projects/slackbuildsdirectlinks/files/ > ? > Give me your SF username and I will add you to SBo direct links. :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Sat Nov 7 21:03:20 2015 From: thedoogster at gmail.com (Doogster) Date: Sat, 7 Nov 2015 13:03:20 -0800 Subject: [Slackbuilds-users] morituri - lsb_release In-Reply-To: References: Message-ID: Replying to slackbuilds-users instead of directly to Johannes. Yeah, I agree with your conclusion that at this point, there's not much else that can be done. I've submitted a new version to SBo that adds pysetuptools and cddb-py as hard dependencies. On Sat, Nov 7, 2015 at 12:14 PM, Johannes Georgi wrote: > Hi Dugan! > >> The missing dependency looks like it might be cddb-py from SBo. Could you >> please try installing that and running "rip" again? > > > I did that, assuming I would not need to rebuild morituri. (Rebuilt it later > which did not change anything noticeable.) > The python stacktrace error message went away, but it still won't rip > anything. > > I got this: > $ LC_ALL=en_US rip cd rip > WARNING: using default offset 0. > Install pycdio and run 'rip offset find' to detect your drive's offset. > Checking device /dev/sr0 > CDDB disc id: X > MusicBrainz disc id X > MusicBrainz lookup URL X > Disc duration: 00:48:30.X, 13 audio tracks > Error: NotFoundException(ResponseError(),) > Continuing without metadata > Submit this disc to MusicBrainz at the above URL. > > FreeDB identifies disc as X > eject: unable to eject, last error: Inappropriate ioctl for device > EOF > > with sudo it just ejected the CD after this, without ripping it. This also > happens when I use the -R switch. > > I compared the track start sector offset numbers that morituri used to id > the release on MusicBrainz with those MusicBrainz had for that CD, and > noticed a skew that gets larger the farther behind the track is, so I > started suspecting that my my drive just "swallows" some single sectors. > (???) Its firmware is somewhat broken anyway since I reflashed it with an > unofficial one and couldn't undo that. (That was > 10 years ago for this > hack where you had to write DVD-ROM as disc id on video DVDs in order for > some hardware players to accept them.) OTOH it should take the offsets from > the TOC, right? > > fyi: The reason for wanting to use morituri was that I wanted to read a very > scratched audio cd ddrescue-style, and had read that ddrescue does not work > on audio cds and to use morituri. But today for testing I used two clean, > factory-made Audio CDs. > > Anyways this begins to look like the error is not really related to morituri > or the SlackBuild. > > Thanks for you efforts! > Greetings, Johannes > > Appendix: > with the -U switch to 'rip cd rip' I get this error, which seems to suggest > a bug in morituri (for that switch): >> >> -U, --unknown whether to continue ripping if the CD is unknown > > $ rip cd rip -U > WARNING: using default offset 0. > Install pycdio and run 'rip offset find' to detect your drive's offset. > Checking device /dev/sr0 > CDDB disc id: X > MusicBrainz disc id X > MusicBrainz lookup URL X > Disc duration: 00:48:30.X, 13 audio tracks > Error: NotFoundException(ResponseError(),) > Continuing without metadata > Submit this disc to MusicBrainz at the above URL. > > FreeDB identifies disc as X > Traceback (most recent call last): > File "/usr/bin/rip", line 41, in > sys.exit(main.main(sys.argv[1:])) > File "/usr/lib/python2.7/site-packages/morituri/rip/main.py", line 45, in > main > ret = c.parse(argv) > File "/usr/lib/python2.7/site-packages/morituri/rip/main.py", line 123, in > parse > logcommand.LogCommand.parse(self, argv) > File > "/usr/lib/python2.7/site-packages/morituri/extern/command/command.py", line > 401, in parse > return self.subCommands[command].parse(args[1:]) > File > "/usr/lib/python2.7/site-packages/morituri/extern/command/command.py", line > 401, in parse > return self.subCommands[command].parse(args[1:]) > File > "/usr/lib/python2.7/site-packages/morituri/extern/command/command.py", line > 363, in parse > ret = self.do(args) > File "/usr/lib/python2.7/site-packages/morituri/rip/cd.py", line 126, in > do > self.program.metadata.discid = self.ittoc.getMusicBrainzDiscId() > AttributeError: 'NoneType' object has no attribute 'discid' > EOF From thedoogster at gmail.com Sat Nov 7 21:23:52 2015 From: thedoogster at gmail.com (Doogster) Date: Sat, 7 Nov 2015 13:23:52 -0800 Subject: [Slackbuilds-users] morituri - lsb_release In-Reply-To: References: Message-ID: And for the -U switch crash, it's #89 in their GitHub issues. I've submitted new SlackBuild that applies a patch to fix that. Would you like to try it out? https://www.dropbox.com/s/q4r2inae39or96o/morituri.tar.bz2?dl=0 On Sat, Nov 7, 2015 at 12:14 PM, Johannes Georgi wrote: > Hi Dugan! > >> The missing dependency looks like it might be cddb-py from SBo. Could you >> please try installing that and running "rip" again? > > > I did that, assuming I would not need to rebuild morituri. (Rebuilt it later > which did not change anything noticeable.) > The python stacktrace error message went away, but it still won't rip > anything. > > I got this: > $ LC_ALL=en_US rip cd rip > WARNING: using default offset 0. > Install pycdio and run 'rip offset find' to detect your drive's offset. > Checking device /dev/sr0 > CDDB disc id: X > MusicBrainz disc id X > MusicBrainz lookup URL X > Disc duration: 00:48:30.X, 13 audio tracks > Error: NotFoundException(ResponseError(),) > Continuing without metadata > Submit this disc to MusicBrainz at the above URL. > > FreeDB identifies disc as X > eject: unable to eject, last error: Inappropriate ioctl for device > EOF > > with sudo it just ejected the CD after this, without ripping it. This also > happens when I use the -R switch. > > I compared the track start sector offset numbers that morituri used to id > the release on MusicBrainz with those MusicBrainz had for that CD, and > noticed a skew that gets larger the farther behind the track is, so I > started suspecting that my my drive just "swallows" some single sectors. > (???) Its firmware is somewhat broken anyway since I reflashed it with an > unofficial one and couldn't undo that. (That was > 10 years ago for this > hack where you had to write DVD-ROM as disc id on video DVDs in order for > some hardware players to accept them.) OTOH it should take the offsets from > the TOC, right? > > fyi: The reason for wanting to use morituri was that I wanted to read a very > scratched audio cd ddrescue-style, and had read that ddrescue does not work > on audio cds and to use morituri. But today for testing I used two clean, > factory-made Audio CDs. > > Anyways this begins to look like the error is not really related to morituri > or the SlackBuild. > > Thanks for you efforts! > Greetings, Johannes > > Appendix: > with the -U switch to 'rip cd rip' I get this error, which seems to suggest > a bug in morituri (for that switch): >> >> -U, --unknown whether to continue ripping if the CD is unknown > > $ rip cd rip -U > WARNING: using default offset 0. > Install pycdio and run 'rip offset find' to detect your drive's offset. > Checking device /dev/sr0 > CDDB disc id: X > MusicBrainz disc id X > MusicBrainz lookup URL X > Disc duration: 00:48:30.X, 13 audio tracks > Error: NotFoundException(ResponseError(),) > Continuing without metadata > Submit this disc to MusicBrainz at the above URL. > > FreeDB identifies disc as X > Traceback (most recent call last): > File "/usr/bin/rip", line 41, in > sys.exit(main.main(sys.argv[1:])) > File "/usr/lib/python2.7/site-packages/morituri/rip/main.py", line 45, in > main > ret = c.parse(argv) > File "/usr/lib/python2.7/site-packages/morituri/rip/main.py", line 123, in > parse > logcommand.LogCommand.parse(self, argv) > File > "/usr/lib/python2.7/site-packages/morituri/extern/command/command.py", line > 401, in parse > return self.subCommands[command].parse(args[1:]) > File > "/usr/lib/python2.7/site-packages/morituri/extern/command/command.py", line > 401, in parse > return self.subCommands[command].parse(args[1:]) > File > "/usr/lib/python2.7/site-packages/morituri/extern/command/command.py", line > 363, in parse > ret = self.do(args) > File "/usr/lib/python2.7/site-packages/morituri/rip/cd.py", line 126, in > do > self.program.metadata.discid = self.ittoc.getMusicBrainzDiscId() > AttributeError: 'NoneType' object has no attribute 'discid' > EOF From slackalaxy at gmail.com Sun Nov 8 12:32:13 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 8 Nov 2015 14:32:13 +0200 Subject: [Slackbuilds-users] Anyone wants QtiPlot? Message-ID: Hi! Is anyone interested in taking the maintenance of QtiPlot, as well as it's dependencies alglib, muParser, tamu_anova and qt-assistant-compat? I rarely use it and I believe someone else may actually do a better job. I _will_ continue maintaining the above entries if noone wants to take them. bye Petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Sun Nov 8 23:39:57 2015 From: yalhcru at gmail.com (B Watson) Date: Sun, 8 Nov 2015 18:39:57 -0500 Subject: [Slackbuilds-users] webkitgtk needs its -j1 back? Message-ID: http://slackbuilds.org/cgit/slackbuilds/commit/libraries/webkitgtk?id=5fba3a487717f55eb8c6f0ea6f45647e8c884f64 That commit removed the -j1 from the make command... I'm trying to build using the script that's in the repo now, version 2.4.9, and it fails pretty early on in the build process without the -j1. I'm on Slackware64 14.1, no multilib. I have MAKEFLAGS=-j8 set in the environment. I've got make-3.82-x86_64-4 installed (which is the version on the DVD) and I don't see an updated make in 14.1's patches/ dir. From yalhcru at gmail.com Mon Nov 9 06:41:03 2015 From: yalhcru at gmail.com (B Watson) Date: Mon, 9 Nov 2015 01:41:03 -0500 Subject: [Slackbuilds-users] zita-ajbridge 0.6.0 Message-ID: Does anyone else use zita-ajbridge? I'm the maintainer, and I'm seriously considering reverting to 0.4.0 (I just upgraded it to 0.6.0 last week). Before I submitted the update, I did minimal testing, basically just checked whether or not it worked, let it run for a few seconds, called it good. It turns out that 0.6.0 fails after a few minutes runtime... but I only have one system available to test it on [*]. So I'd like to know: - Did anyone else have problems after upgrading to 0.6.0? - Did anyone have problems with 0.4.0 that were fixed by upgrading to 0.6.0? [*] Before anyone asks, no, zita-ajbridge can't be usefully tested on a VM. There's no place to plug in a guitar (or microphone, etc) on a VM, other that the hosts's sound hardware (which might be the case of the problem)... and getting the jack-audio realtime stuff to work correctly in a VM is a nightmare I don't care to revisit. From hostmaster at slackonly.com Mon Nov 9 15:46:52 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Mon, 9 Nov 2015 17:46:52 +0200 Subject: [Slackbuilds-users] gnuradio version Message-ID: <5640BFEC.1010105@slackonly.com> Hi!, In gnuradio version showing as 3.7.5.1 instead from 3.7.8.1 Thanks. From willysr at slackbuilds.org Mon Nov 9 15:53:16 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 9 Nov 2015 22:53:16 +0700 Subject: [Slackbuilds-users] gnuradio version In-Reply-To: <5640BFEC.1010105@slackonly.com> References: <5640BFEC.1010105@slackonly.com> Message-ID: <5640C16C.2060400@slackbuilds.org> > In gnuradio version showing as 3.7.5.1 instead from 3.7.8.1 Fixed -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slackalaxy at gmail.com Tue Nov 10 11:25:51 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 10 Nov 2015 13:25:51 +0200 Subject: [Slackbuilds-users] Future of QtiPlot Message-ID: Hi to all, A new version of QtiPlot (0.9.9) is out. I was hoping that it would build on -current. However, the source code is not available. I contacted the developer, Ion Vasilief, and it seems that it will not be made public anytime soon. here's a quote from our conversation: --- > where can I download the source code of QtiPlot 0.9.9? From nowhere. For the moment you cann't, the source code for the latest QtiPlot version will be made available in a few years. The license has changed, no longer GPL. --- So, guys. What would you advise me to do? We can stick with the last version (0.9.8.9) that is GPL (already quite old, released in 2011) and I can try to keep it buildable in the future. In principle, I do not mind maintaining a SlackBuild for 'abandoned' source. However, QtiPlot is not all that trivial to build and I am afraid that I lack the skills to fix future issues. May be it's time to look for an alternative, like ScidaVis? http://scidavis.sourceforge.net/about.html It looks similar and IIRC it was forked from QtiPlot. The latest version is from this year and the license is GPL. I will appreciate any suggestions. bye Petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Nov 10 12:37:26 2015 From: yalhcru at gmail.com (B Watson) Date: Tue, 10 Nov 2015 07:37:26 -0500 Subject: [Slackbuilds-users] Future of QtiPlot In-Reply-To: References: Message-ID: On 11/10/15, Petar Petrov wrote: > A new version of QtiPlot (0.9.9) is out. I was hoping that it would build > on -current. However, the source code is not available. I contacted the > developer, Ion Vasilief, and it seems that it will not be made public > anytime soon. There's no rule that says everything on SBo has to be GPL or open source. Does the new closed-source version work? You could do a binary repackage, if you wanted to. From slackalaxy at gmail.com Tue Nov 10 12:42:05 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 10 Nov 2015 14:42:05 +0200 Subject: [Slackbuilds-users] Future of QtiPlot In-Reply-To: References: Message-ID: the only binary available is a DEMO for 32bit. in the past the precompiled version of QTiPlot for Linux was also 32bit and lacked features. Also, every time you would start the program it asked you to support the project or something. Therefore I decided to do things the hard way and compile it from source. 2015-11-10 14:37 GMT+02:00 B Watson : > On 11/10/15, Petar Petrov wrote: > > > A new version of QtiPlot (0.9.9) is out. I was hoping that it would build > > on -current. However, the source code is not available. I contacted the > > developer, Ion Vasilief, and it seems that it will not be made public > > anytime soon. > > There's no rule that says everything on SBo has to be GPL or open > source. Does the new closed-source version work? You could do a binary > repackage, if you wanted to. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Nov 10 12:58:06 2015 From: yalhcru at gmail.com (B Watson) Date: Tue, 10 Nov 2015 07:58:06 -0500 Subject: [Slackbuilds-users] Future of QtiPlot In-Reply-To: References: Message-ID: On 11/10/15, Petar Petrov wrote: > the only binary available is a DEMO for 32bit. in the past the precompiled > version of QTiPlot for Linux was also 32bit and lacked features. Also, > every time you would start the program it asked you to support the project > or something. Therefore I decided to do things the hard way and compile it > from source. Ah, nevermind. Nagware and crippled demos suck. I haven't got a horse in this race (never even heard of qtiplot before now), but... is the "abandoned" version OK? Does it work, is it useful? Just because something is "old" doesn't mean it's bad. From slackalaxy at gmail.com Tue Nov 10 13:02:23 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 10 Nov 2015 15:02:23 +0200 Subject: [Slackbuilds-users] Future of QtiPlot In-Reply-To: References: Message-ID: it works on 14.1 for -current, people are experiencing problems when trying to build... check this post (and before) at LQ: http://www.linuxquestions.org/questions/slackware-14/that-which-could-be-fixed-in-sbo-thread-4175532869/page21.html#post5446862 i have not had the time to try and find a fix for it on -current. Today i saw the new version was released and was hoping it would build easier. 2015-11-10 14:58 GMT+02:00 B Watson : > On 11/10/15, Petar Petrov wrote: > > the only binary available is a DEMO for 32bit. in the past the > precompiled > > version of QTiPlot for Linux was also 32bit and lacked features. Also, > > every time you would start the program it asked you to support the > project > > or something. Therefore I decided to do things the hard way and compile > it > > from source. > > Ah, nevermind. Nagware and crippled demos suck. > > I haven't got a horse in this race (never even heard of qtiplot > before now), but... is the "abandoned" version OK? Does it work, is it > useful? Just because something is "old" doesn't mean it's bad. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From igor29768 at gmail.com Wed Nov 11 16:25:44 2015 From: igor29768 at gmail.com (Igor Drozdovsky) Date: Wed, 11 Nov 2015 17:25:44 +0100 Subject: [Slackbuilds-users] SlackBuild for dvisvgm Message-ID: Hello, I have a few comments on the Slack Build files for the dvisvgm (DVI to SVG converter), as a standalone package in graphics/: - dvisvgm.info points to a broken download link of its source. In fact, this old release is at http://sourceforge.net/projects/dvisvgm/files/dvisvgm/old-releases/1.4/dvisvgm-1.4.tar.gz Besides, the current version 1.11 is available at https://github.com/mgieseki/dvisvgm/releases/download/1.11/dvisvgm-1.11.tar.gz, which appears to build and run well. - doinst.sh of the package requests to run a non-existent gconf config source "blah.schemas". - dvisvgm.SlackBuild attempts to make symbolic links outside of the installation package > ln -s /usr/share/texmf/include/kpathsea /usr/include/kpathsea > ln -s /usr/share/texmf/lib/libkpathsea.a > /usr/lib${LIBDIRSUFFIX}/libkpathsea.a > ln -s /usr/share/texmf/lib/libkpathsea.la /usr/lib${LIBDIRSUFFIX}/ > libkpathsea.la > I am aware that dvisvgm is also a part of texlive-20140525, but that version 1.6 is also rather old. Here is, for example, my revised version of the dvisvgm Slackware build files: https://github.com/igorek7/SlackBuilds/tree/master/dvisvgm Cheers, Igor -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Nov 11 16:31:31 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 11 Nov 2015 23:31:31 +0700 Subject: [Slackbuilds-users] SlackBuild for dvisvgm In-Reply-To: References: Message-ID: <56436D63.5040000@slackbuilds.org> > I have a few comments on the Slack Build files for the > dvisvgm (DVI to SVG converter), as a standalone package in graphics/: > > > - dvisvgm.info points to a broken download link of its source. > In fact, this old release is at > http://sourceforge.net/projects/dvisvgm/files/dvisvgm/old-releases/1.4/dvisvgm-1.4.tar.gz > Besides, the current version 1.11 > is available at > https://github.com/mgieseki/dvisvgm/releases/download/1.11/dvisvgm-1.11.tar.gz, > > which appears to build and run well. > - doinst.sh of the package requests to run a non-existent gconf config > source "blah.schemas". > - dvisvgm.SlackBuild attempts to make symbolic links outside of the > installation package > >> ln -s /usr/share/texmf/include/kpathsea /usr/include/kpathsea >> ln -s /usr/share/texmf/lib/libkpathsea.a >> /usr/lib${LIBDIRSUFFIX}/libkpathsea.a >> ln -s /usr/share/texmf/lib/libkpathsea.la /usr/lib${LIBDIRSUFFIX}/ >> libkpathsea.la It's already fixed on my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mralk3 at exitstatusone.com Thu Nov 12 00:06:40 2015 From: mralk3 at exitstatusone.com (MrAlk3) Date: Wed, 11 Nov 2015 17:06:40 -0700 Subject: [Slackbuilds-users] Update w3af 1.0 to w3af 1.6.49 Message-ID: <2351479.VtKzG3rRyv@mothership> Hello, Just last week I picked up maintenance of w3af. I'm working on updating w3af to version 1.6.49. There is a significant list of dependencies missing from SBo to be able to install 1.6.49. Still not sure if I have identified all the dependencies. I am relatively new still as a SlackBuilds maintainer, and I have not maintained software for any Linux distro in the past. I need a bit of advice on how to proceed further into this little project. Here is the ticket I am using to track my progress on Github: https://github.com/BrentonEarl/es1-slackware-stuff/issues/3 I've made a separate branch for w3af as well, here: https://github.com/BrentonEarl/es1-slackware-stuff/tree/w3af-1.6.49 Should I create SlackBuilds for all the python modules required for w3af? Is it possible to have pip install the missing dependencies from within the w3af.SlackBuild script? Or is this against SBo policiy? I would like to maintain w3af, but it is proving to be more demanding than I originally thought it would be. Guidance from someone with more experience as a SBo maintainer would be welcome. I am not asking for anyone to do the work for me, just some ideas as to what path I should take. Thanks, Brenton Earl From willysr at slackbuilds.org Thu Nov 12 00:15:23 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 12 Nov 2015 07:15:23 +0700 Subject: [Slackbuilds-users] Update w3af 1.0 to w3af 1.6.49 In-Reply-To: <2351479.VtKzG3rRyv@mothership> References: <2351479.VtKzG3rRyv@mothership> Message-ID: <5643DA1B.1050208@slackbuilds.org> > Should I create SlackBuilds for all the python modules required for w3af? Yes :) > Is it possible to have pip install the missing dependencies from within the > w3af.SlackBuild script? Or is this against SBo policiy? No, we do not allow pip or git command inside the script everything must be satisfied using REQUIRES you can start by adding the python modules required by newer w3af and when you think you have them all, you can finally upgrade w3af. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mralk3 at exitstatusone.com Thu Nov 12 00:52:39 2015 From: mralk3 at exitstatusone.com (Brenton Earl) Date: Wed, 11 Nov 2015 17:52:39 -0700 Subject: [Slackbuilds-users] Update w3af 1.0 to w3af 1.6.49 In-Reply-To: <5643DA1B.1050208@slackbuilds.org> References: <2351479.VtKzG3rRyv@mothership> <5643DA1B.1050208@slackbuilds.org> Message-ID: Ok, that's what I figured. Just trying to be thorough. Thanks, Brenton Earl On Nov 11, 2015 5:15 PM, "Willy Sudiarto Raharjo" wrote: > > Should I create SlackBuilds for all the python modules required for w3af? > > Yes :) > > > Is it possible to have pip install the missing dependencies from within > the > > w3af.SlackBuild script? Or is this against SBo policiy? > > No, we do not allow pip or git command inside the script > everything must be satisfied using REQUIRES > > you can start by adding the python modules required by newer w3af and > when you think you have them all, you can finally upgrade w3af. > > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbernts at broadpark.no Thu Nov 12 06:54:57 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 12 Nov 2015 07:54:57 +0100 Subject: [Slackbuilds-users] Libreoffice 5.0.2.2 error In-Reply-To: <563C789D.2020605@slackbuilds.org> References: <20151105211516.GB1862@jostein> <20151106083720.GC1862@jostein> <563C789D.2020605@slackbuilds.org> Message-ID: <20151112065457.GB17417@jostein> On 06.11.15,16:53, Willy Sudiarto Raharjo wrote: > > I try to redownload, but gets the same error message. I have sync the repo, > > but it is still v. 5.0.2.2? > > 5.0.3 is still in my branch > will be part of the next public update > I still get the same error message when installing the new version. Jostein From jbernts at broadpark.no Thu Nov 12 06:56:26 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 12 Nov 2015 07:56:26 +0100 Subject: [Slackbuilds-users] (no subject) Message-ID: <20151112065626.GC17417@jostein> The new version of ncmpcpp is now on v. 0.6.7 while the repo version is at 0.5.10. Should this be updated? Jostein From yalhcru at gmail.com Thu Nov 12 07:37:15 2015 From: yalhcru at gmail.com (B Watson) Date: Thu, 12 Nov 2015 02:37:15 -0500 Subject: [Slackbuilds-users] find/chmod revisited Message-ID: I've always known the template code that sanitizes the source permissions is a bit slow... for mame, it takes a full minute to execute (using tmpfs for TMP), since there are over 18 thousand files/dirs in the mame src. find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; ...executes one chmod process for each file/dir it finds. For mame: $ find /tmp/mame-mame0167/|wc -l 18664 That's a lot of child processes! So I thought "maybe I can use xargs and cut the time down some". Result is this: find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -print0 | \ xargs -0 chmod 755 find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -print0 | \ xargs -0 chmod 644 ...which (on tmpfs) executes so fast I can't measure it accurately. Maybe the template code could be updated? mame isn't the only build that is affected by this. Anything with lots of files will be noticeably faster with this change. From ricardo at palmtx.com.ar Thu Nov 12 15:42:00 2015 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 12 Nov 2015 12:42:00 -0300 Subject: [Slackbuilds-users] find/chmod revisited In-Reply-To: References: Message-ID: <201511121242.00693.ricardo@palmtx.com.ar> El Jueves 12/11/2015, B Watson escribi?: > I've always known the template code that sanitizes the source permissions > is a bit slow... for mame, it takes a full minute to execute (using tmpfs > for TMP), since there are over 18 thousand files/dirs in the mame src. > > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > > ...executes one chmod process for each file/dir it finds. For mame: > > $ find /tmp/mame-mame0167/|wc -l > 18664 > > That's a lot of child processes! So I thought "maybe I can use xargs > and cut the time down some". Result is this: > > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -print0 | \ > xargs -0 chmod 755 > find -L . \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -print0 | \ > xargs -0 chmod 644 > > ...which (on tmpfs) executes so fast I can't measure it accurately. > > Maybe the template code could be updated? mame isn't the only build > that is affected by this. Anything with lots of files will be noticeably > faster with this change. And if xargs is not desired, find (at least on Slackware 14.1) suports '-exec ... {} \+'. Also, find supports -executable, maybe those commands could be replaced by something like this?: find -L . -executable -exec chmod 755 {} \+ find -L . -not -executable -exec chmod 644 {} \+ Not tested, and maybe should be checked against older versions of Slackware if appropriate. Relevant sections of 'man find': -exec command {} + This variant of the -exec action runs the specified command on the selected files, but the command line is built by appending each selected file name at the end; the total number of invocations of the command will be much less than the number of matched files. The command line is built in much the same way that xargs builds its command lines. Only one instance of `{}' is allowed within the command. The command is executed in the starting directory. -executable Matches files which are executable and directories which are searchable (in a file name resolution sense). This takes into account access control lists and other permissions artefacts which the -perm test ignores. This test makes use of the access(2) system call, and so can be fooled by NFS servers which do UID mapping (or root-squashing), since many systems implement access(2) in the client's kernel and so cannot make use of the UID mapping information held on the server. Because this test is based only on the result of the access(2) system call, there is no guarantee that a file for which this test succeeds can actually be executed. Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From willysr at slackbuilds.org Thu Nov 12 16:21:18 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 12 Nov 2015 23:21:18 +0700 Subject: [Slackbuilds-users] (no subject) In-Reply-To: <20151112065626.GC17417@jostein> References: <20151112065626.GC17417@jostein> Message-ID: <5644BC7E.80107@slackbuilds.org> > The new version of ncmpcpp is now on v. 0.6.7 while the repo version is at > 0.5.10. Should this be updated? The maintainer is no longer active feel free to take this package and update it -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Fri Nov 13 04:00:33 2015 From: yalhcru at gmail.com (B Watson) Date: Thu, 12 Nov 2015 23:00:33 -0500 Subject: [Slackbuilds-users] mame update Message-ID: *Finally* there's an updated mame, pushed to my branch (user/urchlay/updates). Sorry for taking so long on this. From arkadiusz at drabczyk.org Fri Nov 13 21:23:51 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Fri, 13 Nov 2015 21:23:51 +0000 (UTC) Subject: [Slackbuilds-users] find/chmod revisited References: <201511121242.00693.ricardo@palmtx.com.ar> Message-ID: On 2015-11-12, Ricardo J. Barberis wrote: > El Jueves 12/11/2015, B Watson escribi??: >> I've always known the template code that sanitizes the source permissions >> is a bit slow... for mame, it takes a full minute to execute (using tmpfs >> for TMP), since there are over 18 thousand files/dirs in the mame src. >> (...) >> That's a lot of child processes! So I thought "maybe I can use xargs >> and cut the time down some". >> (...) > > And if xargs is not desired, find (at least on Slackware 14.1) > suports '-exec ... {} \+'. One annoying feature of both xargs and find ... -exec \+ is that both will try to run a specified command even if there are no arguments. Example: $ find . -name 'a' | xargs -0 chmod 644 chmod: missing operand after ?644? Try 'chmod --help' for more information. $ find . -name 'a' -exec chmod 644 \+ find: missing argument to `-exec' In case of GNU xargs it's easily fixed using -r and I think it should be used here in an unlikely event of all files having correct permissions: --no-run-if-empty -r If the standard input does not contain any nonblanks, do not run the command. Normally, the command is run once even if there is no input. This option is a GNU extension. That being said, on my machine with SanDisk SSD it took 20.363s to process all files using current -exec method and 0.025s + 0.051s using a new method so I think it's worth considering. -- Arkadiusz Drabczyk From ryan.q at linux.com Fri Nov 13 21:27:13 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 13 Nov 2015 21:27:13 +0000 Subject: [Slackbuilds-users] find/chmod revisited In-Reply-To: References: <201511121242.00693.ricardo@palmtx.com.ar> Message-ID: > > That being said, on my machine with SanDisk SSD it took 20.363s to > process all files using current -exec method and 0.025s + 0.051s using > a new method so I think it's worth considering. > Nice point Arkadiusz and Watson. I think this is definitely worth implementing. Perhaps there could be a massive search and replace done when the repo switches to 14.2, since there may also need to be a massive replacement for i586, might be nice to lump these two changes together. Just an idea. 8^] -Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Nov 14 00:25:25 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 14 Nov 2015 07:25:25 +0700 Subject: [Slackbuilds-users] Updates - 20151114.1 Message-ID: <56467F75.6010307@slackbuilds.org> Sat Nov 14 00:09:50 UTC 2015 academic/bedtools: Updated for version 2.25.0. academic/cutadapt: Updated for version 1.9. academic/genometools: Updated for version 1.5.7. academic/ij-plugins-LOCI: Updated for version 5.1.5. academic/io_lib: Updated for version 1.14.6. academic/jalview: Updated for version 2.9. academic/ncbi-blast-plus: Updated for version 2.2.31. academic/sequence-analysis: Updated for version 1.7.2. academic/snpEff: Updated for version 4.1l. academic/spades: Updated for version 3.6.1. academic/squizz: Updated for version 0.99c. academic/tophat: Updated for version 2.1.0. academic/vcftools: Updated for version 0.1.14_2_g78add55. academic/zotero: Updated for version 4.0.28. audio/calf-ladspa: Added (legacy audio plugin pack). audio/calf: Updated for version 0.0.60. audio/guitarix: Updated for version 0.34.0. audio/jack-tools: Updated for version 20141211. audio/lv2-mda-metapiano: Updated for version 0.0.2. audio/morituri: Update DEPS and added patch. audio/vocoder-ladspa: Updated for version 0.4. desktop/openbox-menu: Update DEP. desktop/plank: Add DEP. desktop/seafile-gui: Updated for version 4.4.2. desktop/wmclock: Updated for version 1.0.14. development/eagle: Updated for version 7.4.0. development/gnuradio: Fix VERSION. development/hhvm-pgsql: Added (Postgres Extension for HipHop). development/hhvm: (VM to execute Hack and PHP). development/jdk: Updated for version 8u66. development/kaaedit: Updated for version 0.46.0. development/nodejs: Added (JavaScript runtime). development/openjdk: Updated for version 7u91b1. development/pycharm: Updated for version 5.0. development/textadept: Updated for version 8.4. development/zed: Fix .desktop file. games/mame: Updated for version 0.167. games/mgba: Change HOMEPAGE url. games/wesnoth: Updated for version 1.12.5. graphics/dvisvgm: Fix DOWNLOAD url + update script. graphics/feh: Updated for version 2.14. graphics/qcad: Updated for version 3.12.1.0. libraries/Impacket: Updated for version 0.9.13. libraries/SFML: Updated for version 2.3.2. libraries/http-parser: Updated for version 2.6.0. libraries/libb64: Added (C routines for base64 encoding/decoding) libraries/libbluray: Updated for version 0.9.1. libraries/libgit2: Updated for version 0.23.3. libraries/librelp: Updated for version 1.2.8. libraries/libsodium: Updated for version 1.0.6. libraries/libvirt-python: Updated for version 1.2.21. libraries/libvirt: Updated for version 1.2.21. libraries/libwhisker2: New maintainer. libraries/libwnck3: Remove DEP. libraries/live555: Updated for version 2015.11.09. libraries/lvtk: Updated for version 1.2.0. libraries/pybloomfiltermmap: Added (bloom filter for python). libraries/webkitgtk: Bring back -j1. misc/mosquitto: Updated for version 1.4.5. multimedia/cuetools: Added alternative untarring routine. multimedia/flashplayer-plugin: Updated for version 11.2.202.548. multimedia/kodi: Updated for version 15.2. multimedia/plexmediaserver: Updated for version 0.9.12.18.1520. network/NetworkManager-openconnect: Updated for version 0.9.8.6. network/ccnet: Updated for version 4.4.6. network/clipgrab: Updated for version 3.5.4. network/davmail: Fix path. network/dovecot-pigeonhole: Updated for version 0.4.9. network/dovecot: Updated for version 2.2.19. network/dsniff: Add more patches. network/haproxy: Updated for version 1.6.2. network/hping3: Add more patches + new maintainer. network/icinga2: Updated for version 2.3.11. network/insync: Updated for version 1.3.3.36056. network/iojs: Updated for version 3.3.1. network/kde-networkmanagement-openconnect: Updated for version 0.9.0.12. network/nikto: Updated for version 2.1.5. network/openconnect: Updated for version 7.06. network/otter: Fix font size. network/packit: Update DOWNLOAD url + new maintainer. network/polipo: Updated for version 1.1.1. network/postfix: Updated for version 3.0.3. network/putty: Updated for version 0.66. network/qTox: Updated for version 20151108. network/seafile-client: Updated for version 4.4.6. network/seafile-server: Updated for version 4.4.6. network/seahub: Updated for version 4.4.6. network/spamassassin: Updated for version 3.4.1. network/sqlmap: Misc tweaks and new maintainer network/tor-browser: Updated for version 5.0.4. network/toxcore: Updated for version 20151103. network/viber: Update script. network/vivaldi: Updated for version 1.0.321.3_1. network/xtables-addons: Updated for version 2.9. network/you-get: Updated for version 0.4.136. network/youtube-dl: Updated for version 2015.11.10. office/abiword: Updated for version 3.0.1. office/mu: Updated for version 0.9.15. office/notmuch: Updated for version 0.21. office/task: Updated for version 2.5.0. office/texmaker: Updated for version 4.5. office/zim: Updated for version 0.65 + new maintainer. perl/libwww-perl: Updated for version 6.13. perl/perl-Test-Differences: Update DEPS. perl/perl-Time-Piece: Updated for version 1.31. perl/perl-encode-locale: Updated for version 1.05. perl/perl-http-message: Updated for version 6.11. perl/perl-net-dns: Updated for version 1.02. perl/perl-net-http: Updated for version 6.09. python/html2text: Updated for version 2015.11.4. python/numexpr: Updated for version 2.4.6. python/pyPdf: Updated for version 1.25.1. python/pyflakes: Updated for version 1.0.0. python/pytables: Updated for version 3.2.0. python/python-clamd: Added (python interface to Clamav). python/regex: Updated for version 2015.11.09. python/tox: Updated for version 2.2.1. system/Iosevka: Updated for version 1.0_beta7. system/apache-activemq: Updated for version 5.12.1. system/cantarell-fonts: Updated for version 0.0.18.1. system/ccid: Updated for version 1.4.21. system/clamtk: Updated for version 5.20. system/drbd-utils: Updated for version 8.9.4. system/evilvte: Added (highly customizable terminal emulator). system/gencfs: Added (Graphical Front End for Encfs). system/icingaweb2: Updated for version 2.0.0. system/irqbalance: Updated for version 1.0.9. system/monitorix: Updated for version 3.8.1. system/rar2fs: Updated for version 1.21.0. system/rar: Updated for version 5.3.b6. system/rsyslog: Updated for version 8.14.0. system/sysdig: Updated for version 0.5.0. system/unrar: Updated for version 5.3.7. system/virt-manager: Updated for version 1.2.1. system/xen: Updated for version 4.5.2. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From thedoogster at gmail.com Sat Nov 14 06:43:54 2015 From: thedoogster at gmail.com (Doogster) Date: Fri, 13 Nov 2015 22:43:54 -0800 Subject: [Slackbuilds-users] mame update In-Reply-To: References: Message-ID: Well, I'm glad we got it. And if you're a MAME player, try it with smoothing shader or a CRT shader: http://www.linuxquestions.org/questions/linux-games-33/howto-use-mame-shaders-4175549677/ On Thu, Nov 12, 2015 at 8:00 PM, B Watson wrote: > *Finally* there's an updated mame, pushed to my branch > (user/urchlay/updates). Sorry for taking so long on this. From slackalaxy at gmail.com Sun Nov 15 20:07:51 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 15 Nov 2015 22:07:51 +0200 Subject: [Slackbuilds-users] QtiPlot on current Message-ID: Hi to all, Here's a working QtiPlot.SlackBuild for -current: https://sourceforge.net/projects/sboppetrov/files/QtiPlot/ I installed slackware64 -current (the 'almost beta' release) and modified the SlackBuild to go around the gsl problem ( http://www.linuxquestions.org/questions/slackware-14/that-which-could-be-fixed-in-sbo-thread-4175532869/page21.html#post5446862). Instead of using the gsl that comes with Slackware, I tried to build in the 1.16 version. I hope I did it right! I have not checked on -current x86 yet. Also, any feedback will be much appreciated. bye Petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbernts at broadpark.no Mon Nov 16 08:05:54 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Mon, 16 Nov 2015 09:05:54 +0100 Subject: [Slackbuilds-users] (no subject) In-Reply-To: <5644BC7E.80107@slackbuilds.org> References: <20151112065626.GC17417@jostein> <5644BC7E.80107@slackbuilds.org> Message-ID: <20151116080554.GA2083@jostein> On 12.11.15,23:21, Willy Sudiarto Raharjo wrote: > > The new version of ncmpcpp is now on v. 0.6.7 while the repo version is at > > 0.5.10. Should this be updated? > > The maintainer is no longer active > feel free to take this package and update it > I have now submitted the updated script for v.0.6.8. Jostein From baildon.research at googlemail.com Wed Nov 18 20:51:32 2015 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 18 Nov 2015 20:51:32 +0000 Subject: [Slackbuilds-users] QtiPlot on current In-Reply-To: References: Message-ID: > Instead of using the gsl that comes with Slackware, I tried to build in the > 1.16 version. I hope I did it right! Here's a patch for the gsl2 API, it'll be better than building gsl-1.16 internally. (There are more packages that fail to build with gsl2, including Kst and root, and they all need similar patches.) Hope it works for you :-) -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: qtiplot-0.9.8.9_gsl-2.patch Type: text/x-patch Size: 1375 bytes Desc: not available URL: From jebrhansen+SBo at gmail.com Thu Nov 19 02:09:18 2015 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 18 Nov 2015 21:09:18 -0500 Subject: [Slackbuilds-users] Upgrade of lirc -- unable to contact maintainer Message-ID: I did some work (with the help of David Spencer) to get lirc to compile on -current. In the process of doing this, I attempted to contact the current maintainer, Murat D. Kadirov , and the email was no longer valid. I had originally just intended on sending my changes to Matteo to get added to his unofficial -current repo, but David suggested I verify that it works on 14.1 and then contact the mailing list to see if I can take it over. I have verified it works with 14.1, although, because of the new lirc version, it does require python3 and python3-PyYAML (I just submitted the second one to SBo today and it's in the pending queue). Are there any objections to me becoming the maintainer of lirc or does anyone know how to get in touch with Murat? Thanks Jeremy/bassmadrigal -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Thu Nov 19 03:21:58 2015 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Thu, 19 Nov 2015 10:21:58 +0700 Subject: [Slackbuilds-users] Upgrade of lirc -- unable to contact maintainer In-Reply-To: References: Message-ID: Just send an update and i will try to verify it on stable release Willy Sudiarto Raharjo On Nov 19, 2015 9:09 AM, "Jeremy Hansen" wrote: > I did some work (with the help of David Spencer) to get lirc to compile on > -current. In the process of doing this, I attempted to contact the current > maintainer, Murat D. Kadirov , and the email > was no longer valid. > > I had originally just intended on sending my changes to Matteo to get > added to his unofficial -current repo, but David suggested I verify that it > works on 14.1 and then contact the mailing list to see if I can take it > over. I have verified it works with 14.1, although, because of the new lirc > version, it does require python3 and python3-PyYAML (I just submitted the > second one to SBo today and it's in the pending queue). > > Are there any objections to me becoming the maintainer of lirc or does > anyone know how to get in touch with Murat? > > Thanks > Jeremy/bassmadrigal > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.becker at gmail.com Thu Nov 19 16:17:33 2015 From: glenn.becker at gmail.com (Glenn Becker) Date: Thu, 19 Nov 2015 11:17:33 -0500 Subject: [Slackbuilds-users] abcde SlackBuild Message-ID: Hi -- Rather than have me sit on it any longer (I'm trying to finish up nanowrimo, for one), would someone more adept like to take over the SlackBuild for abcde? Thanks, Glenn Becker -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Thu Nov 19 20:04:28 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Thu, 19 Nov 2015 22:04:28 +0200 Subject: [Slackbuilds-users] QtiPlot on current In-Reply-To: References: Message-ID: thank you so much! here's the updated SlackBuild for -current: http://sourceforge.net/projects/sboppetrov/files/current/QtiPlot.tar.gz it builds fine on x86_64, i will check it on x86 in the near future. Many thanks to all af you who found patches! bye Petar 2015-11-18 22:51 GMT+02:00 David Spencer : > > Instead of using the gsl that comes with Slackware, I tried to build in > the > > 1.16 version. I hope I did it right! > > Here's a patch for the gsl2 API, it'll be better than building > gsl-1.16 internally. > > (There are more packages that fail to build with gsl2, including Kst > and root, and they all need similar patches.) > > Hope it works for you :-) > -D. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Thu Nov 19 20:39:59 2015 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 19 Nov 2015 20:39:59 +0000 Subject: [Slackbuilds-users] QtiPlot on current In-Reply-To: References: Message-ID: > here's the updated SlackBuild for -current: > http://sourceforge.net/projects/sboppetrov/files/current/QtiPlot.tar.gz > > it builds fine on x86_64, i will check it on x86 in the near future. Many > thanks to all af you who found patches! Hi Petar, errr, sorry but I made a newer version of the patch last night, it's better in a lot of ways as you can see :-/ https://raw.githubusercontent.com/Ponce/slackbuilds/bd79604434306695697c5a77df75837e32e91734/academic/QtiPlot/qtiplot-0.9.8.9_gsl-2.patch Sorry again and thanks -D. From koenigdavidmj at gmail.com Thu Nov 19 21:13:42 2015 From: koenigdavidmj at gmail.com (David Koenig) Date: Thu, 19 Nov 2015 13:13:42 -0800 Subject: [Slackbuilds-users] Please remove me as broadcom-sta maintainer Message-ID: I do not run Slackware anymore, so I can't own this package. From fernando.lopezjr at gmail.com Fri Nov 20 01:58:51 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 19 Nov 2015 18:58:51 -0700 Subject: [Slackbuilds-users] Please remove me as broadcom-sta maintainer In-Reply-To: References: Message-ID: :( On Thu, Nov 19, 2015 at 2:13 PM, David Koenig wrote: > I do not run Slackware anymore, so I can't own this package. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at andreasvoegele.com Fri Nov 20 04:46:32 2015 From: andreas at andreasvoegele.com (Andreas =?utf-8?Q?V=C3=B6gele?=) Date: Fri, 20 Nov 2015 05:46:32 +0100 Subject: [Slackbuilds-users] Please remove me as broadcom-sta maintainer References: Message-ID: <87lh9tuvkn.fsf@sophie-scholl.andreasvoegele.com> David Koenig writes: > I do not run Slackware anymore, so I can't own this package. I use broadcom-sta and could take this package. Regards, Andreas From andreas at andreasvoegele.com Fri Nov 20 05:37:07 2015 From: andreas at andreasvoegele.com (Andreas =?utf-8?Q?V=C3=B6gele?=) Date: Fri, 20 Nov 2015 06:37:07 +0100 Subject: [Slackbuilds-users] abcde SlackBuild References: Message-ID: <87h9khut8c.fsf@sophie-scholl.andreasvoegele.com> Glenn Becker writes: > Rather than have me sit on it any longer (I'm trying to finish up > nanowrimo, for one), would someone more adept like to take over the > SlackBuild for abcde? Unless somebody else wants to maintain the abcde SlackBuild I could take over. BTW, I've got a SlackBuild for debootstrap 1.0.67 at https://github.com/voegelas/slackbuilds-mystuff/tree/master/debootstrap that might help you update the debootstrap SlackBuild. From glenn.becker at gmail.com Fri Nov 20 14:33:34 2015 From: glenn.becker at gmail.com (Glenn Becker) Date: Fri, 20 Nov 2015 09:33:34 -0500 Subject: [Slackbuilds-users] abcde SlackBuild In-Reply-To: <87h9khut8c.fsf@sophie-scholl.andreasvoegele.com> References: <87h9khut8c.fsf@sophie-scholl.andreasvoegele.com> Message-ID: Thanks, Andreas -- for both things! :) On Fri, Nov 20, 2015 at 12:37 AM, Andreas V?gele wrote: > Glenn Becker writes: > > > Rather than have me sit on it any longer (I'm trying to finish up > > nanowrimo, for one), would someone more adept like to take over the > > SlackBuild for abcde? > > Unless somebody else wants to maintain the abcde SlackBuild I could take > over. > > BTW, I've got a SlackBuild for debootstrap 1.0.67 at > https://github.com/voegelas/slackbuilds-mystuff/tree/master/debootstrap > that might help you update the debootstrap SlackBuild. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Fri Nov 20 17:08:07 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 20 Nov 2015 19:08:07 +0200 Subject: [Slackbuilds-users] QtiPlot on current In-Reply-To: References: Message-ID: thank you! i think i will wait for at least RC1 of Slackware 14.2 again, if someone wants to take over the maintenance of QtiPlot, i will be happy bye Petar 2015-11-19 22:39 GMT+02:00 David Spencer : > > here's the updated SlackBuild for -current: > > http://sourceforge.net/projects/sboppetrov/files/current/QtiPlot.tar.gz > > > > it builds fine on x86_64, i will check it on x86 in the near future. Many > > thanks to all af you who found patches! > > Hi Petar, errr, sorry but I made a newer version of the patch last > night, it's better in a lot of ways as you can see :-/ > > > https://raw.githubusercontent.com/Ponce/slackbuilds/bd79604434306695697c5a77df75837e32e91734/academic/QtiPlot/qtiplot-0.9.8.9_gsl-2.patch > > Sorry again and thanks > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Nov 21 05:04:12 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 21 Nov 2015 12:04:12 +0700 Subject: [Slackbuilds-users] Updates - 20151121.1 Message-ID: <564FFB4C.5040207@slackbuilds.org> Sat Nov 21 04:45:59 UTC 2015 academic/squizz: Fix VERSION. audio/apulse: Updated for version 20151031. audio/ncmpcpp: Updated for version 0.6.8. audio/xmms-mp4: Fix compile for -current. desktop/obsession: Update script. desktop/py3status: Updated for version 2.7. development/atom: Updated for version 1.2.1. development/bas55: Updated for version 1.06. development/composer: Updated for version 1.0.0_alpha11. development/luajit: Updated for version 2.0.4. development/nodejs: Add additional DOCS. development/p4: Updated for version 2015.2.1264740. development/pandas: Updated for version 0.17.1. development/pycharm: Updated for version 5.0.1. development/universal-ctags: Updated for version 4d32ace. games/ace: Added (Unix/X solitaire games). games/openjazz: Fix compile issue. gis/grass: Updated for version 7.0.2. gis/rasterio: Updated for version 0.30.0. graphics/PyMOL: Updated for version 1.8.0.0. graphics/blender: Updated for version 2.76b. graphics/dvisvgm: Updated for version 1.12 + new maintainer. graphics/vips: Added (Free Image Processing System). libraries/LibRaw: Updated for version 0.17.0. libraries/OpenSceneGraph: Fixed download url. libraries/PyYAML: Updated for version 3.11. libraries/belle-sip: Updated for version 1.4.2. libraries/bzrtp: Added (ZRTP Key Exchange Library). libraries/cffi: Updated for version 1.3.1. libraries/cln: Updated for version 1.3.4 + new maintainer. libraries/dropbox-python: Updated for version 3.41. libraries/ipaddress: Updated for version 1.0.15. libraries/mbedtls: Added (Cryptographic and SSL/TLS library). libraries/mpir: Updated for version 2.7.2. libraries/python-ntlm: Added (Python NTLM Support). libraries/python3-PyYAML: Added (YAML parser and emitter). libraries/qt5: Updated for version 5.5.1. misc/opencc: Added (Open Chinese Convert). misc/tegaki-zinnia-japanese: Added (Japanese handwriting model). misc/zinnia: Added (hand recognition system). multimedia/bdtools: Added (Blu-ray disc utilities). multimedia/cuetools: Updated for version 1.4.1. multimedia/lives: Updated for version 2.4.3. multimedia/pitivi: Update to .xz DOWNLOADs. multimedia/plexmediaserver: Updated for version 0.9.14.1.1544. network/Pafy: Updated for version 0.4.2. network/bitcoin: Updated for version 0.11.2. network/cicb: Minor fix for -current. network/clipgrab: Updated for version 3.5.5. network/google-cli: Updated for version 1.9. network/linphone: Updated for version 3.9.1. network/nbd: Updated for version 3.12.1. network/owncloud-server: Updated for version 8.2.1. network/palemoon: Updated for version 25.8.0. network/qTox: Updated for version 20151114. network/scapy: Updated for version 2.3.1. network/shorewall-core: Updated for version 4.6.13.2. network/shorewall6: Updated for version 4.6.13.2. network/shorewall: Updated for version 4.6.13.2. network/suricata: Updated for version 2.0.9. network/synergy: Updated for version 1.7.5. network/tmate: Added (instant terminal sharing). network/toxcore: Updated for version 20151119. network/you-get: Updated for version 0.4.156. network/youtube-dl: Updated for version 2015.11.18. office/rednotebook: Updated for version 1.11. python/darts.util.lru: Added (Dictionary with LRU behaviour). python/halberd: Added (HTTP load balancer detector). python/lxml: Updated for version 3.5.0. python/phply: Added (PHP lexer and parser in Python). python/pyrfc3339: Added (Python module). python/pytest: Updated for version 2.8.3. python/python-certifi: Updated for version 2015.11.20. python/python-clamd: Update DEP. python/python-configargparse: Added (Python module). python/python-esmre: Added (Regular expression accelerator). python/python-futures: Added (Backport concurrent.futures package). python/python-ndg_httpsclient: Added (Python module). python/python-oauth2client: Updated for version 1.5.2. python/python-parsedatetime: Added (Python module). python/python-pdfminer: Added (PDF parser and analyzer). python/python-tblib: Added (Traceback fiddling library). python/python-vulndb: Added (vulndb Python SDK). python/regex: Updated for version 2015.11.14. python/rsa: Updated for version 3.2.3. python/stopit: Added (Raise asynchronous exceptions). system/barman: Updated for version 1.5.1. system/driconf: Added .desktop file. system/forkstat: Updated for version 0.01.12. system/intel-microcode: Updated for version 20151106. system/jmtpfs: Add alternate source. system/lirc: Updated for version 0.9.3a + new maintainer. system/secure-delete: Add more patches. system/slpkg: Updated for version 3.0.2. system/sysdig: Updated for version 0.5.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yavor at atanasov.us Sat Nov 21 06:27:09 2015 From: yavor at atanasov.us (Yavor Atanasov) Date: Sat, 21 Nov 2015 01:27:09 -0500 Subject: [Slackbuilds-users] ffmpeg error Message-ID: <2488131448087229@web24h.yandex.ru> Hello guys, I trying to install minidlna package and requirement for it is ffmpeg package - my problem is that I getting error when compilation starts - here is some info about the error: --------------------------------------------------------------------------------------------------- ffmpeg-2.6.3/tests/utils.c ffmpeg-2.6.3/tests/Makefile ffmpeg-2.6.3/tests/ffserver.regression.ref ffmpeg-2.6.3/tests/tiny_ssim.c ffmpeg-2.6.3/tests/fate-valgrind.supp ffmpeg-2.6.3/tests/lavf-regression.sh ffmpeg-2.6.3/tests/tiny_psnr.c ffmpeg-2.6.3/ffserver.c ffmpeg-2.6.3/ffmpeg.h ffmpeg-2.6.3/ffmpeg_dxva2.c ffmpeg-2.6.3/cmdutils_opencl.c ffmpeg-2.6.3/COPYING.LGPLv2.1 ffmpeg-2.6.3/README.md ERROR: caca not found using pkg-config If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "config.log" produced by configure as this will help solve the problem. Failure encountered while building ffmpeg: ffmpeg.SlackBuild return non-zero Do you want to proceed [n] ------------------------------------------------------------------------------------------------------------------ compilation hangs-up here after README.md. What in the name of Christ is "caca"? The only package I found researching with google is "caca-utils" which are not present in slackbuilds... any help will be appreciated. Thanks in advance From matteo.bernardini at gmail.com Sat Nov 21 08:04:26 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 21 Nov 2015 09:04:26 +0100 Subject: [Slackbuilds-users] ffmpeg error In-Reply-To: <2488131448087229@web24h.yandex.ru> References: <2488131448087229@web24h.yandex.ru> Message-ID: 2015-11-21 7:27 GMT+01:00 Yavor Atanasov : > ERROR: caca not found using pkg-config > > If you think configure made a mistake, make sure you are using the latest > version from Git. If the latest version fails, report the problem to the > ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. > Include the log file "config.log" produced by configure as this will help > solve the problem. > Failure encountered while building ffmpeg: > ffmpeg.SlackBuild return non-zero > > Do you want to proceed [n] > ------------------------------------------------------------------------------------------------------------------ > compilation hangs-up here after README.md. What in the name of Christ is "caca"? The only package I found researching with google is "caca-utils" which are not present in slackbuilds... hi Yavor, most probably you need libcaca, a package included in a Slackware full installation. Matteo From yavor at atanasov.us Sat Nov 21 20:18:07 2015 From: yavor at atanasov.us (Yavor Atanasov) Date: Sat, 21 Nov 2015 15:18:07 -0500 Subject: [Slackbuilds-users] ffmpeg error In-Reply-To: References: <2488131448087229@web24h.yandex.ru> Message-ID: <835331448137087@web18g.yandex.ru> Hello Matteo, Thanks for answer but I have full installation and libcaca is present: ------------------- root at DellPE840:~# slackpkg search libcaca Looking for libcaca in package list. Please wait... DONE The list below shows all packages with name matching "libcaca". [ installed ] - libcaca-0.99.beta18-x86_64-2 You can search specific files using "slackpkg file-search file" ---------------------- The error is still the same... Any other ideas guys? 21.11.2015, 03:04, "Matteo Bernardini" : > 2015-11-21 7:27 GMT+01:00 Yavor Atanasov : >> ?ERROR: caca not found using pkg-config >> >> ?If you think configure made a mistake, make sure you are using the latest >> ?version from Git. If the latest version fails, report the problem to the >> ?ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. >> ?Include the log file "config.log" produced by configure as this will help >> ?solve the problem. >> ?Failure encountered while building ffmpeg: >> ???ffmpeg.SlackBuild return non-zero >> >> ?Do you want to proceed [n] >> ?------------------------------------------------------------------------------------------------------------------ >> ?compilation hangs-up here after README.md. What in the name of Christ is "caca"? The only package I found researching with google is "caca-utils" which are not present in slackbuilds... > > hi Yavor, > > most probably you need libcaca, a package included in a Slackware full > installation. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ From matteo.bernardini at gmail.com Sat Nov 21 22:17:24 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 21 Nov 2015 23:17:24 +0100 Subject: [Slackbuilds-users] ffmpeg error In-Reply-To: <835331448137087@web18g.yandex.ru> References: <2488131448087229@web24h.yandex.ru> <835331448137087@web18g.yandex.ru> Message-ID: 2015-11-21 21:18 GMT+01:00 Yavor Atanasov : > Hello Matteo, > Thanks for answer but I have full installation and libcaca is present: > ------------------- > root at DellPE840:~# slackpkg search libcaca > Looking for libcaca in package list. Please wait... DONE > The list below shows all packages with name matching "libcaca". > [ installed ] - libcaca-0.99.beta18-x86_64-2 > You can search specific files using "slackpkg file-search file" > ---------------------- > The error is still the same... Any other ideas guys? > > > 21.11.2015, 03:04, "Matteo Bernardini" : >> 2015-11-21 7:27 GMT+01:00 Yavor Atanasov : >>> ERROR: caca not found using pkg-config >>> >>> If you think configure made a mistake, make sure you are using the latest >>> version from Git. If the latest version fails, report the problem to the >>> ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. >>> Include the log file "config.log" produced by configure as this will help >>> solve the problem. try posting the config.log somewhere (like pastebin.com) and link it here. From arkadiusz at drabczyk.org Sun Nov 22 00:12:13 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 22 Nov 2015 00:12:13 +0000 (UTC) Subject: [Slackbuilds-users] ffmpeg error References: <2488131448087229@web24h.yandex.ru> <835331448137087@web18g.yandex.ru> Message-ID: On 2015-11-21, Yavor Atanasov wrote: > Hello Matteo, > Thanks for answer but I have full installation and libcaca is present: > ------------------- > root at DellPE840:~# slackpkg search libcaca > Looking for libcaca in package list. Please wait... DONE > The list below shows all packages with name matching "libcaca". > [ installed ] - libcaca-0.99.beta18-x86_64-2 > You can search specific files using "slackpkg file-search file" > ---------------------- > The error is still the same... Any other ideas guys? It might have happened that caca.pc has been somehow removed from your system. What's the output of this: $ pkg-config --modversion caca On my system it shows: 0.99.beta18 If it says that caca was not found try re-installing libcaca with slackpkg. Also make sure that your $PKG_CONFIG_PATH, if set points to the correct directory. -- Arkadiusz Drabczyk From willysr at slackbuilds.org Tue Nov 24 23:40:43 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 25 Nov 2015 06:40:43 +0700 Subject: [Slackbuilds-users] Scripts Available for Maintainers Message-ID: <5654F57B.4010406@slackbuilds.org> Hi i just noticed that Howard Pepper is no longer using Slackware so his packages are free now ham/xlog ham/hamlib ham/qrq office/xpad feel free to take above packages -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryan.q at linux.com Tue Nov 24 23:45:33 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Tue, 24 Nov 2015 15:45:33 -0800 Subject: [Slackbuilds-users] Scripts Available for Maintainers In-Reply-To: <5654F57B.4010406@slackbuilds.org> References: <5654F57B.4010406@slackbuilds.org> Message-ID: >feel free to take above packages >office/xpad This looks interesting. If someone else is already using this they should probably take it. But I wouldn't mind taking it over if no one else wants it. -- [ryanpcmcquen.org] On Nov 24, 2015 3:40 PM, "Willy Sudiarto Raharjo" wrote: > Hi > > i just noticed that Howard Pepper is no longer using Slackware so his > packages are free now > > ham/xlog > ham/hamlib > ham/qrq > office/xpad > > feel free to take above packages > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshuakwood at gmail.com Wed Nov 25 01:42:28 2015 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 24 Nov 2015 19:42:28 -0600 Subject: [Slackbuilds-users] Scripts Available for Maintainers In-Reply-To: References: <5654F57B.4010406@slackbuilds.org> Message-ID: > ham/xlog > ham/hamlib > ham/qrq I can take these. --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Fri Nov 27 17:24:21 2015 From: yalhcru at gmail.com (B Watson) Date: Fri, 27 Nov 2015 12:24:21 -0500 Subject: [Slackbuilds-users] fltk in -current Message-ID: So Slackware-current finally has fltk... has anyone else been going through their fltk-using builds, testing against Pat's extra/fltk package? Pat's fltk is 1.3, ours is 1.1... a few of mine compile with 1.3, a few more require some trivial patching (mostly because we have /usr/include/Fl as a symlink to /usr/include/FL, and Pat doesn't... and there are lots of #include ). Is the SBo fltk build going to stay in the repo, maybe renamed to fltk11 or fltk-legacy? Or will it go away, and everything that uses fltk get patched to work with 1.3 (if possible)? From matteo.bernardini at gmail.com Fri Nov 27 17:40:39 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 27 Nov 2015 18:40:39 +0100 Subject: [Slackbuilds-users] fltk in -current In-Reply-To: References: Message-ID: 2015-11-27 18:24 GMT+01:00 B Watson : > So Slackware-current finally has fltk... has anyone else been going > through their fltk-using builds, testing against Pat's extra/fltk package? > > Pat's fltk is 1.3, ours is 1.1... a few of mine compile with 1.3, a few > more require some trivial patching (mostly because we have /usr/include/Fl > as a symlink to /usr/include/FL, and Pat doesn't... and there are lots of > #include ). > > Is the SBo fltk build going to stay in the repo, maybe renamed to fltk11 > or fltk-legacy? Or will it go away, and everything that uses fltk get > patched to work with 1.3 (if possible)? just some points to add to the discussion, IMHO: - ATM we have both the version in SBo, fltk (the 1.1 branch) and fltk13 (the 1.3 branch); - to be fair we have also fltk2 (something like an alpha, a subversion snapshot), that seems needed for flpsed; - usually we have not cared for what is in /extra (look at java/jdk, for example): if it's a dependency for something in our repository we have provided it also if present there; - we have a lot of stuff depending of fltk-1.1.x, I have some doubt that everything could be patched to build with 1.3.x; - version naming is really up to the mantainer: let's see what Luca thinks about it (as he maintains both the versions). Matteo From yalhcru at gmail.com Fri Nov 27 18:27:12 2015 From: yalhcru at gmail.com (B Watson) Date: Fri, 27 Nov 2015 13:27:12 -0500 Subject: [Slackbuilds-users] fltk in -current In-Reply-To: References: Message-ID: On 11/27/15, Matteo Bernardini wrote: > just some points to add to the discussion, IMHO: > - ATM we have both the version in SBo, fltk (the 1.1 branch) and > fltk13 (the 1.3 branch); Yep. But anything that uses fltk13 should work fine with Pat's fltk 1.3, possibly with a trivial patch to any #includes that use Fl/ instead of FL/. > - to be fair we have also fltk2 (something like an alpha, a subversion > snapshot), that seems needed for flpsed; Haven't even looked at that. Assuming it will stay in the 14.2 repo as-is. Upstream has abandoned their 2.x branch (see http://www.fltk.org/software.php), so not expecting anything to change there. > - usually we have not cared for what is in /extra (look at java/jdk, > for example): if it's a dependency for something in our repository we > have provided it also if present there; What I'm seeing: SBo didn't have a jdk build until Slack 14.0, which was also the first Slack release that didn't have a binary package of it: - SBo for 13.37 has no jdk, and Slack 13.37 has jdk-6 in /extra. - SBo for 14.0 has jdk, and Slack 14.0 has only a SlackBuild (no package) for java in /extra. A non-java example: Slackware 13.0 and 13.1 have qt3 in /extra/kde3-compat, which was dropped in 13.37.... and 13.37 is the first appearance of the SBo qt3 package. There are quite a few builds from SBo's 13.1 repo that have this in their README: "This requires the qt3 package from extra/kde3-compat/" ...of course back then, the .info file didn't have a REQUIRES field. > - we have a lot of stuff depending of fltk-1.1.x, I have some doubt > that everything could be patched to build with 1.3.x; The ones I patched turned out to be less work than I expected, but yes, it would be some work that might not be worth doing. There are 25 builds requiring fltk. 8 of them are mine, and 7 of them have been patched to work with either fltk 1.1 or 1.3. > - version naming is really up to the mantainer: let's see what Luca > thinks about it (as he maintains both the versions). Fair enough. I vote that whatever ends up happening, we don't end up with SBo having a fltk build that conflicts with Pat's fltk in /extra... but I'm aware it's not really up for voting. From willysr at slackbuilds.org Sat Nov 28 00:42:36 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Nov 2015 07:42:36 +0700 Subject: [Slackbuilds-users] Updates - 20151128.1 Message-ID: <5658F87C.1060101@slackbuilds.org> Sat Nov 28 00:29:19 UTC 2015 academic/units: Updated for version 2.12. accessibility/xdotool: Fix include permissions. audio/clam: Updated for version r15456. audio/clam_annotator: Fix compile issue. audio/clam_voice2midi: Fix compile issue. audio/flake: Fix buffer overrun. audio/grip2: Fix compile issue. audio/horgand: Fix compile issue. audio/match-vamp-plugin: Fix compile issue. audio/rakarrack: Fix compile issue. desktop/dwm: Updated for version 6.1. desktop/numix-gtk-theme: Added (modern flat theme). desktop/numix-icon-theme-bevel: Added (icon theme). desktop/numix-icon-theme-circle: Added (icon theme). desktop/numix-icon-theme: Added (icon theme). desktop/openbox-simple-theme: Updated for version 20151121. desktop/wmmon: Updated for version 1.1+20131205. development/atom: Updated for version 1.2.3. development/bas55: Updated for version 1.07. development/ltrace: Fix compile issue. development/makedepf90: Added (Makefile-style dependency generator). games/generator_cbiere: Fix compile issue. games/glbsp: Fix compile issue. games/gtklife: Fix compile issue. games/jezzball-kazzmir: Fix compile issue. games/pioneer: Added (A game of lonely space adventure). games/supermariowar: Fix compile issue. games/ufoai: Fix compile issue. games/uqm: Fix compile issue. games/wesnoth: Do not build tests. games/wmquake: Added (Quake DockApp). games/wmwebcam: Added (Webcam DockApp). games/yae: Fix compile issue. gis/pdal: Updated for version 1.1.0. graphics/dvisvgm: Remove deps that are part of Slackware. graphics/fbv: Fix compile issue. graphics/vips: Update MD5SUM. libraries/DevIL: Add patch for gcc 5. libraries/botocore: Updated for version 1.3.9. libraries/cchardet: Updated for version 1.0.0. libraries/dropbox-python: Updated for version 3.42. libraries/libevhtp: Updated for version 1.2.11n. libraries/libtorrent: Updated for version 0.13.6. libraries/msx264: Updated for version 1.5.2. libraries/php-redis: Added (Redis bindings for PHP). libraries/plumbum: Updated for version 1.6.0. libraries/pycparser: Updated for version 2.14. misc/grc: Added (generic colouriser). multimedia/aegisub: Fix build on -current. multimedia/devedeng: Updated for version 4.4.0. multimedia/lives: Updated for version 2.4.4. multimedia/obs-studio: Updated for version 0.12.2. multimedia/spotify32: Improve icon install. multimedia/spotify64: Improve icon install. multimedia/vivaldi-codecs-ffmpeg-extra: Change source to latest deb. network/ClusterSSH: Updated for version 4.04_01. network/awscli: Updated for version 1.9.9. network/darkhttpd: Updated for version 1.11. network/elemental-ircd: Added (high performance irc daemon). network/pidgin-skypeweb: Updated for version 1.0. network/qbittorrent: Added qbittorrent-nox + an rc init script. network/rtorrent: Updated for version 0.9.6. network/telegram: Updated for version 0.9.13 + new maintainer. network/tixati: Updated for version 2.27_1. network/vivaldi: Updated for version 1.0.330.3_1. network/you-get: Updated for version 0.4.167. network/youtube-dl: Updated for version 2015.11.19. office/CherryTree: Updated for version 0.36.0. office/pdfshuffler: Built against newer PyPDF + new maintainer. office/unoconv: Update deps. office/xpad: Remove upstream patch + new maintainer. perl/perl-Test-Differences: Updated for version 0.64. perl/perl-file-desktopentry: Updated for version 0.21. perl/perl-text-aspell: Added (Interface to the GNU Aspell library). python/click: Updated for version 6.0. python/cryptography: Updated for version 1.1.1. python/hpack: Added (HPACK header compression). python/idna: Added (Internationalized Domain Names in Applications). python/monty: Updated for version 0.7.2. python/passlib: Added (comprehensive password hashing framework). python/pilkit: Updated for version 1.1.13. python/python-ndg_httpsclient: Removed (duplicate). python/regex: Updated for version 2015.11.22. system/foomatic-db-engine: Added (Foomatic's database engine). system/foomatic-db: Added (Foomatic's XML database). system/fsviewer: Fix compile issue. system/gpart: Added (Guess PC-type hard disk partitions). system/guix: Added (package manager). system/man-db: Fix compile issue. system/multibootusb: Added (Install live linux on a USB disk). system/parallel: Updated for version 20151122. system/sbotools: Updated for version 1.9 + new maintainer. system/spacefm: Updated for version 1.0.4 + optional gdb support. system/systrace: Fix compile issue. system/virt-manager: Updated for version 1.3.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From falsetti at clansco.org Sun Nov 29 13:47:20 2015 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sun, 29 Nov 2015 14:47:20 +0100 Subject: [Slackbuilds-users] Grass plugin in Qgis Message-ID: <20151129144720.ccee9397b92ef574584766e7@clansco.org> Hi, thanks for SBo slackbuilds, Qgis-2.10 need Grass6 but SBo have only Grass7. I use Qgis SBo slackbuild to install Qgis-2.12.1 that needs qca-2.0.3+, Slack 14.1 have qca-2.0.2 I upgrade qca with slackbuild for current (2.0.3 + patch) It works fine and I have now Grass plugin installed: /usr/lib/qgis/libgrassplugin7.so There is a Python error : ImportError: No module named pyspatialite => http://ftp.slackware.com/pub/ubuntu/pool/universe/p/pyspatialite/ From willysr at slackbuilds.org Sun Nov 29 16:34:10 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 29 Nov 2015 23:34:10 +0700 Subject: [Slackbuilds-users] Grass plugin in Qgis In-Reply-To: <20151129144720.ccee9397b92ef574584766e7@clansco.org> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> Message-ID: <565B2902.4040404@slackbuilds.org> > Hi, > thanks for SBo slackbuilds, > Qgis-2.10 need Grass6 but SBo have only Grass7. > I use Qgis SBo slackbuild to install Qgis-2.12.1 > that needs qca-2.0.3+, Slack 14.1 have qca-2.0.2 > I upgrade qca with slackbuild for current (2.0.3 + patch) Hi Thanks for the info about Qgis, but we can't bump a package that require packages outside of what's supplied in the -stable version of Slackware. You may have to wait until next Slackware release or bump it manually just like what you did -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Nov 29 16:51:03 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 29 Nov 2015 17:51:03 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B2902.4040404@slackbuilds.org> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> Message-ID: <565B2CF7.2000404@gmail.com> Hi, What do you think about putting optional (available from SBo) dependencies in the info file? I think that would allow for further automation. What I have noticed is that, it's sometimes hard to go through the README and spot all the optional deps, because everybody writes README as she/he sees fit. Also, I don't know how, but it could be possibly worth if all the variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one well structured place. This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all of those thoughts, because SlackBuild for 'ffmpeg' is actually well written. But if some more rigid structure, possibly easily understood by computers, was enforced, it could make users' life easier. What do you think? -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Nov 29 16:56:07 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 29 Nov 2015 23:56:07 +0700 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B2CF7.2000404@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> Message-ID: <565B2E27.6000708@slackbuilds.org> > What do you think about putting optional (available from SBo) > dependencies in the info file? > I think that would allow for further automation. > > What I have noticed is that, it's sometimes hard to go through the > README and spot all the optional deps, because everybody writes README > as she/he sees fit. > > Also, I don't know how, but it could be possibly worth if all the > variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one > well structured place. > > This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all > of those thoughts, because SlackBuild for 'ffmpeg' is actually well > written. > > But if some more rigid structure, possibly easily understood by > computers, was enforced, it could make users' life easier. > > What do you think? It's really up to the maintainer to set which deps should go into REQUIRES since he/she is the one knows best about it. We only make sure that it builds normally with all the deps mentioned on the README. my personal thought: I like to keep the packages minimum and list all the optional ones in the README. I don't want to have a bloated systems with all deps are listed just to satisfy minor functionality -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Nov 29 17:10:41 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 29 Nov 2015 18:10:41 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B2E27.6000708@slackbuilds.org> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> Message-ID: <565B3191.6020006@gmail.com> On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: >> What do you think about putting optional (available from SBo) >> dependencies in the info file? >> I think that would allow for further automation. >> >> What I have noticed is that, it's sometimes hard to go through the >> README and spot all the optional deps, because everybody writes README >> as she/he sees fit. >> >> Also, I don't know how, but it could be possibly worth if all the >> variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one >> well structured place. >> >> This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all >> of those thoughts, because SlackBuild for 'ffmpeg' is actually well >> written. >> >> But if some more rigid structure, possibly easily understood by >> computers, was enforced, it could make users' life easier. >> >> What do you think? > > It's really up to the maintainer to set which deps should go into > REQUIRES since he/she is the one knows best about it. We only make sure > that it builds normally with all the deps mentioned on the README. > > my personal thought: > I like to keep the packages minimum and list all the optional ones in > the README. I don't want to have a bloated systems with all deps are > listed just to satisfy minor functionality Well, your the boss;) What do you mean by bloated system? If the optional deps are placed in the info file, then automated tools can benefit from that. It's still up to the user to decide if she wants them. Putting optional deps in info makes just for easier processing, I don't see any possibility of bloating here. And SBo maintainers could declare that optional deps are not tested. What do you think? > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Pozdrawiam, Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Sun Nov 29 17:17:44 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 29 Nov 2015 18:17:44 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B3191.6020006@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> Message-ID: 2015-11-29 18:10 GMT+01:00 Andrzej Telszewski : > On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: >>> >>> What do you think about putting optional (available from SBo) >>> dependencies in the info file? >>> I think that would allow for further automation. >>> >>> What I have noticed is that, it's sometimes hard to go through the >>> README and spot all the optional deps, because everybody writes README >>> as she/he sees fit. >>> >>> Also, I don't know how, but it could be possibly worth if all the >>> variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one >>> well structured place. >>> >>> This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all >>> of those thoughts, because SlackBuild for 'ffmpeg' is actually well >>> written. >>> >>> But if some more rigid structure, possibly easily understood by >>> computers, was enforced, it could make users' life easier. >>> >>> What do you think? >> >> >> It's really up to the maintainer to set which deps should go into >> REQUIRES since he/she is the one knows best about it. We only make sure >> that it builds normally with all the deps mentioned on the README. >> >> my personal thought: >> I like to keep the packages minimum and list all the optional ones in >> the README. I don't want to have a bloated systems with all deps are >> listed just to satisfy minor functionality > > > Well, your the boss;) > > What do you mean by bloated system? If the optional deps are placed in the > info file, then automated tools can benefit from that. It's still up to the > user to decide if she wants them. > > Putting optional deps in info makes just for easier processing, I don't see > any possibility of bloating here. > > And SBo maintainers could declare that optional deps are not tested. > > What do you think? some points that comes to mind: - optional dependencies in the info file will require nevertheless an explaination of what they enable and that could make the info file messy; - some are autodetected, some require passing the script a variable to enable them... there's no standard and not because we doesn't want it to be but becauseit depends on the software in question; - everybody should read the README of whatever they build from SBo in *any* case. Matteo From atelszewski at gmail.com Sun Nov 29 17:32:37 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 29 Nov 2015 18:32:37 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> Message-ID: <565B36B5.5070501@gmail.com> On 29/11/15 18:17, Matteo Bernardini wrote: > 2015-11-29 18:10 GMT+01:00 Andrzej Telszewski : >> On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: >>>> >>>> What do you think about putting optional (available from SBo) >>>> dependencies in the info file? >>>> I think that would allow for further automation. >>>> >>>> What I have noticed is that, it's sometimes hard to go through the >>>> README and spot all the optional deps, because everybody writes README >>>> as she/he sees fit. >>>> >>>> Also, I don't know how, but it could be possibly worth if all the >>>> variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one >>>> well structured place. >>>> >>>> This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all >>>> of those thoughts, because SlackBuild for 'ffmpeg' is actually well >>>> written. >>>> >>>> But if some more rigid structure, possibly easily understood by >>>> computers, was enforced, it could make users' life easier. >>>> >>>> What do you think? >>> >>> >>> It's really up to the maintainer to set which deps should go into >>> REQUIRES since he/she is the one knows best about it. We only make sure >>> that it builds normally with all the deps mentioned on the README. >>> >>> my personal thought: >>> I like to keep the packages minimum and list all the optional ones in >>> the README. I don't want to have a bloated systems with all deps are >>> listed just to satisfy minor functionality >> >> >> Well, your the boss;) >> >> What do you mean by bloated system? If the optional deps are placed in the >> info file, then automated tools can benefit from that. It's still up to the >> user to decide if she wants them. >> >> Putting optional deps in info makes just for easier processing, I don't see >> any possibility of bloating here. >> >> And SBo maintainers could declare that optional deps are not tested. >> >> What do you think? > > some points that comes to mind: > - optional dependencies in the info file will require nevertheless an > explaination of what they enable and that could make the info file > messy; > - some are autodetected, some require passing the script a variable to > enable them... there's no standard and not because we doesn't want it > to be but becauseit depends on the software in question; > - everybody should read the README of whatever they build from SBo in > *any* case. OK, forget it. It would be too much work over little benefit. Now I would just vote for better, that is more structured READMEs. But that too might be only me who has the feeling that the READMEs aren't as good as they should be. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Pozdrawiam, Best regards, Andrzej Telszewski From slackalaxy at gmail.com Sun Nov 29 17:41:39 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 29 Nov 2015 19:41:39 +0200 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B3191.6020006@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> Message-ID: do you suggest that all dependencies are listed in the REQUIRES field or that there is a new field eg OPTIONAL introduced? for example in case of EMBOSS: REQUIRES="jdk" OPTIONAL="clustalw primer3" 2015-11-29 19:10 GMT+02:00 Andrzej Telszewski : > On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: > >> What do you think about putting optional (available from SBo) >>> dependencies in the info file? >>> I think that would allow for further automation. >>> >>> What I have noticed is that, it's sometimes hard to go through the >>> README and spot all the optional deps, because everybody writes README >>> as she/he sees fit. >>> >>> Also, I don't know how, but it could be possibly worth if all the >>> variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one >>> well structured place. >>> >>> This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all >>> of those thoughts, because SlackBuild for 'ffmpeg' is actually well >>> written. >>> >>> But if some more rigid structure, possibly easily understood by >>> computers, was enforced, it could make users' life easier. >>> >>> What do you think? >>> >> >> It's really up to the maintainer to set which deps should go into >> REQUIRES since he/she is the one knows best about it. We only make sure >> that it builds normally with all the deps mentioned on the README. >> >> my personal thought: >> I like to keep the packages minimum and list all the optional ones in >> the README. I don't want to have a bloated systems with all deps are >> listed just to satisfy minor functionality >> > > Well, your the boss;) > > What do you mean by bloated system? If the optional deps are placed in the > info file, then automated tools can benefit from that. It's still up to the > user to decide if she wants them. > > Putting optional deps in info makes just for easier processing, I don't > see any possibility of bloating here. > > And SBo maintainers could declare that optional deps are not tested. > > What do you think? > > >> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > > -- > Pozdrawiam, > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Nov 29 17:45:34 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 30 Nov 2015 00:45:34 +0700 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> Message-ID: <565B39BE.9080104@slackbuilds.org> > do you suggest that all dependencies are listed in the REQUIRES field or > that there is a new field eg OPTIONAL introduced? > > for example in case of EMBOSS: > > REQUIRES="jdk" > > OPTIONAL="clustalw primer3" That will make maintainer and admin's job becomes more complicated :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Nov 29 17:45:53 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 29 Nov 2015 18:45:53 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> Message-ID: <565B39D1.6070900@gmail.com> On 29/11/15 18:41, Petar Petrov wrote: > do you suggest that all dependencies are listed in the REQUIRES field or > that there is a new field eg OPTIONAL introduced? > > for example in case of EMBOSS: > > REQUIRES="jdk" > > OPTIONAL="clustalw primer3" > > > > 2015-11-29 19:10 GMT+02:00 Andrzej Telszewski >: > > On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: > > What do you think about putting optional (available from SBo) > dependencies in the info file? > I think that would allow for further automation. > > What I have noticed is that, it's sometimes hard to go > through the > README and spot all the optional deps, because everybody > writes README > as she/he sees fit. > > Also, I don't know how, but it could be possibly worth if > all the > variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be > gathered in one > well structured place. > > This thoughts came to me when I wanted to build 'ffmpeg'. > Well, not all > of those thoughts, because SlackBuild for 'ffmpeg' is > actually well > written. > > But if some more rigid structure, possibly easily understood by > computers, was enforced, it could make users' life easier. > > What do you think? > > > It's really up to the maintainer to set which deps should go into > REQUIRES since he/she is the one knows best about it. We only > make sure > that it builds normally with all the deps mentioned on the README. > > my personal thought: > I like to keep the packages minimum and list all the optional > ones in > the README. I don't want to have a bloated systems with all deps are > listed just to satisfy minor functionality > > > Well, your the boss;) > > What do you mean by bloated system? If the optional deps are placed > in the info file, then automated tools can benefit from that. It's > still up to the user to decide if she wants them. > > Putting optional deps in info makes just for easier processing, I > don't see any possibility of bloating here. > > And SBo maintainers could declare that optional deps are not tested. > > What do you think? > > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > > -- > Pozdrawiam, > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > I meant something like OPTIONAL="clustalw primer3". -- Best regards, Andrzej Telszewski From brent at exitstatusone.com Sun Nov 29 17:51:58 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Sun, 29 Nov 2015 10:51:58 -0700 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B39D1.6070900@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> Message-ID: <565B3B3E.2040008@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 This would require that package managers be added the feature that enables them to look at the optional line as well. They would need to have the ability to ask if the optional dependencies are added and which specific deps depending on which features are required. Furthermore, the package managers would need to know how to switch on those features or the SlackBuilds would need to have an additonal hook that tells the package manager what to do with those optional deps. On 11/29/2015 10:45 AM, Andrzej Telszewski wrote: > On 29/11/15 18:41, Petar Petrov wrote: >> do you suggest that all dependencies are listed in the REQUIRES >> field or that there is a new field eg OPTIONAL introduced? >> >> for example in case of EMBOSS: >> >> REQUIRES="jdk" >> >> OPTIONAL="clustalw primer3" >> >> >> On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: >> >> What do you think about putting optional (available from SBo) >> dependencies in the info file? I think that would allow for >> further automation. >> >> What I have noticed is that, it's sometimes hard to go through >> the README and spot all the optional deps, because everybody >> writes README as she/he sees fit. >> >> Also, I don't know how, but it could be possibly worth if all >> the variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be >> gathered in one well structured place. >> >> This thoughts came to me when I wanted to build 'ffmpeg'. Well, >> not all of those thoughts, because SlackBuild for 'ffmpeg' is >> actually well written. >> >> But if some more rigid structure, possibly easily understood by >> computers, was enforced, it could make users' life easier. >> >> What do you think? >> >> >> It's really up to the maintainer to set which deps should go >> into REQUIRES since he/she is the one knows best about it. We >> only make sure that it builds normally with all the deps >> mentioned on the README. >> >> my personal thought: I like to keep the packages minimum and list >> all the optional ones in the README. I don't want to have a >> bloated systems with all deps are listed just to satisfy minor >> functionality >> >> >> Well, your the boss;) >> >> What do you mean by bloated system? If the optional deps are >> placed in the info file, then automated tools can benefit from >> that. It's still up to the user to decide if she wants them. >> >> Putting optional deps in info makes just for easier processing, >> I don't see any possibility of bloating here. >> >> And SBo maintainers could declare that optional deps are not >> tested. >> >> What do you think? >> > > I meant something like OPTIONAL="clustalw primer3". > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWWzs+AAoJEMAWbOXyIOfznxEH/AkRAMz1mmYLs8EeuWT3j7Tn +5a6KUPv/+s7kOKqZoY63OHsDBMljqE+MYH3YCLrJQxdjw4HbQN3rvi9G5er8fgF D4xcwlSgpdTAIEziANvuJXTJYggJwfmM29inWWswGyXKtbNwic6qkfoS3r2V9Ooe +XfdE198k6pRPOItg6wgVFgOFgug+mwKif6S+MfvvHFWjLHScBppOspExoN9KKm6 Gw6GswwVmZRZ5CY0ZkSCRuXIEQh7x06F/ArfT+oTRm3pRN4MqQ8k9VpLxdyilrk2 5uxcBIpuj50bfRIY71GEyssX81RBlXdCCwje7xwXani1bK8KDyRzevY15Hmzk6Y= =b+er -----END PGP SIGNATURE----- From atelszewski at gmail.com Sun Nov 29 18:07:14 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 29 Nov 2015 19:07:14 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B3B3E.2040008@exitstatusone.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> Message-ID: <565B3ED2.1030102@gmail.com> On 29/11/15 18:51, Brenton Earl wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > This would require that package managers be added the feature that > enables them to look at the optional line as well. They would need to > have the ability to ask if the optional dependencies are added and > which specific deps depending on which features are required. > Furthermore, the package managers would need to know how to switch on > those features or the SlackBuilds would need to have an additonal hook > that tells the package manager what to do with those optional deps. > > On 11/29/2015 10:45 AM, Andrzej Telszewski wrote: >> On 29/11/15 18:41, Petar Petrov wrote: >>> do you suggest that all dependencies are listed in the REQUIRES >>> field or that there is a new field eg OPTIONAL introduced? >>> >>> for example in case of EMBOSS: >>> >>> REQUIRES="jdk" >>> >>> OPTIONAL="clustalw primer3" >>> >>> >>> On 29/11/15 17:56, Willy Sudiarto Raharjo wrote: >>> >>> What do you think about putting optional (available from SBo) >>> dependencies in the info file? I think that would allow for >>> further automation. >>> >>> What I have noticed is that, it's sometimes hard to go through >>> the README and spot all the optional deps, because everybody >>> writes README as she/he sees fit. >>> >>> Also, I don't know how, but it could be possibly worth if all >>> the variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be >>> gathered in one well structured place. >>> >>> This thoughts came to me when I wanted to build 'ffmpeg'. Well, >>> not all of those thoughts, because SlackBuild for 'ffmpeg' is >>> actually well written. >>> >>> But if some more rigid structure, possibly easily understood by >>> computers, was enforced, it could make users' life easier. >>> >>> What do you think? >>> >>> >>> It's really up to the maintainer to set which deps should go >>> into REQUIRES since he/she is the one knows best about it. We >>> only make sure that it builds normally with all the deps >>> mentioned on the README. >>> >>> my personal thought: I like to keep the packages minimum and list >>> all the optional ones in the README. I don't want to have a >>> bloated systems with all deps are listed just to satisfy minor >>> functionality >>> >>> >>> Well, your the boss;) >>> >>> What do you mean by bloated system? If the optional deps are >>> placed in the info file, then automated tools can benefit from >>> that. It's still up to the user to decide if she wants them. >>> >>> Putting optional deps in info makes just for easier processing, >>> I don't see any possibility of bloating here. >>> >>> And SBo maintainers could declare that optional deps are not >>> tested. >>> >>> What do you think? >>> >> >> I meant something like OPTIONAL="clustalw primer3". >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJWWzs+AAoJEMAWbOXyIOfznxEH/AkRAMz1mmYLs8EeuWT3j7Tn > +5a6KUPv/+s7kOKqZoY63OHsDBMljqE+MYH3YCLrJQxdjw4HbQN3rvi9G5er8fgF > D4xcwlSgpdTAIEziANvuJXTJYggJwfmM29inWWswGyXKtbNwic6qkfoS3r2V9Ooe > +XfdE198k6pRPOItg6wgVFgOFgug+mwKif6S+MfvvHFWjLHScBppOspExoN9KKm6 > Gw6GswwVmZRZ5CY0ZkSCRuXIEQh7x06F/ArfT+oTRm3pRN4MqQ8k9VpLxdyilrk2 > 5uxcBIpuj50bfRIY71GEyssX81RBlXdCCwje7xwXani1bK8KDyRzevY15Hmzk6Y= > =b+er > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > For the moment I thought that we could use something similar to Linux kernel kconfig for additional options. The point is, I guess in almost all of the cases we could have a well structured system, but initial effort would quite high and I don't know if it's worth. I think that after the transition, the maintenance cost wouldn't be much bigger. If, instead of plain text README, the website would parse all the structured configs, then there would be nothing to do. Also, well structured system is easier to check in automated fashion. -- Pozdrawiam, Best regards, Andrzej Telszewski From slackbuilds at jaxartes.net Sun Nov 29 18:27:38 2015 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 29 Nov 2015 10:27:38 -0800 Subject: [Slackbuilds-users] Grass plugin in Qgis In-Reply-To: <20151129144720.ccee9397b92ef574584766e7@clansco.org> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> Message-ID: <1952015.yFac92vWVH@wintermute> On November 29, 2015 14:47:20 Fr?d?ric Falsetti wrote: > Hi, > thanks for SBo slackbuilds, > Qgis-2.10 need Grass6 but SBo have only Grass7. > I use Qgis SBo slackbuild to install Qgis-2.12.1 > that needs qca-2.0.3+, Slack 14.1 have qca-2.0.2 > I upgrade qca with slackbuild for current (2.0.3 + patch) I have not upgraded the SlackBuild to QGIS 2.12 because of the qca package in 14.1 being too old. Once 14.2 is released, I will be updating it. In the meantime, 2.12 and 2.12.1 run fine on Slackware-current. Best, Ben From chris.willing at iinet.net.au Sun Nov 29 22:56:44 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 30 Nov 2015 08:56:44 +1000 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B3ED2.1030102@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> Message-ID: <565B82AC.5080405@iinet.net.au> One of the nice things about the .info files is that just about anything can be added to them; automated build tools will generally ignore any new fields you may choose to add. From my clone of the SBo repo, I have a branch named "spbuilder" (after the name of the build tool I use). In that branch I make any modifications that I want, in particular the addition of an ENVOPTS field in which I place any environment variables I want exported before building. For instance my ffmpeg.info has: ENVOPTS="LAME=yes X264=yes CELT=yes DC1394=yes FREI0R=yes GSM=yes RTMP=yes SCHROEDINGER=yes SPEEX=yes VPX=yes XVID=yes BLURAY=yes ASS=yes OPENAL=yes IEC61883=yes ILBC=yes MODPLUG=yes OPUS=yes TWOLAME=yes LADSPA=yes PULSEAUDIO=yes X265=yes ZVBI=yes OPENCORE=yes FAAC=yes OPENSSL=yes DECKLINK=yes " I use this as example as it demonstrates exactly the sort of thing I don't want to have to remember when I build ffmpeg. I could keep a note about it somewhere - how about as an ENVOPTS field in the .info file? Another sometimes useful option is ENVOPTS="MAKEFLAGS=-j1". Since each build is done in a new container, there's no problem with polluting the environment for future builds. That said, I have sometimes used a qemu or vbox VM to build an app and all its dependencies and I didn't find environment pollution due to multiple exports of the different ENVOPTS to be a problem. The only work is adding the options you want but that is also the advantage - you have the options _you_ want rather some some arbitrary set of options the maintainer wants or believes end users will want. Naturally not all SlackBuilds need any options set so the number of changes is actually quite small (I have 9 modified out of the 434 that I have builds of), so the amount of work for an individual is quite low. Of course it will need support by build tools to be useful. Luckily I have my own build tool that supports it. If the recognised tools won't support it, fork one of them and add such support yourself - the general idea is just to just export the ENVOPTS field immediately before the .SlackBuild is run (at least after the .info file is sourced or parsed). I guess more complete support could include unsetting each of the added options after each build. Lastly, ENVOPTS was just my choice of name - you can name it whatever you like. chris From atelszewski at gmail.com Sun Nov 29 23:11:07 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 30 Nov 2015 00:11:07 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B82AC.5080405@iinet.net.au> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> Message-ID: <565B860B.4010205@gmail.com> On 29/11/15 23:56, Christoph Willing wrote: > The only work is adding the options you want but that is also the > advantage - you have the options _you_ want rather some some arbitrary > set of options the maintainer wants or believes end users will want. Actually, it's like that at the moment and it always will be like that. I mean you will always have some choices that you can or not adjust to your needs. The difference is that "optional options" are mentioned in README, whereas "required options" are placed in info - you put the optional deps in *.info, which gives the whole thing better structure. But it is always *YOU* who has to make the choice, the difference is how the information about possible dependencies is given to you. -- Pozdrawiam, Best regards, Andrzej Telszewski From chris.willing at iinet.net.au Sun Nov 29 23:31:34 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 30 Nov 2015 09:31:34 +1000 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B860B.4010205@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> <565B860B.4010205@gmail.com> Message-ID: <565B8AD6.5040809@iinet.net.au> On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: > On 29/11/15 23:56, Christoph Willing wrote: >> The only work is adding the options you want but that is also the >> advantage - you have the options _you_ want rather some some arbitrary >> set of options the maintainer wants or believes end users will want. > > Actually, it's like that at the moment and it always will be like that. > I mean you will always have some choices that you can or not adjust to > your needs. > > The difference is that "optional options" are mentioned in README, > whereas "required options" are placed in info - you put the optional > deps in *.info, which gives the whole thing better structure. > > But it is always *YOU* who has to make the choice, the difference is how > the information about possible dependencies is given to you. We need to bear in mind the difference between options and dependencies. An added option may, or may not, entail an added build dependency i.e. any added ENVOPTS (or whatever) field _may_ need adjustment to the REQUIRED field too. In order to keep existing .info fields pristine, I use an additional PREREQS field to keep track of additional dependencies, leaving the REQUIRED field intact. chris From gerardo.zamudio at linux.com Mon Nov 30 01:23:15 2015 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sun, 29 Nov 2015 19:23:15 -0600 Subject: [Slackbuilds-users] Nodejs vs node Message-ID: <565BA503.1010201@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I notice there are two similar packages on SBo: nodejs and node. What's the difference between them besides the version number and npm completion scripts? - -- Gerardo Zamudio Linux System Administrator https://gerardozamudio.mx -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWW6UDAAoJEPbPpamee1lXOr0P/RqgcG+FFuh3tv/K03Cz5Mkp TonHk7DwYkaxRHHyA/bPigAbvTzDLksVmmVD919QLbrrlxJdCrUopRObMto9zn5b jSJ8WzR88Fmyk64g38GXwky0iL/7ApbpJlrn5zglEvHuerQcw1hfxsTF+T9eijli r8WBzyisCAgcdDBuVSI7JJLSzJdH5xsth5wuBbMeHVMYhjHz2bPqbD3X5Q00trPi Qgq4G9Q7MpTm5yNK6vELcajX2rStn8BEoKmtkktCcP+n6rEiVVEP9dTZdfXAeH7E 8IL62QLCQnsf2ci6MJzobcA+D7EvFa0P3bvLNZp4GtHwT4qWgK/icfAexVoKsm0j 5Q6TeUdfJ1qBqAqTweK7Ov0s3kznbUpc9WWeyLjedkzTifBYEydsJyilxRbXZ0Tu WwHC6zYGioaUtKhN0YWu9keyQXWaeMywitFWRMu9hFANZXQsTPJnetORfvagPBdM R5AzFjxSHZ2vu/RfBvMa0v6bPAqcf/jgxPq51snQKfoC01scL/AWysD4wGGwCnN+ ZWY2SdHwjkVZiPOwSZj1ZwkMNuQv6Udb1Win9REAFooPhE302isntNv/+F1ZqyHW 1lymEAcMTUvlE4hPIieEDkn2bAfuKkluwLLzrpM/fw4uVRKMufsksUn76OWa3t8y isYaQlgyHr6Iv/n5ougs =prFl -----END PGP SIGNATURE----- From miguel at thedeanda.com Mon Nov 30 01:41:57 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Sun, 29 Nov 2015 17:41:57 -0800 Subject: [Slackbuilds-users] Nodejs vs node In-Reply-To: <565BA503.1010201@linux.com> References: <565BA503.1010201@linux.com> Message-ID: I think nodejs is newer. Nodejs had a fork and I merged back recently and version numbers got confusing. On Nov 29, 2015 5:23 PM, "Gerardo Zamudio" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > I notice there are two similar packages on SBo: nodejs and node. > What's the difference between them besides the version number and npm > completion scripts? > > - -- > Gerardo Zamudio > Linux System Administrator > https://gerardozamudio.mx > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCgAGBQJWW6UDAAoJEPbPpamee1lXOr0P/RqgcG+FFuh3tv/K03Cz5Mkp > TonHk7DwYkaxRHHyA/bPigAbvTzDLksVmmVD919QLbrrlxJdCrUopRObMto9zn5b > jSJ8WzR88Fmyk64g38GXwky0iL/7ApbpJlrn5zglEvHuerQcw1hfxsTF+T9eijli > r8WBzyisCAgcdDBuVSI7JJLSzJdH5xsth5wuBbMeHVMYhjHz2bPqbD3X5Q00trPi > Qgq4G9Q7MpTm5yNK6vELcajX2rStn8BEoKmtkktCcP+n6rEiVVEP9dTZdfXAeH7E > 8IL62QLCQnsf2ci6MJzobcA+D7EvFa0P3bvLNZp4GtHwT4qWgK/icfAexVoKsm0j > 5Q6TeUdfJ1qBqAqTweK7Ov0s3kznbUpc9WWeyLjedkzTifBYEydsJyilxRbXZ0Tu > WwHC6zYGioaUtKhN0YWu9keyQXWaeMywitFWRMu9hFANZXQsTPJnetORfvagPBdM > R5AzFjxSHZ2vu/RfBvMa0v6bPAqcf/jgxPq51snQKfoC01scL/AWysD4wGGwCnN+ > ZWY2SdHwjkVZiPOwSZj1ZwkMNuQv6Udb1Win9REAFooPhE302isntNv/+F1ZqyHW > 1lymEAcMTUvlE4hPIieEDkn2bAfuKkluwLLzrpM/fw4uVRKMufsksUn76OWa3t8y > isYaQlgyHr6Iv/n5ougs > =prFl > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Mon Nov 30 01:47:25 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 29 Nov 2015 17:47:25 -0800 Subject: [Slackbuilds-users] Nodejs vs node In-Reply-To: References: <565BA503.1010201@linux.com> Message-ID: >I notice there are two similar packages on SBo: nodejs and node. What's the difference between them besides the version number and npm completion scripts? Below is the explanation I sent to the SBo admin list upon submitting 'nodejs': I will do my best to explain the mess created here by upstream. node was first. Unfortunately it was governed by the company Joyent, who suppressed the developers from keeping development at the pace they wanted. For this reason the developers forked node in to iojs. It worked out well and the developers won governance. Hence the projects were combined, and 'nodejs' was born. nodejs is based off of iojs. Hence there were major advancements between the version of node we have on SBo (0.12.7) and the current version of nodejs (v4.2.2, based off of iojs). The important thing here is that these are SIGNIFICANT BREAKING CHANGES. I imagine 0.12.7 will have to stay around for a while until everyone catches up (could take a significant amount of time if history is any indicator). For this reason we should probably have both on SBo, I am open to changes in the naming convention if that would help. -- [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerardo.zamudio at linux.com Mon Nov 30 02:18:09 2015 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sun, 29 Nov 2015 20:18:09 -0600 Subject: [Slackbuilds-users] Nodejs vs node In-Reply-To: References: <565BA503.1010201@linux.com> Message-ID: <565BB1E1.3020208@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/29/2015 07:47 PM, Ryan P.C. McQuen wrote: > Below is the explanation I sent to the SBo admin list upon > submitting 'nodejs': > > I will do my best to explain the mess created here by upstream. > > node was first. Unfortunately it was governed by the company > Joyent, who suppressed the developers from keeping development at > the pace they wanted. For this reason the developers forked node in > to iojs. It worked out well and the developers won governance. > Hence the projects were combined, and 'nodejs' was born. nodejs is > based off of iojs. Hence there were major advancements between the > version of node we have on SBo (0.12.7) and the current version of > nodejs (v4.2.2, based off of iojs). > > The important thing here is that these are SIGNIFICANT BREAKING > CHANGES. I imagine 0.12.7 will have to stay around for a while > until everyone catches up (could take a significant amount of time > if history is any indicator). > > For this reason we should probably have both on SBo, I am open to > changes in the naming convention if that would help. Thanks for the explanation, Ryan. It makes sense and I agree we should keep both. It might be a good idea to give this a brief mention in the README, something like "nodejs is the project that was forked from node and merged back. It includes many breaking changes". Maybe advise users to stick with 0.12.7 until they test their application. Guess I'll try out nodejs and see if it breaks anything. I'm sticking with LTS instead of the stable branch since that one seems like it breaks even more things. - -- Gerardo Zamudio Linux System Administrator https://gerardozamudio.mx -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJWW7HgAAoJEPbPpamee1lXBYkQAI1jH7E6c/RFVqNV2SiurPUB Qz2IAKpmtTdLkw2TEkqcwNu0CSAUxA/1jXKT8/zrzxdiFg5CdaHoCSjGgJDrgPhi Dz57LHdmOjrciR7Ro2LrjKnqDDbq9z7A9yGSY8u8uhJ7dGz55OPpFpGP/ImihunR Ny7yAMBIeiG0bIFA0d7A3JiERSACkEg/EQtYw0gNm7+oYkIxE9NnDxwNQs8b8TGJ OEbdzvYzazUNHBLYJh65BjJ3Hux9n2IhOz8Jv3V2hw7n9icr5LRAJ9xKAymwkTvG nW937VE4WMt1nO4njt99GbbWt5QJphfSxlT3eReLYGeu8El0z42xcxmHKPEhobC9 9hRFlgja1GHGwr7ZG9BpPrVNMfWjmIeR4q0i831MPTuI0BGrWKy7cFG5xVOvCjua PVIZKcHmDDAwQvZkk6xPhCCUEbcQ80UoidFgON3fTgEJF+fDfPOjD/bovSEm4qk1 7aXYnM5lMrsoqBz8RY3b7IxaDa7hb/q3nLquki0cm4r+fYfnmA2YUxeQoPMq2BId +pH1iCHHqZnvAjeidVPNnNhcG9Q+U7ZXZ5JN62SGLeg5e6Q8Pt/0nA4pqc4Ak561 yxEfKyB9FtnT8Qq2FqQ7/UkxEOyklNzKZT/pDJLMg7T4n6MjOgo62moe5v2qsVvn nZBgZ3wWadRtYYBX0G1D =kEph -----END PGP SIGNATURE----- From ryan.q at linux.com Mon Nov 30 02:42:14 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 30 Nov 2015 02:42:14 +0000 Subject: [Slackbuilds-users] Nodejs vs node In-Reply-To: <565BB1E1.3020208@linux.com> References: <565BA503.1010201@linux.com> <565BB1E1.3020208@linux.com> Message-ID: > > Thanks for the explanation, Ryan. It makes sense and I agree we should > keep both. It might be a good idea to give this a brief mention in the > README, something like "nodejs is the project that was forked from > node and merged back. It includes many breaking changes". Maybe advise > users to stick with 0.12.7 until they test their application. > > Guess I'll try out nodejs and see if it breaks anything. I'm sticking > with LTS instead of the stable branch since that one seems like it > breaks even more things. > There is a note now about the conflict, but I agree, the explanation should be a bit more robust. :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Mon Nov 30 09:13:06 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 30 Nov 2015 10:13:06 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565B8AD6.5040809@iinet.net.au> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> <565B860B.4010205@gmail.com> <565B8AD6.5040809@iinet.net.au> Message-ID: <565C1322.3030608@gmail.com> On 30/11/15 00:31, Christoph Willing wrote: > On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: >> On 29/11/15 23:56, Christoph Willing wrote: >>> The only work is adding the options you want but that is also the >>> advantage - you have the options _you_ want rather some some arbitrary >>> set of options the maintainer wants or believes end users will want. >> >> Actually, it's like that at the moment and it always will be like that. >> I mean you will always have some choices that you can or not adjust to >> your needs. >> >> The difference is that "optional options" are mentioned in README, >> whereas "required options" are placed in info - you put the optional >> deps in *.info, which gives the whole thing better structure. >> >> But it is always *YOU* who has to make the choice, the difference is how >> the information about possible dependencies is given to you. > > We need to bear in mind the difference between options and dependencies. > An added option may, or may not, entail an added build dependency i.e. > any added ENVOPTS (or whatever) field _may_ need adjustment to the > REQUIRED field too. In order to keep existing .info fields pristine, I > use an additional PREREQS field to keep track of additional > dependencies, leaving the REQUIRED field intact. I think we understand each other, it's just wording that's awkward. I would see it more less (without longer thinking) like that: - additional file for optional dependencies, together with the environment variable (if applicable), - additional file for environment variables that do not require software dependency. That would require at least 2 things: - forcing SlackBuild-s creators to use the particular structure - that's not a problem, because SBo already has some requirements, - making the website processing additional information to display it to the user; it's important, because it would be error prone to expect the SlackBuild creator to maintain README and additional meta-data files in sync. Still, is it worth? (Willy, I can here your voice behind my back:)) > > chris > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Pozdrawiam, Best regards, Andrzej Telszewski From didier at slint.fr Mon Nov 30 10:13:17 2015 From: didier at slint.fr (Didier Spaier) Date: Mon, 30 Nov 2015 11:13:17 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565C1322.3030608@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> <565B860B.4010205@gmail.com> <565B8AD6.5040809@iinet.net.au> <565C1322.3030608@gmail.com> Message-ID: <565C213D.1030503@slint.fr> On 30/11/2015 10:13, Andrzej Telszewski wrote: > On 30/11/15 00:31, Christoph Willing wrote: >> On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: >>> On 29/11/15 23:56, Christoph Willing wrote: >>>> The only work is adding the options you want but that is also the >>>> advantage - you have the options _you_ want rather some some arbitrary >>>> set of options the maintainer wants or believes end users will want. >>> >>> Actually, it's like that at the moment and it always will be like that. >>> I mean you will always have some choices that you can or not adjust to >>> your needs. >>> >>> The difference is that "optional options" are mentioned in README, >>> whereas "required options" are placed in info - you put the optional >>> deps in *.info, which gives the whole thing better structure. >>> >>> But it is always *YOU* who has to make the choice, the difference is how >>> the information about possible dependencies is given to you. >> >> We need to bear in mind the difference between options and dependencies. >> An added option may, or may not, entail an added build dependency i.e. >> any added ENVOPTS (or whatever) field _may_ need adjustment to the >> REQUIRED field too. In order to keep existing .info fields pristine, I >> use an additional PREREQS field to keep track of additional >> dependencies, leaving the REQUIRED field intact. > > I think we understand each other, it's just wording that's awkward. > > I would see it more less (without longer thinking) like that: > - additional file for optional dependencies, together with the > environment variable (if applicable), > - additional file for environment variables that do not require software > dependency. > > That would require at least 2 things: > - forcing SlackBuild-s creators to use the particular structure - that's > not a problem, because SBo already has some requirements, Good luck to get that done, but do not hold your breath. > - making the website processing additional information to display it to > the user; it's important, because it would be error prone to expect the > SlackBuild creator to maintain README and additional meta-data files in > sync. I will let the website maintainers and admins answer that. I am reluctant. _ If a dependency is optional it's up to a human being to take or refuse it. _ We have already a lot of (I almost wrote "too many") package managers, as listed by David (thanks again for the list): http://idlemoor.github.io/slackrepo/links.html It would take a lot of time to modify all of them accordingly. _ Along the time package managers naturally tend to provide more and more features less and less useful, that just complicate their usage and sometimes introduce bugs. _ Some features, although they be useful, exist since a long time and come handy, are probably not used by many folks, like editing a SlackBuild or a .info from sbopkg. The more features, the more time needed by end users to use them. _ It is not that difficult to list optional dependencies in a SlackBuild if the target audience is human beings, not computer propgrams. This is just an example: http://slackbuilds.org/repository/14.1/misc/po4a/ > Still, is it worth? No, IMHO. I hope that this negative answer will not discourage you. We do need folks to make proposals, be they accepted or not, so thanks for this one Andrzej. Bien cordialement. Best regards, Pozdrawiam. Didier From atelszewski at gmail.com Mon Nov 30 10:44:46 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 30 Nov 2015 11:44:46 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565C213D.1030503@slint.fr> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> <565B860B.4010205@gmail.com> <565B8AD6.5040809@iinet.net.au> <565C1322.3030608@gmail.com> <565C213D.1030503@slint.fr> Message-ID: <565C289E.4030206@gmail.com> On 30/11/15 11:13, Didier Spaier wrote: > On 30/11/2015 10:13, Andrzej Telszewski wrote: >> On 30/11/15 00:31, Christoph Willing wrote: >>> On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: >>>> On 29/11/15 23:56, Christoph Willing wrote: >>>>> The only work is adding the options you want but that is also the >>>>> advantage - you have the options _you_ want rather some some arbitrary >>>>> set of options the maintainer wants or believes end users will want. >>>> >>>> Actually, it's like that at the moment and it always will be like that. >>>> I mean you will always have some choices that you can or not adjust to >>>> your needs. >>>> >>>> The difference is that "optional options" are mentioned in README, >>>> whereas "required options" are placed in info - you put the optional >>>> deps in *.info, which gives the whole thing better structure. >>>> >>>> But it is always *YOU* who has to make the choice, the difference is how >>>> the information about possible dependencies is given to you. >>> >>> We need to bear in mind the difference between options and dependencies. >>> An added option may, or may not, entail an added build dependency i.e. >>> any added ENVOPTS (or whatever) field _may_ need adjustment to the >>> REQUIRED field too. In order to keep existing .info fields pristine, I >>> use an additional PREREQS field to keep track of additional >>> dependencies, leaving the REQUIRED field intact. >> >> I think we understand each other, it's just wording that's awkward. >> >> I would see it more less (without longer thinking) like that: >> - additional file for optional dependencies, together with the >> environment variable (if applicable), >> - additional file for environment variables that do not require software >> dependency. >> >> That would require at least 2 things: >> - forcing SlackBuild-s creators to use the particular structure - that's >> not a problem, because SBo already has some requirements, > Good luck to get that done, but do not hold your breath. > >> - making the website processing additional information to display it to >> the user; it's important, because it would be error prone to expect the >> SlackBuild creator to maintain README and additional meta-data files in >> sync. > I will let the website maintainers and admins answer that. > > I am reluctant. > _ If a dependency is optional it's up to a human being to take or refuse it. > _ We have already a lot of (I almost wrote "too many") package managers, as > listed by David (thanks again for the list): > http://idlemoor.github.io/slackrepo/links.html > It would take a lot of time to modify all of them accordingly. > _ Along the time package managers naturally tend to provide more and more > features less and less useful, that just complicate their usage and > sometimes introduce bugs. > _ Some features, although they be useful, exist since a long time and come > handy, are probably not used by many folks, like editing a SlackBuild or > a .info from sbopkg. The more features, the more time needed by end users > to use them. > _ It is not that difficult to list optional dependencies in a SlackBuild > if the target audience is human beings, not computer propgrams. > This is just an example: > http://slackbuilds.org/repository/14.1/misc/po4a/ > >> Still, is it worth? > No, IMHO. Well, I too think that it would be much work, it's probably not worth it. What is your opinion on the READMEs? For me it was the culprit, that made me propose what I've proposed. It's my personal opinion, but the READMEs are not well readable;) I would propose to allow markdown in READMEs, but still, the maintainers would have to use it in consistent way. I know one should read the READMEs thoroughly, but it's much easier to spot what's important, if it's *for example in bold*. Like any other well written software, SBo deserves good documentation:) I don't think we'll go much further with that for a moment;) > > I hope that this negative answer will not discourage you. We do need folks > to make proposals, be they accepted or not, so thanks for this one Andrzej. No worries:) > > Bien cordialement. > Best regards, > Pozdrawiam. Saludos cordiales:) > > Didier > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Pozdrawiam, Best regards, Andrzej Telszewski From joshuakwood at gmail.com Mon Nov 30 16:05:25 2015 From: joshuakwood at gmail.com (JK Wood) Date: Mon, 30 Nov 2015 10:05:25 -0600 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: <565C289E.4030206@gmail.com> References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> <565B860B.4010205@gmail.com> <565B8AD6.5040809@iinet.net.au> <565C1322.3030608@gmail.com> <565C213D.1030503@slint.fr> <565C289E.4030206@gmail.com> Message-ID: On Nov 30, 2015 4:44 AM, "Andrzej Telszewski" wrote: > > On 30/11/15 11:13, Didier Spaier wrote: >> >> On 30/11/2015 10:13, Andrzej Telszewski wrote: >>> >>> On 30/11/15 00:31, Christoph Willing wrote: >>>> >>>> On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: >>>>> >>>>> On 29/11/15 23:56, Christoph Willing wrote: >>>>>> >>>>>> The only work is adding the options you want but that is also the >>>>>> advantage - you have the options _you_ want rather some some arbitrary >>>>>> set of options the maintainer wants or believes end users will want. >>>>> >>>>> >>>>> Actually, it's like that at the moment and it always will be like that. >>>>> I mean you will always have some choices that you can or not adjust to >>>>> your needs. >>>>> >>>>> The difference is that "optional options" are mentioned in README, >>>>> whereas "required options" are placed in info - you put the optional >>>>> deps in *.info, which gives the whole thing better structure. >>>>> >>>>> But it is always *YOU* who has to make the choice, the difference is how >>>>> the information about possible dependencies is given to you. >>>> >>>> >>>> We need to bear in mind the difference between options and dependencies. >>>> An added option may, or may not, entail an added build dependency i.e. >>>> any added ENVOPTS (or whatever) field _may_ need adjustment to the >>>> REQUIRED field too. In order to keep existing .info fields pristine, I >>>> use an additional PREREQS field to keep track of additional >>>> dependencies, leaving the REQUIRED field intact. >>> >>> >>> I think we understand each other, it's just wording that's awkward. >>> >>> I would see it more less (without longer thinking) like that: >>> - additional file for optional dependencies, together with the >>> environment variable (if applicable), >>> - additional file for environment variables that do not require software >>> dependency. >>> >>> That would require at least 2 things: >>> - forcing SlackBuild-s creators to use the particular structure - that's >>> not a problem, because SBo already has some requirements, >> >> Good luck to get that done, but do not hold your breath. >> >>> - making the website processing additional information to display it to >>> the user; it's important, because it would be error prone to expect the >>> SlackBuild creator to maintain README and additional meta-data files in >>> sync. >> >> I will let the website maintainers and admins answer that. >> >> I am reluctant. >> _ If a dependency is optional it's up to a human being to take or refuse it. >> _ We have already a lot of (I almost wrote "too many") package managers, as >> listed by David (thanks again for the list): >> http://idlemoor.github.io/slackrepo/links.html >> It would take a lot of time to modify all of them accordingly. >> _ Along the time package managers naturally tend to provide more and more >> features less and less useful, that just complicate their usage and >> sometimes introduce bugs. >> _ Some features, although they be useful, exist since a long time and come >> handy, are probably not used by many folks, like editing a SlackBuild or >> a .info from sbopkg. The more features, the more time needed by end users >> to use them. >> _ It is not that difficult to list optional dependencies in a SlackBuild >> if the target audience is human beings, not computer propgrams. >> This is just an example: >> http://slackbuilds.org/repository/14.1/misc/po4a/ >> >>> Still, is it worth? >> >> No, IMHO. > > > Well, I too think that it would be much work, it's probably not worth it. > > What is your opinion on the READMEs? For me it was the culprit, that made me propose what I've proposed. It's my personal opinion, but the READMEs are not well readable;) > > I would propose to allow markdown in READMEs, but still, the maintainers would have to use it in consistent way. > > I know one should read the READMEs thoroughly, but it's much easier to spot what's important, if it's *for example in bold*. > > Like any other well written software, SBo deserves good documentation:) > > I don't think we'll go much further with that for a moment;) > > >> >> I hope that this negative answer will not discourage you. We do need folks >> to make proposals, be they accepted or not, so thanks for this one Andrzej. > > > No worries:) > > >> >> Bien cordialement. >> Best regards, >> Pozdrawiam. > > > Saludos cordiales:) > > >> >> Didier >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > > > -- > Pozdrawiam, > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > READMEs are meant to be human readable, not to be machine readable. Further, we expect them to not only be human readable, but also to actually be read by humans. Markdown is fine for the web, but I read package READMEs in vim on the command line - markdown would make that quite a bit messier. We have few enough maintainers as it is. I provide my SlackBuilds free of charge, without compensation, and on my own time. My intention is to provide a good starting point from which to build and package a piece of software. Advanced usage is up to the end user, and the onus should not be on me to make it easier for some automated tool to facilitate that advanced usage. I have enough problems from the software I package alone without having more demands made on my time for very little benefit. If you have an issue with a particular README from a particular SlackBuild, a more productive approach would be to email that maintainer rather than defaulting to suggesting there's a systemic problem with the way we do things on the public mailing list. --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Mon Nov 30 16:39:32 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 30 Nov 2015 17:39:32 +0100 Subject: [Slackbuilds-users] Optional dependencies in info file In-Reply-To: References: <20151129144720.ccee9397b92ef574584766e7@clansco.org> <565B2902.4040404@slackbuilds.org> <565B2CF7.2000404@gmail.com> <565B2E27.6000708@slackbuilds.org> <565B3191.6020006@gmail.com> <565B39D1.6070900@gmail.com> <565B3B3E.2040008@exitstatusone.com> <565B3ED2.1030102@gmail.com> <565B82AC.5080405@iinet.net.au> <565B860B.4010205@gmail.com> <565B8AD6.5040809@iinet.net.au> <565C1322.3030608@gmail.com> <565C213D.1030503@slint.fr> <565C289E.4030206@gmail.com> Message-ID: <565C7BC4.10703@gmail.com> On 30/11/15 17:05, JK Wood wrote: > > On Nov 30, 2015 4:44 AM, "Andrzej Telszewski" > wrote: > > > > On 30/11/15 11:13, Didier Spaier wrote: > >> > >> On 30/11/2015 10:13, Andrzej Telszewski wrote: > >>> > >>> On 30/11/15 00:31, Christoph Willing wrote: > >>>> > >>>> On 11/30/2015 09:11 AM, Andrzej Telszewski wrote: > >>>>> > >>>>> On 29/11/15 23:56, Christoph Willing wrote: > >>>>>> > >>>>>> The only work is adding the options you want but that is also the > >>>>>> advantage - you have the options _you_ want rather some some > arbitrary > >>>>>> set of options the maintainer wants or believes end users will want. > >>>>> > >>>>> > >>>>> Actually, it's like that at the moment and it always will be like > that. > >>>>> I mean you will always have some choices that you can or not > adjust to > >>>>> your needs. > >>>>> > >>>>> The difference is that "optional options" are mentioned in README, > >>>>> whereas "required options" are placed in info - you put the optional > >>>>> deps in *.info, which gives the whole thing better structure. > >>>>> > >>>>> But it is always *YOU* who has to make the choice, the difference > is how > >>>>> the information about possible dependencies is given to you. > >>>> > >>>> > >>>> We need to bear in mind the difference between options and > dependencies. > >>>> An added option may, or may not, entail an added build dependency i.e. > >>>> any added ENVOPTS (or whatever) field _may_ need adjustment to the > >>>> REQUIRED field too. In order to keep existing .info fields pristine, I > >>>> use an additional PREREQS field to keep track of additional > >>>> dependencies, leaving the REQUIRED field intact. > >>> > >>> > >>> I think we understand each other, it's just wording that's awkward. > >>> > >>> I would see it more less (without longer thinking) like that: > >>> - additional file for optional dependencies, together with the > >>> environment variable (if applicable), > >>> - additional file for environment variables that do not require > software > >>> dependency. > >>> > >>> That would require at least 2 things: > >>> - forcing SlackBuild-s creators to use the particular structure - > that's > >>> not a problem, because SBo already has some requirements, > >> > >> Good luck to get that done, but do not hold your breath. > >> > >>> - making the website processing additional information to display it to > >>> the user; it's important, because it would be error prone to expect the > >>> SlackBuild creator to maintain README and additional meta-data files in > >>> sync. > >> > >> I will let the website maintainers and admins answer that. > >> > >> I am reluctant. > >> _ If a dependency is optional it's up to a human being to take or > refuse it. > >> _ We have already a lot of (I almost wrote "too many") package > managers, as > >> listed by David (thanks again for the list): > >> http://idlemoor.github.io/slackrepo/links.html > >> It would take a lot of time to modify all of them accordingly. > >> _ Along the time package managers naturally tend to provide more and > more > >> features less and less useful, that just complicate their usage and > >> sometimes introduce bugs. > >> _ Some features, although they be useful, exist since a long time > and come > >> handy, are probably not used by many folks, like editing a > SlackBuild or > >> a .info from sbopkg. The more features, the more time needed by > end users > >> to use them. > >> _ It is not that difficult to list optional dependencies in a SlackBuild > >> if the target audience is human beings, not computer propgrams. > >> This is just an example: > >> http://slackbuilds.org/repository/14.1/misc/po4a/ > >> > >>> Still, is it worth? > >> > >> No, IMHO. > > > > > > Well, I too think that it would be much work, it's probably not worth it. > > > > What is your opinion on the READMEs? For me it was the culprit, that > made me propose what I've proposed. It's my personal opinion, but the > READMEs are not well readable;) > > > > I would propose to allow markdown in READMEs, but still, the > maintainers would have to use it in consistent way. > > > > I know one should read the READMEs thoroughly, but it's much easier > to spot what's important, if it's *for example in bold*. > > > > Like any other well written software, SBo deserves good documentation:) > > > > I don't think we'll go much further with that for a moment;) > > > > > >> > >> I hope that this negative answer will not discourage you. We do need > folks > >> to make proposals, be they accepted or not, so thanks for this one > Andrzej. > > > > > > No worries:) > > > > > >> > >> Bien cordialement. > >> Best regards, > >> Pozdrawiam. > > > > > > Saludos cordiales:) > > > > > >> > >> Didier > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > > >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - http://slackbuilds.org/faq/ > >> > >> > > > > > > -- > > Pozdrawiam, > > Best regards, > > Andrzej Telszewski > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > READMEs are meant to be human readable, not to be machine readable. > Further, we expect them to not only be human readable, but also to > actually be read by humans. Markdown is fine for the web, but I read > package READMEs in vim on the command line - markdown would make that > quite a bit messier. Agreed. > > We have few enough maintainers as it is. I provide my SlackBuilds free > of charge, without compensation, and on my own time. My intention is to > provide a good starting point from which to build and package a piece of > software. Advanced usage is up to the end user, and the onus should not > be on me to make it easier for some automated tool to facilitate that > advanced usage. I have enough problems from the software I package alone > without having more demands made on my time for very little benefit. Like many of us. > > If you have an issue with a particular README from a particular > SlackBuild, a more productive approach would be to email that maintainer > rather than defaulting to suggesting there's a systemic problem with the > way we do things on the public mailing list. I report the problem or suggest features in the place where I think it's appropriate and here we are. I don't think SBo list was a bad choice to discuss my idea. We were discussing here addition of a future and I think it's perfectly fine place to do that. You on the other side seem to be telling me what should I do, which I don't like. I don't think I have abused the public mailing list. > > --JK > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski