From mauro.giachero at gmail.com Mon May 3 10:43:09 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Mon, 3 May 2010 12:43:09 +0200 Subject: [Slackbuilds-users] Stale oblige/oblige subdirectory Message-ID: Hello everybody, this is just to inform the admins that the Oblige entry contains a stale 'oblige' subdirectory which should be removed. Regards -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From datimmay at gmail.com Wed May 5 19:03:49 2010 From: datimmay at gmail.com (Tim King) Date: Wed, 5 May 2010 14:03:49 -0500 Subject: [Slackbuilds-users] portmidi Message-ID: Hi all, I'm trying to build hydrogen on Slack 13.0 64 and I've built and installed all the dependencies but for some reason or other it looks like the portmidi package doesn't include portmidi.h. I'll probably just explode, add it and repackage but I figured I'd see if it's just me or something I'm not doing right. Almost forgot to add the error when I try to build hydrogen is just that it can't find the portmidi header file. I checked the package and it's not in there for me. Regards, Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at unrealize.co.uk Wed May 5 21:11:04 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 5 May 2010 22:11:04 +0100 Subject: [Slackbuilds-users] portmidi In-Reply-To: References: Message-ID: <20100505211104.GA20587@Junius> On (14:03 05/05/10), Tim King put forth the proposition: >Hi all, > >I'm trying to build hydrogen on Slack 13.0 64 and I've built and installed >all the dependencies but for some reason or other it looks like the portmidi >package doesn't include portmidi.h. I'll probably just explode, add it and >repackage but I figured I'd see if it's just me or something I'm not doing >right. > >Almost forgot to add the error when I try to build hydrogen is just that it >can't find the portmidi header file. I checked the package and it's not in >there for me. Hi Tim, I'll have a look at this. Thanks for letting me know David > >Regards, >Tim >_______________________________________________ >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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From dave at unrealize.co.uk Thu May 6 01:17:41 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Thu, 6 May 2010 02:17:41 +0100 Subject: [Slackbuilds-users] portmidi In-Reply-To: References: Message-ID: <20100506011741.GA7724@Junius> On (14:03 05/05/10), Tim King put forth the proposition: >Hi all, > >I'm trying to build hydrogen on Slack 13.0 64 and I've built and installed >all the dependencies but for some reason or other it looks like the portmidi >package doesn't include portmidi.h. I'll probably just explode, add it and >repackage but I figured I'd see if it's just me or something I'm not doing >right. Tim, I just build portmidi and hydrogen with no problems and portmidi.h is installed to /usr/include Are you using the portmidi script from SBo too? David > >Almost forgot to add the error when I try to build hydrogen is just that it >can't find the portmidi header file. I checked the package and it's not in >there for me. > >Regards, >Tim >_______________________________________________ >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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From datimmay at gmail.com Thu May 6 17:34:25 2010 From: datimmay at gmail.com (Tim King) Date: Thu, 6 May 2010 12:34:25 -0500 Subject: [Slackbuilds-users] portmidi In-Reply-To: <20100506011741.GA7724@Junius> References: <20100506011741.GA7724@Junius> Message-ID: Hi thanks for checking David. Yes I'm using the script from SBo for hydrogen and all depends including portmidi. I AM using multilib as well (which I neglected to mention), but I am not using the 32 bit environment at all. All of my build commands look like so: ARCH=x86_64 ./portmidi.SlackBuild Does all this need to be built 32 bit instead or is there something I need to do differently because of the multilib? Tim On Wed, May 5, 2010 at 8:17 PM, David Woodfall wrote: > On (14:03 05/05/10), Tim King put forth the > proposition: > >> Hi all, >> >> >> I'm trying to build hydrogen on Slack 13.0 64 and I've built and installed >> all the dependencies but for some reason or other it looks like the >> portmidi >> package doesn't include portmidi.h. I'll probably just explode, add it >> and >> repackage but I figured I'd see if it's just me or something I'm not doing >> right. >> > > Tim, I just build portmidi and hydrogen with no problems and > portmidi.h is installed to /usr/include > Are you using the portmidi script from SBo too? > > David > > > > >> Almost forgot to add the error when I try to build hydrogen is just that >> it >> can't find the portmidi header file. I checked the package and it's not >> in >> there for me. >> >> Regards, >> Tim >> > > _______________________________________________ >> 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/ >> >> > > -- > Don't look back, the lemmings are gaining on you. > > _______________________________________________ > 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 dave at unrealize.co.uk Thu May 6 19:01:48 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Thu, 6 May 2010 20:01:48 +0100 Subject: [Slackbuilds-users] portmidi In-Reply-To: References: <20100506011741.GA7724@Junius> Message-ID: <20100506190148.GA15575@Junius> On (12:34 06/05/10), Tim King put forth the proposition: >Hi thanks for checking David. > >Yes I'm using the script from SBo for hydrogen and all depends including >portmidi. I AM using multilib as well (which I neglected to mention), but I >am not using the 32 bit environment at all. All of my build commands look >like so: > >ARCH=x86_64 ./portmidi.SlackBuild > >Does all this need to be built 32 bit instead or is there something I need >to do differently because of the multilib? I need to check on this. I only have shell access to an _64 box but I'll do that now and see what happens. > >Tim > >On Wed, May 5, 2010 at 8:17 PM, David Woodfall wrote: > >> On (14:03 05/05/10), Tim King put forth the >> proposition: >> >>> Hi all, >>> >>> >>> I'm trying to build hydrogen on Slack 13.0 64 and I've built and installed >>> all the dependencies but for some reason or other it looks like the >>> portmidi >>> package doesn't include portmidi.h. I'll probably just explode, add it >>> and >>> repackage but I figured I'd see if it's just me or something I'm not doing >>> right. >>> >> >> Tim, I just build portmidi and hydrogen with no problems and >> portmidi.h is installed to /usr/include >> Are you using the portmidi script from SBo too? >> >> David >> >> >> >> >>> Almost forgot to add the error when I try to build hydrogen is just that >>> it >>> can't find the portmidi header file. I checked the package and it's not >>> in >>> there for me. >>> >>> Regards, >>> Tim >>> >> >> _______________________________________________ >>> 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/ >>> >>> >> >> -- >> Don't look back, the lemmings are gaining on you. >> >> _______________________________________________ >> 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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From dave at unrealize.co.uk Fri May 7 03:12:13 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Fri, 7 May 2010 04:12:13 +0100 Subject: [Slackbuilds-users] portmidi In-Reply-To: References: <20100506011741.GA7724@Junius> Message-ID: <20100507031213.GA8104@Junius> On (12:34 06/05/10), Tim King put forth the proposition: >Hi thanks for checking David. > >Yes I'm using the script from SBo for hydrogen and all depends including >portmidi. I AM using multilib as well (which I neglected to mention), but I >am not using the 32 bit environment at all. All of my build commands look >like so: > >ARCH=x86_64 ./portmidi.SlackBuild > >Does all this need to be built 32 bit instead or is there something I need >to do differently because of the multilib? I just built on x86_64 without problems, except I needed to edit the ladspa slackbuild. I really don't know if multilib will affect things. I would be inclined to think passing ARCH=x86_64 would just build as if it's plain x86_64. Perhaps someone else on the list will know more about that. > >Tim > >On Wed, May 5, 2010 at 8:17 PM, David Woodfall wrote: > >> On (14:03 05/05/10), Tim King put forth the >> proposition: >> >>> Hi all, >>> >>> >>> I'm trying to build hydrogen on Slack 13.0 64 and I've built and installed >>> all the dependencies but for some reason or other it looks like the >>> portmidi >>> package doesn't include portmidi.h. I'll probably just explode, add it >>> and >>> repackage but I figured I'd see if it's just me or something I'm not doing >>> right. >>> >> >> Tim, I just build portmidi and hydrogen with no problems and >> portmidi.h is installed to /usr/include >> Are you using the portmidi script from SBo too? >> >> David >> >> >> >> >>> Almost forgot to add the error when I try to build hydrogen is just that >>> it >>> can't find the portmidi header file. I checked the package and it's not >>> in >>> there for me. >>> >>> Regards, >>> Tim >>> >> >> _______________________________________________ >>> 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/ >>> >>> >> >> -- >> Don't look back, the lemmings are gaining on you. >> >> _______________________________________________ >> 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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From joshuakwood at gmail.com Fri May 7 03:41:12 2010 From: joshuakwood at gmail.com (JK Wood) Date: Thu, 6 May 2010 22:41:12 -0500 Subject: [Slackbuilds-users] portmidi In-Reply-To: <20100507031213.GA8104@Junius> References: <20100506011741.GA7724@Junius> <20100507031213.GA8104@Junius> Message-ID: On Thursday, May 6, 2010, David Woodfall wrote: > On (12:34 06/05/10), Tim King put forth the proposition: > > Hi thanks for checking David. > > Yes I'm using the script from SBo for hydrogen and all depends including > portmidi. ?I AM using multilib as well (which I neglected to mention), but I > am not using the 32 bit environment at all. ?All of my build commands look > like so: > > ARCH=x86_64 ./portmidi.SlackBuild > > Does all this need to be built 32 bit instead or is there something I need > to do differently because of the multilib? > > > I just built on x86_64 without problems, except I needed to edit the > ladspa slackbuild. > > I really don't know if multilib will affect things. I would be > inclined to think passing ARCH=x86_64 would just build as if it's > plain x86_64. > > Perhaps someone else on the list will know more about that. > > > > Tim > Occasionally, you have to force it to use the correct libraries in a multilib environment. SlackBuilds.org recommends LDFLAGS="-L/usr/lib${LIBSUFFIX}" but I invariably use LDFLAGS="-L/lib${LIBSUFFIX} -L/usr/lib${LIBSUFFIX}" in front of your configure lines. Otherwise, assuming you still have problems, you might want to look for a Gentoo patch for multilib or something. --JK From datimmay at gmail.com Fri May 7 08:17:10 2010 From: datimmay at gmail.com (Tim King) Date: Fri, 7 May 2010 03:17:10 -0500 Subject: [Slackbuilds-users] portmidi In-Reply-To: References: <20100506011741.GA7724@Junius> <20100507031213.GA8104@Junius> Message-ID: Alright so...I just re-ran the build script for portmidi and the header file is now included with two others that weren't in the package when I tried to build it yesterday. I'm just not sure at all why. The package I got yesterday showed /usr/include but no files installed to it. Now there are three. I am stumped but I'm not going to complain. Hydrogen is building as we speak. I really appreciate you looking into it and I wish I could say what happened :D Regards, Tim On Thu, May 6, 2010 at 10:41 PM, JK Wood wrote: > On Thursday, May 6, 2010, David Woodfall wrote: > > On (12:34 06/05/10), Tim King put forth the > proposition: > > > > Hi thanks for checking David. > > > > Yes I'm using the script from SBo for hydrogen and all depends including > > portmidi. I AM using multilib as well (which I neglected to mention), > but I > > am not using the 32 bit environment at all. All of my build commands > look > > like so: > > > > ARCH=x86_64 ./portmidi.SlackBuild > > > > Does all this need to be built 32 bit instead or is there something I > need > > to do differently because of the multilib? > > > > > > I just built on x86_64 without problems, except I needed to edit the > > ladspa slackbuild. > > > > I really don't know if multilib will affect things. I would be > > inclined to think passing ARCH=x86_64 would just build as if it's > > plain x86_64. > > > > Perhaps someone else on the list will know more about that. > > > > > > > > Tim > > > > Occasionally, you have to force it to use the correct libraries in a > multilib environment. SlackBuilds.org recommends > LDFLAGS="-L/usr/lib${LIBSUFFIX}" but I invariably use > LDFLAGS="-L/lib${LIBSUFFIX} -L/usr/lib${LIBSUFFIX}" in front of your > configure lines. > > Otherwise, assuming you still have problems, you might want to look > for a Gentoo patch for multilib or something. > > --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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukenshiro at ngi.it Sat May 8 11:29:40 2010 From: lukenshiro at ngi.it (LukenShiro) Date: Sat, 8 May 2010 13:29:40 +0200 Subject: [Slackbuilds-users] efax-gtk removal request Message-ID: <20100508132940.448bca85lukenshiro@ngi.it@starchild.grp> Hello, can anyone remove my efax-gtk .tar.gz from pending queue, please? Meantime efax-gtk's author has released a new interesting version and I'd like to submit it instead of previous one. Thank you in advance. -- GNU/Linux * Slackware64 current Slackware 13.0-32bit VM LU #210970 SU #12583 LM #98222/#412913 From mjjzf at syntaktisk.dk Sun May 9 01:36:24 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Sat, 8 May 2010 21:36:24 -0400 Subject: [Slackbuilds-users] poEdit maintenance Message-ID: <20100508213624.5d50868f@espero.syntaktisk.dk> Just wanted to ask on the list - I have emailed maintainter Niklas ?kerstr?m about poEdit without response. I can see that the submission is a couple of versions behind. Should I take over the Slackbuild? I will be updating it for my own use anyway. Yours, Morten __ Morten Juhl-Johansen Z?lde-Fej?r http://syntaktisk.dk * mjjzf at syntaktisk.dk From nille.kungen at gmail.com Sun May 9 23:34:44 2010 From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_=27Nille=27_=C5kerstr=F6m?=) Date: Mon, 10 May 2010 01:34:44 +0200 Subject: [Slackbuilds-users] poEdit maintenance In-Reply-To: <20100508213624.5d50868f@espero.syntaktisk.dk> References: <20100508213624.5d50868f@espero.syntaktisk.dk> Message-ID: <4BE74694.1050909@gmail.com> On 2010-05-09 03:36, Morten Juhl-Johansen Z?lde-Fej?r wrote: > Just wanted to ask on the list - I have emailed maintainter Niklas > ?kerstr?m about poEdit without response. I can see that the submission > is a couple of versions behind. Should I take over the Slackbuild? I > will be updating it for my own use anyway. > > Yours, > Morten > __ > Morten Juhl-Johansen Z?lde-Fej?r > http://syntaktisk.dk * mjjzf at syntaktisk.dk > _______________________________________________ > 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 have an updated SlackBuild for poedit but since SBo is closed for new submissions until 13.1 i can't submit it. But i attached it to this mail. I will upload it for 13.1 once SBo opens for submission again, but after that you are free to take over as maintainer of poedit if you want. /Nille -------------- next part -------------- A non-text attachment was scrubbed... Name: poedit.tar.gz Type: application/gzip Size: 2309 bytes Desc: not available URL: From niels.horn at gmail.com Sun May 9 23:42:47 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 9 May 2010 20:42:47 -0300 Subject: [Slackbuilds-users] poEdit maintenance In-Reply-To: <4BE74694.1050909@gmail.com> References: <20100508213624.5d50868f@espero.syntaktisk.dk> <4BE74694.1050909@gmail.com> Message-ID: 2010/5/9 Niklas 'Nille' ?kerstr?m : ... but since SBo is closed for new submissions until 13.1 i can't submit it. ... /Nille Is this official? Niels From xgizzmo at gmail.com Mon May 10 00:20:03 2010 From: xgizzmo at gmail.com (xgizzmo at gmail.com) Date: Sun, 9 May 2010 20:20:03 -0400 Subject: [Slackbuilds-users] poEdit maintenance In-Reply-To: References: <20100508213624.5d50868f@espero.syntaktisk.dk> <4BE74694.1050909@gmail.com> Message-ID: <201005092020.03389.xgizzmo@slackbuilds.org> On Sunday 09 May 2010 19:42:47 Niels Horn wrote: > 2010/5/9 Niklas 'Nille' ?kerstr?m : > > ... but since SBo is closed for new > submissions until 13.1 i can't submit it. > ... > > /Nille > > > Is this official? > Yes it is. --dsomero From niels.horn at gmail.com Mon May 10 00:25:58 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 9 May 2010 21:25:58 -0300 Subject: [Slackbuilds-users] poEdit maintenance In-Reply-To: <201005092020.03389.xgizzmo@slackbuilds.org> References: <20100508213624.5d50868f@espero.syntaktisk.dk> <4BE74694.1050909@gmail.com> <201005092020.03389.xgizzmo@slackbuilds.org> Message-ID: On Sun, May 9, 2010 at 9:20 PM, wrote: > On Sunday 09 May 2010 19:42:47 Niels Horn wrote: >> 2010/5/9 Niklas 'Nille' ?kerstr?m : >> >> ... ?but since SBo is closed for new >> submissions until 13.1 i can't submit it. >> ... >> >> /Nille >> >> >> Is this official? >> > > Yes it is. > --dsomero > _______________________________________________ > 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/ > > Was this announced somewhere? I guess I missed it and am still submitting... :-/ Niels From chris.abela at maltats.com Mon May 10 07:16:15 2010 From: chris.abela at maltats.com (Chris Abela) Date: Mon, 10 May 2010 09:16:15 +0200 Subject: [Slackbuilds-users] poEdit maintenance In-Reply-To: Message-ID: While one must appreciate the work involved in the 13.0 to 13.1 update, a warning on this mail list that the submissions shall be closing would have been conductive to the combined effort solicited to maintain scripts. -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Niels Horn Sent: 10 May 2010 02:26 To: SlackBuilds.org Users List Subject: Re: [Slackbuilds-users] poEdit maintenance On Sun, May 9, 2010 at 9:20 PM, wrote: > On Sunday 09 May 2010 19:42:47 Niels Horn wrote: >> 2010/5/9 Niklas 'Nille' ?kerstr?m : >> >> ... ?but since SBo is closed for new >> submissions until 13.1 i can't submit it. >> ... >> >> /Nille >> >> >> Is this official? >> > > Yes it is. > --dsomero > _______________________________________________ > 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/ > > Was this announced somewhere? I guess I missed it and am still submitting... :-/ Niels _______________________________________________ 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 chris.abela at maltats.com Mon May 10 11:14:47 2010 From: chris.abela at maltats.com (Chris Abela) Date: Mon, 10 May 2010 13:14:47 +0200 Subject: [Slackbuilds-users] The sed story of the qhull patch comes to a happy ending Message-ID: In order to submit an update for qhull-2010 I had written a patch to be able to compile it and build it on Slack. I also verified that the Octave build in the repository could also pick it up. Yet a few weeks later an updated Octave was submitted, and in order to be able to compile against qhull-2010 the following "sed" line and comments were necessary in the octave.SlackBuild # qhull 2010.1 does not install qhull/qhull.h; this file is for "backwards # compatibility" and just redirects to qhull/libqhull.h. Octave tries to # use the old header only to compile a test during ./configure. The test # fails because the old header doesn't exist, and as a result Octave won't # use qhull. This line fixes the test, but you may need to comment it out # if you intend on using an older version of qhull. sed -i 's/qhull\/qhull\.h/qhull\/libqhull\.h/g' configure aclocal.m4 Although this hack works and qhull is indeed integrated in octave, I thought that we could do better. So I am submitting an updated academic/qhull/Make-config.sh.patch that is to substitute the one on repository. The octave comments and the "sed" line should be deleted. I tested octave to confirm that qhull is picked and it actually works on Slack13.0 Multilib, 32 and pure_64. Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: Make-config.sh.patch Type: application/octet-stream Size: 808 bytes Desc: not available URL: From andrew.david.52 at gmail.com Mon May 10 13:03:54 2010 From: andrew.david.52 at gmail.com (andrew) Date: Mon, 10 May 2010 23:03:54 +1000 Subject: [Slackbuilds-users] nero-aac.SlackBuild... no neroAacTag? Message-ID: <20100510130354.GA11357@skamandros.andrews-corner.org> Hi, I have been using the SlackBuild for Nero's AAC Encoder and Decoder put together by Erik Hanson, for which my thanks! I was a little curious as to why the tagger that comes in the zipfile, neroAacTag, is not included in the package? I have included it in my own build of this package by simply adding: install -D -s -m 0755 linux/neroAacTag $PKG/usr/bin/neroAacTag but I remain a little curious as to why wiser heads than mine have omitted it? Thanks for your trouble, Andrew -- Do you think that's air you're breathing? From erik at slackbuilds.org Mon May 10 14:00:05 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 10 May 2010 09:00:05 -0500 Subject: [Slackbuilds-users] nero-aac.SlackBuild... no neroAacTag? In-Reply-To: <20100510130354.GA11357@skamandros.andrews-corner.org> References: <20100510130354.GA11357@skamandros.andrews-corner.org> Message-ID: <20100510090005.67e2bbbb@shaggy.doo> On May 10, 2010, at 11:03 PM, andrew wrote: > Hi, Hello, > I have been using the SlackBuild for Nero's AAC Encoder and Decoder > put together by Erik Hanson, for which my thanks! I was a little > curious as to why the tagger that comes in the zipfile, neroAacTag, is > not included in the package? I have included it in my own build of > this package by simply adding: > > install -D -s -m 0755 linux/neroAacTag $PKG/usr/bin/neroAacTag > > but I remain a little curious as to why wiser heads than mine have > omitted it? It's probably newer to the zip file than when I originally wrote the SlackBuild. I don't remember seeing this, or I would have installed it. I'll try to remember to add it in a future update. Thanks for noticing! -- Erik Hanson http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From contact at burro-net.com Tue May 11 15:02:39 2010 From: contact at burro-net.com (Service Client Burro-net) Date: Tue, 11 May 2010 17:02:39 +0200 Subject: [Slackbuilds-users] samba4 slackbuild scripts Message-ID: <4BE9718F.80406@burro-net.com> I made some samba4 slackbuild scripts and packages. As submission to slackbuilds.org is disabled at the moment and both samba4 and my scripts are quite alpha, they wouldn?t be ready to be submitted anyway. But if someone is interested in downloading that kind of stuff, you can download it at ftp://intern.tuxane.com Cheers, Jens from TuxaneSoft From mjjzf at syntaktisk.dk Wed May 12 18:22:56 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Wed, 12 May 2010 14:22:56 -0400 Subject: [Slackbuilds-users] Python Slackbuilds Message-ID: <20100512142256.7c2ee9ba@espero.syntaktisk.dk> Dear all, Is there a specific Slackbuild documentation for packaging Python apps? Yours, Morten __ Morten Juhl-Johansen Z?lde-Fej?r http://syntaktisk.dk * mjjzf at syntaktisk.dk From lmello.009 at gmail.com Wed May 12 18:55:11 2010 From: lmello.009 at gmail.com (Luis Henrique F. Cardoso de Mello) Date: Wed, 12 May 2010 15:55:11 -0300 Subject: [Slackbuilds-users] Python Slackbuilds In-Reply-To: <20100512142256.7c2ee9ba@espero.syntaktisk.dk> References: <20100512142256.7c2ee9ba@espero.syntaktisk.dk> Message-ID: <4BEAF98F.3060802@gmail.com> Usually, it's enough to substitute the ./configure \ $(build options) make make install DESTDIR=$PKG bit for python setup.py install --root $PKG isn't it? On 05/12/2010 03:22 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: > Dear all, > Is there a specific Slackbuild documentation for packaging Python apps? > > Yours, > Morten > __ > Morten Juhl-Johansen Z?lde-Fej?r > http://syntaktisk.dk * mjjzf at syntaktisk.dk > _______________________________________________ > 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 bmg.andre at gmail.com Thu May 13 03:09:37 2010 From: bmg.andre at gmail.com (=?ISO-8859-1?Q?Andr=E9_Barboza?=) Date: Thu, 13 May 2010 00:09:37 -0300 Subject: [Slackbuilds-users] Python Slackbuilds In-Reply-To: <4BEAF98F.3060802@gmail.com> References: <20100512142256.7c2ee9ba@espero.syntaktisk.dk> <4BEAF98F.3060802@gmail.com> Message-ID: Hi Morten, Packing python application is quite simple in general. As you maybe has done, just take a look at a SlackBuild for another python application. The command line suggested by Luis is available when the application uses the Distutils. http://docs.python.org/distutils/introduction.html http://docs.python.org/install/index.html#install-index On 12 May 2010 15:55, Luis Henrique F. Cardoso de Mello wrote: > Usually, it's enough to substitute the > > ./configure \ > ?$(build options) > make > make install DESTDIR=$PKG > > bit for > > python setup.py install --root $PKG > > isn't it? > > On 05/12/2010 03:22 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: >> >> Dear all, >> Is there a specific Slackbuild documentation for packaging Python apps? >> >> Yours, >> Morten >> __ >> Morten Juhl-Johansen Z?lde-Fej?r >> http://syntaktisk.dk * mjjzf at syntaktisk.dk >> _______________________________________________ >> 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/ > > From larryhaja at gmail.com Thu May 13 03:28:48 2010 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 12 May 2010 20:28:48 -0700 Subject: [Slackbuilds-users] Python Slackbuilds In-Reply-To: References: <20100512142256.7c2ee9ba@espero.syntaktisk.dk> <4BEAF98F.3060802@gmail.com> Message-ID: There are some options that you can pass to the setup.py file in your slackbuild. To find out what options are available w/out installing, try running: python setup.py build -h or python setup.py install -h These are only needed if your package needs some special configuration. Otherwise, just running 'python setup.py install --root=$PKG' should do the trick for most python installs. --Larry 2010/5/12 Andr? Barboza : > Hi Morten, > > Packing python application is quite simple in general. As you maybe > has done, just take a look at a SlackBuild for another python > application. The command line suggested by Luis is available when the > application uses the Distutils. > > http://docs.python.org/distutils/introduction.html > http://docs.python.org/install/index.html#install-index > > On 12 May 2010 15:55, Luis Henrique F. Cardoso de Mello > wrote: >> Usually, it's enough to substitute the >> >> ./configure \ >> ?$(build options) >> make >> make install DESTDIR=$PKG >> >> bit for >> >> python setup.py install --root $PKG >> >> isn't it? >> >> On 05/12/2010 03:22 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: >>> >>> Dear all, >>> Is there a specific Slackbuild documentation for packaging Python apps? >>> >>> Yours, >>> Morten >>> __ >>> Morten Juhl-Johansen Z?lde-Fej?r >>> http://syntaktisk.dk * mjjzf at syntaktisk.dk >>> _______________________________________________ >>> 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/ >> >> > _______________________________________________ > 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 s at ramov.com Thu May 13 17:56:20 2010 From: s at ramov.com (=?UTF-8?Q?=C5=A0ime=20Ramov?=) Date: Thu, 13 May 2010 19:56:20 +0200 (CEST) Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot Message-ID: <1273773380.87676557@192.168.2.228> Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 as of this writing. It is available here: Unix installer script is completely rewritten. More about latest packaging: Prefix is hard coded (in addition to other annoyances like no DESTDIR support) and they actually recommend using the .deb archive and re- packaging that until they release a more capable install script. Please note Opera no longer depends on QT -- they use they own native libraries. Comments welcome. Thanks! From s at ramov.com Thu May 13 18:09:08 2010 From: s at ramov.com (=?UTF-8?Q?=C5=A0ime=20Ramov?=) Date: Thu, 13 May 2010 20:09:08 +0200 (CEST) Subject: [Slackbuilds-users] Vi Message-ID: <1273774148.949915685@192.168.2.228> Hello again - I've created classic Vi SlackBuild script. Other than being original, additional benefit is UTF-8 support. I will submit it to SBo when submissions open up, but posting it here for immediate benefit for those who might want it. From chris.abela at maltats.com Fri May 14 08:15:18 2010 From: chris.abela at maltats.com (Chris Abela) Date: Fri, 14 May 2010 10:15:18 +0200 Subject: [Slackbuilds-users] Vi In-Reply-To: <1273774148.949915685@192.168.2.228> Message-ID: On my multilib -stable-13.0: Script started on Fri 14 May 2010 10:14:26 AM CEST root at DeepThought:~/slackbuilds/vi# / ./t  vi.SlackBuild ex-050325/ex.spec ex-050325/regexp.h ex-050325/libuxre/wcharm.h ex-050325/libuxre/regex.h ex-050325/libuxre/regdfa.h ex-050325/libuxre/re.h ex-050325/libuxre/colldata.h ex-050325/libterm/libterm.h ex-050325/ex_vis.h ex-050325/ex_vars.h ex-050325/ex_tune.h ex-050325/ex_tty.h ex-050325/ex_temp.h ex-050325/ex_re.h ex-050325/ex_proto.h ex-050325/ex_argv.h ex-050325/ex.h ex-050325/config.h ex-050325/printf.c ex-050325/mapmalloc.c ex-050325/malloc.c ex-050325/libuxre/stubs.c ex-050325/libuxre/regparse.c ex-050325/libuxre/regnfa.c ex-050325/libuxre/regfree.c ex-050325/libuxre/regexec.c ex-050325/libuxre/regerror.c ex-050325/libuxre/regdfa.c ex-050325/libuxre/regcomp.c ex-050325/libuxre/onefile.c ex-050325/libuxre/bracket.c ex-050325/libuxre/_collmult.c ex-050325/libuxre/_collelem.c ex-050325/libterm/tputs.c ex-050325/libterm/tgoto.c ex-050325/libterm/termcap.c ex-050325/exrecover.c ex-050325/expreserve.c ex-050325/ex_vwind.c ex-050325/ex_vput.c ex-050325/ex_vops3.c ex-050325/ex_vops2.c ex-050325/ex_vops.c ex-050325/ex_voper.c ex-050325/ex_vmain.c ex-050325/ex_vget.c ex-050325/ex_version.c ex-050325/ex_vadj.c ex-050325/ex_v.c ex-050325/ex_unix.c ex-050325/ex_tty.c ex-050325/ex_temp.c ex-050325/ex_tagio.c ex-050325/ex_subr.c ex-050325/ex_set.c ex-050325/ex_re.c ex-050325/ex_put.c ex-050325/ex_io.c ex-050325/ex_get.c ex-050325/ex_extern.c ex-050325/ex_data.c ex-050325/ex_cmdsub.c ex-050325/ex_cmds2.c ex-050325/ex_cmds.c ex-050325/ex_addr.c ex-050325/ex.c ex-050325/libuxre/COPYING.LGPL ex-050325/vi.1 ex-050325/ex.1 ex-050325/makeoptions ex-050325/libuxre/NOTES ex-050325/libuxre/Makefile ex-050325/libterm/Makefile ex-050325/catd/en_US ex-050325/TODO ex-050325/README ex-050325/Makefile ex-050325/LICENSE ex-050325/Changes patching file config.h cc -O2 -pipe -DLISPCODE -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 -DVMUNIX -DEXRECOVER=\"/usr/libexec/exrecover\" -DEXPRESERVE=\"/usr/libexec/expreserve\" -I./libuxre -DUXRE -c exrecover.c make[1]: Entering directory `/tmp/SBo/ex-050325/libuxre' cc -O2 -pipe -DVMUNIX -I. -c regnfa.c regnfa.c: In function 'newctxt': regnfa.c:538: error: expected expression before 'Context' make[1]: *** [regnfa.o] Error 1 make[1]: Leaving directory `/tmp/SBo/ex-050325/libuxre' make: *** [uxre] Error 2 make: *** Waiting for unfinished jobs.... root at DeepThought:~/slackbuilds/vi# exit exit Script done on Fri 14 May 2010 10:14:34 AM CEST -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of ?ime Ramov Sent: 13 May 2010 20:09 To: slackbuilds-users at slackbuilds.org Subject: [Slackbuilds-users] Vi Hello again - I've created classic Vi SlackBuild script. Other than being original, additional benefit is UTF-8 support. I will submit it to SBo when submissions open up, but posting it here for immediate benefit for those who might want it. _______________________________________________ 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 belka.ew at gmail.com Fri May 14 10:05:19 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Fri, 14 May 2010 12:05:19 +0200 Subject: [Slackbuilds-users] ghc again Message-ID: Hi guys, There's new version of ghc (6.12.2) and it doesn't provide utf8-string again. An old utf8-string slackbuild is removed. I can't build xmonad-contrib. Who can help to solve the problem? Configuring xmonad-contrib-0.9.1... Setup.lhs: At least the following dependencies are missing: utf8-string -any Best regards Eugene -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.abela at maltats.com Fri May 14 14:06:04 2010 From: chris.abela at maltats.com (Chris Abela) Date: Fri, 14 May 2010 16:06:04 +0200 Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot In-Reply-To: <1273773380.87676557@192.168.2.228> Message-ID: Works here! -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of ?ime Ramov Sent: 13 May 2010 19:56 To: slackbuilds-users at slackbuilds.org Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 as of this writing. It is available here: Unix installer script is completely rewritten. More about latest packaging: Prefix is hard coded (in addition to other annoyances like no DESTDIR support) and they actually recommend using the .deb archive and re- packaging that until they release a more capable install script. Please note Opera no longer depends on QT -- they use they own native libraries. Comments welcome. 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 Manuel.Spam at nurfuerspam.de Fri May 14 16:38:32 2010 From: Manuel.Spam at nurfuerspam.de (Manuel Reimer) Date: Fri, 14 May 2010 18:38:32 +0200 Subject: [Slackbuilds-users] Fix for merkaartor SlackBuild (patch attached) Message-ID: Hello, I've attached a patch for the merkaartor SlackBuild file, which already is part of the SBo package repository. The most important fix, I've added, is, that I've found out how I get merkaartor to include all its language files. This took me some hours to find out, so it would be great if you could leave the short credits line, I've added, where it is. The two smaller fixes are: - NODEBUG=1 --> should be set according to the documentation - Dropped the perl module stuff. Merkaartor doesn't ship any perl modules, so I don't think we should keep those lines. Thanks in advance Yours Manuel Reimer -------------- next part -------------- A non-text attachment was scrubbed... Name: merkaartorsb.diff Type: text/x-diff Size: 1490 bytes Desc: not available URL: From Manuel.Spam at nurfuerspam.de Fri May 14 16:48:31 2010 From: Manuel.Spam at nurfuerspam.de (Manuel Reimer) Date: Fri, 14 May 2010 18:48:31 +0200 Subject: [Slackbuilds-users] Fix for merkaartor SlackBuild (patch attached) In-Reply-To: References: Message-ID: Reposting patch, gzipped now. Gmane seems to "anonymize" mail addresses :-( Manuel Reimer wrote: > Hello, > > I've attached a patch for the merkaartor SlackBuild file, which already > is part of the SBo package repository. > > The most important fix, I've added, is, that I've found out how I get > merkaartor to include all its language files. This took me some hours to > find out, so it would be great if you could leave the short credits > line, I've added, where it is. > > The two smaller fixes are: > - NODEBUG=1 > --> should be set according to the documentation > - Dropped the perl module stuff. Merkaartor doesn't ship any perl > modules, so I don't think we should keep those lines. > > Thanks in advance > > Yours > > Manuel Reimer > -------------- next part -------------- A non-text attachment was scrubbed... Name: merkaartorsb.diff.gz Type: application/gzip Size: 788 bytes Desc: not available URL: From pilbender at gmail.com Sat May 15 00:02:12 2010 From: pilbender at gmail.com (Richard Scott Smith) Date: Fri, 14 May 2010 17:02:12 -0700 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 48, Issue 4 In-Reply-To: References: Message-ID: <4BEDE484.3000809@gmail.com> slackbuilds-users-request at slackbuilds.org wrote: > Message: 3 > Date: Thu, 13 May 2010 19:56:20 +0200 (CEST) > From: "=?UTF-8?Q?=C5=A0ime=20Ramov?=" > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot > Message-ID: <1273773380.87676557 at 192.168.2.228> > Content-Type: text/plain;charset=UTF-8 > > Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 > as of this writing. It is available here: > > > > Unix installer script is completely rewritten. More about latest > packaging: > > > > Prefix is hard coded (in addition to other annoyances like no DESTDIR > support) and they actually recommend using the .deb archive and re- > packaging that until they release a more capable install script. > > Please note Opera no longer depends on QT -- they use they own native > libraries. > > > Comments welcome. Thanks! > > ------------------------------ > > Message: 7 > Date: Fri, 14 May 2010 16:06:04 +0200 > From: "Chris Abela" > To: "'SlackBuilds.org Users List'" > Subject: Re: [Slackbuilds-users] Call for testing: Latest Opera > snapshot > Message-ID: > Content-Type: text/plain; charset="iso-8859-2" > > Works here! > > -----Original Message----- > From: slackbuilds-users-bounces at slackbuilds.org > [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of ?ime Ramov > Sent: 13 May 2010 19:56 > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot > > Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 > as of this writing. It is available here: > > > > Unix installer script is completely rewritten. More about latest > packaging: > > > > Prefix is hard coded (in addition to other annoyances like no DESTDIR > support) and they actually recommend using the .deb archive and re- > packaging that until they release a more capable install script. > > Please note Opera no longer depends on QT -- they use they own native > libraries. > > > Comments welcome. 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/ > > > It does work well. Nice going. Java is not being picked up. I'm on the 64 bit version. Check time.gov for a Java applet to test. From s at ramov.com Sat May 15 10:59:24 2010 From: s at ramov.com (=?UTF-8?Q?=C5=A0ime=20Ramov?=) Date: Sat, 15 May 2010 12:59:24 +0200 (CEST) Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 48, Issue 4 In-Reply-To: <4BEDE484.3000809@gmail.com> References: <4BEDE484.3000809@gmail.com> Message-ID: <1273921164.485130254@192.168.2.229> Hello, > It does work well. Nice going. Java is not being picked up. According to Under 'Unix Known Issues': - Java is listed as not working. From wxj.g.sh at gmail.com Sat May 15 11:46:21 2010 From: wxj.g.sh at gmail.com (vvoody) Date: Sat, 15 May 2010 19:46:21 +0800 (CST) Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot In-Reply-To: <1273773380.87676557@192.168.2.228> References: <1273773380.87676557@192.168.2.228> Message-ID: <4bee89a9.09ff8c0a.5533.7f06@mx.google.com> From: "?ime Ramov" Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot Date: Thu, 13 May 2010 19:56:20 +0200 (CEST) Message-ID: <1273773380.87676557 at 192.168.2.228> > Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 > as of this writing. It is available here: > > > > Unix installer script is completely rewritten. More about latest > packaging: > > > > Prefix is hard coded (in addition to other annoyances like no DESTDIR > support) and they actually recommend using the .deb archive and re- > packaging that until they release a more capable install script. > > Please note Opera no longer depends on QT -- they use they own native > libraries. > > > Comments welcome. Thanks! > Works, thank you Ramov. Opera's installation script gets even weirder. Now we have to generate the slack package by depending on the deb pkg. LOL... Hope for a enhanced script. From thomas at beingboiled.info Sat May 15 12:35:43 2010 From: thomas at beingboiled.info (Thomas Morper) Date: Sat, 15 May 2010 14:35:43 +0200 Subject: [Slackbuilds-users] small fix for perl-dbd-sqlite Message-ID: <201005151435.44158.thomas@beingboiled.info> Hello *, There's a small bug in my SlackBuild for perl-dbd-sqlite. On anything else than Slackware 13.0 with Perl 5.10.0 the hardcoded Perl version number prevents the $PKG dir from being cleaned up prior to "makepkg". The problem is in line 76: rm -rf $PKG/usr/lib$LIBDIRSUFFIX/perl5/5.10.0 Quick and dirty solution for the upcoming Slackware 13.1: rm -rf $PKG/usr/lib$LIBDIRSUFFIX/perl5/5.10.1 A more generic approach: find $PKG \( -name perllocal.pod -o -name .packlist \ -o -name '*.bs' -empty \) -delete find $PKG -depth -type d -empty -delete Could one of the admins please fix this? Thanks! -- From donaldcallen at gmail.com Sat May 15 12:51:04 2010 From: donaldcallen at gmail.com (Donald Allen) Date: Sat, 15 May 2010 08:51:04 -0400 Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot In-Reply-To: <4bee89a9.09ff8c0a.5533.7f06@mx.google.com> References: <1273773380.87676557@192.168.2.228> <4bee89a9.09ff8c0a.5533.7f06@mx.google.com> Message-ID: Have any of you run opera and top at the same time? I tried opera for the umpteenth time a few months ago on a Linux system and found that while it worked, the processor utilization was extremely high, much higher than Firefox. I've also seen complaints about this on opera user groups. So, for the umpteen+1th time, I gave up on it. I'd be curious to know if any of you are seeing the same thing. /Don On Sat, May 15, 2010 at 7:46 AM, vvoody wrote: > From: "?ime Ramov" > Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot > Date: Thu, 13 May 2010 19:56:20 +0200 (CEST) > Message-ID: <1273773380.87676557 at 192.168.2.228> > >> Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 >> as of this writing. It is available here: >> >> >> >> Unix installer script is completely rewritten. More about latest >> packaging: >> >> >> >> Prefix is hard coded (in addition to other annoyances like no DESTDIR >> support) and they actually recommend using the .deb archive and re- >> packaging that until they release a more capable install script. >> >> Please note Opera no longer depends on QT -- they use they own native >> libraries. >> >> >> Comments welcome. Thanks! >> > Works, thank you Ramov. > Opera's installation script gets even weirder. > Now we have to generate the slack package by depending on the deb pkg. LOL... > Hope for a enhanced script. > _______________________________________________ > 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 wxj.g.sh at gmail.com Sat May 15 13:06:02 2010 From: wxj.g.sh at gmail.com (vvoody) Date: Sat, 15 May 2010 21:06:02 +0800 (CST) Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot In-Reply-To: References: <1273773380.87676557@192.168.2.228> <4bee89a9.09ff8c0a.5533.7f06@mx.google.com> Message-ID: <4bee9c40.0b698d0a.3980.ffffe05c@mx.google.com> From: Donald Allen Subject: Re: [Slackbuilds-users] Call for testing: Latest Opera snapshot Date: Sat, 15 May 2010 08:51:04 -0400 Message-ID: > Have any of you run opera and top at the same time? I tried opera for > the umpteenth time a few months ago on a Linux system and found that > while it worked, the processor utilization was extremely high, much > higher than Firefox. I've also seen complaints about this on opera > user groups. So, for the umpteen+1th time, I gave up on it. I'd be > curious to know if any of you are seeing the same thing. > > /Don > No extrememly high processor utilization here. I think, Opera 10.5x is better than previous versions at CPU control. - Slackware 13.0, 2.6.29.6, Opera build 6336 From rworkman at slackbuilds.org Sun May 16 02:27:20 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 15 May 2010 21:27:20 -0500 Subject: [Slackbuilds-users] small fix for perl-dbd-sqlite In-Reply-To: <201005151435.44158.thomas@beingboiled.info> References: <201005151435.44158.thomas@beingboiled.info> Message-ID: <20100515212720.326f2bd7@liberty.rlwhome.lan> On Sat, 15 May 2010 14:35:43 +0200 Thomas Morper wrote: > Hello *, > > There's a small bug in my SlackBuild for perl-dbd-sqlite. On anything > else than Slackware 13.0 with Perl 5.10.0 the hardcoded Perl version > number prevents the $PKG dir from being cleaned up prior to "makepkg". > > The problem is in line 76: > rm -rf $PKG/usr/lib$LIBDIRSUFFIX/perl5/5.10.0 > > Quick and dirty solution for the upcoming Slackware 13.1: > rm -rf $PKG/usr/lib$LIBDIRSUFFIX/perl5/5.10.1 > > A more generic approach: > find $PKG \( -name perllocal.pod -o -name .packlist \ > -o -name '*.bs' -empty \) -delete > find $PKG -depth -type d -empty -delete > > Could one of the admins please fix this? Thanks! > Done in local branch ; will be in next public update. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun May 16 03:24:41 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 15 May 2010 22:24:41 -0500 Subject: [Slackbuilds-users] Fix for merkaartor SlackBuild (patch attached) In-Reply-To: References: Message-ID: <20100515222441.4e46fecb@liberty.rlwhome.lan> On Fri, 14 May 2010 18:38:32 +0200 Manuel Reimer wrote: > Hello, > > I've attached a patch for the merkaartor SlackBuild file, which > already is part of the SBo package repository. > > The most important fix, I've added, is, that I've found out how I get > merkaartor to include all its language files. This took me some hours > to find out, so it would be great if you could leave the short > credits line, I've added, where it is. > > The two smaller fixes are: > - NODEBUG=1 > --> should be set according to the documentation > - Dropped the perl module stuff. Merkaartor doesn't ship any perl > modules, so I don't think we should keep those lines. A slightly tweaked version of that will be in the next public update; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun May 16 03:39:11 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 15 May 2010 22:39:11 -0500 Subject: [Slackbuilds-users] Kismet update In-Reply-To: <20100430204107.GA29958@kiras.geris> References: <20100430204107.GA29958@kiras.geris> Message-ID: <20100515223911.2c7b01b3@liberty.rlwhome.lan> On Fri, 30 Apr 2010 23:41:07 +0300 Audrius Ka?ukauskas wrote: > I'm going to submit updated Kismet SlackBuild (thanks goes to Antonio > Hern?ndez Blas for updating it), but before that I want to ask > something. Kismet developers strongly encourage to use 'make > suidinstall' for new version which makes it work only for the members > of 'kismet' group. I've tested that during installation this group is > created automatically, but I wanted to ask if it would be a better > idea to add it to file and > require it before starting the build process as I've seen in other > scripts that use UIDs and GIDs from SBo list? If so, should I take > the next unused GID from the list and add the code to check for the > group or should I leave it for SBo admins to do? See that link again -- you have uid/gid 234. Use responsibly. ;-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sun May 16 03:42:00 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 15 May 2010 22:42:00 -0500 Subject: [Slackbuilds-users] Stale oblige/oblige subdirectory In-Reply-To: References: Message-ID: <20100515224200.54a9587c@liberty.rlwhome.lan> On Mon, 3 May 2010 12:43:09 +0200 Mauro Giachero wrote: > Hello everybody, > > this is just to inform the admins that the Oblige entry contains a > stale 'oblige' subdirectory which should be removed. That was interesting, and it's fixed now. Thanks! :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From vmj at linuxbox.fi Sun May 16 15:30:30 2010 From: vmj at linuxbox.fi (Mikko Varri) Date: Sun, 16 May 2010 18:30:30 +0300 Subject: [Slackbuilds-users] ghc again In-Reply-To: References: Message-ID: <20100516153030.GA16292@linuxbox.fi> On Fri, May 14, 2010 at 12:05:19PM +0200, Eugen Wissner wrote: > > There's new version of ghc (6.12.2) and it doesn't provide utf8-string > again. An old utf8-string slackbuild is removed. I can't build > xmonad-contrib. Who can help to solve the problem? > Hi Eugen, I'm maintaining the GHC SlackBuild, and I am not going to update it for Slackware 13.0 anymore. Next update is coming for Slackware 13.1. There's couple of reasons: First, GHC 6.12.2 is known to be more buggy than GHC 6.12.1 (see [1]). Second, I'm in the process of updating the whole Haskell stack for Slackware 13.1. But you can probably take some other haskell slackbuild and modify it for utf8-string? -vmj [1] http://old.nabble.com/HEADS-UP:-bugs-in-GHC-6.12.2-td28533387.html From rworkman at slackbuilds.org Mon May 17 04:49:29 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 17 May 2010 04:49:29 +0000 Subject: [Slackbuilds-users] Updates - 20100517 Message-ID: <20100517044929.GA6382@slackbuilds.org> Mon May 17 04:45:59 UTC 2010 Well folks, this is likely to be the last update for our 13.0 repository, assuming nothing important comes up. We'll be trying to get everything in order for 13.1 now, so stay tuned for more information! As always, thanks to all of our maintainers and users for everything you do. academic/mathomatic: Updated for version 15.0.8. academic/rkward: Updated for version 0.5.3. academic/sword: Updated for version 1.6.1. academic/sympy: Updated for version 0.6.7. Thanks to the new maintainer, Jo?o Felipe Santo. academic/wxMaxima: Updated for version 0.8.5. audio/cmus: Updated for version 2.3.2. audio/ncmpcpp: Updated for version 0.5.3. audio/rosegarden: Updated for version 10.04.1. desktop/gtk-engines: Updated for version 2.20.1. desktop/scrotwm: Updated for version 0.9.23. desktop/xmobar: Added (status bar for xmonad wm). Thanks to Andy Bailey. development/Pygments: Updated for version 1.3.1. Thanks to the new maintainer, LukenShiro. development/apache-ant: Updated for version 1.8.1. development/bakefile: Added (a makefile generator). Thanks to Luis Henrique. development/cvsd: Added (wrapper for cvs in pserver mode). Thanks to Zordrak. development/eclipse: Updated for version 3.5.2. development/perl-xml-twig: Added (renamed from 'xml-twig') and updated for version 3.34. Thanks to Heinz Wiesinger. development/pip: Updated for version 0.7.1. development/squirrel-sql: Added (universal database client in java). Thanks to Dario Nicodemi. development/xdebug: Added (PHP extension for debugging PHP scripts). Thanks to Antonio Hern?ndez Blas. development/xml-twig: Removed (renamed to perl-xml-twig). games/lincity-ng: Added (SDL city simulation game). Thanks to M.Dinslage. games/warzone2100: Updated for version 2.3.0. graphics/FreeCAD: Added (a 3D CAD modeler). Thanks to Niels Horn. graphics/OpenCASCADE: Added (SDP for 3D modeling and such). Thanks to Niels Horn. graphics/brlcad: Added (open source solid modeling system). Thanks to Niels Horn. libraries/Mako: Updated for version 0.3.2. libraries/dietlibc: Added (small libc implementation). Thanks to Markus Reichelt. libraries/haskell-X11-xft: Added (XFT bindings for Haskell). Thanks to Andy Bailey. libraries/haskell-hinotify: Added (inotify support for haskell). Thanks to Andy Bailey. libraries/libcli: Added (a Cisco-like command-line interface library). Thanks to Heinz Wiesinger. libraries/libcsv: Added (a small/simple/fast CSV library). Thanks to Tarantino Antonino. libraries/libetpan: Updated for version 1.0. libraries/libnice: Updated for version 0.0.11. libraries/libquicktime: Updated for version 1.1.5. libraries/python-dateutil: Updated for version 1.5. libraries/python-distutils-extra: Updated for version 2.18. misc/merkaartor: Enabled translations (and other minor fixes). Thanks to Manuel Reimer. misc/nfoview: Added (viewer for NFO files). Thanks to Erik Hanson. network/claws-mail: Updated for version 3.7.6. network/claws-mail-extra-plugins: Updated for version 3.7.6. network/dovecot-cmusieve: Updated for version 1.1.8. network/efax-gtk: Updated for version 3.2.2. network/google-chrome: Updated for version 5.0.375.23. network/hiawatha: Updated for version 7.2. network/iscsitarget: Updated for version 1.4.19. network/maildrop: Added (a mail filtering agent). Thanks to ?ime Ramo. network/mz: Updated for version 0.39. network/policyd2: Added (policy server for MTAs). Thanks to Nishant Limbachia. network/vde2: Added - VDE is an ethernet compliant virtual network. Thanks to Antonio Hern?ndez Blas. network/vidalia: Updated for version 0.2.8. network/weechat: Added (a curses-based IRC client). Thanks to Coredumb. network/wol: Updated for version 0.7.1. network/xtables-addons: Updated for version 1.26 office/adobe-reader: Updated for version 9.3.2. office/scribus: Updated for version 1.3.6. system/apache-tomcat: Added - Java Servlet / JavaServer Pages implementation. Thanks to Heinz Wiesinger. system/atool: Added (an archive manager script). Thanks to David Woodfall. system/commons-daemon: Updated for version 1.0.2. system/fslint: Updated for version 2.42. system/makepassword: Added (pseudorandom password generator). Thanks to Pablo Santamaria. system/mucommander: Added (a light cross-platform file manager). Thanks to Dario Nicodemi. system/pyserial: Added - this is a python module for serial port access. Thanks to Grissiom. system/ranger: Added - ranger is an ncurses file manager with support for vi keybindings. Thanks to David Woodfall. system/sqlite2: Added - sqlite version 2, which is able to be installed alongside sqlite version 3 in Slackware. Thanks to V'yacheslav Stetskevych. system/terminus-font: Updated for version 4.30. system/zeroinstall-injector: Updated for version 0.47. From audrius at neutrino.lt Mon May 17 07:04:26 2010 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Mon, 17 May 2010 10:04:26 +0300 Subject: [Slackbuilds-users] Kismet update In-Reply-To: <20100515223911.2c7b01b3@liberty.rlwhome.lan> References: <20100430204107.GA29958@kiras.geris> <20100515223911.2c7b01b3@liberty.rlwhome.lan> Message-ID: <20100517070426.GA3359@kiras> On Sat, 2010-05-15 at 22:39:11 -0500, Robby Workman wrote: > See that link again -- you have uid/gid 234. Use responsibly. ;-) Great, thanks! Although kismet only requires gid, so I guess uid could be left blank (as it is for kvm). I'll be submitting the script when submissions are open, but for now it is attached for those who want to test it and can't wait. -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: kismet.tar.gz Type: application/x-tar-gz Size: 2474 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From niels.horn at gmail.com Mon May 17 10:12:11 2010 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 17 May 2010 07:12:11 -0300 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100517044929.GA6382@slackbuilds.org> References: <20100517044929.GA6382@slackbuilds.org> Message-ID: On Mon, May 17, 2010 at 1:49 AM, Robby Workman wrote: > Mon May 17 04:45:59 UTC 2010 > Well folks, this is likely to be the last update for our 13.0 repository, > ?assuming nothing important comes up. ?We'll be trying to get everything > ?in order for 13.1 now, so stay tuned for more information! ?As always, > ?thanks to all of our maintainers and users for everything you do. This is the first time I will experience a Slackware version change as a maintainer of some SlackBuilds, so I have a practical question about how things will work... Will the 13.0 repository still be updated? I maintain a few scripts for programs that are typically installed on servers, which might take a bit longer to be upgraded to 13.1 If upstream releases a security patch that needs an update to the SlackBuild (or even just the .info or README file), will an update to the 13.0 SlackBuild be accepted by the admins of SlackBuilds.org? I guess this should be limited to security updates only, with rare exceptions (following what Pat V. does with previous Slackware versions). Niels Horn From pwcazenave at gmail.com Mon May 17 13:19:30 2010 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Mon, 17 May 2010 14:19:30 +0100 Subject: [Slackbuilds-users] gimp-deskew-plugin Message-ID: <4BF14262.7040506@gmail.com> The gimp-deskew-plugin homepage and associated source link seem to have gone down. There also appears to be no contact from the author either. Would SlackBuilds.org be able to host the source or should I try and find a home for it myself? I have the copy of the source I originally used to test the SlackBuild on my machine. Thanks, Pierre From belka.ew at gmail.com Tue May 18 01:21:10 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Tue, 18 May 2010 03:21:10 +0200 Subject: [Slackbuilds-users] ghc again In-Reply-To: <20100516153030.GA16292@linuxbox.fi> References: <20100516153030.GA16292@linuxbox.fi> Message-ID: Hello, thanks for your answer. I've installed the old version of ghc. I could also modify other haskell-slackbuild for utf8-string:), but I thought, that maybe you have the utf8-string and someone else need it. Good luck! 2010/5/16 Mikko Varri > > > > > On Fri, May 14, 2010 at 12:05:19PM +0200, Eugen Wissner wrote: > > > > There's new version of ghc (6.12.2) and it doesn't provide utf8-string > > again. An old utf8-string slackbuild is removed. I can't build > > xmonad-contrib. Who can help to solve the problem? > > > > Hi Eugen, > > > I'm maintaining the GHC SlackBuild, and I am not going to update it > for Slackware 13.0 anymore. Next update is coming for Slackware 13.1. > There's couple of reasons: > > First, GHC 6.12.2 is known to be more buggy than GHC 6.12.1 (see [1]). > > Second, I'm in the process of updating the whole Haskell stack for > Slackware 13.1. > > But you can probably take some other haskell slackbuild and modify it > for utf8-string? > > > -vmj > > [1] http://old.nabble.com/HEADS-UP:-bugs-in-GHC-6.12.2-td28533387.html > > _______________________________________________ > 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 hba.nihilismus at gmail.com Tue May 18 01:47:06 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Mon, 17 May 2010 20:47:06 -0500 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100517044929.GA6382@slackbuilds.org> References: <20100517044929.GA6382@slackbuilds.org> Message-ID: On Sun, May 16, 2010 at 11:49 PM, Robby Workman wrote: > Mon May 17 04:45:59 UTC 2010 > Well folks, this is likely to be the last update for our 13.0 repository, > ?assuming nothing important comes up. ?We'll be trying to get everything > ?in order for 13.1 now, so stay tuned for more information! ?As always, > ?thanks to all of our maintainers and users for everything you do. Some VERSION mismatch between info and SlackBuild files: misc/heyu VERSION value in info file is: '2.4.0' But VERSION value in SlackBuild file is: '2.8.0' misc/tangogps VERSION value in info file is: '0.99.32' But VERSION value in SlackBuild file is: '0.99.2' desktop/xmobar VERSION value in info file is: '0.9.1' But VERSION value in SlackBuild file is: '0.9.2' audio/caps VERSION value in info file is: '0.4' But VERSION value in SlackBuild file is: '0.4.4' audio/cuberok VERSION value in info file is: '0.11' But VERSION value in SlackBuild file is: '0.0.11' games/openarena VERSION value in info file is: '0.8.5' But VERSION value in SlackBuild file is: '0.8.1' libraries/libgringotts VERSION value in info file is: '1.21' But VERSION value in SlackBuild file is: '1.2.1' libraries/libnice VERSION value in info file is: '0.0.10' But VERSION value in SlackBuild file is: '0.0.11' libraries/libetpan VERSION value in info file is: '0.58' But VERSION value in SlackBuild file is: '1.0' libraries/libreplaygain VERSION value in info file is: 'r435' But VERSION value in SlackBuild file is: 'r453' multimedia/dvdstyler VERSION value in info file is: '1.0.8b2' But VERSION value in SlackBuild file is: '1.8.0b3' multimedia/subtitlecomposer VERSION value in info file is: '0.53' But VERSION value in SlackBuild file is: '0.5.3' accessibility/linuxwacom VERSION value in info file is: '0.8.4_6' But VERSION value in SlackBuild file is: '0.8.4_4' network/r2e VERSION value in info file is: '2.6.6' But VERSION value in SlackBuild file is: '2.66' network/knock VERSION value in info file is: '.0.5' But VERSION value in SlackBuild file is: '0.5' network/dnstop VERSION value in info file is: '20080502' But VERSION value in SlackBuild file is: '20090128' -- - hba From rworkman at slackbuilds.org Tue May 18 04:47:15 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 17 May 2010 23:47:15 -0500 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: References: <20100517044929.GA6382@slackbuilds.org> Message-ID: <20100517234715.38ed682f@liberty.rlwhome.lan> On Mon, 17 May 2010 07:12:11 -0300 Niels Horn wrote: > On Mon, May 17, 2010 at 1:49 AM, Robby Workman > wrote: > > Mon May 17 04:45:59 UTC 2010 > > Well folks, this is likely to be the last update for our 13.0 > > repository, assuming nothing important comes up. ?We'll be trying > > to get everything in order for 13.1 now, so stay tuned for more > > information! ?As always, thanks to all of our maintainers and users > > for everything you do. > > > This is the first time I will experience a Slackware version change as > a maintainer of some SlackBuilds, so I have a practical question about > how things will work... > > Will the 13.0 repository still be updated? > > I maintain a few scripts for programs that are typically installed on > servers, which might take a bit longer to be upgraded to 13.1 > If upstream releases a security patch that needs an update to the > SlackBuild (or even just the .info or README file), will an update to > the 13.0 SlackBuild be accepted by the admins of SlackBuilds.org? > I guess this should be limited to security updates only, with rare > exceptions (following what Pat V. does with previous Slackware > versions). Once we go live with the 13.1 repo, 13.0 is pretty much dead. In the meantime, it's *possible* that we might accept a serious security fix, but no promises - it depends on available time. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue May 18 05:26:52 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 18 May 2010 00:26:52 -0500 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: References: <20100517044929.GA6382@slackbuilds.org> Message-ID: <20100518002652.2db6c62a@liberty.rlwhome.lan> On Mon, 17 May 2010 20:47:06 -0500 Antonio Hern?ndez Blas wrote: > On Sun, May 16, 2010 at 11:49 PM, Robby Workman > wrote: > > Mon May 17 04:45:59 UTC 2010 > > Well folks, this is likely to be the last update for our 13.0 > > repository, assuming nothing important comes up. ?We'll be trying > > to get everything in order for 13.1 now, so stay tuned for more > > information! ?As always, thanks to all of our maintainers and users > > for everything you do. > > Some VERSION mismatch between info and SlackBuild files: All of these should be fixed now except this one: > games/openarena > VERSION value in info file is: '0.8.5' > But VERSION value in SlackBuild file is: '0.8.1' The problem here is not in the .info file but rather the script itself. The final package version is indeed 0.8.5, but the source tarball is versioned with 0.8.1. This one will need better logic in the SlackBuild script, and I'm too busy with other stuff to handle that - mail the maintainer so that it can be done on the next update. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From niels.horn at gmail.com Tue May 18 09:32:19 2010 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 18 May 2010 06:32:19 -0300 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100518002652.2db6c62a@liberty.rlwhome.lan> References: <20100517044929.GA6382@slackbuilds.org> <20100518002652.2db6c62a@liberty.rlwhome.lan> Message-ID: On Tue, May 18, 2010 at 2:26 AM, Robby Workman wrote: > On Mon, 17 May 2010 20:47:06 -0500 > Antonio Hern?ndez Blas wrote: > >> On Sun, May 16, 2010 at 11:49 PM, Robby Workman >> wrote: >> > Mon May 17 04:45:59 UTC 2010 >> > Well folks, this is likely to be the last update for our 13.0 >> > repository, assuming nothing important comes up. ?We'll be trying >> > to get everything in order for 13.1 now, so stay tuned for more >> > information! ?As always, thanks to all of our maintainers and users >> > for everything you do. >> >> Some VERSION mismatch between info and SlackBuild files: > > > All of these should be fixed now except this one: > >> games/openarena >> ? ? VERSION value in info file is: '0.8.5' >> ? ? ? ? But VERSION value in SlackBuild file is: '0.8.1' > > > The problem here is not in the .info file but rather the > script itself. ?The final package version is indeed 0.8.5, > but the source tarball is versioned with 0.8.1. > > This one will need better logic in the SlackBuild script, > and I'm too busy with other stuff to handle that - mail > the maintainer so that it can be done on the next update. > > -RW > > _______________________________________________ > 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/ > > > Just a suggestion, but maybe the script that checks the submission (and complains when you leave MD5SUM empty, etc.) could check the VERSIONs between the SlackBuild and the .info file? Niels From chess at chessgriffin.com Tue May 18 10:17:56 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 18 May 2010 06:17:56 -0400 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100518002652.2db6c62a@liberty.rlwhome.lan> References: <20100517044929.GA6382@slackbuilds.org> <20100518002652.2db6c62a@liberty.rlwhome.lan> Message-ID: <20100518101756.GA16409@localhost> * Robby Workman [2010-05-18 00:26:52]: > On Mon, 17 May 2010 20:47:06 -0500 > Antonio Hern?ndez Blas wrote: > > > On Sun, May 16, 2010 at 11:49 PM, Robby Workman > > wrote: > > > Mon May 17 04:45:59 UTC 2010 > > > Well folks, this is likely to be the last update for our 13.0 > > > repository, assuming nothing important comes up. ?We'll be trying > > > to get everything in order for 13.1 now, so stay tuned for more > > > information! ?As always, thanks to all of our maintainers and users > > > for everything you do. > > > > Some VERSION mismatch between info and SlackBuild files: > > > All of these should be fixed now except this one: > > > games/openarena > > VERSION value in info file is: '0.8.5' > > But VERSION value in SlackBuild file is: '0.8.1' > > > The problem here is not in the .info file but rather the > script itself. The final package version is indeed 0.8.5, > but the source tarball is versioned with 0.8.1. > > This one will need better logic in the SlackBuild script, > and I'm too busy with other stuff to handle that - mail > the maintainer so that it can be done on the next update. > > -RW And since this script is one of mine, I thought I would respond. The script works fine and the real problem is the stupid way upstream (OpenArena) handles versioning, but indeed the script can be improved with better logic to handle said stupidity. It's been on my $TODO, in fact, but I have not had the time. Patches to the script are welcome, or if somebody wants to take maintainership of the script and fix it, that is fine too. Otherwise, I'll update the script when I can -- and I will try to bring it to a front burner but no promises. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From s at ramov.com Tue May 18 11:37:03 2010 From: s at ramov.com (=?UTF-8?Q?=C5=A0ime=20Ramov?=) Date: Tue, 18 May 2010 13:37:03 +0200 (CEST) Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100517044929.GA6382@slackbuilds.org> References: <20100517044929.GA6382@slackbuilds.org> Message-ID: <1274182623.5562573@192.168.2.228> Hi, > network/maildrop: Added (a mail filtering agent). > Thanks to ?ime Ramo. That would be ?ime Ramov :) From chaos.proton at gmail.com Tue May 18 13:08:12 2010 From: chaos.proton at gmail.com (Grissiom) Date: Tue, 18 May 2010 21:08:12 +0800 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: References: <20100517044929.GA6382@slackbuilds.org> Message-ID: 2010/5/18 Antonio Hern?ndez Blas > Some VERSION mismatch between info and SlackBuild files: > > misc/heyu > VERSION value in info file is: '2.4.0' > But VERSION value in SlackBuild file is: '2.8.0' > > ... > network/r2e > VERSION value in info file is: '2.6.6' > But VERSION value in SlackBuild file is: '2.66' > > network/knock > VERSION value in info file is: '.0.5' > But VERSION value in SlackBuild file is: '0.5' > > network/dnstop > VERSION value in info file is: '20080502' > But VERSION value in SlackBuild file is: '20090128' > > I think it's impossible to find all the mismatches by hand. So did you use a script or something like that to check them? I'm curious about this because the job is much like what my little project should do -- sbo-dev-helper ;) -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From hba.nihilismus at gmail.com Tue May 18 18:37:00 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Tue, 18 May 2010 13:37:00 -0500 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: References: <20100517044929.GA6382@slackbuilds.org> Message-ID: On Tue, May 18, 2010 at 8:08 AM, Grissiom wrote: > I think it's?impossible?to find all the mismatches by hand. So did you use a > script or something like that to check them? > I'm?curious?about this because the job is much like what my little project > should do -- sbo-dev-helper ;) > http://hba.ath.cx/sbo_bugs.sh.txt And yeap... it used to "work" two years ago :-) -- - hba From chess at chessgriffin.com Tue May 18 18:43:38 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 18 May 2010 14:43:38 -0400 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100518101756.GA16409@localhost> References: <20100517044929.GA6382@slackbuilds.org> <20100518002652.2db6c62a@liberty.rlwhome.lan> <20100518101756.GA16409@localhost> Message-ID: <20100518184338.GA11790@localhost> * Chess Griffin [2010-05-18 06:17:56]: > And since this script is one of mine, I thought I would respond. The > script works fine and the real problem is the stupid way upstream > (OpenArena) handles versioning, but indeed the script can be improved > with better logic to handle said stupidity. It's been on my $TODO, in > fact, but I have not had the time. > > Patches to the script are welcome, or if somebody wants to take > maintainership of the script and fix it, that is fine too. Otherwise, > I'll update the script when I can -- and I will try to bring it to a > front burner but no promises. > Well, that front burner came free. :-) Attached is a patch to the openarena.SlackBuild. It seems to work fine here, but I would welcome some testers. -- Chess Griffin -------------- next part -------------- --- /var/lib/sbopkg/SBo/13.0/games/openarena/openarena.SlackBuild 2010-04-18 21:56:59.000000000 -0400 +++ /home/chess/builds/openarena/openarena.SlackBuild 2010-05-18 09:06:47.000000000 -0400 @@ -2,7 +2,7 @@ # Slackware build script for OpenArena -# Copyright 2007-2009 Chess Griffin +# Copyright 2007-2010 Chess Griffin # All rights reserved. # # Redistribution and use of this script, with or without modification, is @@ -23,10 +23,10 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=openarena -VERSION=${VERSION:-0.8.1} -FINAL_VERSION=${FINAL_VERSION:-0.8.5} # Keep this for future patches +VERSION=${VERSION:-0.8.5} +SRC_VERSION=${SRC_VERSION:-0.8.1} # Keep this for future patches ARCH=${ARCH:-i486} -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} TAG=${TAG:-_SBo} CWD=$(pwd) @@ -62,11 +62,11 @@ fi rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP -rm -rf $PRGNAM-$VERSION +rm -rf $PRGNAM-$SRC_VERSION unzip -o $CWD/oa081.zip # Keep the following for any future patches unzip -o $CWD/oa085p.zip -cd $PRGNAM-$VERSION +cd $PRGNAM-$SRC_VERSION chown -R root:root . find . \ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ @@ -92,9 +92,9 @@ install -D -m 0644 $CWD/openarena.deskto mkdir -p $PKG/usr/share/pixmaps cp $CWD/*.png $PKG/usr/share/pixmaps -mkdir -p $PKG/usr/doc/$PRGNAM-$FINAL_VERSION -cp $DOCS $PKG/usr/doc/$PRGNAM-$FINAL_VERSION -find $PKG/usr/doc/$PRGNAM-$FINAL_VERSION -type f -exec chmod 0644 {} \; +mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION +cp $DOCS $PKG/usr/doc/$PRGNAM-$VERSION +find $PKG/usr/doc/$PRGNAM-$VERSION -type f -exec chmod 0644 {} \; mkdir -p $PKG/usr/share/games/openarena/{baseoa,missionpack} cp -rf {baseoa,missionpack}/ $PKG/usr/share/games/openarena/ @@ -121,4 +121,4 @@ fi chmod 755 $PKG/usr/games/openarena* cd $PKG -/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$FINAL_VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} +/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue May 18 19:32:01 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 18 May 2010 14:32:01 -0500 Subject: [Slackbuilds-users] Updates - 20100517 In-Reply-To: <20100518184338.GA11790@localhost> References: <20100517044929.GA6382@slackbuilds.org> <20100518002652.2db6c62a@liberty.rlwhome.lan> <20100518101756.GA16409@localhost> <20100518184338.GA11790@localhost> Message-ID: <20100518143201.42a52c97@liberty.rlwhome.lan> On Tue, 18 May 2010 14:43:38 -0400 Chess Griffin wrote: > * Chess Griffin [2010-05-18 06:17:56]: > > > And since this script is one of mine, I thought I would respond. > > The script works fine and the real problem is the stupid way > > upstream (OpenArena) handles versioning, but indeed the script can > > be improved with better logic to handle said stupidity. It's been > > on my $TODO, in fact, but I have not had the time. > > > > Patches to the script are welcome, or if somebody wants to take > > maintainership of the script and fix it, that is fine too. > > Otherwise, I'll update the script when I can -- and I will try to > > bring it to a front burner but no promises. > > > > Well, that front burner came free. :-) > > Attached is a patch to the openarena.SlackBuild. It seems to work > fine here, but I would welcome some testers. It passes the "looks good" inspection, so it's done; thanks! :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From donaldcallen at gmail.com Sat May 22 01:48:42 2010 From: donaldcallen at gmail.com (Donald Allen) Date: Fri, 21 May 2010 21:48:42 -0400 Subject: [Slackbuilds-users] fotoxx problem Message-ID: On the page http://slackbuilds.org/repository/13.0/graphics/fotoxx/ if you click the fotoxx-9.9.tar.gz link, you get a "Page not found" error. /Don From niels.horn at gmail.com Sat May 22 02:08:48 2010 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 21 May 2010 23:08:48 -0300 Subject: [Slackbuilds-users] fotoxx problem In-Reply-To: References: Message-ID: On Fri, May 21, 2010 at 10:48 PM, Donald Allen wrote: > On the page > > http://slackbuilds.org/repository/13.0/graphics/fotoxx/ > > if you click the > > fotoxx-9.9.tar.gz > > link, you get a "Page not found" error. > > /Don Newer versions were released since the SlackBuild was approved. Have you tried using the script with the newer tarballs from here: http://kornelix.squarespace.com/downloads/ Niels From donaldcallen at gmail.com Sat May 22 02:57:10 2010 From: donaldcallen at gmail.com (Donald Allen) Date: Fri, 21 May 2010 22:57:10 -0400 Subject: [Slackbuilds-users] fotoxx problem In-Reply-To: References: Message-ID: On Fri, May 21, 2010 at 10:08 PM, Niels Horn wrote: > On Fri, May 21, 2010 at 10:48 PM, Donald Allen wrote: >> On the page >> >> http://slackbuilds.org/repository/13.0/graphics/fotoxx/ >> >> if you click the >> >> fotoxx-9.9.tar.gz >> >> link, you get a "Page not found" error. >> >> /Don > > Newer versions were released since the SlackBuild was approved. > Have you tried using the script with the newer tarballs from here: > http://kornelix.squarespace.com/downloads/ Thanks for the pointer, but my main purpose in sending the message was to alert Robby et al that the source link on this page was dangling. /Don > > Niels > _______________________________________________ > 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 niels.horn at gmail.com Sat May 22 03:08:19 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 22 May 2010 00:08:19 -0300 Subject: [Slackbuilds-users] fotoxx problem In-Reply-To: References: Message-ID: On Fri, May 21, 2010 at 11:57 PM, Donald Allen wrote: > On Fri, May 21, 2010 at 10:08 PM, Niels Horn wrote: >> On Fri, May 21, 2010 at 10:48 PM, Donald Allen wrote: >>> On the page >>> >>> http://slackbuilds.org/repository/13.0/graphics/fotoxx/ >>> >>> if you click the >>> >>> fotoxx-9.9.tar.gz >>> >>> link, you get a "Page not found" error. >>> >>> /Don >> >> Newer versions were released since the SlackBuild was approved. >> Have you tried using the script with the newer tarballs from here: >> http://kornelix.squarespace.com/downloads/ > > Thanks for the pointer, but my main purpose in sending the message was > to alert Robby et al that the source link on this page was dangling. > > /Don > >> >> Niels >> _______________________________________________ I'm sure he'll pick it up, but SlackBuilds is closed for new submissions awaiting the release of Slackware 13.1 I use fotoxx as well, but have not had time yet to try the newer version of the source :) Niels From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Sun May 23 14:22:53 2010 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Sun, 23 May 2010 16:22:53 +0200 Subject: [Slackbuilds-users] Small bug in g3data slackbuild In-Reply-To: <20100517044929.GA6382@slackbuilds.org> References: <20100517044929.GA6382@slackbuilds.org> Message-ID: <4BF93A3D.2020906@skmail.ikp.physik.tu-darmstadt.de> Hello! I know that not much will happen until the new Slackware is out, but just FYI: the g3data slackbuild is installing g3data.destop instead of g3data.desktop. Patch is attached. Best regards, Serban Udrea -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: g3data.SlackBuild.patch URL: From belka.ew at gmail.com Tue May 25 14:36:00 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Tue, 25 May 2010 15:36:00 +0100 Subject: [Slackbuilds-users] 13.1 Message-ID: hello, can we resubmit our slackbuilds for 13.1? it's out! Should we use .txz as extension or $PKGTYPE variable as earlier? Best regards Eugene. From dragonwisard at gmail.com Tue May 25 15:03:47 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Tue, 25 May 2010 11:03:47 -0400 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: Message-ID: On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner wrote: > Should we use .txz as extension or $PKGTYPE variable as earlier? > I think we should still use $PKGTYPE, but the question is whether the default should be .txz. Personally, I'm in favor of changing the default to txz. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Tue May 25 15:13:04 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Tue, 25 May 2010 18:13:04 +0300 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: Message-ID: 2010/5/25 Ben Mendis : > > > On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner wrote: >> >> Should we use .txz as extension or $PKGTYPE variable as earlier? > > I think we should still use $PKGTYPE, but the question is whether the > default should be .txz. > > Personally, I'm in favor of changing the default to txz. i'm, too but we have to think of the compress-decompress speed, too. i didn't see much difference. i'll do some time mesuares of the script runs sometime tomarrow (i still haven't finished the update) . -- Ozan From ml at mareichelt.com Tue May 25 16:11:07 2010 From: ml at mareichelt.com (markus reichelt) Date: Tue, 25 May 2010 18:11:07 +0200 Subject: [Slackbuilds-users] slackbuilds tested for 13.1 Message-ID: <20100525161107.GE5993@pc21.mareichelt.com> hi, i tested and verified the slackbuilds i maintain for 13.1, they can just be copied over (less hassle for me :-) libraries/dietlibc network/vidalia as just mentioned already on this list, i as well intend to switch to the default .txz pkgtype with the next update of those scripts. -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From mfilpot at gmail.com Tue May 25 16:43:50 2010 From: mfilpot at gmail.com (Matthew Fillpot) Date: Tue, 25 May 2010 12:43:50 -0400 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: Message-ID: In my experiences tgz compresses faster, it is larger but the space differences shouldn't matter if it is for local use only. Now if we can make the default script set compression type then it would be more open for the users to decide which is best for their needs. On May 25, 2010 11:13 AM, "Ozan T?rky?lmaz" wrote: 2010/5/25 Ben Mendis : > > > On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner wrote: >> >> Should we us... i'm, too but we have to think of the compress-decompress speed, too. i didn't see much difference. i'll do some time mesuares of the script runs sometime tomarrow (i still haven't finished the update) . -- Ozan _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at sla... -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob0 at slackbuilds.org Tue May 25 18:29:05 2010 From: rob0 at slackbuilds.org (Rob McGee) Date: Tue, 25 May 2010 13:29:05 -0500 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: Message-ID: <20100525182905.GC19868@cardinal> On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote: > On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner > wrote: > > > Should we use .txz as extension or $PKGTYPE variable as earlier? > > I think we should still use $PKGTYPE, but the question is whether > the default should be .txz. > > Personally, I'm in favor of changing the default to txz. I am not. xz is a fine tool, possibly superior to gz in every way. But it has not been around as long. I run numerous older boxes, some of which are not likely to get upgraded soon if ever, and sometimes it's nice to be able to look inside a binary package. With .tgz that is well supported anywhere. Not so with .txz. As for the space savings, with this discussion we have surely wasted more bytes than gz would ever waste. I say leave it as is, default to .tgz for $PKGTYPE. From dragonwisard at gmail.com Tue May 25 19:34:36 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Tue, 25 May 2010 15:34:36 -0400 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100525182905.GC19868@cardinal> References: <20100525182905.GC19868@cardinal> Message-ID: For the sake of debate, only. (Please don't take offense at any of my comments.) On Tue, May 25, 2010 at 2:29 PM, Rob McGee wrote: > xz is a fine tool, possibly superior to gz in every way. But it has > not been around as long. "Linux is a fine tool, possibly superior to MS-DOS in every way. But it has not been around as long." Your argument appears to stipulate that we should prefer older solutions even when the alternatives are superior in function. > I run numerous older boxes, some of which > are not likely to get upgraded soon if ever, Ignoring the obvious security concern of not keeping your boxes updated, how long are the rest of us expected to wait for you to join to the 21st century? I'm sure your situation is common in this community (even I have a couple old installs on P3s), however our collective procrastination is holding back progress and potential. Setting *some* deadline and sticking to it will give people incentive to prepare their systems for xz. Otherwise people will procrastinate indefinitely and never be ready for it. As for the space savings, with this discussion we have surely wasted > more bytes than gz would ever waste. > For any given package, yes. But the aggregate savings would be more than what we've "wasted" so far. > > I say leave it as is, default to .tgz for $PKGTYPE. > It is _just_ a default. Changing the default won't prevent you from using gz, but it will encourage people to upgrade to xz. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mickeytintincolle at yahoo.fr Tue May 25 20:02:01 2010 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Tue, 25 May 2010 22:02:01 +0200 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100525182905.GC19868@cardinal> References: <20100525182905.GC19868@cardinal> Message-ID: <20100525220201.5d51a620@yahoo.fr> Le Tue, 25 May 2010 13:29:05 -0500, Rob McGee a ?crit : > On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote: > > On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner > > wrote: > > > > > Should we use .txz as extension or $PKGTYPE variable as earlier? > > > > I think we should still use $PKGTYPE, but the question is whether > > the default should be .txz. > > > > Personally, I'm in favor of changing the default to txz. > > I am not. > > xz is a fine tool, possibly superior to gz in every way. But it has > not been around as long. I run numerous older boxes, some of which > are not likely to get upgraded soon if ever, and sometimes it's nice > to be able to look inside a binary package. tar-1.22 and xz from Slackware 13.0 sources just build fine even on Slackware 11.0 (and I did it yesterday) . > > With .tgz that is well supported anywhere. Not so with .txz. > > As for the space savings, with this discussion we have surely wasted > more bytes than gz would ever waste. > > I say leave it as is, default to .tgz for $PKGTYPE. > _______________________________________________ > 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 banderols at gmail.com Tue May 25 20:01:36 2010 From: banderols at gmail.com (Murat D. Kadirov) Date: Wed, 26 May 2010 02:01:36 +0600 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100525182905.GC19868@cardinal> References: <20100525182905.GC19868@cardinal> Message-ID: <4BFC2CA0.1000303@gmail.com> On 26.05.2010 00:29, Rob McGee wrote: > On Tue, May 25, 2010 at 11:03:47AM -0400, Ben Mendis wrote: > >> On Tue, May 25, 2010 at 10:36 AM, Eugen Wissner >> wrote: >> >> >>> Should we use .txz as extension or $PKGTYPE variable as earlier? >>> >> I think we should still use $PKGTYPE, but the question is whether >> the default should be .txz. >> >> Personally, I'm in favor of changing the default to txz. >> > I am not. > > xz is a fine tool, possibly superior to gz in every way. But it has > not been around as long. I run numerous older boxes, some of which > are not likely to get upgraded soon if ever, and sometimes it's nice > to be able to look inside a binary package. > > With .tgz that is well supported anywhere. Not so with .txz. > > As for the space savings, with this discussion we have surely wasted > more bytes than gz would ever waste. > > I say leave it as is, default to .tgz for $PKGTYPE. > Slackware 13.x use xz. Even leaving aside the benefits of the xz, the use of xz is more logical for latest versions of Slackware. I for the use of xz by default for $PKGTYPE -- Murat D. Kadirov PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 76EE 1B97 0A0E CEC0 6AA0 From sombriks at gmail.com Tue May 25 20:11:19 2010 From: sombriks at gmail.com (Leonardo) Date: Tue, 25 May 2010 17:11:19 -0300 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <4BFC2CA0.1000303@gmail.com> References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> Message-ID: all the question is about to make the 13.x repo to be retrocompatible or not. just leave it .tgz, http://darkstar.ist.utl.pt/slackware/slackware-current/source/a/pkgtools/scripts/ makepkg script adds also .tbz and .tlz as compression options, so if it's so important to support the new format, why not suport those ones too? anyway the user can easily grab the .SlackBuild, read and change it to the desired compression strategy From ash at spooksoftware.com Tue May 25 20:14:22 2010 From: ash at spooksoftware.com (Ash Wiren) Date: Wed, 26 May 2010 04:14:22 +0800 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> Message-ID: I just flipped a coin, and it came up tails for tgz, so thats my vote. I flipped a coin because really its a meaningless point considering one can override the default at build time. On Wed, May 26, 2010 at 4:11 AM, Leonardo wrote: > all the question is about to make the 13.x repo to be retrocompatible or not. > > just leave it .tgz, > > http://darkstar.ist.utl.pt/slackware/slackware-current/source/a/pkgtools/scripts/ > > makepkg script adds also .tbz and .tlz as compression options, so if > it's so important to support the new format, why not suport those ones > too? > > anyway the user can easily grab the .SlackBuild, read and change it to > the desired compression strategy > _______________________________________________ > 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 belka.ew at gmail.com Wed May 26 02:12:06 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Wed, 26 May 2010 03:12:06 +0100 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> Message-ID: we decided to use .tgz at least for 13.0 http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-July/004281.html but now we have 13.1 and I don't think, that there are so many changes, that sbo couldn't make one more update. We can use standard slackware format (.txz) and leave it in $PKGTYPE, so everybody can change it for .tlz, .tgz etc. And could be better to define $PKGTYPE at the start of our scripts with other variables such arch. 2010/5/25 Ash Wiren : > I just flipped a coin, and it came up tails for tgz, so thats my vote. > I flipped a coin because really its a meaningless point considering > one can override the default at build time. > > On Wed, May 26, 2010 at 4:11 AM, Leonardo wrote: >> all the question is about to make the 13.x repo to be retrocompatible or not. >> >> just leave it .tgz, >> >> http://darkstar.ist.utl.pt/slackware/slackware-current/source/a/pkgtools/scripts/ >> >> makepkg script adds also .tbz and .tlz as compression options, so if >> it's so important to support the new format, why not suport those ones >> too? >> >> anyway the user can easily grab the .SlackBuild, read and change it to >> the desired compression strategy >> _______________________________________________ >> 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/ > > From rworkman at slackbuilds.org Wed May 26 03:30:39 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 25 May 2010 22:30:39 -0500 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> Message-ID: <20100525223039.1ce5f107@liberty.rlwhome.lan> On Wed, 26 May 2010 03:12:06 +0100 Eugen Wissner wrote: > we decided to use .tgz at least for 13.0 > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-July/004281.html As it turned out, we *did* make it configurable by passing an alternate value to PKGTYPE when invoking the script, and that's still the case. > but now we have 13.1 and I don't think, that there are so many > changes, that sbo couldn't make one more update. We can use standard > slackware format (.txz) and leave it in $PKGTYPE, so everybody can > change it for .tlz, .tgz etc. That's actually *more* work than the present situation - there's no need to edit any scripts even *now* if you want to make txz packages: PKGTYPE=txz ./app.SlackBuild And could be better to define $PKGTYPE > at the start of our scripts with other variables such arch. There's no need to define it anywhere -- see above. Anyway, since there seems to be some desire for a definitive statement on this, I'm going to make one: There are no plans to change the default package compression at any point in the near future. The reasons include, but are not necessarily limited to, the following: 1. We like it that way. :-) 2. It works fine as is. 3. It minimizes the time required to build a package. 4. It's easy to customize if the admin prefers something else. 5. There's no compelling reason to change it. 6. We like it that way. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From volkerdi at slackware.com Wed May 26 03:41:44 2010 From: volkerdi at slackware.com (Patrick J. Volkerding) Date: Tue, 25 May 2010 22:41:44 -0500 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100525223039.1ce5f107@liberty.rlwhome.lan> References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> <20100525223039.1ce5f107@liberty.rlwhome.lan> Message-ID: <4BFC9878.8030305@slackware.com> On 05/25/2010 10:30 PM, Robby Workman wrote: > Anyway, since there seems to be some desire for a definitive > statement on this, I'm going to make one: > > There are no plans to change the default package compression at > any point in the near future. The reasons include, but are not > necessarily limited to, the following: > > 1. We like it that way. :-) > > 2. It works fine as is. > > 3. It minimizes the time required to build a package. > > 4. It's easy to customize if the admin prefers something else. > > 5. There's no compelling reason to change it. > > 6. We like it that way. :-) I'd have to agree. For local package builds, a .tgz default makes sense. But if you happen to be running out of space for packages on a CD, then you can switch to .txz easily enough. :-D Take care, Pat From rworkman at slackbuilds.org Wed May 26 05:58:56 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 00:58:56 -0500 Subject: [Slackbuilds-users] Status Report Message-ID: <20100526005856.5478ced1@liberty.rlwhome.lan> I know there's a bit of anticipation by now, and probably some pondering as to why we haven't got a set of scripts out there for 13.1 yet, so I guess some explanation/discussion is in order... Basically, the Slackware 13.1 release snuck up on us (yes, even though several of the SBo admin team *knew* it was coming), and it happened to coincide with real-life conflicts for several of the admins, so we didn't get as far along with preparation as we normally would have. Because we believe that, like Slackware, it should only go public "when it's ready," we decided to wait until we were comfortable calling things "ready" for public consumption before spinning tarballs and such and putting out a public changelog in the usual manner. The other major factor that's played a part in the delay is something that lots of people have long requested, and that is tracking the repository in git. Yes, that's right - we now have a git repo with everything in it. Consider the ensuing comments to be NON-FINAL, NON-BINDING, and SUBJECT TO CHANGE based on feedback, our preferences, logistics, phase of the moon, and various other known and unknown factors... http://slackbuilds.org/gitweb/ has a web interface to the git repositories - you will notice that there is a 'slackbuilds' repo and a 'templates' repo, and each of them contains exactly what the name implies. The 'slackbuilds' repo contains several "predictable" branches: 11.0, 12.0, 12.1, 12.2, 13.0, and 13.1, and each of those has exactly what the branch name implies. It's a bit early to be setting anything in stone, but unless something changes, the '13.1' branch at any given moment should be the equivalent of what is available on the website (in other words, it's exactly what you would have gotten from an rsync of the slackbuilds/13.1/ tree if we didn't have a git repo). Each admin will have one or more separate branches (which might have various names) where he will push approved submissions as they are cleared. From time to time, one of us will gather the various commits from the admin-specific branches and commit them to master, and once we decide to do a public push to http (the "old" way of doing things), then we'll merge master into the 13.1 branch, generate the tarballs, gpg sigs, and ChangeLog, and sync that over to the http tree. Again, the http tree (the old way) will always be in sync with the 13.1 branch (until 14.0 is out). For those of you who don't know git and/or have no desire to learn it, fear not -- nothing changes with respect to the rest of our site. Everything stays the same in regard to rsync, ftp, http, and so on. For those of you who *do* know/use git, this is another option for you. For the time being, submissions will still be done using the existing method - git pull requests are not an option right now. [1] This probably doesn't need to be said, but for your own sanity, DO NOT base any work on an admin-specific branch (e.g. on my 'rworkman' branch) -- those are subject to be rebased, removed, etcetera at any time. Anyway, we hope to have all the kinks ironed out of this soon, and once we do, we'll get everything up and running normally. Thanks for your support and patience, and in the meantime, enjoy 13.1! [1] That's not to say that a git pull request won't be honored. In fact, if you were to clone master and host it on e.g. github, and create a separate branch for each app that you submit via our submission form, and note that in the comments of the submission, it's certainly possible that some of us :) might use that. This is particularly true for cases where: [ $admin == rworkman ] && [ $changetype == trivial ] :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Wed May 26 07:08:58 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Wed, 26 May 2010 10:08:58 +0300 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100525223039.1ce5f107@liberty.rlwhome.lan> References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> <20100525223039.1ce5f107@liberty.rlwhome.lan> Message-ID: 2010/5/26 Robby Workman : > On Wed, 26 May 2010 03:12:06 +0100 > Eugen Wissner wrote: > >> we decided to use .tgz at least for 13.0 >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-July/004281.html > > > As it turned out, we *did* make it configurable by passing an > alternate value to PKGTYPE when invoking the script, and that's > still the case. well because variable defined at the end of the script, any ordinary user can't see if PKGTYPE is a changable variable simply. moving to more user seeable place next to TMP etc would be much better. -- Ozan From matteo.bernardini at sns.it Wed May 26 08:14:32 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Wed, 26 May 2010 10:14:32 +0200 Subject: [Slackbuilds-users] Status Report In-Reply-To: <20100526005856.5478ced1@liberty.rlwhome.lan> References: <20100526005856.5478ced1@liberty.rlwhome.lan> Message-ID: <4BFCD868.1040603@sns.it> On 26/05/2010 07:58, Robby Workman wrote: > Yes, that's right - we > now have a git repo with everything in it. > I can only say: "great shot!" or "yabba dabba doo!" :D thanks a lot also for this, really appreciated :) Matteo From s at ramov.com Wed May 26 09:44:44 2010 From: s at ramov.com (=?windows-1252?Q?=8Aime_Ramov?=) Date: Wed, 26 May 2010 11:44:44 +0200 Subject: [Slackbuilds-users] MuPDF Message-ID: <4BFCED8C.40003@ramov.com> Hello - I see that MuPDF is removed from the current git tree because of the bogus download link. It's a shame as it is a simple fix and a nice PDF viewer (I personally use it). A stable release tarballs are now available. If the original maintainer is not available to update it, I can take it over. From artourter at gmail.com Wed May 26 15:26:42 2010 From: artourter at gmail.com (Greg' Ar Tourter) Date: Wed, 26 May 2010 16:26:42 +0100 Subject: [Slackbuilds-users] broadcom-sta on 13.1 Message-ID: Hi I see DSomero removed broadcom-sta from the 13.1 branch on git, I have submitted a patch a while back to Ponce for his "unofficial -current" git repo on github which solves the build issue. feel free to use it for the release. ArTourter From dave at unrealize.co.uk Wed May 26 16:28:11 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 26 May 2010 17:28:11 +0100 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <4BFC9878.8030305@slackware.com> References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> <20100525223039.1ce5f107@liberty.rlwhome.lan> <4BFC9878.8030305@slackware.com> Message-ID: <20100526162811.GA15058@Junius> On (22:41 25/05/10), Patrick Volkerdink put forth the proposition: > On 05/25/2010 10:30 PM, Robby Workman wrote: >> Anyway, since there seems to be some desire for a definitive >> statement on this, I'm going to make one: >> >> There are no plans to change the default package compression at >> any point in the near future. The reasons include, but are not >> necessarily limited to, the following: >> >> 1. We like it that way. :-) >> >> 2. It works fine as is. >> >> 3. It minimizes the time required to build a package. >> >> 4. It's easy to customize if the admin prefers something else. >> >> 5. There's no compelling reason to change it. >> >> 6. We like it that way. :-) I don't really see any need to change. I set PKGTYPE and ARCH up in shell long ago. > > I'd have to agree. For local package builds, a .tgz default makes > sense. But if you happen to be running out of space for packages on a > CD, then you can switch to .txz easily enough. :-D > > Take care, > > Pat > _______________________________________________ > 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/ -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From not0read0765 at yopmail.com Wed May 26 17:03:12 2010 From: not0read0765 at yopmail.com (Olive) Date: Wed, 26 May 2010 21:03:12 +0400 Subject: [Slackbuilds-users] slackbuilds 13.1 Message-ID: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> Does anyone have an idea of when the slackbuilds will be released for 13.1 (Yeah I know when it is ready, but maybe has a more precise idea). Olive From belka.ew at gmail.com Wed May 26 17:40:04 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Wed, 26 May 2010 18:40:04 +0100 Subject: [Slackbuilds-users] slackbuilds 13.1 In-Reply-To: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> References: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> Message-ID: You can install programs with the old slackbuilds, there is not much difference. I suppose, a lot of slackbuilds will be copied from 13.0 repo for 13.1. 2010/5/26 Olive : > Does anyone have an idea of when the slackbuilds will be released for > 13.1 (Yeah I know when it is ready, but maybe has a more precise idea). > > Olive > > > _______________________________________________ > 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 gmartin at gmartin.org Wed May 26 18:04:24 2010 From: gmartin at gmartin.org (gmartin) Date: Wed, 26 May 2010 12:04:24 -0600 Subject: [Slackbuilds-users] slackbuilds 13.1 In-Reply-To: References: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> Message-ID: See Robbie's message titled: Status Report \\Greg On Wed, May 26, 2010 at 11:40 AM, Eugen Wissner wrote: > You can install programs with the old slackbuilds, there is not much > difference. I suppose, a lot of slackbuilds will be copied from 13.0 > repo for 13.1. > > 2010/5/26 Olive : > > Does anyone have an idea of when the slackbuilds will be released for > > 13.1 (Yeah I know when it is ready, but maybe has a more precise idea). > > > > Olive > > > > > > _______________________________________________ > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From belka.ew at gmail.com Wed May 26 18:06:48 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Wed, 26 May 2010 19:06:48 +0100 Subject: [Slackbuilds-users] slackbuilds 13.1 In-Reply-To: References: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> Message-ID: we're waiting for concrete date:) 2010/5/26 gmartin : > See Robbie's message titled: Status Report > \\Greg > > > > On Wed, May 26, 2010 at 11:40 AM, Eugen Wissner wrote: >> >> You can install programs with the old slackbuilds, there is not much >> difference. I suppose, a lot of slackbuilds will be copied from 13.0 >> repo for 13.1. >> >> 2010/5/26 Olive : >> > Does anyone have an idea of when the slackbuilds will be released for >> > 13.1 (Yeah I know when it is ready, but maybe has a more precise idea). >> > >> > Olive >> > >> > >> > _______________________________________________ >> > 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/ >> > > > _______________________________________________ > 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 s at ramov.com Wed May 26 18:20:34 2010 From: s at ramov.com (=?utf-8?B?xaBpbWU=?= Ramov) Date: Wed, 26 May 2010 20:20:34 +0200 Subject: [Slackbuilds-users] slackbuilds 13.1 In-Reply-To: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> References: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> Message-ID: <20100526181920.GA21095@ramov.com> * Olive [2010-05-26 21:03+0400]: > Does anyone have an idea of when the slackbuilds will be released for > 13.1 (Yeah I know when it is ready, but maybe has a more precise idea). Why not use the Git repo? Most of it should work without issues, if not, it is an easy case of fixing it most times. --S. From mjjzf at syntaktisk.dk Wed May 26 19:15:19 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Wed, 26 May 2010 15:15:19 -0400 Subject: [Slackbuilds-users] My Slackbuilds Message-ID: <20100526151519.276cca2b@darkstar.example.net> I tested my Slackbuilds to the extent I can - * Uget - 13.0 build works on 13.1 * Gajim - 13.0 build works on 13.1; pyOpenSSL, which is a dep for Gajim, also works. * GTK-Recordmydesktop: Well, it seems that the Recordmydesktop slackbuild for 13.0 doesn't build right on 13.1, so I can't say anything about the frontend. ... and just to make Slackware do what I want it to, I immediately installed Claws Mail. The 13.0 builds for Claws-mail, claws-mail-extra-plugins and libetpan all work as they should. Yours, Morten From dave at unrealize.co.uk Wed May 26 19:41:07 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 26 May 2010 20:41:07 +0100 Subject: [Slackbuilds-users] rxvt-unicode in 13.1 Message-ID: <20100526194107.GA30585@Junius> There is a problem when using a png icon file: libpng warning: Application was compiled with png.h from libpng-1.2.37 libpng warning: Application is running with png.c from libpng-1.4.2 libpng warning: Incompatible libpng version in application and library urxvt: Loading image icon failed, continuing without. Also mailing mainainer about this, but if anyone knows a solution it would be handy. David -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From joao.eel at gmail.com Wed May 26 19:47:11 2010 From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=) Date: Wed, 26 May 2010 16:47:11 -0300 Subject: [Slackbuilds-users] rxvt-unicode in 13.1 In-Reply-To: <20100526194107.GA30585@Junius> References: <20100526194107.GA30585@Junius> Message-ID: On Wed, May 26, 2010 at 4:41 PM, David Woodfall wrote: > There is a problem when using a png icon file: > > libpng warning: Application was compiled with png.h from libpng-1.2.37 > libpng warning: Application ?is ?running with png.c from libpng-1.4.2 > libpng warning: Incompatible libpng version in application and library > urxvt: Loading image icon failed, continuing without. > > Also mailing mainainer about this, but if anyone knows a solution it > would be handy. > > David > Have you upgraded to 13.1 without recompiling your old SBo packages? 13.1 uses a new version of libpng that breaks compatibility with the older version. Some applications need to be patched, but others just need to be recompiled to work again. -- Jo?o From niels.horn at gmail.com Wed May 26 20:34:36 2010 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 26 May 2010 17:34:36 -0300 Subject: [Slackbuilds-users] rxvt-unicode in 13.1 In-Reply-To: References: <20100526194107.GA30585@Junius> Message-ID: 2010/5/26 Jo?o Felipe Santos : > On Wed, May 26, 2010 at 4:41 PM, David Woodfall wrote: >> There is a problem when using a png icon file: >> >> libpng warning: Application was compiled with png.h from libpng-1.2.37 >> libpng warning: Application ?is ?running with png.c from libpng-1.4.2 >> libpng warning: Incompatible libpng version in application and library >> urxvt: Loading image icon failed, continuing without. >> >> Also mailing mainainer about this, but if anyone knows a solution it >> would be handy. >> >> David >> > > Have you upgraded to 13.1 without recompiling your old SBo packages? > 13.1 uses a new version of libpng that breaks compatibility with the > older version. Some applications need to be patched, but others just > need to be recompiled to work again. > > -- Jo?o > _______________________________________________ This is happening with several packages built after the libpng update. They build fine but have to be started in SW13.1 with a LD_PRELOAD command. I've been looking for a solution for my packages, but have not found one until now. If I do I'll report back here. If anyone else finds a solution before me, please share it here :) Niels From niels.horn at gmail.com Wed May 26 20:34:36 2010 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 26 May 2010 17:34:36 -0300 Subject: [Slackbuilds-users] rxvt-unicode in 13.1 In-Reply-To: References: <20100526194107.GA30585@Junius> Message-ID: 2010/5/26 Jo?o Felipe Santos : > On Wed, May 26, 2010 at 4:41 PM, David Woodfall wrote: >> There is a problem when using a png icon file: >> >> libpng warning: Application was compiled with png.h from libpng-1.2.37 >> libpng warning: Application ?is ?running with png.c from libpng-1.4.2 >> libpng warning: Incompatible libpng version in application and library >> urxvt: Loading image icon failed, continuing without. >> >> Also mailing mainainer about this, but if anyone knows a solution it >> would be handy. >> >> David >> > > Have you upgraded to 13.1 without recompiling your old SBo packages? > 13.1 uses a new version of libpng that breaks compatibility with the > older version. Some applications need to be patched, but others just > need to be recompiled to work again. > > -- Jo?o > _______________________________________________ This is happening with several packages built after the libpng update. They build fine but have to be started in SW13.1 with a LD_PRELOAD command. I've been looking for a solution for my packages, but have not found one until now. If I do I'll report back here. If anyone else finds a solution before me, please share it here :) Niels From dave at unrealize.co.uk Wed May 26 21:01:15 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 26 May 2010 22:01:15 +0100 Subject: [Slackbuilds-users] rxvt-unicode in 13.1 In-Reply-To: References: <20100526194107.GA30585@Junius> Message-ID: <20100526210115.GA23885@Junius> On (17:34 26/05/10), Niels Horn put forth the proposition: >2010/5/26 Jo?o Felipe Santos : >> On Wed, May 26, 2010 at 4:41 PM, David Woodfall wrote: >>> There is a problem when using a png icon file: >>> >>> libpng warning: Application was compiled with png.h from libpng-1.2.37 >>> libpng warning: Application ?is ?running with png.c from libpng-1.4.2 >>> libpng warning: Incompatible libpng version in application and library >>> urxvt: Loading image icon failed, continuing without. >>> >>> Also mailing mainainer about this, but if anyone knows a solution it >>> would be handy. >>> >>> David >>> >> >> Have you upgraded to 13.1 without recompiling your old SBo packages? >> 13.1 uses a new version of libpng that breaks compatibility with the >> older version. Some applications need to be patched, but others just >> need to be recompiled to work again. >> >> -- Jo?o >> _______________________________________________ > >This is happening with several packages built after the libpng update. >They build fine but have to be started in SW13.1 with a LD_PRELOAD command. >I've been looking for a solution for my packages, but have not found >one until now. > >If I do I'll report back here. If anyone else finds a solution before >me, please share it here :) Ok, thanks to deryni in #rxvt-unicode the solution turns out to be fairly simple - rebuild libAfterImage then rxvt-unicode. Now the caveat - I'm using a cvs version of libAfterImage so ymmv on using the SBo version. David > >Niels >_______________________________________________ >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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dave at unrealize.co.uk Wed May 26 21:09:34 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 26 May 2010 22:09:34 +0100 Subject: [Slackbuilds-users] rxvt-unicode in 13.1 In-Reply-To: <20100526210115.GA23885@Junius> References: <20100526194107.GA30585@Junius> <20100526210115.GA23885@Junius> Message-ID: <20100526210934.GA2123@Junius> On (22:01 26/05/10), David Woodfall put forth the proposition: > On (17:34 26/05/10), Niels Horn put forth the proposition: >> 2010/5/26 Jo?o Felipe Santos : >>> On Wed, May 26, 2010 at 4:41 PM, David Woodfall wrote: >>>> There is a problem when using a png icon file: >>>> >>>> libpng warning: Application was compiled with png.h from libpng-1.2.37 >>>> libpng warning: Application ?is ?running with png.c from libpng-1.4.2 >>>> libpng warning: Incompatible libpng version in application and library >>>> urxvt: Loading image icon failed, continuing without. >>>> >>>> Also mailing mainainer about this, but if anyone knows a solution it >>>> would be handy. >>>> >>>> David >>>> >>> >>> Have you upgraded to 13.1 without recompiling your old SBo packages? >>> 13.1 uses a new version of libpng that breaks compatibility with the >>> older version. Some applications need to be patched, but others just >>> need to be recompiled to work again. >>> >>> -- Jo?o >>> _______________________________________________ >> >> This is happening with several packages built after the libpng update. >> They build fine but have to be started in SW13.1 with a LD_PRELOAD command. >> I've been looking for a solution for my packages, but have not found >> one until now. >> >> If I do I'll report back here. If anyone else finds a solution before >> me, please share it here :) > > Ok, thanks to deryni in #rxvt-unicode the solution turns out to be > fairly simple - rebuild libAfterImage then rxvt-unicode. > > Now the caveat - I'm using a cvs version of libAfterImage so ymmv on > using the SBo version. Link to my cvs slackbuild: http://www.dawoodfall.net/slackbuilds/13.0/libAfterImage/ > > David > >> >> Niels >> _______________________________________________ >> 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/ >> > > -- > Don't look back, the lemmings are gaining on you. >_______________________________________________ >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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From andrew.david.52 at gmail.com Wed May 26 21:54:15 2010 From: andrew.david.52 at gmail.com (andrew) Date: Thu, 27 May 2010 07:54:15 +1000 Subject: [Slackbuilds-users] leafnode 2 and Slackware 13.1 Message-ID: <20100526215329.GA1980@skamandros.andrews-corner.org> Hi, I had a look at the slackbuilds.org git repository and I noticed that the script for leafnode 2 has been dropped from 13.1 because it fails to compile. I have managed to get it running quite nicely with a small patch + adjust the stripping options as for many of the 13.1 scripts. I attach the patch to this email in case someone can adjust the script before the 13.1 slackbuilds become publicly available, or if it is a little too hectic I can resubmit the whole thing when submissions become available again. Thanks for your trouble, Andrew -- Do you think that's air you're breathing? -------------- next part -------------- --- system.h 2008-12-29 22:24:30.000000000 +1100 +++ system.h_patched 2010-05-26 19:39:22.376358080 +1000 @@ -20,9 +20,6 @@ #include #elif HAVE_STDINT_H #include -#elif sizeof(unsigned long) == 4 && sizeof(unsigned char) == 1 -typedef unsigned long uint32_t; -typedef unsigned char uint8_t; #else #error "I cannot figure how to define uint32_t and uint8_t." #endif From artourter at gmail.com Wed May 26 22:21:14 2010 From: artourter at gmail.com (Greg' Ar Tourter) Date: Wed, 26 May 2010 23:21:14 +0100 Subject: [Slackbuilds-users] broadcom-sta on 13.1 In-Reply-To: References: Message-ID: I have made a clone to the @master on github ( git://github.com/ArTourter/Slackbuilds.org.git at broadcom-sta ) and have create a branch for the broadcom-sta changes I attach the tarball in case the maintainer is here. Cheers ArTourter On 26 May 2010 16:26, Greg' Ar Tourter wrote: > Hi > > I see DSomero removed broadcom-sta from the 13.1 branch on git, I have > submitted a patch a while back to Ponce for his "unofficial -current" > git repo on github which solves the build issue. feel free to use it > for the release. > > ArTourter > -------------- next part -------------- A non-text attachment was scrubbed... Name: broadcom-sta.tar.gz Type: application/x-gzip Size: 2085 bytes Desc: not available URL: From rob0 at slackbuilds.org Wed May 26 22:57:59 2010 From: rob0 at slackbuilds.org (Rob McGee) Date: Wed, 26 May 2010 17:57:59 -0500 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100525220201.5d51a620@yahoo.fr> References: <20100525182905.GC19868@cardinal> <20100525220201.5d51a620@yahoo.fr> Message-ID: <20100526225759.GE19868@cardinal> On Tue, May 25, 2010 at 10:02:01PM +0200, Antoine NONYME wrote: > Rob McGee: > > xz is a fine tool, possibly superior to gz in every way. But it > > has not been around as long. I run numerous older boxes, some of > > which are not likely to get upgraded soon if ever, and sometimes > > it's nice to be able to look inside a binary package. > tar-1.22 and xz from Slackware 13.0 sources just build fine even > on Slackware 11.0 (and I did it yesterday) . I have found in two cases, one of which was 11.x[1], that installing the *binary* xz package and upgradepkg pkgtools is all it takes to get the ability to deal with .txz in the packaging system[2,3]. I didn't do anything with tar. [1] I can't check the exact version, because that one WAS upgraded. [2] And that was HOW it was upgraded, installpkg -root /new ... [3] There are things outside pkgtools where it is sometimes useful or desirable to be able to look inside a binary package. For example, mc(1) works well to view a package, but only if it is also upgraded (and I doubt the binary 13.0 mc package would work on older systems.) PS to Ben: As requested, I have chosen not to take offense at your irrelevant and fallacious remarks, which otherwise need no comment. But please, *do* fix your MUA's formatting problem. The staggered line ends are very annoying to read and difficult on the eyes. From kingbeowulf at gmail.com Thu May 27 00:46:44 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 26 May 2010 18:46:44 -0600 Subject: [Slackbuilds-users] slackbuilds 13.1 In-Reply-To: <20100526181920.GA21095@ramov.com> References: <20100526210312.2fbab3d7@pcolivier.chezmoi.net> <20100526181920.GA21095@ramov.com> Message-ID: I see no compelling reason to badger the SBo team to rush the 13.1 repository. Good grief, have some patience, people. -Ed On 5/26/10, ?ime Ramov wrote: > * Olive [2010-05-26 21:03+0400]: >> Does anyone have an idea of when the slackbuilds will be released for >> 13.1 (Yeah I know when it is ready, but maybe has a more precise idea). > > Why not use the Git repo? Most of it should work without issues, if not, > it is an easy case of fixing it most times. > > > --S. > _______________________________________________ > 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/ > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From kingbeowulf at gmail.com Thu May 27 01:01:01 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 26 May 2010 19:01:01 -0600 Subject: [Slackbuilds-users] Status Report In-Reply-To: <20100526005856.5478ced1@liberty.rlwhome.lan> References: <20100526005856.5478ced1@liberty.rlwhome.lan> Message-ID: I appreciate the hard work of all the SBo admins. So tale your time. Its not like I can install 13.1 yet anyway - its d/l via bittorent and then I had to hop a plane for work. Also, on behalf of some whiner slackers ("are we there yet? NO!!), I apologize for all their impatience. And while I'm on a rant, why can't those lazy bastards just TRY the 13.0 slackbuild on 13.1 (as some have, kudos)? Maybe these kids would rather go with Ubuntu? -Ed On 5/25/10, Robby Workman wrote: > I know there's a bit of anticipation by now, and probably some > pondering as to why we haven't got a set of scripts out there > for 13.1 yet, so I guess some explanation/discussion is in > order... > > Basically, the Slackware 13.1 release snuck up on us (yes, even > though several of the SBo admin team *knew* it was coming), and > it happened to coincide with real-life conflicts for several of > the admins, so we didn't get as far along with preparation as we > normally would have. Because we believe that, like Slackware, > it should only go public "when it's ready," we decided to wait > until we were comfortable calling things "ready" for public > consumption before spinning tarballs and such and putting out > a public changelog in the usual manner. > > The other major factor that's played a part in the delay is > something that lots of people have long requested, and that > is tracking the repository in git. Yes, that's right - we > now have a git repo with everything in it. Consider the ensuing > comments to be NON-FINAL, NON-BINDING, and SUBJECT TO CHANGE > based on feedback, our preferences, logistics, phase of the > moon, and various other known and unknown factors... > > http://slackbuilds.org/gitweb/ has a web interface to the > git repositories - you will notice that there is a 'slackbuilds' > repo and a 'templates' repo, and each of them contains exactly > what the name implies. > > The 'slackbuilds' repo contains several "predictable" branches: > 11.0, 12.0, 12.1, 12.2, 13.0, and 13.1, and each of those has > exactly what the branch name implies. It's a bit early to be > setting anything in stone, but unless something changes, the > '13.1' branch at any given moment should be the equivalent of > what is available on the website (in other words, it's exactly > what you would have gotten from an rsync of the slackbuilds/13.1/ > tree if we didn't have a git repo). > > Each admin will have one or more separate branches (which might > have various names) where he will push approved submissions as > they are cleared. From time to time, one of us will gather the > various commits from the admin-specific branches and commit them > to master, and once we decide to do a public push to http (the > "old" way of doing things), then we'll merge master into the 13.1 > branch, generate the tarballs, gpg sigs, and ChangeLog, and sync > that over to the http tree. Again, the http tree (the old way) > will always be in sync with the 13.1 branch (until 14.0 is out). > > For those of you who don't know git and/or have no desire to learn > it, fear not -- nothing changes with respect to the rest of our > site. Everything stays the same in regard to rsync, ftp, http, > and so on. > > For those of you who *do* know/use git, this is another option for > you. For the time being, submissions will still be done using the > existing method - git pull requests are not an option right now. [1] > > This probably doesn't need to be said, but for your own sanity, > DO NOT base any work on an admin-specific branch (e.g. on my > 'rworkman' branch) -- those are subject to be rebased, removed, > etcetera at any time. > > Anyway, we hope to have all the kinks ironed out of this soon, > and once we do, we'll get everything up and running normally. > Thanks for your support and patience, and in the meantime, > enjoy 13.1! > > [1] That's not to say that a git pull request won't be honored. > In fact, if you were to clone master and host it on e.g. github, > and create a separate branch for each app that you submit via > our submission form, and note that in the comments of the > submission, it's certainly possible that some of us :) might > use that. This is particularly true for cases where: > [ $admin == rworkman ] && [ $changetype == trivial ] :-) > > -RW > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From dragonwisard at gmail.com Thu May 27 01:31:52 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Wed, 26 May 2010 21:31:52 -0400 Subject: [Slackbuilds-users] Status Report In-Reply-To: References: <20100526005856.5478ced1@liberty.rlwhome.lan> Message-ID: I would also point out that if the package hasn't been updated in the official git repository, it might have been updated in the unofficial -current repository on github. On Wed, May 26, 2010 at 9:01 PM, King Beowulf wrote: > I appreciate the hard work of all the SBo admins. So tale your time. > Its not like I can install 13.1 yet anyway - its d/l via bittorent and > then I had to hop a plane for work. Also, on behalf of some whiner > slackers ("are we there yet? NO!!), I apologize for all their > impatience. > > And while I'm on a rant, why can't those lazy bastards just TRY the > 13.0 slackbuild on 13.1 (as some have, kudos)? Maybe these kids would > rather go with Ubuntu? > > -Ed > > > On 5/25/10, Robby Workman wrote: > > I know there's a bit of anticipation by now, and probably some > > pondering as to why we haven't got a set of scripts out there > > for 13.1 yet, so I guess some explanation/discussion is in > > order... > > > > Basically, the Slackware 13.1 release snuck up on us (yes, even > > though several of the SBo admin team *knew* it was coming), and > > it happened to coincide with real-life conflicts for several of > > the admins, so we didn't get as far along with preparation as we > > normally would have. Because we believe that, like Slackware, > > it should only go public "when it's ready," we decided to wait > > until we were comfortable calling things "ready" for public > > consumption before spinning tarballs and such and putting out > > a public changelog in the usual manner. > > > > The other major factor that's played a part in the delay is > > something that lots of people have long requested, and that > > is tracking the repository in git. Yes, that's right - we > > now have a git repo with everything in it. Consider the ensuing > > comments to be NON-FINAL, NON-BINDING, and SUBJECT TO CHANGE > > based on feedback, our preferences, logistics, phase of the > > moon, and various other known and unknown factors... > > > > http://slackbuilds.org/gitweb/ has a web interface to the > > git repositories - you will notice that there is a 'slackbuilds' > > repo and a 'templates' repo, and each of them contains exactly > > what the name implies. > > > > The 'slackbuilds' repo contains several "predictable" branches: > > 11.0, 12.0, 12.1, 12.2, 13.0, and 13.1, and each of those has > > exactly what the branch name implies. It's a bit early to be > > setting anything in stone, but unless something changes, the > > '13.1' branch at any given moment should be the equivalent of > > what is available on the website (in other words, it's exactly > > what you would have gotten from an rsync of the slackbuilds/13.1/ > > tree if we didn't have a git repo). > > > > Each admin will have one or more separate branches (which might > > have various names) where he will push approved submissions as > > they are cleared. From time to time, one of us will gather the > > various commits from the admin-specific branches and commit them > > to master, and once we decide to do a public push to http (the > > "old" way of doing things), then we'll merge master into the 13.1 > > branch, generate the tarballs, gpg sigs, and ChangeLog, and sync > > that over to the http tree. Again, the http tree (the old way) > > will always be in sync with the 13.1 branch (until 14.0 is out). > > > > For those of you who don't know git and/or have no desire to learn > > it, fear not -- nothing changes with respect to the rest of our > > site. Everything stays the same in regard to rsync, ftp, http, > > and so on. > > > > For those of you who *do* know/use git, this is another option for > > you. For the time being, submissions will still be done using the > > existing method - git pull requests are not an option right now. [1] > > > > This probably doesn't need to be said, but for your own sanity, > > DO NOT base any work on an admin-specific branch (e.g. on my > > 'rworkman' branch) -- those are subject to be rebased, removed, > > etcetera at any time. > > > > Anyway, we hope to have all the kinks ironed out of this soon, > > and once we do, we'll get everything up and running normally. > > Thanks for your support and patience, and in the meantime, > > enjoy 13.1! > > > > [1] That's not to say that a git pull request won't be honored. > > In fact, if you were to clone master and host it on e.g. github, > > and create a separate branch for each app that you submit via > > our submission form, and note that in the comments of the > > submission, it's certainly possible that some of us :) might > > use that. This is particularly true for cases where: > > [ $admin == rworkman ] && [ $changetype == trivial ] :-) > > > > -RW > > > > -- > Sent from my mobile device > > You! What PLANET is this! > -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > _______________________________________________ > 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 rworkman at slackbuilds.org Thu May 27 01:50:47 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 20:50:47 -0500 Subject: [Slackbuilds-users] MuPDF In-Reply-To: <4BFCED8C.40003@ramov.com> References: <4BFCED8C.40003@ramov.com> Message-ID: <20100526205047.0e9c92c3@liberty.rlwhome.lan> On Wed, 26 May 2010 11:44:44 +0200 ?ime Ramov wrote: > Hello - I see that MuPDF is removed from the current git tree because > of the bogus download link. It's a shame as it is a simple fix and a > nice PDF viewer (I personally use it). > > A stable release tarballs are now available. If the original > maintainer is not available to update it, I can take it over. Mail a fixed tarball to me and I'll see about getting it back in. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu May 27 03:04:00 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 22:04:00 -0500 Subject: [Slackbuilds-users] broadcom-sta on 13.1 In-Reply-To: References: Message-ID: <20100526220400.3079e22e@liberty.rlwhome.lan> On Wed, 26 May 2010 23:21:14 +0100 "Greg' Ar Tourter" wrote: > I have made a clone to the @master on github ( > git://github.com/ArTourter/Slackbuilds.org.git at broadcom-sta ) and have > create a branch for the broadcom-sta changes > > I attach the tarball in case the maintainer is here. This is fixed in my branch (with you as GIT_AUTHOR) - see the commit message for a better idea about how we want those to look :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu May 27 03:05:18 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 22:05:18 -0500 Subject: [Slackbuilds-users] leafnode 2 and Slackware 13.1 In-Reply-To: <20100526215329.GA1980@skamandros.andrews-corner.org> References: <20100526215329.GA1980@skamandros.andrews-corner.org> Message-ID: <20100526220518.586f608c@liberty.rlwhome.lan> On Thu, 27 May 2010 07:54:15 +1000 andrew wrote: > I had a look at the slackbuilds.org git repository and I noticed that > the script for leafnode 2 has been dropped from 13.1 because it fails > to compile. I have managed to get it running quite nicely with a small > patch + adjust the stripping options as for many of the 13.1 scripts. > > I attach the patch to this email in case someone can adjust the script > before the 13.1 slackbuilds become publicly available, or if it is a > little too hectic I can resubmit the whole thing when submissions > become available again. > > Thanks for your trouble, Thanks for yours - it's in my branch now. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu May 27 03:08:52 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 22:08:52 -0500 Subject: [Slackbuilds-users] slackbuilds tested for 13.1 In-Reply-To: <20100525161107.GE5993@pc21.mareichelt.com> References: <20100525161107.GE5993@pc21.mareichelt.com> Message-ID: <20100526220852.28bda071@liberty.rlwhome.lan> On Tue, 25 May 2010 18:11:07 +0200 markus reichelt wrote: > i tested and verified the slackbuilds i maintain for 13.1, they can > just be copied over (less hassle for me :-) > > libraries/dietlibc > network/vidalia Thanks for testing; I just tweaked them to match the latest template and pushed them into my branch. > as just mentioned already on this list, i as well intend to switch to > the default .txz pkgtype with the next update of those scripts. We intend to change it back. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu May 27 03:12:25 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 22:12:25 -0500 Subject: [Slackbuilds-users] 13.1 In-Reply-To: References: <20100525182905.GC19868@cardinal> <4BFC2CA0.1000303@gmail.com> <20100525223039.1ce5f107@liberty.rlwhome.lan> Message-ID: <20100526221225.604725d2@liberty.rlwhome.lan> On Wed, 26 May 2010 10:08:58 +0300 Ozan T?rky?lmaz wrote: > 2010/5/26 Robby Workman : > > On Wed, 26 May 2010 03:12:06 +0100 > > Eugen Wissner wrote: > > > >> we decided to use .tgz at least for 13.0 > >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-July/004281.html > > > > > > As it turned out, we *did* make it configurable by passing an > > alternate value to PKGTYPE when invoking the script, and that's > > still the case. > > well because variable defined at the end of the script, any ordinary > user can't see if PKGTYPE is a changable variable simply. moving to > more user seeable place next to TMP etc would be much better. An ordinary user doesn't care and won't be changing it anyway. An ordinary user will accept the default. An ordinary user that happens to be a bit extraordinary will know to edit the makepkg line, at which point (s)he will see the PKGTYPE usage, at which point we're back to my previous email. Sorry, but we're not changing this in the foreseeable future; there's a consensus among the admins (and Pat too, for that matter), so the issue is settled - let's all move on :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu May 27 03:16:34 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 22:16:34 -0500 Subject: [Slackbuilds-users] Small bug in g3data slackbuild In-Reply-To: <4BF93A3D.2020906@skmail.ikp.physik.tu-darmstadt.de> References: <20100517044929.GA6382@slackbuilds.org> <4BF93A3D.2020906@skmail.ikp.physik.tu-darmstadt.de> Message-ID: <20100526221634.6932f11f@liberty.rlwhome.lan> On Sun, 23 May 2010 16:22:53 +0200 Serban Udrea wrote: > I know that not much will happen until the new Slackware is out, but > just FYI: the g3data slackbuild is installing g3data.destop instead > of g3data.desktop. Patch is attached. Fixed in my branch; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu May 27 04:02:40 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 May 2010 23:02:40 -0500 Subject: [Slackbuilds-users] My Slackbuilds In-Reply-To: <20100526151519.276cca2b@darkstar.example.net> References: <20100526151519.276cca2b@darkstar.example.net> Message-ID: <20100526230240.20f795bd@liberty.rlwhome.lan> On Wed, 26 May 2010 15:15:19 -0400 Morten Juhl-Johansen Z?lde-Fej?r wrote: > I tested my Slackbuilds to the extent I can - > * Uget - 13.0 build works on 13.1 > * Gajim - 13.0 build works on 13.1; pyOpenSSL, which is a dep for > Gajim, also works. Miscellaneous tweaks to all of these in my branch now; thanks. > * GTK-Recordmydesktop: Well, it seems that the Recordmydesktop > slackbuild for 13.0 doesn't build right on 13.1, so I can't say > anything about the frontend. I just fixed up recordmydesktop in my branch, so have a look there for the solution, and then let me know about the frontend. > ... and just to make Slackware do what I want it to, I immediately > installed Claws Mail. The 13.0 builds for Claws-mail, > claws-mail-extra-plugins and libetpan all work as they should. Sure; they're also updated/tweaked in master. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From slakmagik at gmail.com Thu May 27 04:23:20 2010 From: slakmagik at gmail.com (slakmagik) Date: Thu, 27 May 2010 00:23:20 -0400 Subject: [Slackbuilds-users] sbopkg and git Message-ID: <20100527042320.GA29068@devbox> (I'm cross-posting this to slackbuilds-users for wider exposure, even though this doesn't relate to people using the git repos manually.) As Robby Workman mentioned in the Status Report http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005627.html SBo git repositories are publicly available while the regular 13.1 repo is not yet. For those who might be interested in using sbopkg with this repository, we recommend waiting for the usual rsync-able 13.1 repo to open. However, if you absolutely can't wait, you might be able to temporarily create an /etc/sbopkg/repos.d/70-sbogit.repo file with something like the following line SBogit 13.1 "SBo-git repository for Slackware 13.1" _SBo git git://slackbuilds.org/slackbuilds.git at 13.1 "" Make sure $REPO_ROOT/SBogit does not exist, switch your repo to SBogit/13.1 and do an initial sync. If you do this, beware that this is not supported nor really tested. And be advised that the git sync will remove anything currently in the target directory. This behavior may be familiar to slamd64 users but may be unexpected to SBo/rsync users. For more information: http://code.google.com/p/sbopkg/issues/detail?id=47 We will be releasing 0.33.1 of sbopkg as soon as safely possible after SBo 13.1 goes live, but 0.32.0 does not "know about" some of the changes in the git repo. Basically, this is all untested and unsupported, but good luck with whatever you do. :) Also, apologies to anyone who downloaded sbopkg 0.33.0. There was a twilight zone where I was testing for release and had uploaded it but hadn't made any release announcement. Due to the need to take account of some changes in the SlackBuild template, that release was pulled. Nevertheless, it appears some people downloaded it. Mea culpa. From belka.ew at gmail.com Thu May 27 05:33:43 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Thu, 27 May 2010 06:33:43 +0100 Subject: [Slackbuilds-users] sakura Message-ID: Hello, who is author of sakura's slackbuild? I wrote an email to esterlinsh at gmail.com and got the message, that the email doesn't exist. Can I take over the script and write a patch for new version? Best regards Eugene Wissner From rworkman at slackbuilds.org Thu May 27 06:12:23 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 27 May 2010 01:12:23 -0500 Subject: [Slackbuilds-users] sakura In-Reply-To: References: Message-ID: <20100527011223.4c6c9b66@liberty.rlwhome.lan> On Thu, 27 May 2010 06:33:43 +0100 Eugen Wissner wrote: > who is author of sakura's slackbuild? I wrote an email to > esterlinsh at gmail.com and got the message, that the email doesn't > exist. Can I take over the script and write a patch for new version? If the maintainer mail is not valid, then sure - have at it. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From s at ramov.com Thu May 27 09:42:55 2010 From: s at ramov.com (=?UTF-8?Q?=C5=A0ime?= Ramov) Date: Thu, 27 May 2010 11:42:55 +0200 Subject: [Slackbuilds-users] My SlackBuilds Message-ID: <1274953375.2202.6.camel@sime.local> Hello, Due to some unfortunate private circumstances I am no longer available to maintain any of my SlackBuilds, which includes the following: imapfilter libcuefile libev libreplaygain maildrop musepack-tools perl-Text-Autoformat perl-Text-Reform pyquery viewnior Feel free to grab any/all of it. I am sorry for the situation but it came as unexpected. --S. From dave at unrealize.co.uk Thu May 27 09:51:37 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Thu, 27 May 2010 10:51:37 +0100 Subject: [Slackbuilds-users] Slackbuilds tested for 13.1 - working and problems Message-ID: <20100527095137.GA14267@Junius> WORKING WITH NO MODIFICATION: aiksaurus hydrogoen js kqemu lash libnice libtar openssl-certs portmidi regionset FIXED AND WORKING: atool bbdock daa2iso farsight2 grun imwheel shed shell-fm uif2iso whowatch xforge xonclock UPGRADED VERSION AND WORKING: qbittorrent ranger PROBLEMS: clementine compile problems figlet unable to log in to ftp.figlet to get source I've asked about the install method for the new version of clementine on kde-apps, but no reply yet. It no longer uses qmake and I can't get make install to work yet. If anyone has a copy of the figlet source can they email it me and I will host it. I have emailed the devs about the ftp problem but the release is old enough for me to worry that it may be a dead project. Most of the fixes were related to bash4 so a simple || true will fix things. David -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dave at unrealize.co.uk Thu May 27 10:06:06 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Thu, 27 May 2010 11:06:06 +0100 Subject: [Slackbuilds-users] Slackbuilds tested for 13.1 - working and problems In-Reply-To: <20100527095137.GA14267@Junius> References: <20100527095137.GA14267@Junius> Message-ID: <20100527100606.GA22182@Junius> On (10:51 27/05/10), David Woodfall put forth the proposition: > WORKING WITH NO MODIFICATION: > aiksaurus > hydrogoen > js > kqemu > lash > libnice > libtar > openssl-certs > portmidi > regionset > > > FIXED AND WORKING: > atool > bbdock + clementine > daa2iso > farsight2 > grun > imwheel > shed > shell-fm > uif2iso > whowatch > xforge > xonclock > > UPGRADED VERSION AND WORKING: > qbittorrent > ranger > > PROBLEMS: > clementine compile problems > figlet unable to log in to ftp.figlet to get source > > I've asked about the install method for the new version of clementine > on kde-apps, but no reply yet. It no longer uses qmake and I can't > get make install to work yet. Ok, clementine is now working. > > If anyone has a copy of the figlet source can they email it me and I > will host it. I have emailed the devs about the ftp problem but the > release is old enough for me to worry that it may be a dead project. > > Most of the fixes were related to bash4 so a simple || true will > fix things. > > David > > -- > Don't look back, the lemmings are gaining on you. >_______________________________________________ >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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dave at unrealize.co.uk Thu May 27 10:16:53 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Thu, 27 May 2010 11:16:53 +0100 Subject: [Slackbuilds-users] Slackbuilds tested for 13.1 - working and problems In-Reply-To: <20100527100606.GA22182@Junius> References: <20100527095137.GA14267@Junius> <20100527100606.GA22182@Junius> Message-ID: <20100527101653.GA5558@Junius> On (11:06 27/05/10), David Woodfall put forth the proposition: > On (10:51 27/05/10), David Woodfall put forth the proposition: >> WORKING WITH NO MODIFICATION: >> aiksaurus >> hydrogoen >> js >> kqemu >> lash >> libnice >> libtar >> openssl-certs >> portmidi >> regionset >> >> >> FIXED AND WORKING: >> atool >> bbdock > + clementine >> daa2iso >> farsight2 + figlet >> grun >> imwheel >> shed >> shell-fm >> uif2iso >> whowatch >> xforge >> xonclock >> >> UPGRADED VERSION AND WORKING: >> qbittorrent >> ranger >> >> PROBLEMS: >> clementine compile problems >> figlet unable to log in to ftp.figlet to get source >> >> I've asked about the install method for the new version of clementine >> on kde-apps, but no reply yet. It no longer uses qmake and I can't >> get make install to work yet. > > Ok, clementine is now working. > >> >> If anyone has a copy of the figlet source can they email it me and I >> will host it. I have emailed the devs about the ftp problem but the >> release is old enough for me to worry that it may be a dead project. Ok, I found an alternative location for the source, but I will wait for a reply from devs before decided what to go with. >> Most of the fixes were related to bash4 so a simple || true will >> fix things. >> >> David >> >> -- >> Don't look back, the lemmings are gaining on you. > > > >> _______________________________________________ >> 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/ >> > > > -- > Don't look back, the lemmings are gaining on you. >_______________________________________________ >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/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From artourter at gmail.com Thu May 27 11:21:34 2010 From: artourter at gmail.com (Greg' Ar Tourter) Date: Thu, 27 May 2010 12:21:34 +0100 Subject: [Slackbuilds-users] perl-html-parser in 13.1 repo Message-ID: Hi, just a heads up if it hasn't been caught yet, the source URL for perl-html-parser is not valid any more. Upstream seems to have removed the old source and only provide the latest version 3.65 which can be found at http://search.cpan.org/CPAN/authors/id/G/GA/GAAS/HTML-Parser-3.65.tar.gz with the md5sum being cbc220e201b427bfcf231d95bee3c7ca hope this helps Cheers ArTourter From lukenshiro at ngi.it Thu May 27 12:44:26 2010 From: lukenshiro at ngi.it (LukenShiro) Date: Thu, 27 May 2010 14:44:26 +0200 Subject: [Slackbuilds-users] perl-html-parser in 13.1 repo In-Reply-To: References: Message-ID: <20100527144426.379e5482lukenshiro@ngi.it@multiverse.sigil.edu> Il giorno Thu, 27 May 2010 12:21:34 +0100 "Greg' Ar Tourter" ha scritto: > just a heads up if it hasn't been caught yet, the source URL for > perl-html-parser is not valid any more. Upstream seems to have removed > the old source and only provide the latest version 3.65 which can be > found at > http://search.cpan.org/CPAN/authors/id/G/GA/GAAS/HTML-Parser-3.65.tar.gz > with the md5sum being > cbc220e201b427bfcf231d95bee3c7ca Thank you, this problem is known to me, unfortunately it seems to be a nasty cycling attitude for some upstream developers :-// 3.65 should be built without modification, as well. Anyway I was waiting for a green light from SBo admins, in order to upgrade scripts for 13.1. Personally I would intend to wait for official submissions' reopening before causing too much hassle and pressure to admins. As I see some maintainers already sending some corrections via ML, I would like to know if we (as maintainers) are supposed to send _now_ modifications, corrections or upgrades, instead. OTOH, admins, how viable could be a global modification to .info files in order to add an (optional for maintainers) fallback alternative way for a source file's download link, if main link somehow gets failed? e.g.: DOWNLOAD="...." MD5SUM="...." DOWNLOAD_ALT="...." #personal source repository or taken from other distro repository, just in case But I don't know how much work it needs to be implemented in support programs such as sbopkg etc.. Best regards. -- GNU/Linux * Slackware64 13.1 LU #210970 SU #12583 LM #98222/#412913 From niels.horn at gmail.com Thu May 27 13:07:05 2010 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 27 May 2010 10:07:05 -0300 Subject: [Slackbuilds-users] perl-html-parser in 13.1 repo In-Reply-To: <-7849005652755750412@unknownmsgid> References: <-7849005652755750412@unknownmsgid> Message-ID: On Thu, May 27, 2010 at 9:44 AM, LukenShiro wrote: > OTOH, admins, > ?how viable could be a global modification to .info files in order to > ?add an (optional for maintainers) fallback alternative way for a source > ?file's download link, if main link somehow gets failed? > > e.g.: > > DOWNLOAD="...." > MD5SUM="...." > DOWNLOAD_ALT="...." > #personal source repository or taken from other distro repository, just > in case > > But I don't know how much work it needs to be implemented in support > programs such as sbopkg etc.. > > Best regards. > > -- > GNU/Linux * Slackware64 13.1 > LU #210970 SU #12583 LM #98222/#412913 This is a problem inherent with external source repositories... I had a SlackBuild removed from 13.1 as well because of a dead download link. I found the new link for the sources and took the opportunity to clean up some other things in the script and will resubmit as soon as this option is available. The "DOWNLOAD_ALT" link might work for some people (like me) who have personal repositories etc. Giving voice to the admins now... :) Niels From mickeytintincolle at yahoo.fr Thu May 27 15:01:48 2010 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 27 May 2010 17:01:48 +0200 Subject: [Slackbuilds-users] 13.1 In-Reply-To: <20100526225759.GE19868@cardinal> References: <20100525182905.GC19868@cardinal> <20100525220201.5d51a620@yahoo.fr> <20100526225759.GE19868@cardinal> Message-ID: <20100527170148.499d2698@yahoo.fr> Le Wed, 26 May 2010 17:57:59 -0500, Rob McGee a ?crit : > I have found in two cases, one of which was 11.x[1], that installing > the *binary* xz package and upgradepkg pkgtools is all it takes to > get the ability to deal with .txz in the packaging system[2,3]. I > didn't do anything with tar. I didn't look at pkgtools if xz is used inside a tar command or in a separate command, so I upgraded tar . According to what you are saying, xz is used in a separate command so tar needs not know about xz and so it needs not be upgraded . > [1] I can't check the exact version, because that one WAS upgraded. There is only one 11.x version of Slackware - it is 11.0 . > [2] And that was HOW it was upgraded, installpkg -root /new ... > [3] There are things outside pkgtools where it is sometimes useful > or desirable to be able to look inside a binary package. For > example, mc(1) works well to view a package, but only if it is > also upgraded (and I doubt the binary 13.0 mc package would work > on older systems.) From belka.ew at gmail.com Thu May 27 15:32:52 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Thu, 27 May 2010 17:32:52 +0200 Subject: [Slackbuilds-users] sakura In-Reply-To: <20100527011223.4c6c9b66@liberty.rlwhome.lan> References: <20100527011223.4c6c9b66@liberty.rlwhome.lan> Message-ID: In sakura.Slackbuild is written, that "# Written by Erik Hanson erik at slackbuilds.org". So far as I know Erik Hanson is active. Do you want to be the maintainer? Otherwise I've rewritten the Slackbuild a little bit and diff-file is attached, then source must be updated to version 2.3.8. Yet one more question: I don't use anymore some programs, which are maintained by me. I don't know, whether someone needs them: gnome-colors, trayer, gkrellm-volume (there should be something better) That's all for now..... :) 2010/5/27 Robby Workman : > On Thu, 27 May 2010 06:33:43 +0100 > Eugen Wissner wrote: > >> who is author of sakura's slackbuild? I wrote an email to >> esterlinsh at gmail.com and got the message, that the email doesn't >> exist. Can I take over the script and write a patch for new version? > > > If the maintainer mail is not valid, then sure - have at it. > > -RW > > _______________________________________________ > 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: sakura.SlackBuild.diff Type: application/octet-stream Size: 943 bytes Desc: not available URL: From erik at slackbuilds.org Thu May 27 15:45:29 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 27 May 2010 10:45:29 -0500 Subject: [Slackbuilds-users] sakura In-Reply-To: References: <20100527011223.4c6c9b66@liberty.rlwhome.lan> Message-ID: <20100527104529.708ee5d4@shaggy.doo> On May 27, 2010, at 5:32 PM, Eugen Wissner wrote: > In sakura.Slackbuild is written, that "# Written by Erik Hanson > erik at slackbuilds.org". So far as I know Erik Hanson is active. Do you > want to be the maintainer? Otherwise I've rewritten the Slackbuild a > little bit and diff-file is attached, then source must be updated to > version 2.3.8. If you want to take over, that's fine. I don't plan to update it. However, please be sure to look at our current template before you submit. Some changes in the diff would not be acceptable. -- Erik Hanson http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From belka.ew at gmail.com Thu May 27 16:01:13 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Thu, 27 May 2010 18:01:13 +0200 Subject: [Slackbuilds-users] sakura In-Reply-To: <20100527104529.708ee5d4@shaggy.doo> References: <20100527011223.4c6c9b66@liberty.rlwhome.lan> <20100527104529.708ee5d4@shaggy.doo> Message-ID: Ok, I wait for finaly update of the template and resubmit our slackbuild later. Thanks, Erik. -- Eugene Wissner > If you want to take over, that's fine. I don't plan to update it. > However, please be sure to look at our current template before you submit. > Some changes in the diff would not be acceptable. > > -- > Erik Hanson > http://slackbuilds.org/ > > _______________________________________________ > 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 ozan.turkyilmaz at gmail.com Thu May 27 18:48:40 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 27 May 2010 21:48:40 +0300 Subject: [Slackbuilds-users] ibus-anthy Message-ID: Hi, ibus-anthy script runs nicely under bash4. i have to test it more for 13.1 thou. boncuk script runs nicely, too. again more testes are needed for 13.1. i updated both scripts for new SBo template. by the way ibus-qt fails at compile time. it complains that gcc can't even compile a simple test program. i tried latest one from the ibus project, too. -- Ozan From slakmagik at gmail.com Thu May 27 19:04:26 2010 From: slakmagik at gmail.com (slakmagik) Date: Thu, 27 May 2010 15:04:26 -0400 Subject: [Slackbuilds-users] Sbopkg 0.33.1 Released Message-ID: <20100527190426.GA19554@devbox> sbopkg 0.33.1 is released. This release brings us into alignment with SBo and Slackware 13.1, squashes several more or less obscure bugs, and adds a couple of features, too. Here are the changes since the last official release: * Addressed an apparent bash 4.1 bug that causes the 'obsolete sources' function to break. * Addressed issue 44 where hitting ^C during the download of part of a queue and restarting the queue could result in a download failure. Thanks to slava18 for the report. * Changed the menu order of the "Build options" dialog to default to using "Saved" options rather than "None". * Fixed issue 45 where packages with '+' in the name were not properly detected in some cases. Thanks to skalkoto for the report. * Added a help item to the main menu of the dialog interface with pointers to documentation and other resources. * Added an option to print the version of sbopkg. We try not to change the meaning of flags but note that this does change what was the '-v' flag to '-V' and now uses '-v' for its customary 'version' purpose. Note that the new -V flag now accepts a '?' argument (sbopkg -V ?) which will display the list of valid repositories. * Tweak the logic re determining ARCH and modify some ARCH-related evals and conditionals in check_for_updates and info_item. * Fixed a bug which could result in some sources being missed when checking for obsolete sources. * Added a command line option '-P' to access the 'remove uninstalled packages' function which had previously only been accessible from the dialog interface. * Miscellaneous tweaks in preparation for release and to bring in line with Slackware 13.1. * Tweaked widgets in select_repository() (no or less scrolling) and load_user_queue() (better button) and modified check_gpg() to not disrupt the dialog interface with gpg output * Revised the KNOWN_ISSUES file and other documentation As always, thanks to our users who have tested sbopkg and reported bugs and given us such positive, encouraging feedback. This release can be downloaded from http://www.sbopkg.org or http://code.google.com/p/sbopkg/ Thanks also to my fellow developers, Chess Griffin and Mauro Giachero. As may be obvious from the From line and from other signs, Chess is not doing this release but, never fear, he is still actively involved in sbopkg development and was a tremendous help with this release process. I've just agreed to help with releases and other administrative duties in addition to development. Have fun! From joao.eel at gmail.com Fri May 28 00:20:14 2010 From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=) Date: Thu, 27 May 2010 21:20:14 -0300 Subject: [Slackbuilds-users] matplotlib missing (and patch) Message-ID: Hello, I've noticed matplotlib is missing from the 13.1 repository (probably because it needs a patch to compile with the new libpng), and since scipy (and my work!) depends on it, I got the old version from 13.0 and updated it to 0.99.1.2 (the newest version). In case the maintainer does not have interest in updating it, I can take care of this package. I'm not very experienced with git, but following a tutorial I managed to create a patch to add matplotlib to the master branch (attached). If it is wrong please let me know and I can create it again (or forget about it and get back to the good old tarball :). -- Jo?o Felipe Santos -------------- next part -------------- A non-text attachment was scrubbed... Name: add_matplotlib.patch Type: application/octet-stream Size: 5679 bytes Desc: not available URL: From belka.ew at gmail.com Fri May 28 04:54:37 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Fri, 28 May 2010 06:54:37 +0200 Subject: [Slackbuilds-users] evince Message-ID: Hello, there's an error in evince.SlackBuild. The if-condition with "NLS" returns always true. It should be if [ "$NLS" != "YES" ]; then ... ($NLS is variable). Patch is attached. Best regards Eugene Wissner -------------- next part -------------- A non-text attachment was scrubbed... Name: evince.SlackBuild.diff Type: application/octet-stream Size: 428 bytes Desc: not available URL: From chaos.proton at gmail.com Fri May 28 05:10:47 2010 From: chaos.proton at gmail.com (Grissiom) Date: Fri, 28 May 2010 13:10:47 +0800 Subject: [Slackbuilds-users] ibus-anthy In-Reply-To: References: Message-ID: 2010/5/28 Ozan T?rky?lmaz > > by the way ibus-qt fails at compile time. it complains that gcc can't > even compile > a simple test program. i tried latest one from the ibus project, too. > > Hmm, really? ibus-qt compile and run happily on my box(slackware13.1-64bit) Anyway, you can get the "current" version from here: http://gitorious.org/~grissiom/slackbuilds/grissioms-clone/trees/master/ibus-qt I haven't update it to the lastest template yet. -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Fri May 28 06:41:22 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 28 May 2010 01:41:22 -0500 Subject: [Slackbuilds-users] evince In-Reply-To: References: Message-ID: <20100528014122.3960e36f@shaggy.doo> On May 28, 2010, at 6:54 AM, Eugen Wissner wrote: > Hello, > there's an error in evince.SlackBuild. The if-condition with "NLS" > returns always true. It should be > if [ "$NLS" != "YES" ]; then > ... ($NLS is variable). > Patch is attached. Fixed in my branch, thanks. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From the_emmel at gmx.net Fri May 28 11:05:12 2010 From: the_emmel at gmx.net (emmel) Date: Fri, 28 May 2010 13:05:12 +0200 Subject: [Slackbuilds-users] xulrunner Message-ID: <20100528110512.GA25812@pollux.mlnet> Well, byt the looks of it the xulrunner slackbuild isn't quite ready for 13.1. I'm running current here and what I get is: In file included from ../../../../dist/system_wrappers/X11/Xlibint.h:3, from cairo-xlib-display.c:41: /usr/include/X11/Xlibint.h:192: error: expected declaration specifiers or '...' before 'XGenericEventCookie' Any idea how to fix this? -- emmel GPG signed Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7 Certserver : hkp://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From andrew.david.52 at gmail.com Fri May 28 13:39:56 2010 From: andrew.david.52 at gmail.com (andrew) Date: Fri, 28 May 2010 23:39:56 +1000 Subject: [Slackbuilds-users] faac 1.28 does not build against libmp4v2 Message-ID: <20100528133956.GA25804@skamandros.andrews-corner.org> Hi, I am having a little trouble with the Slackware 13.1 build script for faac 1.28. Although faac builds and runs well enough there seems to be a problem with faac building against either internal or external libmp4v2 under gcc 4.4.4 and thus under 13.1. This patch enables support for the internal library: http://git.debian.org/?p=pkg-multimedia/faac.git;a=blob;f=debian/patches/build-fix.patch;hb=HEAD and works well enough on my system, but I could see no way of getting support for the external library. I am not sure how active the faac developers are any more, some discussion here: http://sourceforge.net/tracker/index.php?func=detail&aid=2894310&group_id=704&atid=100704 I would be interested to hear the thoughts of the script maintainer or slackbuilds.org crew on this matter, I will admit that compiling faac against libmp4v2 makes my head spin a little at the best of times. Andrew -- Do you think that's air you're breathing? From baildon.research at googlemail.com Fri May 28 14:24:31 2010 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 28 May 2010 15:24:31 +0100 Subject: [Slackbuilds-users] faac 1.28 does not build against libmp4v2 In-Reply-To: <20100528133956.GA25804@skamandros.andrews-corner.org> References: <20100528133956.GA25804@skamandros.andrews-corner.org> Message-ID: > I am having a little trouble with the Slackware 13.1 build script for > faac 1.28. Although faac builds and runs well enough there seems to be > a problem with faac building against either internal or external > libmp4v2 under gcc 4.4.4 and thus under 13.1. This patch enables > support for the internal library: > > http://git.debian.org/?p=pkg-multimedia/faac.git;a=blob;f=debian/patches/build-fix.patch;hb=HEAD > > and works well enough on my system, but I could see no way of getting > support for the external library. I'm not the maintainer, but this is what I found. http://ftp.eenet.ee/gentoo-portage/media-libs/faac/files/faac-1.28-external-libmp4v2.patch As the patch changes the configure.in file, you need to perform the following act of violence against automake before running configure. patch -p1 < $CWD/faac-1.28-external-libmp4v2.patch libtoolize --force --copy aclocal autoconf automake --add-missing Attached are the patch and the revised SlackBuild. Hope this is helpful! -D. (Third attempt at sending - *damn* the googlemail.com -> gmail.com migration!) -------------- next part -------------- A non-text attachment was scrubbed... Name: faac.SlackBuild Type: application/octet-stream Size: 4620 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: faac-1.28-external-libmp4v2.patch Type: application/octet-stream Size: 1765 bytes Desc: not available URL: From andrew.david.52 at gmail.com Fri May 28 14:49:48 2010 From: andrew.david.52 at gmail.com (andrew) Date: Sat, 29 May 2010 00:49:48 +1000 Subject: [Slackbuilds-users] faac 1.28 does not build against libmp4v2 In-Reply-To: References: <20100528133956.GA25804@skamandros.andrews-corner.org> Message-ID: <20100528144947.GA17069@skamandros.andrews-corner.org> On Fri, May 28, 2010 at 03:24:31PM +0100, David Spencer wrote: > Attached are the patch and the revised SlackBuild. > Hope this is helpful! Worked very well on my system, thanks :). Andrew -- Do you think that's air you're breathing? From chaos.proton at gmail.com Fri May 28 15:34:15 2010 From: chaos.proton at gmail.com (Grissiom) Date: Fri, 28 May 2010 23:34:15 +0800 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? Message-ID: Hello all, It's exciting to hear and see that SBo team have a public git repo now(You have SCM finally ;-). It is very good for cooperating. Although it's a little earlier, I just wonder, will there be a "current" branch that oriented to -current ? Ponce has a repo dedicated for -current ( http://github.com/Ponce/SBo-git ) but that's a different repo and the SBo one is much more cleaner. I think -current users will be very happy if SBo has a current branch and it could collect more work from them. What do you think? ;) -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Fri May 28 16:03:36 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Fri, 28 May 2010 19:03:36 +0300 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: 2010/5/28 Grissiom : > Hello all, > It's exciting to hear and see that SBo team have a public git repo now(You > have SCM?finally?;-). It is very good for cooperating. Although it's a > little earlier, ?I just wonder, will there be a "current" branch that > oriented to -current ? Ponce has a repo dedicated for -current > (?http://github.com/Ponce/SBo-git?) but that's a different repo and the SBo > one is much more cleaner. I think -current users will be very happy if SBo > has a current branch and it could collect more work from them. > What do you think? ;) if there will be a repo for current, i won't able to maintain any package for it on grounds of lack of time. current changes too much too fast, and keeping track of it is itself a big job. -- Ozan From mfilpot at gmail.com Fri May 28 16:23:34 2010 From: mfilpot at gmail.com (Matthew Fillpot) Date: Fri, 28 May 2010 12:23:34 -0400 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: Having a current branch in git only (not having it visible to the website) will help to have preparations done for the upcoming releases. Although not all maintainers will not be able to keep it current, it would be useful to reduce load on the sbo team when new releases are pushed. On May 28, 2010 12:03 PM, "Ozan T?rky?lmaz" wrote: 2010/5/28 Grissiom : > Hello all, > It's exciting to hear and see that SBo team have a public git repo now(You > have SCM... if there will be a repo for current, i won't able to maintain any package for it on grounds of lack of time. current changes too much too fast, and keeping track of it is itself a big job. -- Ozan _______________________________________________ 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 xgizzmo at gmail.com Fri May 28 16:32:34 2010 From: xgizzmo at gmail.com (xgizzmo) Date: Fri, 28 May 2010 12:32:34 -0400 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: On Fri, May 28, 2010 at 12:23 PM, Matthew Fillpot wrote: > Having a current branch in git only (not having it visible to the website) > will help to have preparations done for the upcoming releases. Although not > all maintainers will not be able to keep it current, it would be useful to > reduce load on the sbo team when new releases are pushed. > > On May 28, 2010 12:03 PM, "Ozan T?rky?lmaz" > wrote: > > 2010/5/28 Grissiom : > >> Hello all, >> It's exciting to hear and see that SBo team have a public git repo now(You >> have SCM... > > if there will be a repo for current, i won't able to maintain any package > for it > on grounds of lack of time. current changes too much too fast, and keeping > track of it is itself a big job. > > -- > Ozan > _______________________________________________ > 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 don't not speak for the whole admin staff. But I feel it is almost pointless to try and maintain anything based on -current. You will expend tons of time doing it, and run the risk of having everything you worked on being undone by a single up date to -current. If we made a -current repo then we would be forced into keeping it up to date with -current, something I do not intend to do. From niels.horn at gmail.com Fri May 28 17:59:29 2010 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 28 May 2010 14:59:29 -0300 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: On Fri, May 28, 2010 at 1:32 PM, xgizzmo wrote: > On Fri, May 28, 2010 at 12:23 PM, Matthew Fillpot wrote: >> Having a current branch in git only (not having it visible to the website) >> will help to have preparations done for the upcoming releases. Although not >> all maintainers will not be able to keep it current, it would be useful to >> reduce load on the sbo team when new releases are pushed. >> >> On May 28, 2010 12:03 PM, "Ozan T?rky?lmaz" >> wrote: >> >> 2010/5/28 Grissiom : >> >>> Hello all, >>> It's exciting to hear and see that SBo team have a public git repo now(You >>> have SCM... >> >> if there will be a repo for current, i won't able to maintain any package >> for it >> on grounds of lack of time. current changes too much too fast, and keeping >> track of it is itself a big job. >> >> -- >> Ozan >> _______________________________________________ >> 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 don't not speak for the whole admin staff. But I feel it is almost > pointless to try and maintain anything based on -current. You will > expend tons of time doing it, and run the risk of having everything > you worked on being undone by a single up date to -current. If we made > a -current repo then we would be forced into keeping it up to date > with -current, something I do not intend to do. > _______________________________________________ I agree... -current is a "moving target". I have a machine running current all the time, and all the time things change. Look what changed between 13.0 and 13.1 that affected SlackBuilds: - new bash - new libpng - new gcc - ... and some other stuff... The first three items alone caused work for several SlackBuilds. If SBo creates a public repository (even if it's only git, not http), people expect it to be stable, which it will almost never be. My two (Brazilian) cents... Niels From mjjzf at syntaktisk.dk Fri May 28 21:09:31 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Fri, 28 May 2010 17:09:31 -0400 Subject: [Slackbuilds-users] LyX Slackbuild Message-ID: <20100528170931.173a2eb5@darkstar.example.net> Dear Slackbuilders, I wrote eroc at linuxmail.org a while back with an updated Slackbuild of LyX, but I got no response. Is it still being actively maintained, or should I take it over? Yours, Morten __ Morten Juhl-Johansen Z?lde-Fej?r http://syntaktisk.dk * mjjzf at syntaktisk.dk From hba.nihilismus at gmail.com Fri May 28 21:18:57 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Fri, 28 May 2010 16:18:57 -0500 Subject: [Slackbuilds-users] LyX Slackbuild In-Reply-To: <20100528170931.173a2eb5@darkstar.example.net> References: <20100528170931.173a2eb5@darkstar.example.net> Message-ID: On Fri, May 28, 2010 at 4:09 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: > Dear Slackbuilders, > > I wrote eroc at linuxmail.org a while back with an updated Slackbuild of > LyX, but I got no response. I used to use that email account but not anymore since a long time ago. > Is it still being actively maintained, or should I take it over? No, i dropped it?s maintenance so feel free to take it. -- - hba From ozan.turkyilmaz at gmail.com Fri May 28 21:19:23 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 29 May 2010 00:19:23 +0300 Subject: [Slackbuilds-users] ibus-anthy In-Reply-To: References: Message-ID: 2010/5/28 Grissiom : > 2010/5/28 Ozan T?rky?lmaz >> >> by the way ibus-qt fails at compile time. it complains that gcc can't >> even compile >> a simple test program. i tried latest one from the ibus project, too. >> > > Hmm, really? ibus-qt compile and run happily on my box(slackware13.1-64bit) > Anyway, you can get the "current" version from here: > http://gitorious.org/~grissiom/slackbuilds/grissioms-clone/trees/master/ibus-qt > I haven't update it to the lastest template yet. it turns out i and bash screwed up. -- Ozan From mjjzf at syntaktisk.dk Fri May 28 21:32:38 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Fri, 28 May 2010 17:32:38 -0400 Subject: [Slackbuilds-users] LyX Slackbuild In-Reply-To: References: <20100528170931.173a2eb5@darkstar.example.net> Message-ID: <20100528173238.749672bc@darkstar.example.net> On Fri, 28 May 2010 16:18:57 -0500 Antonio Hern?ndez Blas wrote: > On Fri, May 28, 2010 at 4:09 PM, Morten Juhl-Johansen Z?lde-Fej?r > wrote: > > Dear Slackbuilders, > > > > I wrote eroc at linuxmail.org a while back with an updated Slackbuild > > of LyX, but I got no response. > > I used to use that email account but not anymore since a long time > ago. > > > Is it still being actively maintained, or should I take it over? > > No, i dropped it?s maintenance so feel free to take it. > Right, I'll do that - thank you. Will submit shortly. From chaos.proton at gmail.com Sat May 29 00:27:53 2010 From: chaos.proton at gmail.com (Grissiom) Date: Sat, 29 May 2010 08:27:53 +0800 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: On Sat, May 29, 2010 at 12:32 AM, xgizzmo wrote: > I don't not speak for the whole admin staff. But I feel it is almost > pointless to try and maintain anything based on -current. You will > expend tons of time doing it, and run the risk of having everything > you worked on being undone by a single up date to -current. If we made > a -current repo then we would be forced into keeping it up to date > with -current, something I do not intend to do. > Hmm, that's a good reason. For the seek of ease of maintain and stability, I agree with you. So it seems that I have to keep a stable release of Slackware to maintain my SlackBuilds, which will cancel out my desire to track -current.... ;( -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From chaos.proton at gmail.com Sat May 29 00:30:42 2010 From: chaos.proton at gmail.com (Grissiom) Date: Sat, 29 May 2010 08:30:42 +0800 Subject: [Slackbuilds-users] ibus-anthy In-Reply-To: References: Message-ID: 2010/5/29 Ozan T?rky?lmaz > it turns out i and bash screwed up. > Hmm? It is the ibus-qt.SlackBuild screwed up your bash or some else? From the error message in the original post, it looks like a ARCH issue: set it to x86_64 if you are running 64bit slackware. -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Sat May 29 00:33:44 2010 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 29 May 2010 07:33:44 +0700 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: > So it seems that I have to keep a stable release of Slackware to maintain my > SlackBuilds, which will cancel out my desire to track -current.... ;( You can have your own private git for tracking -Current though :) -- Willy Sudiarto Raharjo Registered Linux User : 336579 Web : http://www.informatix.or.id/willy Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com From niels.horn at gmail.com Sat May 29 00:51:07 2010 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 28 May 2010 21:51:07 -0300 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: On Fri, May 28, 2010 at 9:27 PM, Grissiom wrote: > On Sat, May 29, 2010 at 12:32 AM, xgizzmo wrote: >> >> I don't not speak for the whole admin staff. But I feel it is almost >> pointless to try and maintain anything based on -current. You will >> expend tons of time doing it, and run the risk of having everything >> you worked on being undone by a single up date to -current. If we made >> a -current repo then we would be forced into keeping it up to date >> with -current, something I do not intend to do. > > > Hmm, that's a good reason. For the seek of ease of?maintain?and stability, I > agree with you. > So it seems that I have to keep a stable release of Slackware to maintain my > SlackBuilds, which will cancel out my desire to track -current.... ;( > > -- > Cheers, > Grissiom > You can either: 1) run -current in a Virtual Machine or 2) maintain clean stable Virtual Machines I test all my SlackBuilds in clean VMs, both 32 & 64 bits. Personally I use qemu-kvm with the -snapshot option, so that it always returns in the same state when firing it up. I keep sources and SlackBuilds on my "real" machine, with the directory mounted r/o through nfs on the VMs. It is fast and reliable. The "clean" machines have the complete Slackware installation, with http, php & mysql configured & running, but zero extra packages, so that I discover all needed dependencies. Niels From kev at pulo.com.au Sat May 29 01:16:39 2010 From: kev at pulo.com.au (Kevin Pulo) Date: Sat, 29 May 2010 11:16:39 +1000 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: <20100529011639.GW7867@pulo.com.au> On Fri, May 28, 2010 at 02:59:29PM -0300, Niels Horn wrote: > If SBo creates a public repository (even if it's only git, not http), > people expect it to be stable, which it will almost never be. I have to say, I really don't understand this. If Pat is able to make -current public, and people understand that it's explicitly not stable, then why can't SBo have a -current branch that is also understood to be completely and utterly unstable. When I choose to run -current, I know that all bets are off. To expect stable SBo scripts for an unstable distro branch is unreasonable. It is true that a lot of work may be lost when -current updates, but the people doing that work are likely to be the ones investing time into -current anyway (since they're tracking it for their own usage), so they are still getting benefit from having their scripts working in the time before the update. This way, it may save some others time. Also, feature changes from version upgrades (eg. bash4) tend to be once-off things that aren't reverted, and will need to be done come the next stable version anyway. Kev. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From niels.horn at gmail.com Sat May 29 01:34:42 2010 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 28 May 2010 22:34:42 -0300 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: <20100529011639.GW7867@pulo.com.au> References: <20100529011639.GW7867@pulo.com.au> Message-ID: On Fri, May 28, 2010 at 10:16 PM, Kevin Pulo wrote: > On Fri, May 28, 2010 at 02:59:29PM -0300, Niels Horn wrote: > >> If SBo creates a public repository (even if it's only git, not http), >> people expect it to be stable, which it will almost never be. > > I have to say, I really don't understand this. > > If Pat is able to make -current public, and people understand that > it's explicitly not stable, then why can't SBo have a -current branch > that is also understood to be completely and utterly unstable. ?When I > choose to run -current, I know that all bets are off. ?To expect > stable SBo scripts for an unstable distro branch is unreasonable. > > It is true that a lot of work may be lost when -current updates, but > the people doing that work are likely to be the ones investing time > into -current anyway (since they're tracking it for their own usage), > so they are still getting benefit from having their scripts working in > the time before the update. ?This way, it may save some others time. > Also, feature changes from version upgrades (eg. bash4) tend to be > once-off things that aren't reverted, and will need to be done come > the next stable version anyway. > > Kev. > Good to know that *you* understand that "current" != "stable". But many people don't get that idea. Even with the 13.0 repository I have seen tons of questions like "Hey, foo.SlackBuild does not work on my machine I just installed the latest Slackware-current version on!". I always say this: If you are brave enough to run -current, you really should have enough knowledge to adapt the SlackBuilds yourself. If not, you should *not* be running -current. Yes, I know I'm harsh sometimes. Comes with the Dutch background :) Niels From dragonwisard at gmail.com Sat May 29 02:20:36 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Fri, 28 May 2010 22:20:36 -0400 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: <20100529011639.GW7867@pulo.com.au> References: <20100529011639.GW7867@pulo.com.au> Message-ID: On Fri, May 28, 2010 at 9:16 PM, Kevin Pulo wrote: > On Fri, May 28, 2010 at 02:59:29PM -0300, Niels Horn wrote: > > > If SBo creates a public repository (even if it's only git, not http), > > people expect it to be stable, which it will almost never be. > > I have to say, I really don't understand this. > > If Pat is able to make -current public, and people understand that > it's explicitly not stable, then why can't SBo have a -current branch > that is also understood to be completely and utterly unstable. When I > choose to run -current, I know that all bets are off. To expect > stable SBo scripts for an unstable distro branch is unreasonable. > > It is true that a lot of work may be lost when -current updates, but > the people doing that work are likely to be the ones investing time > into -current anyway (since they're tracking it for their own usage), > so they are still getting benefit from having their scripts working in > the time before the update. This way, it may save some others time. > Also, feature changes from version upgrades (eg. bash4) tend to be > once-off things that aren't reverted, and will need to be done come > the next stable version anyway.http://github.com/Ponce/SBo-git > > Kev. > I agree with most of the points you're making, however it's not *our* time/effort that we should be thinking about but the time/effort of the SBo team. They're busy guys (and I very much appreciate all the work you guys are doing!) and their time is valuable. Asking them to manage an official -current repository on top of all the good work they're already doing for Slackware and SBo seems a bit unreasonable. There is already an unofficial repository for -current on GitHub. I suggest that those of us who are interested in following the tip of -current should contribute our efforts to the unofficial -current tree. The SBo team always has the option to pull from that tree if they see fit. Thanks to the distributed nature of Git, there is nothing stopping us from collaborating on slackbuilds for -current even if the authors of the official tree choose not to. I see http://slackbuilds.org/gitweb/ and http://github.com/Ponce/SBo-git as being complementary (not competing) projects. My $0.02. Regards, Ben > > > _______________________________________________ > 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 rob0 at slackbuilds.org Sat May 29 03:38:01 2010 From: rob0 at slackbuilds.org (/dev/rob0) Date: Fri, 28 May 2010 22:38:01 -0500 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: References: Message-ID: <20100529033801.GF19868@cardinal> On Fri, May 28, 2010 at 09:51:07PM -0300, Niels Horn wrote: > On Fri, May 28, 2010 at 9:27 PM, Grissiom > > On Sat, May 29, 2010 at 12:32 AM, xgizzmo wrote: > >> > >> I don't not speak for the whole admin staff. But I feel it is > >> almost pointless to try and maintain anything based on -current. > >> You will expend tons of time doing it, and run the risk of > >> having everything you worked on being undone by a single up date > >> to -current. If we made a -current repo then we would be forced > >> into keeping it up to date with -current, something I do not > >> intend to do. > > > > Hmm, that's a good reason. For the seek of ease of?maintain?and > > stability, I agree with you. > > So it seems that I have to keep a stable release of Slackware to > > maintain my SlackBuilds, which will cancel out my desire to track > > -current.... ;( > > You can either: > > 1) run -current in a Virtual Machine > > or > > 2) maintain clean stable Virtual Machines A virtual machine is overkill, generally. A chroot works well. These are my bind-mounts: cd /home/slackware-13.1 # where I have done a full install using # installpkg -root /home/slackware-13.1 for MOUNT in proc proc/bus/usb sys tmp home ; do mount -v --bind \ /$MOUNT $MOUNT ; done chroot . You might not want/need /tmp and /home in that list, but I do. The whole mess could be scripted with proper environment variables and everything. My main computer has an aging slamd64 install with a shiny newish kernel. I'm using it to build some packages for my 32-bit netbook which is running 13.1. In some cases there could be obscure bugs occurring from the different kernels (I have a custom 2.6.31 rather than a stock 13.1 kernel on here), but that's not likely, and something that the SBo review process would probably find, if you submitted a build tested in such a chroot. > I test all my SlackBuilds in clean VMs, both 32 & 64 bits. > Personally I use qemu-kvm with the -snapshot option, so that > it always returns in the same state when firing it up. > I keep sources and SlackBuilds on my "real" machine, with > the directory mounted r/o through nfs on the VMs. > It is fast and reliable. > > The "clean" machines have the complete Slackware installation, > with http, php & mysql configured & running, but zero extra > packages, so that I discover all needed dependencies. -- Offlist mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header From listreader at lupulin.net Sat May 29 03:50:13 2010 From: listreader at lupulin.net (paul wisehart) Date: Fri, 28 May 2010 23:50:13 -0400 Subject: [Slackbuilds-users] Will there be a "current" branch in official SBo git repo? In-Reply-To: <20100529033801.GF19868@cardinal> References: <20100529033801.GF19868@cardinal> Message-ID: <4C008EF5.40509@lupulin.net> /dev/rob0 wrote: > On Fri, May 28, 2010 at 09:51:07PM -0300, Niels Horn wrote: >> >> 1) run -current in a Virtual Machine >> >> or >> >> 2) maintain clean stable Virtual Machines > > A virtual machine is overkill, generally. A chroot works well. > These are my bind-mounts: > > cd /home/slackware-13.1 # where I have done a full install using > # installpkg -root /home/slackware-13.1 > for MOUNT in proc proc/bus/usb sys tmp home ; do mount -v --bind \ > /$MOUNT $MOUNT ; done > chroot . > > You might not want/need /tmp and /home in that list, but I do. The > whole mess could be scripted with proper environment variables and > everything. > > My main computer has an aging slamd64 install with a shiny newish > kernel. I'm using it to build some packages for my 32-bit netbook > which is running 13.1. In some cases there could be obscure bugs > occurring from the different kernels (I have a custom 2.6.31 rather > than a stock 13.1 kernel on here), but that's not likely, and > something that the SBo review process would probably find, if you > submitted a build tested in such a chroot. > au contraire mon fraire, That virtual machine setup is ideal for package building/testing. of course your setup is very nice also :) --pw From erik at slackbuilds.org Sat May 29 04:37:39 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 28 May 2010 23:37:39 -0500 Subject: [Slackbuilds-users] faac 1.28 does not build against libmp4v2 In-Reply-To: References: <20100528133956.GA25804@skamandros.andrews-corner.org> Message-ID: <20100528233739.5b7b79ee@shaggy.doo> On May 28, 2010, at 3:24 PM, David Spencer wrote: > > Attached are the patch and the revised SlackBuild. > Hope this is helpful! Added this to my branch, Thanks. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sat May 29 05:51:01 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 29 May 2010 00:51:01 -0500 Subject: [Slackbuilds-users] matplotlib missing (and patch) In-Reply-To: References: Message-ID: <20100529005101.50bd0794@liberty.rlwhome.lan> On Thu, 27 May 2010 21:20:14 -0300 Jo?o Felipe Santos wrote: > I've noticed matplotlib is missing from the 13.1 repository (probably > because it needs a patch to compile with the new libpng), and since > scipy (and my work!) depends on it, I got the old version from 13.0 > and updated it to 0.99.1.2 (the newest version). In case the > maintainer does not have interest in updating it, I can take care of > this package. > > I'm not very experienced with git, but following a tutorial I managed > to create a patch to add matplotlib to the master branch (attached). > If it is wrong please let me know and I can create it again (or forget > about it and get back to the good old tarball :). I'm going to add this to my branch, but if the previous maintainer (CC'd on this mail) wants to keep maintaining it, I'll revert that portion of the update that changed the maintainer. Alex, let me know if you object... -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sat May 29 06:12:12 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 29 May 2010 01:12:12 -0500 Subject: [Slackbuilds-users] xulrunner In-Reply-To: <20100528110512.GA25812@pollux.mlnet> References: <20100528110512.GA25812@pollux.mlnet> Message-ID: <20100529011212.779134c4@liberty.rlwhome.lan> On Fri, 28 May 2010 13:05:12 +0200 emmel wrote: > Well, byt the looks of it the xulrunner slackbuild isn't quite ready > for 13.1. I'm running current here and what I get is: > > In file included > from ../../../../dist/system_wrappers/X11/Xlibint.h:3, from > cairo-xlib-display.c:41: /usr/include/X11/Xlibint.h:192: error: > expected declaration specifiers or '...' before 'XGenericEventCookie' > > Any idea how to fix this? Nothing to fix here - it builds fine. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From asamardzic at gmail.com Sat May 29 06:28:06 2010 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Sat, 29 May 2010 08:28:06 +0200 Subject: [Slackbuilds-users] matplotlib missing (and patch) In-Reply-To: <20100529005101.50bd0794@liberty.rlwhome.lan> References: <20100529005101.50bd0794@liberty.rlwhome.lan> Message-ID: On Sat, May 29, 2010 at 7:51 AM, Robby Workman wrote: > On Thu, 27 May 2010 21:20:14 -0300 > Jo?o Felipe Santos wrote: > >> I've noticed matplotlib is missing from the 13.1 repository (probably >> because it needs a patch to compile with the new libpng), and since >> scipy (and my work!) depends on it, I got the old version from 13.0 >> and updated it to 0.99.1.2 (the newest version). In case the >> maintainer does not have interest in updating it, I can take care of >> this package. >> >> I'm not very experienced with git, but following a tutorial I managed >> to create a patch to add matplotlib to the master branch (attached). >> If it is wrong please let me know and I can create it again (or forget >> about it and get back to the good old tarball :). > > > I'm going to add this to my branch, but if the previous maintainer > (CC'd on this mail) wants to keep maintaining it, I'll revert that > portion of the update that changed the maintainer. > > Alex, let me know if you object... No, I've already mentioned to Jo?o, through private message, that I would be glad if he'd be willing to take over the maintenance. Also - I don't use numpy anymore too, so if anyone would be willing to take over this one, that would be great... Regards, Alex From ozan.turkyilmaz at gmail.com Sat May 29 07:20:41 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 29 May 2010 10:20:41 +0300 Subject: [Slackbuilds-users] ibus-anthy In-Reply-To: References: Message-ID: 2010/5/29 Grissiom : > 2010/5/29 Ozan T?rky?lmaz >> >> it turns out i and bash screwed up. > > Hmm? It is the ibus-qt.SlackBuild screwed up your bash or some else? From > the error message in the original post, it looks like a ARCH issue: set it > to x86_64 if you are running 64bit slackware. somehow RACH did not get set. -- Ozan From rworkman at slackbuilds.org Sat May 29 08:33:28 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 29 May 2010 08:33:28 +0000 Subject: [Slackbuilds-users] 13.1 Repo Live! Message-ID: <20100529083328.GA11096@slackbuilds.org> Thu May 27 05:13:34 UTC 2010 Okay, folks, it's that time again. We're running a bit behind this time, but we think (most of) the kinks are worked out at this point. As we announced on the mailing list a couple of days ago, we've spent a *lot* of time and effort getting our entire repository into git, so everything is now available there in addition to our "normal" offerings (http, ftp, and rsync). This has not been without a few hiccups along the way, and one of them is a mixed blessing: git keeps track of *everything* :-) As such, it seems like too much time/effort involved in providing a ChangeLog *this* time to detail what's added, removed, patched, and so on; therefore, if you are interested in that (and you should be), have a look here: http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=log;h=refs/heads/13.1 We'll be creating the usual "Slackware-style" ChangeLog.txt from this point forward, so don't get too excited about having to crawl the git logs... :-) Anyway, I (rworkman) would like to take this opportunity to thank the other admins for all of the help with this, particularly: Heinz Wiesinger for providing lots of git expertise and massive improvements to our "system" for managing submissions behind the scenes; Erik Hanson for an outstanding job managing the server; David Somero for test-building the entire tree on -current to find out what was broken; Ezra Free for popping in to fix the occasional "emergency" with the website code; Rob McGee for sitting in the shadows (well, mostly) making sure our DNS resolves correctly and our mail gets delivered; Michiel van Wessem for the "routine" stuff (and laughing at my lame jokes); and for the sake of completeness, Eric Hameleers and Alan Hicks for all of the little things that are so often overlooked and/or unrecognized but nonetheless necessary. Thanks, guys - you are sincerely appreciated! Finally, thanks to all of you readers for helping bring us to where we are today - obviously this applies to those of you who maintain various scripts in the repo, as those are the reason anyone visits the site - but it also applies to the "normal" users. Thanks for the feedback, the bug reports, the fixes, the word-of-mouth recommendations on forums and mailing lists, and so on - we appreciate your votes of confidence. That being said, there are almost surely some bugs lurking in this first batch of public offerings, but maybe we can get those shaken out pretty quickly. We're going to wait a few days (maybe even a week or so) before we open the submission form back up - this will give us time to knock out any bugs that are uncovered. Enjoy! --rworkman From ozan.turkyilmaz at gmail.com Sat May 29 08:54:14 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 29 May 2010 11:54:14 +0300 Subject: [Slackbuilds-users] Status Report In-Reply-To: <20100526005856.5478ced1@liberty.rlwhome.lan> References: <20100526005856.5478ced1@liberty.rlwhome.lan> Message-ID: 2010/5/26 Robby Workman : > > [1] That's not to say that a git pull request won't be honored. > ? ?In fact, if you were to clone master and host it on e.g. github, > ? ?and create a separate branch for each app that you submit via > ? ?our submission form, and note that in the comments of the > ? ?submission, it's certainly possible that some of us :) might > ? ?use that. ? This is particularly true for cases where: > ? ? ?[ $admin == rworkman ] && [ $changetype == trivial ] ?:-) where should we send the request? right now chages are not trivial, hence no git pull request. but most of the chages i did was trvial. it would simpify my and your work (admins). -- Ozan From grbzks at gmail.com Sat May 29 12:22:17 2010 From: grbzks at gmail.com (Grigorios Bouzakis) Date: Sat, 29 May 2010 15:22:17 +0300 Subject: [Slackbuilds-users] 13.1 Repo Live! References: <20100529083328.GA11096@slackbuilds.org> Message-ID: <4c010700.8704df0a.1995.ffff97b1@mx.google.com> Robby Workman wrote: > Thu May 27 05:13:34 UTC 2010 > Okay, folks, it's that time again. We're running a bit behind this time, > but we think (most of) the kinks are worked out at this point. As we > announced on the mailing list a couple of days ago, we've spent a *lot* of > time and effort getting our entire repository into git, so everything is > now available there in addition to our "normal" offerings (http, ftp, and > rsync). This has not been without a few hiccups along the way, and one of > them is a mixed blessing: git keeps track of *everything* :-) As such, > it seems like too much time/effort involved in providing a ChangeLog > *this* time to detail what's added, removed, patched, and so on; > therefore, if you are interested in that (and you should be), have a look > here: > http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=log;h=refs/heads/13.1 > We'll be creating the usual "Slackware-style" ChangeLog.txt from this > point forward, so don't get too excited about having to crawl the git > logs... :-) > Anyway, I (rworkman) would like to take this opportunity to thank the other > admins for all of the help with this, particularly: Heinz Wiesinger for > providing lots of git expertise and massive improvements to our "system" > for managing submissions behind the scenes; Erik Hanson for an outstanding > job managing the server; David Somero for test-building the entire tree on > -current to find out what was broken; Ezra Free for popping in to fix the > occasional "emergency" with the website code; Rob McGee for sitting in the > shadows (well, mostly) making sure our DNS resolves correctly and our mail > gets delivered; Michiel van Wessem for the "routine" stuff (and laughing > at my lame jokes); and for the sake of completeness, Eric Hameleers and > Alan Hicks for all of the little things that are so often overlooked > and/or > unrecognized but nonetheless necessary. Thanks, guys - you are sincerely > appreciated! > Finally, thanks to all of you readers for helping bring us to where we are > today - obviously this applies to those of you who maintain various > scripts in the repo, as those are the reason anyone visits the site - but > it also > applies to the "normal" users. Thanks for the feedback, the bug reports, > the fixes, the word-of-mouth recommendations on forums and mailing lists, > and so on - we appreciate your votes of confidence. That being said, > there are almost surely some bugs lurking in this first batch of public > offerings, > but maybe we can get those shaken out pretty quickly. We're going to wait > a few days (maybe even a week or so) before we open the submission form > back up - this will give us time to knock out any bugs that are uncovered. > Enjoy! --rworkman Thanks a lot! I am curious to see how git will work. -- Greg From the_emmel at gmx.net Sat May 29 12:57:03 2010 From: the_emmel at gmx.net (emmel) Date: Sat, 29 May 2010 14:57:03 +0200 Subject: [Slackbuilds-users] xulrunner In-Reply-To: <20100529011212.779134c4@liberty.rlwhome.lan> References: <20100528110512.GA25812@pollux.mlnet> <20100529011212.779134c4@liberty.rlwhome.lan> Message-ID: <20100529125703.GA2193@pollux.mlnet> On Sat, May 29, 2010 at 01:12:12AM -0500, Robby Workman wrote: > On Fri, 28 May 2010 13:05:12 +0200 > emmel wrote: > > > Well, byt the looks of it the xulrunner slackbuild isn't quite ready > > for 13.1. I'm running current here and what I get is: > > > > In file included > > from ../../../../dist/system_wrappers/X11/Xlibint.h:3, from > > cairo-xlib-display.c:41: /usr/include/X11/Xlibint.h:192: error: > > expected declaration specifiers or '...' before 'XGenericEventCookie' > > > > Any idea how to fix this? > > > Nothing to fix here - it builds fine. > > -RW How do you do that? That's second time my build bailed out and your's worked just fine. I might have a different cairo, though. Did you build yours recently? -- emmel GPG signed Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7 Certserver : hkp://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From joao.eel at gmail.com Sat May 29 14:25:27 2010 From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=) Date: Sat, 29 May 2010 11:25:27 -0300 Subject: [Slackbuilds-users] matplotlib missing (and patch) In-Reply-To: References: <20100529005101.50bd0794@liberty.rlwhome.lan> Message-ID: On Sat, May 29, 2010 at 3:28 AM, Aleksandar Samardzic wrote: >> >> I'm going to add this to my branch, but if the previous maintainer >> (CC'd on this mail) wants to keep maintaining it, I'll revert that >> portion of the update that changed the maintainer. >> >> Alex, let me know if you object... > > No, I've already mentioned to Jo?o, through private message, that I > would be glad if he'd be willing to take over the maintenance. > > Also - I don't use numpy anymore too, so if anyone would be willing to > take over this one, that would be great... > > Regards, > Alex Sorry Alex, I forgot to tell everybody ;) I can take care of numpy too. Soon I'll take over all Python scientific libs! -- Jo?o Felipe Santos From thomas at beingboiled.info Sat May 29 20:39:26 2010 From: thomas at beingboiled.info (Thomas Morper) Date: Sat, 29 May 2010 22:39:26 +0200 Subject: [Slackbuilds-users] small fix for perl-dbd-sqlite In-Reply-To: <20100515212720.326f2bd7@liberty.rlwhome.lan> References: <201005151435.44158.thomas@beingboiled.info> <20100515212720.326f2bd7@liberty.rlwhome.lan> Message-ID: <201005292239.26870.thomas@beingboiled.info> Am Sonntag, 16. Mai 2010 04:27:20 schrieben Sie: > > There's a small bug in my SlackBuild for perl-dbd-sqlite. On > > anything else than Slackware 13.0 with Perl 5.10.0 the hardcoded > > Perl version number prevents the $PKG dir from being cleaned up > > prior to "makepkg". > > Could one of the admins please fix this? Thanks! > Done in local branch ; will be in next public update. Whoops... looks like this got un-fixed again when the patch for bash4- compliance was added two days later. I like gitweb :-) Here's a proper version: - bash4 compliant - version independent cleanup of $PKG - removes the unwanted files only once (stupid me!) Can one of the admins enter this into the repository, please? Thanks! -- -------------- next part -------------- A non-text attachment was scrubbed... Name: perl-dbd-sqlite.SlackBuild Type: application/x-shellscript Size: 1981 bytes Desc: not available URL: From matteo.bernardini at sns.it Sat May 29 20:44:59 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Sat, 29 May 2010 22:44:59 +0200 Subject: [Slackbuilds-users] 13.1 Repo Live! - git stuff In-Reply-To: <20100529083328.GA11096@slackbuilds.org> References: <20100529083328.GA11096@slackbuilds.org> Message-ID: <4C017CCB.2040705@sns.it> I forked slackbuilds.org git master, and I checked all the branches I had done on the github SBo-git repo against that, branching the changes on the new fork. This is the result: (sorry for the pastebin link but it wouldn't be much readable in the email body) http://pastebin.com/raw.php?i=2PH20YzM http://github.com/Ponce/slackbuilds there are branches with: - various fixes; - reverted removals; - cleanups (I checked the slackbuilds in the old branches I had on github :) ); - additions; - optionals updates to ffmpeg, ffmpegthumbnailer, x264, audacity, cherokee, clamav, 2ManDVD, gst-plugins-bad, gst-plugins-ugly, gst-python, kino, wormux; - downgrades for things that seems to break. I checked only the stuff I build usually, and I'll try soon a full build of all my packages from scratch using a new "current" branch in which I'll merge all the others (and that I'll configure in sbopkg). I know subsmission are not open, but feel free to have a look if you like, I hope something can be useful :) Matteo From matteo.bernardini at sns.it Sun May 30 05:48:38 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Sun, 30 May 2010 07:48:38 +0200 Subject: [Slackbuilds-users] 13.1 Repo Live! - git stuff In-Reply-To: <20100529083328.GA11096@slackbuilds.org> References: <20100529083328.GA11096@slackbuilds.org> Message-ID: <4C01FC36.30108@sns.it> sorry for the double posting but yesterday evening I was I little tired and I forgot the most important thing. I tried as much as I can to follow robby advices in committing the branches (also for the commit text): if any of you got suggestions to improve the way I followed or you just spotted some wrong thing in my stuff, please correct me. Matteo From chaos.proton at gmail.com Sun May 30 12:11:28 2010 From: chaos.proton at gmail.com (Grissiom) Date: Sun, 30 May 2010 20:11:28 +0800 Subject: [Slackbuilds-users] updates of the SlackBuilds maintained by me Message-ID: Hello, My updates of the SlackBuilds is here: http://github.com/grissiom/slackbuilds (or git url, git:// github.com/grissiom/slackbuilds.git) Main changes are update with upstream and merge with new templates. I think a git log -p will show all the stuffs ;-) Hope they could be merged into the mainline. If have any problem, feel free to contract with me. -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From nowbrians at yahoo.co.uk Sun May 30 11:52:03 2010 From: nowbrians at yahoo.co.uk (Brian Lawrence) Date: Sun, 30 May 2010 11:52:03 +0000 (GMT) Subject: [Slackbuilds-users] Texlive SlackBuild error Message-ID: <232851.9921.qm@web28504.mail.ukl.yahoo.com> The download of texi2html failed due to the wrong URL in the texlive.info file. I've attached a text file with the details. Hope this is satisfactory, I'm new to bug reporting. Brian (brianL on? LQ) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: texlive_SB_fault.txt URL: From erik at slackbuilds.org Sun May 30 12:26:47 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 30 May 2010 07:26:47 -0500 Subject: [Slackbuilds-users] updates of the SlackBuilds maintained by me In-Reply-To: References: Message-ID: <20100530072647.48d3d5ab@shaggy.doo> On Sun, 30 May 2010 20:11:28 +0800 Grissiom wrote: > Hello, > > My updates of the SlackBuilds is here: > > http://github.com/grissiom/slackbuilds (or git url, git:// > github.com/grissiom/slackbuilds.git) There may be some confusion, this is not how we take updates. You'll need to use the submission form when it re-opens. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From joao.eel at gmail.com Sun May 30 12:28:43 2010 From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=) Date: Sun, 30 May 2010 04:28:43 -0800 Subject: [Slackbuilds-users] Texlive SlackBuild error In-Reply-To: <232851.9921.qm@web28504.mail.ukl.yahoo.com> References: <232851.9921.qm@web28504.mail.ukl.yahoo.com> Message-ID: On Sun, May 30, 2010 at 3:52 AM, Brian Lawrence wrote: > > The download of texi2html failed due to the wrong URL in the texlive.info file. I've attached a text file with the details. Hope this is satisfactory, I'm new to bug reporting. > Brian > (brianL on? LQ) > Hello, I've found this error yesterday, too. Since I did not knew if the mirror was out forever or just for that moment I have not reported it. It is easy to find another texi2html mirror. Try this link to find a mirror near you: http://savannah.nongnu.org/download/texi2html/ -- Jo?o Felipe Santos From omari at smileystation.com Sun May 30 15:24:04 2010 From: omari at smileystation.com (Omari Norman) Date: Sun, 30 May 2010 11:24:04 -0400 Subject: [Slackbuilds-users] lirc for Slackware 13.1 not building on x86 Message-ID: <20100530152404.GA1889@walter> Hi, When I try to build lirc on x86 for Slackware 13.1, I get this error: make all-recursive make[1]: Entering directory `/tmp/SBo/lirc-0.8.6' Making all in drivers make[2]: Entering directory `/tmp/SBo/lirc-0.8.6/drivers' Making all in lirc_dev make[3]: Entering directory `/tmp/SBo/lirc-0.8.6/drivers/lirc_dev' cp ./../lirc_dev/Module*.symvers . cp: cannot stat `./../lirc_dev/Module*.symvers': No such file or directory make[3]: [lirc_dev.o] Error 1 (ignored) mv Makefile Makefile.automake cp ./../Makefile.kernel Makefile CPPFLAGS="" CFLAGS="" LDFLAGS="" \ make -C /lib/modules/2.6.33.4-smp/build/ SUBDIRS=/tmp/SBo/lirc-0.8.6/drivers/lirc_dev modules \ KBUILD_VERBOSE=1 make[4]: Entering directory `/usr/src/linux-2.6.33.4' Makefile:535: /usr/src/linux-2.6.33.4/arch/i486/Makefile: No such file or directory make[4]: *** No rule to make target `/usr/src/linux-2.6.33.4/arch/i486/Makefile'. Stop. make[4]: Leaving directory `/usr/src/linux-2.6.33.4' make[3]: *** [lirc_dev.o] Error 2 make[3]: Leaving directory `/tmp/SBo/lirc-0.8.6/drivers/lirc_dev' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/SBo/lirc-0.8.6/drivers' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/lirc-0.8.6' make: *** [all] Error 2 It seems the problem is that a Makefile in /usr/src/linux-2.6.33.4 is trying to include a file that does not exist because there is no directory for i486. This patch makes it compile by simply saying, compile it for i386. I have no expertise whatsoever so I can't vouch for how good the patch is or whether others should use it, but it does work for me. --- lirc.SlackBuild.orig 2010-05-30 11:01:25.752549326 -0400 +++ lirc.SlackBuild 2010-05-30 11:19:17.600550218 -0400 @@ -33,7 +33,7 @@ # Automatically determine the architecture we're building on: if [ -z "$ARCH" ]; then case "$( uname -m )" in - i?86) export ARCH=i486 ;; + i?86) export ARCH=i386 ;; arm*) export ARCH=arm ;; # Unless $ARCH is already set, use uname -m for all other archs: *) export ARCH=$( uname -m ) ;; @@ -45,8 +45,8 @@ PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} -if [ "$ARCH" = "i486" ]; then - SLKCFLAGS="-O2 -march=i486 -mtune=i686" +if [ "$ARCH" = "i386" ]; then + SLKCFLAGS="-O2 -march=i386 -mtune=i386" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" Thanks for doing the work of making lirc work with the new kernel; without this SlackBuild I probably could not use 13.1 at all. --Omari From xgizzmo at gmail.com Sun May 30 17:56:32 2010 From: xgizzmo at gmail.com (xgizzmo) Date: Sun, 30 May 2010 13:56:32 -0400 Subject: [Slackbuilds-users] lirc for Slackware 13.1 not building on x86 In-Reply-To: <20100530152404.GA1889@walter> References: <20100530152404.GA1889@walter> Message-ID: i?86) export ARCH=i486 ;; arm*) export ARCH=arm ;; Remove the word export from these two lines. From kd5zex at gmail.com Sun May 30 20:35:47 2010 From: kd5zex at gmail.com (Alan) Date: Sun, 30 May 2010 15:35:47 -0500 Subject: [Slackbuilds-users] nvidia-kernel Message-ID: I just did the upgrade to 13.1 and am having the "Unable to determine the target kernel version" error when using the slackbuild. I patched the nvidia source a while back when running current but was under the impression that this was no longer necessary after blacklisting the nouveau driver. Anyone have any insight? Cheers, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From grbzks at xsmail.com Sun May 30 20:51:48 2010 From: grbzks at xsmail.com (Grigorios Bouzakis) Date: Sun, 30 May 2010 23:51:48 +0300 Subject: [Slackbuilds-users] nvidia-kernel In-Reply-To: References: Message-ID: <201005302351.54765.grbzks@xsmail.com> On Sunday 30 of May 2010 23:35:47 Alan wrote: > I just did the upgrade to 13.1 and am having the "Unable to determine the > target kernel version" error when using the slackbuild. I patched the > nvidia source a while back when running current but was under the > impression that this was no longer necessary after blacklisting the > nouveau driver. AFAIK it isn't. Which version did you try to install? I'd go with 195.36.24 which the latest stable. -- Greg -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: From kd5zex at gmail.com Sun May 30 20:59:35 2010 From: kd5zex at gmail.com (Alan) Date: Sun, 30 May 2010 15:59:35 -0500 Subject: [Slackbuilds-users] nvidia-kernel In-Reply-To: <201005302351.54765.grbzks@xsmail.com> References: <201005302351.54765.grbzks@xsmail.com> Message-ID: On Sun, May 30, 2010 at 15:51, Grigorios Bouzakis wrote: > On Sunday 30 of May 2010 23:35:47 Alan wrote: > > I just did the upgrade to 13.1 and am having the "Unable to determine > the > > target kernel version" error when using the slackbuild. I patched the > > nvidia source a while back when running current but was under the > > impression that this was no longer necessary after blacklisting the > > nouveau driver. > > AFAIK it isn't. Which version did you try to install? > I'd go with 195.36.24 which the latest stable. > > -- > Greg > > _______________________________________________ > 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'd go with 195.36.24 which the latest stable. No dice with the latest version either. Same error. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kd5zex at gmail.com Sun May 30 21:11:23 2010 From: kd5zex at gmail.com (Alan) Date: Sun, 30 May 2010 16:11:23 -0500 Subject: [Slackbuilds-users] nvidia-kernel In-Reply-To: References: <201005302351.54765.grbzks@xsmail.com> Message-ID: On Sun, May 30, 2010 at 15:59, Alan wrote: > > > On Sun, May 30, 2010 at 15:51, Grigorios Bouzakis wrote: > >> On Sunday 30 of May 2010 23:35:47 Alan wrote: >> > I just did the upgrade to 13.1 and am having the "Unable to determine >> the >> > target kernel version" error when using the slackbuild. I patched the >> > nvidia source a while back when running current but was under the >> > impression that this was no longer necessary after blacklisting the >> > nouveau driver. >> >> AFAIK it isn't. Which version did you try to install? >> I'd go with 195.36.24 which the latest stable. >> >> -- >> Greg >> >> _______________________________________________ >> 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'd go with 195.36.24 which the latest stable. > > No dice with the latest version either. Same error. > > Alan > Please disregard, I reinstalled the kernel packages and it worked. Cheers, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.antle at gmail.com Mon May 31 06:06:16 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Mon, 31 May 2010 02:06:16 -0400 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt Message-ID: <20100531060614.GA14337@slack> Hello - This is my first attempt at writing a SlackBuild script. If someone would look it over to make sure I haven't screwed anything up, that would be much appreciated. :) #!/bin/sh # Slackware build script for SWI-Prolog # # Copyright 2010 Andrew Antle # All rights reserved. # # Redistribution and use of this script, with or without modification, is # permitted provided that the following conditions are met: # # 1. Redistributions of this script must retain the above copyright # notice, this list of conditions and the following disclaimer. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # # 0.1 2010-05-08 # 0.2 2010-05-31 PRGNAM=swi-prolog VERSION=${VERSION:-5.10.0} ARCH=${ARCH:-i486} BUILD=${BUILD:-2} TAG=${TAG:-_SBo} CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} # Default CFLAGS not set as configure works this out. Is this wrong? if [ "$ARCH" = "i486" ]; then SLKCFLAGS="" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="" LIBDIRSUFFIX="64" fi # Custom variable because source package name differs from what we're # going to call it. TARNAM=pl set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $TARNAM-$VERSION tar xvf $CWD/$TARNAM-$VERSION.tar.gz cd $TARNAM-$VERSION chown -R root:root . find . \ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --localstatedir=/var \ --mandir=/usr/man \ --docdir=/usr/doc/$PRGNAM-$VERSION \ --build=$ARCH-slackware-linux \ --with-world make make install DESTDIR=$PKG # Strip binaries and libraries - this can be done with 'make install-strip' # in many source trees, and that's usually acceptable if so, but if not, # use this: find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true # Compress man pages # If the man pages are installed to /usr/share/man instead, you'll need to either # add the --mandir=/usr/man flag to configure or move them manually after the # make install process is run. find $PKG/usr/man -type f -exec gzip -9 {} \; mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} Thanks, -- Andrew Antle From matteo.bernardini at sns.it Mon May 31 06:35:43 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Mon, 31 May 2010 08:35:43 +0200 Subject: [Slackbuilds-users] build fixes for LiVES, avidemux, vice Message-ID: <4C0358BF.4060607@sns.it> sorry if I hasn't been clear about the build issues I found with the new 13.1 repository (I'm still too enthusiastic about having a git repo to play with :) ), I'll try to list them in a ordered form: ----------------------------------------- LiVES the package is created with a /usr/bin/lives link that points in the build directory: I managed to fix it adding an additional manual link creation to the slackbuild. I also added the miscellaneous cleanups following the template. http://github.com/Ponce/slackbuilds/commit/8302768d094c5f4ac084c3a652e95ce283183e06 ----------------------------------------- diff --git a/multimedia/LiVES/LiVES.SlackBuild b/multimedia/LiVES/LiVES.SlackBuild index eac024b..4be6aa6 100644 --- a/multimedia/LiVES/LiVES.SlackBuild +++ b/multimedia/LiVES/LiVES.SlackBuild @@ -9,10 +9,19 @@ PRGNAM=LiVES VERSION=1.1.8 -ARCH=${ARCH:-i486} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} +# Automatically determine the architecture we're building on: +if [ -z "$ARCH" ]; then + case "$( uname -m )" in + i?86) ARCH=i486 ;; + arm*) ARCH=arm ;; + # Unless $ARCH is already set, use uname -m for all other archs: + *) ARCH=$( uname -m ) ;; + esac +fi + CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM @@ -24,9 +33,12 @@ if [ "$ARCH" = "i486" ]; then elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" - elif [ "$ARCH" = "x86_64" ]; then +elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" +else + SLKCFLAGS="-O2" + LIBDIRSUFFIX="" fi set -e @@ -55,6 +67,10 @@ CFLAGS="$SLKCFLAGS" \ make docdir=/usr/doc/$PRGNAM-$VERSION make install-strip docdir=/usr/doc/$PRGNAM-$VERSION DESTDIR=$PKG +# fix wrong link to lives-exe binary +rm $PKG/usr/bin/lives +ln -s /usr/bin/lives-exe $PKG/usr/bin/lives + mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a COPYING INSTALL NEWS $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild ----------------------------------------- avidemux ----------------------------------------- the package has a wrong md5sum in the info file, installs library in the wrong path on x86_64 and doesn't build the plugins: took the fixes from alien bob's buildscript and applied http://github.com/Ponce/slackbuilds/commit/0e6157ab1b20474e96bf110b0d23087837a8bfc3 ----------------------------------------- diff --git a/multimedia/avidemux/avidemux.SlackBuild b/multimedia/avidemux/avidemux.SlackBuild index b05768d..9ab8f66 100644 --- a/multimedia/avidemux/avidemux.SlackBuild +++ b/multimedia/avidemux/avidemux.SlackBuild @@ -74,6 +74,11 @@ chmod -R a-s,u+w,go+r-w . #Patch that installs i18n in the correct place even if we compile with qt4 support cat $CWD/avidemux-2.5.1-i18n.patch | patch -p1 --verbose --backup --suffix=.orig +if [ "$ARCH" = "x86_64" ]; then + # Some paths are incorrectly hardcoded to "lib": + sed -i -e "s/Dir=\"lib\"/Dir=\"lib${LIBDIRSUFFIX}\"/" $(grep -lr 'Dir="lib"' .) +fi + mkdir build cd build @@ -121,6 +126,23 @@ cd build make DESTDIR=$PKG install/strip cd .. +mkdir -p build_plugins +cd build_plugins + cmake \ + -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \ + -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \ + -DCMAKE_INSTALL_PREFIX=/usr \ + -DMAN_INSTALL_DIR=/usr/man \ + -DSYSCONF_INSTALL_DIR=/etc \ + -DLIB_SUFFIX=${LIBDIRSUFFIX} \ + -DAVIDEMUX_SOURCE_DIR=$(cd .. ; pwd) \ + -DAVIDEMUX_CORECONFIG_DIR=$(cd .. ; pwd)/build/config \ + -DAVIDEMUX_INSTALL_PREFIX=$(cd .. ; pwd)/build \ + ../plugins + make + make DESTDIR=$PKG install/strip +cd - + mkdir -p $PKG/usr/man/man1 cat man/avidemux.1 | gzip -9c > $PKG/usr/man/man1/avidemux.1.gz diff --git a/multimedia/avidemux/avidemux.info b/multimedia/avidemux/avidemux.info index 4ed9891..8622274 100644 --- a/multimedia/avidemux/avidemux.info +++ b/multimedia/avidemux/avidemux.info @@ -3,8 +3,8 @@ VERSION="2.5.2" HOMEPAGE="http://avidemux.org" DOWNLOAD="http://downloads.sourceforge.net/avidemux/avidemux_2.5.2.tar.gz" DOWNLOAD_x86_64="" -MD5SUM="22467c9ea5476d94cbd505685b4c11e7" +MD5SUM="9027e1324c06e833e6c3c22298503cc7" MD5SUM_x86_64="" MAINTAINER="Niklas 'Nille' ?kerstr?m" EMAIL="Nille.kungen[AT]gmail.com" -APPROVED="michiel" +APPROVED="" ----------------------------------------- vice ----------------------------------------- it looks like build breaks because of the new gcc, I managed to add a patch from here http://lists.rpmfusion.org/pipermail/rpmfusion-commits/2009-April/004561.html and I applied the fixes from the default template http://github.com/Ponce/slackbuilds/commit/db3ddaa8211290fdbc19438dc680599be40508cc ----------------------------------------- diff --git a/system/vice/patches/vice-gcc-4.4.patch b/system/vice/patches/vice-gcc-4.4.patch new file mode 100644 index 0000000..505d736 --- /dev/null +++ b/system/vice/patches/vice-gcc-4.4.patch @@ -0,0 +1,11 @@ +--- src/arch/unix/joy.c ++++ src/arch/unix/joy.c +@@ -124,7 +124,7 @@ + #define JS_DATA_TYPE joystick + #define JS_RETURN sizeof(struct joystick) + int use_old_api=1; +-#elif ++#else + #error Unknown Joystick + #endif + diff --git a/system/vice/vice.SlackBuild b/system/vice/vice.SlackBuild index f29eece..ea01802 100644 --- a/system/vice/vice.SlackBuild +++ b/system/vice/vice.SlackBuild @@ -24,10 +24,19 @@ PRGNAM=vice VERSION=2.1 -ARCH=${ARCH:-i486} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} +# Automatically determine the architecture we're building on: +if [ -z "$ARCH" ]; then + case "$( uname -m )" in + i?86) ARCH=i486 ;; + arm*) ARCH=arm ;; + # Unless $ARCH is already set, use uname -m for all other archs: + *) ARCH=$( uname -m ) ;; + esac +fi + CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM @@ -41,7 +50,10 @@ elif [ "$ARCH" = "i686" ]; then LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" - LIBDIRSUFFIX=64 + LIBDIRSUFFIX="64" +else + SLKCFLAGS="-O2" + LIBDIRSUFFIX="" fi set -e # Exit on most errors @@ -66,6 +78,9 @@ patch -p1 <$CWD/patches/vice-fix-help.patch # Use /usr/lib64 on 64-bit Slackware [ "$ARCH" == "x86_64" ] && patch -p1 < $CWD/patches/vice-2.1-64bit.patch +# patch for gcc 4.4 +patch -p0 < $CWD/patches/vice-gcc-4.4.patch + CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ ----------------------------------------- From mauro.giachero at gmail.com Mon May 31 07:27:23 2010 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Mon, 31 May 2010 09:27:23 +0200 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt In-Reply-To: <20100531060614.GA14337@slack> References: <20100531060614.GA14337@slack> Message-ID: On Mon, May 31, 2010 at 8:06 AM, Andrew Antle wrote: > Hello - > Hello Andrew, > This is my first attempt at writing a SlackBuild script. If someone would > look it over to make sure I haven't screwed anything up, that would be > much appreciated. :) > > > #!/bin/sh > > # Slackware build script for SWI-Prolog > # > # Copyright 2010 Andrew Antle > # All rights reserved. > # > # Redistribution and use of this script, with or without modification, is > # permitted provided that the following conditions are met: > # > # 1. Redistributions of this script must retain the above copyright > # notice, this list of conditions and the following disclaimer. > # > # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR > IMPLIED > # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF > # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN > NO > # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, > # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED > TO, > # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR > PROFITS; > # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, > # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR > # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF > # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. > # > # 0.1 2010-05-08 > # 0.2 2010-05-31 > I don't think we usually keep this kind of version tracking. PRGNAM=swi-prolog > VERSION=${VERSION:-5.10.0} > ARCH=${ARCH:-i486} > ARCH isn't set this way any more in the latest template. > BUILD=${BUILD:-2} > This should be 1 in the script you'll submit > TAG=${TAG:-_SBo} > You miss the whole ARCH setting code here -- you'd better use the latest template when submitting scripts. > CWD=$(pwd) > TMP=${TMP:-/tmp/SBo} > PKG=$TMP/package-$PRGNAM > OUTPUT=${OUTPUT:-/tmp} > > # Default CFLAGS not set as configure works this out. Is this wrong? > If configure allows overriding its autodetected parameters with CFLAGS then yes, it's wrong. Of course unless there are strong reasons against overriding them (like huge performance drawbacks) > if [ "$ARCH" = "i486" ]; then > SLKCFLAGS="" > LIBDIRSUFFIX="" > elif [ "$ARCH" = "i686" ]; then > SLKCFLAGS="" > LIBDIRSUFFIX="" > elif [ "$ARCH" = "x86_64" ]; then > SLKCFLAGS="" > LIBDIRSUFFIX="64" > fi > This piece also misses something from the last template. > # Custom variable because source package name differs from what we're > # going to call it. > TARNAM=pl > > set -e > > rm -rf $PKG > mkdir -p $TMP $PKG $OUTPUT > cd $TMP > rm -rf $TARNAM-$VERSION > tar xvf $CWD/$TARNAM-$VERSION.tar.gz > cd $TARNAM-$VERSION > chown -R root:root . > find . \ > \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ > -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm > 400 \) \ > -exec chmod 644 {} \; > > CFLAGS="$SLKCFLAGS" \ > CXXFLAGS="$SLKCFLAGS" \ > ./configure \ > --prefix=/usr \ > --libdir=/usr/lib${LIBDIRSUFFIX} \ > --sysconfdir=/etc \ > --localstatedir=/var \ > --mandir=/usr/man \ > --docdir=/usr/doc/$PRGNAM-$VERSION \ > --build=$ARCH-slackware-linux \ > --with-world > > make > make install DESTDIR=$PKG > > # Strip binaries and libraries - this can be done with 'make install-strip' > # in many source trees, and that's usually acceptable if so, but if not, > # use this: > Drop this comment. > find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF > \ > | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true > > # Compress man pages > # If the man pages are installed to /usr/share/man instead, you'll need to > either > # add the --mandir=/usr/man flag to configure or move them manually after > the > # make install process is run. > This too. > find $PKG/usr/man -type f -exec gzip -9 {} \; > > mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION > cat $CWD/$PRGNAM.SlackBuild > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > > mkdir -p $PKG/install > cat $CWD/slack-desc > $PKG/install/slack-desc > > cd $PKG > /sbin/makepkg -l y -c n > $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} > I don't see other obvious things, but I haven't actually tried running the script. > Thanks, > You're welcome. > -- > Andrew Antle > -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From the_emmel at gmx.net Mon May 31 07:51:49 2010 From: the_emmel at gmx.net (emmel) Date: Mon, 31 May 2010 09:51:49 +0200 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt In-Reply-To: <20100531060614.GA14337@slack> References: <20100531060614.GA14337@slack> Message-ID: <20100531075149.GA2005@pollux.mlnet> On Mon, May 31, 2010 at 02:06:16AM -0400, Andrew Antle wrote: > Hello - > > This is my first attempt at writing a SlackBuild script. If someone would > look it over to make sure I haven't screwed anything up, that would be > much appreciated. :) > CFLAGS="$SLKCFLAGS" \ > CXXFLAGS="$SLKCFLAGS" \ > ./configure \ > --prefix=/usr \ > --libdir=/usr/lib${LIBDIRSUFFIX} \ > --sysconfdir=/etc \ > --localstatedir=/var \ > --mandir=/usr/man \ > --docdir=/usr/doc/$PRGNAM-$VERSION \ > --build=$ARCH-slackware-linux \ > --with-world > > make > make install DESTDIR=$PKG Actually, the preferred way to build swi-prolog ist using the build script. This should work: DESTDIR=$PKG ./build.templ --prefix=/usr I wrote a (non-standard - thus not comitted) build script a couple of months ago when I couldn't get gnu prolog to compile on current. That's the line I used. -- emmel GPG signed Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7 Certserver : hkp://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From andrew.antle at gmail.com Mon May 31 08:03:17 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Mon, 31 May 2010 04:03:17 -0400 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt In-Reply-To: References: <20100531060614.GA14337@slack> Message-ID: <20100531080311.GA4462@slack> On Mon, May 31, 2010 at 09:27:23AM +0200, Mauro Giachero wrote: > On Mon, May 31, 2010 at 8:06 AM, Andrew Antle wrote: > > > ARCH=${ARCH:-i486} > > ARCH isn't set this way any more in the latest template. > > > BUILD=${BUILD:-2} > > This should be 1 in the script you'll submit > > > TAG=${TAG:-_SBo} > > You miss the whole ARCH setting code here -- you'd better use the latest > template when submitting scripts. > > > CWD=$(pwd) > > TMP=${TMP:-/tmp/SBo} > > PKG=$TMP/package-$PRGNAM > > OUTPUT=${OUTPUT:-/tmp} > > > > # Default CFLAGS not set as configure works this out. Is this wrong? > > If configure allows overriding its autodetected parameters with CFLAGS then > yes, it's wrong. > Of course unless there are strong reasons against overriding them (like huge > performance drawbacks) > > > if [ "$ARCH" = "i486" ]; then > > SLKCFLAGS="" > > LIBDIRSUFFIX="" > > elif [ "$ARCH" = "i686" ]; then > > SLKCFLAGS="" > > LIBDIRSUFFIX="" > > elif [ "$ARCH" = "x86_64" ]; then > > SLKCFLAGS="" > > LIBDIRSUFFIX="64" > > fi > > This piece also misses something from the last template. > > > # Strip binaries and libraries - this can be done with 'make install-strip' > > # in many source trees, and that's usually acceptable if so, but if not, > > # use this: > > Drop this comment. > > > find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ > | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true > > > > # Compress man pages > > # If the man pages are installed to /usr/share/man instead, you'll need to > > either > > # add the --mandir=/usr/man flag to configure or move them manually after > > the > > # make install process is run. > > This too. > > > find $PKG/usr/man -type f -exec gzip -9 {} \; > > > > mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION > > cat $CWD/$PRGNAM.SlackBuild > > > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild > > > > mkdir -p $PKG/install > > cat $CWD/slack-desc > $PKG/install/slack-desc > > > > cd $PKG > > /sbin/makepkg -l y -c n > > $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} > > I don't see other obvious things, but I haven't actually tried running the > script. Hi Mauro - Thanks for the feedback. Here's a diff, and the revised SlackBuild is attached. $ diff -u swi-prolog.SlackBuild.orig swi-prolog.SlackBuild --- swi-prolog.SlackBuild.orig 2010-05-31 03:46:17.547816051 -0400 +++ swi-prolog.SlackBuild 2010-05-31 03:58:52.323700794 -0400 @@ -21,31 +21,37 @@ # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -# -# 0.1 2010-05-08 -# 0.2 2010-05-31 PRGNAM=swi-prolog VERSION=${VERSION:-5.10.0} -ARCH=${ARCH:-i486} -BUILD=${BUILD:-2} +BUILD=${BUILD:-1} TAG=${TAG:-_SBo} +if [ -z "$ARCH" ]; then + case "$( uname -m )" in + i?86) ARCH=i486 ;; + arm*) ARCH=arm ;; + *) ARCH=$( uname -m ) ;; + esac +fi + CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} -# Default CFLAGS not set as configure works this out. Is this wrong? if [ "$ARCH" = "i486" ]; then - SLKCFLAGS="" + SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then - SLKCFLAGS="" + SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then - SLKCFLAGS="" + SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" +else + SLKCFLAGS="-O2" + LIBDIRSUFFIX="" fi # Custom variable because source package name differs from what we're @@ -82,16 +88,9 @@ make make install DESTDIR=$PKG -# Strip binaries and libraries - this can be done with 'make install-strip' -# in many source trees, and that's usually acceptable if so, but if not, -# use this: find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true -# Compress man pages -# If the man pages are installed to /usr/share/man instead, you'll need to either -# add the --mandir=/usr/man flag to configure or move them manually after the -# make install process is run. find $PKG/usr/man -type f -exec gzip -9 {} \; mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION Thanks again, -- Andrew Antle -------------- next part -------------- #!/bin/sh # Slackware build script for SWI-Prolog # # Copyright 2010 Andrew Antle # All rights reserved. # # Redistribution and use of this script, with or without modification, is # permitted provided that the following conditions are met: # # 1. Redistributions of this script must retain the above copyright # notice, this list of conditions and the following disclaimer. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=swi-prolog VERSION=${VERSION:-5.10.0} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i486 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" else SLKCFLAGS="-O2" LIBDIRSUFFIX="" fi # Custom variable because source package name differs from what we're # going to call it. TARNAM=pl set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $TARNAM-$VERSION tar xvf $CWD/$TARNAM-$VERSION.tar.gz cd $TARNAM-$VERSION chown -R root:root . find . \ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --localstatedir=/var \ --mandir=/usr/man \ --docdir=/usr/doc/$PRGNAM-$VERSION \ --build=$ARCH-slackware-linux \ --with-world make make install DESTDIR=$PKG find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true find $PKG/usr/man -type f -exec gzip -9 {} \; mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} From ozan.turkyilmaz at gmail.com Mon May 31 08:38:15 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Mon, 31 May 2010 11:38:15 +0300 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt In-Reply-To: <20100531060614.GA14337@slack> References: <20100531060614.GA14337@slack> Message-ID: 2010/5/31 Andrew Antle : > Hello - > CFLAGS="$SLKCFLAGS" \ > CXXFLAGS="$SLKCFLAGS" \ > ./configure \ > ?--prefix=/usr \ > ?--libdir=/usr/lib${LIBDIRSUFFIX} \ > ?--sysconfdir=/etc \ > ?--localstatedir=/var \ > ?--mandir=/usr/man \ > ?--docdir=/usr/doc/$PRGNAM-$VERSION \ > ?--build=$ARCH-slackware-linux \ > ?--with-world if configure allows CFLAGS overrides, this would define them as empty, if you don't wan to override them, don't set them at all. however SLKCFLAGS are quiet sane and usually programmers remove dangerous optimizations in non-overrideble place. -- Ozan From miorimmax at gmail.com Mon May 31 16:25:51 2010 From: miorimmax at gmail.com (Max Miorim) Date: Mon, 31 May 2010 13:25:51 -0300 Subject: [Slackbuilds-users] Fix to SLiM Message-ID: Hi, The SlackBuild script for SLiM (a graphical login manager) goes through the compilation and package creation process just fine, but theres a problem with the resulting binary: it links against both libpng12 and libpng14 (Slackware 13.1 comes with both versions in the same package) and just dies, throwing the following at /var/log/slim.log: libpng warning: Application was compiled with png.h from libpng-1.4.2 libpng warning: Application is running with png.c from libpng-1.2.43 libpng error: Incompatible libpng version in application and library At first, I modified its Makefile to use libpng12 only, it worked but I guess it'd break compatibility with previous Slackware versions... So, I tried with libpng14 (using -I/usr/include/libpng and -lpng - without any version suffix, libpng14 is the /default/ in 13.1) and it's working as intended again: diff --git a/slim-1.3.1-use_only_one_version_of_libpng.patch b/slim-1.3.1-use_only_one_version_of_libpng.patch new file mode 100644 index 0000000..511d68e --- /dev/null +++ b/slim-1.3.1-use_only_one_version_of_libpng.patch @@ -0,0 +1,16 @@ +diff --git a/Makefile b/Makefile +index f7d3d2d..7fea3db 100644 +--- a/Makefile ++++ b/Makefile +@@ -5,9 +5,9 @@ + ####################################################### + CXX=/usr/bin/g++ + CC=/usr/bin/gcc +-CFLAGS=-Wall -I. -I/usr/include/freetype2 -I/usr/include/freetype2/config -I/usr/include/libpng12 -I/usr/include ++CFLAGS=-Wall -I. -I/usr/include/freetype2 -I/usr/include/freetype2/config -I/usr/include/libpng -I/usr/include + CXXFLAGS=$(CFLAGS) +-LDFLAGS=-lXft -lX11 -lfreetype -lXrender -lfontconfig -lpng12 -lz -lm -lcrypt -lXmu -lpng -ljpeg ++LDFLAGS=-lXft -lX11 -lfreetype -lXrender -lfontconfig -lz -lm -lcrypt -lXmu -lpng -ljpeg + CUSTOM=-DHAVE_SHADOW + ifdef USE_PAM + LDFLAGS+= -lpam diff --git a/slim.SlackBuild b/slim.SlackBuild index 4b33bb4..6f58821 100644 --- a/slim.SlackBuild +++ b/slim.SlackBuild @@ -72,6 +72,9 @@ patch -p0 < $CWD/slim.conf.patch # Include stdio.h for -current (but harmless on 13.0) patch -p1 < $CWD/slim-1.3.1-include_stdio_h.patch +# Use the current version of libpng instead of linking against both libpng12 and libpng14 +patch -p1 < $CWD/slim-1.3.1-use_only_one_version_of_libpng.patch + make \ CFLAGS+="$SLKCFLAGS" \ USE_PAM=${USE_PAM} Regards, Max From andrew.antle at gmail.com Mon May 31 18:10:15 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Mon, 31 May 2010 14:10:15 -0400 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt In-Reply-To: <20100531075149.GA2005@pollux.mlnet> References: <20100531060614.GA14337@slack> <20100531075149.GA2005@pollux.mlnet> Message-ID: <20100531181013.GA29177@slack> On Mon, May 31, 2010 at 09:51:49AM +0200, emmel wrote: > On Mon, May 31, 2010 at 02:06:16AM -0400, Andrew Antle wrote: > > CFLAGS="$SLKCFLAGS" \ > > CXXFLAGS="$SLKCFLAGS" \ > > ./configure \ > > --prefix=/usr \ > > --libdir=/usr/lib${LIBDIRSUFFIX} \ > > --sysconfdir=/etc \ > > --localstatedir=/var \ > > --mandir=/usr/man \ > > --docdir=/usr/doc/$PRGNAM-$VERSION \ > > --build=$ARCH-slackware-linux \ > > --with-world > > > > make > > make install DESTDIR=$PKG > > Actually, the preferred way to build swi-prolog ist using the build > script. This should work: > > DESTDIR=$PKG ./build.templ --prefix=/usr > > I wrote a (non-standard - thus not comitted) build script a couple of > months ago when I couldn't get gnu prolog to compile on current. That's > the line I used. Thanks, emmel. I've built it both ways, and haven't noticed a difference, though. I figured I'd go with configure as it's more standard with other SlackBuilds. -- Andrew Antle From andrew.antle at gmail.com Mon May 31 18:15:58 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Mon, 31 May 2010 14:15:58 -0400 Subject: [Slackbuilds-users] swi-prolog SlackBuild - First attempt In-Reply-To: References: <20100531060614.GA14337@slack> Message-ID: <20100531181556.GB29177@slack> On Mon, May 31, 2010 at 11:38:15AM +0300, Ozan T?rky?lmaz wrote: > 2010/5/31 Andrew Antle : > > CFLAGS="$SLKCFLAGS" \ > > CXXFLAGS="$SLKCFLAGS" \ > > ./configure \ > > ?--prefix=/usr \ > > ?--libdir=/usr/lib${LIBDIRSUFFIX} \ > > ?--sysconfdir=/etc \ > > ?--localstatedir=/var \ > > ?--mandir=/usr/man \ > > ?--docdir=/usr/doc/$PRGNAM-$VERSION \ > > ?--build=$ARCH-slackware-linux \ > > ?--with-world > > if configure allows CFLAGS overrides, this would define them as empty, > if you don't wan to override them, don't set them at all. however SLKCFLAGS > are quiet sane and usually programmers remove dangerous optimizations in > non-overrideble place. Thanks, Ozan. I've commented out the FLAGS section; if people want to set them, they can un-comment it. I've set up a git repo at http://github.com/antlechrist/swi-prolog Patches gratefully received. :) -- Andrew Antle