From rworkman at slackbuilds.org Thu May 1 01:12:28 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 1 May 2008 01:12:28 +0000 Subject: [Slackbuilds-users] Critical update suggestions for 12.1 repository Message-ID: <20080501011228.GA29167@slackbuilds.org> Greetings, everyone: We are in the process of (hopefully) finalizing everything for the upcoming Slackware 12.1 release, and while we think we've got most of the major issues handled, there are a few things that might still need to be addressed. First, we have a short list of things in the 12.0 tree that won't build on -current, so if the maintainers of these (or anyone else, if so inclined) would like to investigate them and try to find a solution or update the script for a newer version, we'll try to get them included if you get them to us soon enough. See the end of this mail for a list. Second, if anyone is aware of any *critical* updates that are needed to anything, drop us a note in this thread. Note that this is NOT for routine version bumps (those can be handled after the tree opens); instead, this is for things that have security fixes in newer versions, scripts in which we patch around a problem for -current but newer version eliminates the need to patch, and other similar issues. The following items should be ignored - they have already been handled by us or others (in no particular order): all of the perl stuff (to use vendor_perl), matchbox-panel, brutalchess, wormux, inkscape, OpenAL, picasa, exo-notify, libexif-gtk, libgdiplus, wxGTK, transcode, synaptics, xorg-server-xephyr, and perhaps a few others that caught version bumps but weren't noted as problematic before. Again, requests for routine version updates will be ignored (and perhaps ridiculed) ;-) Here's the list of things that either won't build on -current (for whatever reason) or we don't have valid download links for the source code and nobody was able to find time (or perhaps interest) in updating: baghira, erlang-otp, zaptel, rtl-wifi, stardict, google-desktop, moodin, webpy, python-levenshtein, cmus, ekiga, and skype Thanks in advance, Robby Workman --for the SlackBuilds.org Team From cnguyenminhtan at free.fr Thu May 1 07:59:10 2008 From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr) Date: Thu, 01 May 2008 09:59:10 +0200 Subject: [Slackbuilds-users] Critical update suggestions for 12.1 repository In-Reply-To: <20080501011228.GA29167@slackbuilds.org> References: <20080501011228.GA29167@slackbuilds.org> Message-ID: <1209628750.4819784e8d151@imp.free.fr> Selon Robby Workman : > Here's the list of things that either won't build on -current (for whatever > reason) or we don't have valid download links for the source code and > nobody was able to find time (or perhaps interest) in updating: > baghira, erlang-otp, zaptel, rtl-wifi, stardict, google-desktop, moodin, > webpy, python-levenshtein, cmus, ekiga, and skype > Hello, I submitted the Slackbuild for rtl-wifi. My plan is to check again after my upgrade to 12.1 (I do not use -current). If the version I submitted doesn't work, I'll try other versions available on the site. I'll let you know and re-submit an updated Slackbuild when I'm done. Regards, Christophe Nguyen From mauro.giachero at gmail.com Thu May 1 09:15:08 2008 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 1 May 2008 11:15:08 +0200 Subject: [Slackbuilds-users] rtl-wifi on -current [was: Critical update suggestions for 12.1 repository] Message-ID: On Thu, May 1, 2008 at 9:59 AM, wrote: > I submitted the Slackbuild for rtl-wifi. My plan is to check again after > my > upgrade to 12.1 (I do not use -current). > > If the version I submitted doesn't work, I'll try other versions available > on > the site. Trying to build a working driver I came across this: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/31857/comments/34 While I still can't confirm it actually works, it builds with the current script and, once modprobed, I'm able to see the list of available wireless networks. There's a bunch of scary messages in dmesg about missing symbols, but I haven't investigated them. With best regards Mauro -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnguyenminhtan at free.fr Thu May 1 10:07:48 2008 From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr) Date: Thu, 01 May 2008 12:07:48 +0200 Subject: [Slackbuilds-users] rtl-wifi on -current [was: Critical update suggestions for 12.1 repository] In-Reply-To: References: Message-ID: <1209636468.481996745a5ef@imp.free.fr> Selon Mauro Giachero : > > Trying to build a working driver I came across this: > https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/31857/comments/34 > While I still can't confirm it actually works, it builds with the current > script and, once modprobed, I'm able to see the list of available wireless > networks. There's a bunch of scary messages in dmesg about missing symbols, > but I haven't investigated them. > > With best regards > Mauro > Thank you for the link. Indeed I found the same file in the rtl-wifi forum. I'll give it a try. Regards, Christophe From neobug at tornado.ktu.lt Thu May 1 10:08:23 2008 From: neobug at tornado.ktu.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 1 May 2008 13:08:23 +0300 Subject: [Slackbuilds-users] Critical update suggestions for 12.1 repository In-Reply-To: <20080501011228.GA29167@slackbuilds.org> References: <20080501011228.GA29167@slackbuilds.org> Message-ID: <20080501100823.GA2253@kiras> On Thu, 2008-05-01 at 01:12:28 +0000, Robby Workman wrote: > Second, if anyone is aware of any *critical* updates that are needed > to anything, drop us a note in this thread. Note that this is NOT > for routine version bumps (those can be handled after the tree opens); > instead, this is for things that have security fixes in newer versions, > scripts in which we patch around a problem for -current but newer > version eliminates the need to patch, and other similar issues. You could update Opera to 9.27, because it's a security update: http://www.opera.com/docs/changelogs/linux/927/ -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From xgizzmo at slackbuilds.org Thu May 1 11:41:41 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Thu, 1 May 2008 07:41:41 -0400 Subject: [Slackbuilds-users] =?utf-8?q?Critical_update_suggestions_for_12?= =?utf-8?q?=2E1=09repository?= In-Reply-To: <20080501100823.GA2253@kiras> References: <20080501011228.GA29167@slackbuilds.org> <20080501100823.GA2253@kiras> Message-ID: <200805010741.41736.xgizzmo@slackbuilds.org> On Thursday 01 May 2008 06:08:23 Audrius Ka?ukauskas wrote: > You could update Opera to 9.27, because it's a security update: Already done. David Somero From rworkman at slackbuilds.org Thu May 1 13:17:16 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 01 May 2008 08:17:16 -0500 Subject: [Slackbuilds-users] Critical update suggestions for 12.1 repository In-Reply-To: <200805010741.41736.xgizzmo@slackbuilds.org> References: <20080501011228.GA29167@slackbuilds.org> <20080501100823.GA2253@kiras> <200805010741.41736.xgizzmo@slackbuilds.org> Message-ID: <4819C2DC.2060000@slackbuilds.org> xgizzmo at slackbuilds.org wrote: > On Thursday 01 May 2008 06:08:23 Audrius Ka?ukauskas wrote: >> You could update Opera to 9.27, because it's a security update: > > Already done. Hmm, how did I forget that?? Oh well. :) -RW From hba.nihilismus at gmail.com Thu May 1 18:05:17 2008 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Thu, 1 May 2008 13:05:17 -0500 Subject: [Slackbuilds-users] Critical update suggestions for 12.1 repository In-Reply-To: <20080501011228.GA29167@slackbuilds.org> References: <20080501011228.GA29167@slackbuilds.org> Message-ID: <39be090805011105i1e1d399ep190c876c1d94817f@mail.gmail.com> About baghira, please remove it from the repository as it's quite old(it's not in development anymore) and i can't find a patch to make it work in -current. About cmus, these are the new values you should use in its info file: HOMEPAGE="http://cmus.sourceforge.net/" DOWNLOAD="http://mirror.greaterscope.net/cmus/cmus-2.2.0.tar.bz2" MD5SUM="7a9895ecfc10cd16577c73051436962f" 2008/4/30 Robby Workman : > Greetings, everyone: > > We are in the process of (hopefully) finalizing everything for the > upcoming Slackware 12.1 release, and while we think we've got most > of the major issues handled, there are a few things that might still > need to be addressed. > > First, we have a short list of things in the 12.0 tree that won't > build on -current, so if the maintainers of these (or anyone else, > if so inclined) would like to investigate them and try to find a > solution or update the script for a newer version, we'll try to > get them included if you get them to us soon enough. See the end > of this mail for a list. > > Second, if anyone is aware of any *critical* updates that are needed > to anything, drop us a note in this thread. Note that this is NOT > for routine version bumps (those can be handled after the tree opens); > instead, this is for things that have security fixes in newer versions, > scripts in which we patch around a problem for -current but newer > version eliminates the need to patch, and other similar issues. > The following items should be ignored - they have already been handled > by us or others (in no particular order): > all of the perl stuff (to use vendor_perl), matchbox-panel, brutalchess, > wormux, inkscape, OpenAL, picasa, exo-notify, libexif-gtk, libgdiplus, > wxGTK, transcode, synaptics, xorg-server-xephyr, and perhaps a few others > that caught version bumps but weren't noted as problematic before. > > Again, requests for routine version updates will be ignored (and perhaps > ridiculed) ;-) > > Here's the list of things that either won't build on -current (for whatever > reason) or we don't have valid download links for the source code and > nobody was able to find time (or perhaps interest) in updating: > baghira, erlang-otp, zaptel, rtl-wifi, stardict, google-desktop, moodin, > webpy, python-levenshtein, cmus, ekiga, and skype > > Thanks in advance, > Robby Workman > --for the SlackBuilds.org Team > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > From rworkman at slackbuilds.org Thu May 1 20:17:34 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 01 May 2008 15:17:34 -0500 Subject: [Slackbuilds-users] Critical update suggestions for 12.1 repository In-Reply-To: <39be090805011105i1e1d399ep190c876c1d94817f@mail.gmail.com> References: <20080501011228.GA29167@slackbuilds.org> <39be090805011105i1e1d399ep190c876c1d94817f@mail.gmail.com> Message-ID: <481A255E.1010509@slackbuilds.org> Antonio Hern?ndez Blas wrote: > About baghira, please remove it from the repository as it's quite > old(it's not in development anymore) and i can't find a patch to make > it work in -current. > > About cmus, these are the new values you should use in its info file: > HOMEPAGE="http://cmus.sourceforge.net/" > DOWNLOAD="http://mirror.greaterscope.net/cmus/cmus-2.2.0.tar.bz2" > MD5SUM="7a9895ecfc10cd16577c73051436962f" Got it; thanks! -RW From rworkman at slackbuilds.org Thu May 1 20:18:54 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 01 May 2008 15:18:54 -0500 Subject: [Slackbuilds-users] Add javascript support to elinks In-Reply-To: <48164BD5.9090608@lip6.fr> References: <48164BD5.9090608@lip6.fr> Message-ID: <481A25AE.50002@slackbuilds.org> Mathieu Bouillaguet wrote: > Hi, > > It is possible to enable javascript in elinks without any additional > dependency than the stock seamonkey package. All you have to do is to > pass CFLAGS='-L/usr/lib/seamonkey/' > CPPFLAGS='-I/usr/include/seamonkey/js' to configure and make to find the > spidermonkey headers and library. > > It is quite useful since with javascript enabled I can log in my gmail > account or connect to my online banking account. > > I've attached the patch against the current slackbuild. I'm CC'ing the maintainer of this. Brian, I don't know if you're on the list or not, but if not and you need the patch, let me know. -RW From rworkman at slackbuilds.org Fri May 2 22:27:36 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 2 May 2008 22:27:36 +0000 Subject: [Slackbuilds-users] Slackware 12.1 Released and 12.1 Tree is Open Message-ID: <20080502222736.GA17082@slackbuilds.org> Greetings! In case you haven't noticed, 12.1 is out and our submission form is open again. Enjoy! :) -RW From listreader at lupulin.net Fri May 2 22:50:46 2008 From: listreader at lupulin.net (paul wisehart) Date: Fri, 02 May 2008 18:50:46 -0400 Subject: [Slackbuilds-users] Problem submitting slackbuild In-Reply-To: <20080502222736.GA17082@slackbuilds.org> References: <20080502222736.GA17082@slackbuilds.org> Message-ID: <481B9AC6.8090608@lupulin.net> Robby Workman wrote: > In case you haven't noticed, 12.1 is out and our > submission form is open again. Enjoy! :) I can't get my file to upload thru the submission form. I tried detachtty.tar.gz and just detachtty.tar "Upload failed, could not find: detachtty/detachtty.info" I swear the file is there ? (the following is the exploded version of the file i tried to upload.): ls -l * -rw-r--r-- 1 wise users 10240 2008-05-02 18:44 detachtty.tar detachtty: total 16 -rw-r--r-- 1 wise users 345 2008-05-02 18:39 README -rw-r--r-- 1 wise users 1977 2008-05-02 18:39 detachtty.SlackBuild -rw-r--r-- 1 wise users 254 2008-05-02 18:39 detachtty.info -rw-r--r-- 1 wise users 468 2008-05-02 18:39 slack-desc any ideas? -- paul w From andrew.david.45 at gmail.com Fri May 2 23:08:11 2008 From: andrew.david.45 at gmail.com (andrew) Date: Sat, 3 May 2008 09:08:11 +1000 Subject: [Slackbuilds-users] leafnode write-up Message-ID: <20080502230811.GA29917@ilium.andrews-corner.org> Hi, Is this a good time to ask if the walk-through I wrote for the Leafnode-2 slackbuild script: http://www.andrews-corner.org/leafnode.html is suitable to add next to Garry Knight's page on the README? BTW good to see the big mention of slackbuilds.org in the announcement for 12.1 :-) Andrew -- http://www.andrews-corner.org From chess at chessgriffin.com Fri May 2 23:21:34 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 2 May 2008 19:21:34 -0400 Subject: [Slackbuilds-users] Problem submitting slackbuild In-Reply-To: <481B9AC6.8090608@lupulin.net> References: <20080502222736.GA17082@slackbuilds.org> <481B9AC6.8090608@lupulin.net> Message-ID: <20080502192134.08691525@slackhost.localdomain> On Fri, 02 May 2008 18:50:46 -0400 paul wisehart wrote: > Robby Workman wrote: > > In case you haven't noticed, 12.1 is out and our > > submission form is open again. Enjoy! :) > > I can't get my file to upload thru the submission form. > > I tried detachtty.tar.gz and just detachtty.tar > > "Upload failed, could not find: detachtty/detachtty.info" > > I swear the file is there ? > > (the following is the exploded version of the file i tried to > upload.): > > ls -l * > -rw-r--r-- 1 wise users 10240 2008-05-02 18:44 detachtty.tar > > detachtty: > total 16 > -rw-r--r-- 1 wise users 345 2008-05-02 18:39 README > -rw-r--r-- 1 wise users 1977 2008-05-02 18:39 detachtty.SlackBuild > -rw-r--r-- 1 wise users 254 2008-05-02 18:39 detachtty.info > -rw-r--r-- 1 wise users 468 2008-05-02 18:39 slack-desc > > > any ideas? > > -- > paul w I just had the same problem with a new upload. -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From rworkman at slackbuilds.org Fri May 2 23:30:41 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 02 May 2008 18:30:41 -0500 Subject: [Slackbuilds-users] Problem submitting slackbuild In-Reply-To: <481B9AC6.8090608@lupulin.net> References: <20080502222736.GA17082@slackbuilds.org> <481B9AC6.8090608@lupulin.net> Message-ID: <481BA421.5050707@slackbuilds.org> paul wisehart wrote: > Robby Workman wrote: >> In case you haven't noticed, 12.1 is out and our >> submission form is open again. Enjoy! :) > > I can't get my file to upload thru the submission form. > > I tried detachtty.tar.gz and just detachtty.tar > > "Upload failed, could not find: detachtty/detachtty.info" Fixed. We forgot one thing. Hopefully *only* one. :) -RW From rworkman at slackbuilds.org Fri May 2 23:32:11 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 02 May 2008 18:32:11 -0500 Subject: [Slackbuilds-users] leafnode write-up In-Reply-To: <20080502230811.GA29917@ilium.andrews-corner.org> References: <20080502230811.GA29917@ilium.andrews-corner.org> Message-ID: <481BA47B.9020507@slackbuilds.org> andrew wrote: > Is this a good time to ask if the walk-through I wrote for the > Leafnode-2 slackbuild script: > > http://www.andrews-corner.org/leafnode.html > > is suitable to add next to Garry Knight's page on the README? Definitely. In fact, I'd recommend putting your guide first, since it's a "quick and dirty get this working *now*" thing (note that my use of "dirty" doesn't mean bad) while Garry's is much more detailed (while most of the details aren't needed by most people). > BTW good to see the big mention of slackbuilds.org in the announcement > for 12.1 :-) Indeed it was. :) -RW From chess at chessgriffin.com Sat May 3 00:16:59 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 2 May 2008 20:16:59 -0400 Subject: [Slackbuilds-users] Problem submitting slackbuild In-Reply-To: <481BA421.5050707@slackbuilds.org> References: <20080502222736.GA17082@slackbuilds.org> <481B9AC6.8090608@lupulin.net> <481BA421.5050707@slackbuilds.org> Message-ID: <20080502201659.41403f46@slackhost.localdomain> On Fri, 02 May 2008 18:30:41 -0500 Robby Workman wrote: > paul wisehart wrote: > > Robby Workman wrote: > >> In case you haven't noticed, 12.1 is out and our > >> submission form is open again. Enjoy! :) > > > > I can't get my file to upload thru the submission form. > > > > I tried detachtty.tar.gz and just detachtty.tar > > > > "Upload failed, could not find: detachtty/detachtty.info" > > > Fixed. We forgot one thing. Hopefully *only* one. :) > > -RW > Working now. Warning: multiple incoming. :-) -- Chess Griffin GPG Public Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From slack at ktabic.co.uk Sat May 3 18:58:09 2008 From: slack at ktabic.co.uk (ktabic) Date: Sat, 3 May 2008 18:58:09 +0000 Subject: [Slackbuilds-users] SBo 12.1 download errors Message-ID: <20080503185809.2e196686@griffin.mythic.magic> During a mass compilation session today, I've found the following errors in .info files pysetup: The version number in http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c86.tar.gz is wrong and should be: http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c8.tar.gz KDESvn have moved their downloads links http://kdesvn.alwins-world.de/downloads/kdesvn-0.14.2.tar.bz2 has changed to: http://kdesvn.alwins-world.de/trac.fcgi/downloads/kdesvn-0.14.2.tar.bz2 Rod From frederic.touboul at gmail.com Sun May 4 12:19:15 2008 From: frederic.touboul at gmail.com (Frederic Touboul) Date: Sun, 04 May 2008 14:19:15 +0200 Subject: [Slackbuilds-users] rtl-wifi on -current [was: Critical update suggestions for 12.1 repository] In-Reply-To: <1209636468.481996745a5ef@imp.free.fr> References: <1209636468.481996745a5ef@imp.free.fr> Message-ID: <481DA9C3.5020609@gmail.com> Hello, Note that as of version 2.6.25, the rtl-wifi driver is officially part of the kernel. Not really relevant for Slackware 12.1, but I thought people might be interested. I have it working on my laptop running Slack 11.0 right now, without any problem so far. Regards, Frederic. cnguyenminhtan at free.fr wrote: > Selon Mauro Giachero : > >> Trying to build a working driver I came across this: >> > https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/31857/comments/34 >> While I still can't confirm it actually works, it builds with the current >> script and, once modprobed, I'm able to see the list of available wireless >> networks. There's a bunch of scary messages in dmesg about missing symbols, >> but I haven't investigated them. >> >> With best regards >> Mauro >> > > Thank you for the link. Indeed I found the same file in the rtl-wifi forum. I'll > give it a try. > > Regards, > > Christophe > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > From pc_warner at yahoo.com Sun May 4 18:28:55 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sun, 4 May 2008 11:28:55 -0700 (PDT) Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms Message-ID: <61783.89212.qm@web57707.mail.re3.yahoo.com> The 12.1 SlackBuild scripts don't have execute permissions anymore. I don't think this was intentional, so I thought I'd mention it. --phil --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pc_warner at yahoo.com Sun May 4 18:40:13 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sun, 4 May 2008 11:40:13 -0700 (PDT) Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds Message-ID: <327535.21231.qm@web57706.mail.re3.yahoo.com> I think there should be something in the slackBuilds that says what slackware version the script was designed for. I suggest specifying the slackware version in the .info file and the .slackBuild file. This can be useful for two purposes. One, it can help you to use the right script for a certain slackware version (some differ in more than just subtle ways). Second, it is also possible that having the version stated can help you determine what slackware version the package was built for. This is possible if the slackware version is mentioned in the .slackBuild file, as it is included as a part of every SBo package. So, to determine what version of slackware the SBo package is intended for, you can just look at that file in the package. --phil --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From abrouwers at gmail.com Sun May 4 19:08:08 2008 From: abrouwers at gmail.com (Andrew Brouwers) Date: Sun, 4 May 2008 15:08:08 -0400 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <327535.21231.qm@web57706.mail.re3.yahoo.com> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> Message-ID: <196c22970805041208v59f02db5q1dacbf6cb0371fe9@mail.gmail.com> Hi Phil, What's the purpose, then, of segregating the repo's on slackbuilds.org? That's the reason why there are separate paths for different slackware versions (and why not all scripts are available in each of them). Andrew On Sun, May 4, 2008 at 2:40 PM, Phillip Warner wrote: > I think there should be something in the slackBuilds that says what > slackware version the script was designed for. I suggest specifying the > slackware version in the .info file and the .slackBuild file. > > This can be useful for two purposes. One, it can help you to use the right > script for a certain slackware version (some differ in more than just subtle > ways). Second, it is also possible that having the version stated can > help you determine what slackware version the package was built for. This > is possible if the slackware version is mentioned in the .slackBuild file, > as it is included as a part of every SBo package. So, to determine what > version of slackware the SBo package is intended for, you can just look at > that file in the package. > > --phil > > > ________________________________ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. > > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > From me at alkos333.net Sun May 4 19:11:17 2008 From: me at alkos333.net (alkos333) Date: Sun, 4 May 2008 14:11:17 -0500 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <196c22970805041208v59f02db5q1dacbf6cb0371fe9@mail.gmail.com> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <196c22970805041208v59f02db5q1dacbf6cb0371fe9@mail.gmail.com> Message-ID: Having a version number associated with a script would be helpful if you didn't have access to SBo repo, or a mirror. On Sun, May 4, 2008 at 2:08 PM, Andrew Brouwers wrote: > Hi Phil, > > What's the purpose, then, of segregating the repo's on > slackbuilds.org? That's the reason why there are separate paths for > different slackware versions (and why not all scripts are available in > each of them). > > Andrew > > > > On Sun, May 4, 2008 at 2:40 PM, Phillip Warner wrote: > > I think there should be something in the slackBuilds that says what > > slackware version the script was designed for. I suggest specifying the > > slackware version in the .info file and the .slackBuild file. > > > > This can be useful for two purposes. One, it can help you to use the right > > script for a certain slackware version (some differ in more than just subtle > > ways). Second, it is also possible that having the version stated can > > help you determine what slackware version the package was built for. This > > is possible if the slackware version is mentioned in the .slackBuild file, > > as it is included as a part of every SBo package. So, to determine what > > version of slackware the SBo package is intended for, you can just look at > > that file in the package. > > > > --phil > > > > > > ________________________________ > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > > now. > > > > > > _______________________________________________ > > Slackbuilds-users mailing list > > Slackbuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > > Please read the FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > From squadronguns at gmail.com Sun May 4 21:25:16 2008 From: squadronguns at gmail.com (WS Grant) Date: Sun, 4 May 2008 14:25:16 -0700 Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms In-Reply-To: <61783.89212.qm@web57707.mail.re3.yahoo.com> References: <61783.89212.qm@web57707.mail.re3.yahoo.com> Message-ID: I downloaded 80 SlackBuilds and about 1/2 of them I had to chmod +x I don't think it is a requirement by the package builder to make it executable although it does save the end user a few extra keystrokes. Step 3 in the How To says "If necessary, make the script executable with chmod and then run the script:" On Sun, May 4, 2008 at 11:28 AM, Phillip Warner wrote: > The 12.1 SlackBuild scripts don't have execute permissions anymore. I don't think this was intentional, so I thought I'd mention it. > > --phil > > > > ________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > -- Wade S Grant USMC, Retired From hba.nihilismus at gmail.com Sun May 4 23:20:58 2008 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sun, 4 May 2008 18:20:58 -0500 Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms In-Reply-To: <61783.89212.qm@web57707.mail.re3.yahoo.com> References: <61783.89212.qm@web57707.mail.re3.yahoo.com> Message-ID: <39be090805041620s153a8b75ge844744aec915a58@mail.gmail.com> You can still use "sh $PRGNAM.SlackBuild" to execute it ;) 2008/5/4 Phillip Warner : > The 12.1 SlackBuild scripts don't have execute permissions anymore. I don't > think this was intentional, so I thought I'd mention it. > > --phil > > > ________________________________ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > From klein.rfk at gmail.com Mon May 5 13:11:15 2008 From: klein.rfk at gmail.com (Ricardo Klein) Date: Mon, 5 May 2008 10:11:15 -0300 Subject: [Slackbuilds-users] eclipse.Slackbuild Message-ID: Hi... I dont know if that is an error, but.......sendin to you.... in eclipse.Slackbuild have this: # Add a script to run eclipse in /usr/bin mkdir -p $PKG/usr/bin cat $CWD/eclipse > $PKG/usr/bin/eclipse chmod 0755 $PKG/usr/bin/eclipse But, only works for me if I put + "/eclipse" like that: # Add a script to run eclipse in /usr/bin mkdir -p $PKG/usr/bin cat $CWD/eclipse*/eclipse* > $PKG/usr/bin/eclipse chmod 0755 $PKG/usr/bin/eclipse If thats is not an Script error, I do something wrong? Thanx for attention, and I'm happy to be able to help ps.: Sorry for English errors, I'm Brazilian, and my English is not the BEST one hehe.... -- Att... Ricardo Felipe Klein "I think of PHP very much like I think of chess: It's very easy to learn, but incredibly difficult to truly master." John Coggeshall (Senior Member of Zend Technologies' Global Services Group) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauro.giachero at gmail.com Mon May 5 14:08:04 2008 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Mon, 5 May 2008 16:08:04 +0200 Subject: [Slackbuilds-users] eclipse.Slackbuild In-Reply-To: References: Message-ID: On Mon, May 5, 2008 at 3:11 PM, Ricardo Klein wrote: > Hi... > > I dont know if that is an error, but.......sendin to you.... > > in eclipse.Slackbuild have this: > > # Add a script to run eclipse in /usr/bin > mkdir -p $PKG/usr/bin > cat $CWD/eclipse > $PKG/usr/bin/eclipse > > chmod 0755 $PKG/usr/bin/eclipse > > But, only works for me if I put + "/eclipse" like that: > > # Add a script to run eclipse in /usr/bin > mkdir -p $PKG/usr/bin > cat $CWD/eclipse*/eclipse* > $PKG/usr/bin/eclipse > > chmod 0755 $PKG/usr/bin/eclipse > > > > If thats is not an Script error, I do something wrong? > Apparently you are starting the script from the wrong folder, i.e. this way: root at kappa:/tmp# ls eclipse-SDK-3.3-linux-gtk.tar.gz eclipse.tar.gz root at kappa:/tmp# tar xf eclipse.tar.gz root at kappa:/tmp# sh eclipse/eclipse.SlackBuild You should extract eclipse.tar.gz, put the source tarball in the folder it creates, and start the script from there: jack at kappa:/tmp$ tar xf eclipse.tar.gz jack at kappa:/tmp$ cd eclipse jack at kappa:/tmp/eclipse$ mv *[source folder]*/eclipse-SDK-3.3-linux-gtk.tar.gz . jack at kappa:/tmp/eclipse$ ls README eclipse eclipse.SlackBuild eclipse.info doinst.sh eclipse-SDK-3.3-linux-gtk.tar.gz eclipse.desktop slack-desc jack at kappa:/tmp/eclipse$ su *[root password]* root at kappa:/tmp/eclipse# sh ./eclipse.SlackBuild With best regards M G -------------- next part -------------- An HTML attachment was scrubbed... URL: From pc_warner at yahoo.com Mon May 5 15:17:28 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Mon, 5 May 2008 08:17:28 -0700 (PDT) Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: Message-ID: <259667.59882.qm@web57701.mail.re3.yahoo.com> Even if you do have access to the repo it would be quicker to simply check the .info or .slackBuild file to see what slackware version it is for instead of comparing it to what is in the repo. Either that, or people would just download a fresh copy just to be sure (sometimes the program version is the same in different repos), but that could waste bandwith. The whole point is that if you have a folder full of slackBuilds, what version are they for? Say you have a package you want to install that was built with a slackBuild. What version was it built for? Having the slackware version information would be helpful in these cases. --phil Message: 4 Date: Sun, 4 May 2008 14:11:17 -0500 From: alkos333 Subject: Re: [Slackbuilds-users] specifying slackware version in the slackBuilds To: "SlackBuilds.org Users List" Message-ID: Content-Type: text/plain; charset=UTF-8 Having a version number associated with a script would be helpful if you didn't have access to SBo repo, or a mirror. On Sun, May 4, 2008 at 2:08 PM, Andrew Brouwers wrote: > Hi Phil, > > What's the purpose, then, of segregating the repo's on > slackbuilds.org? That's the reason why there are separate paths for > different slackware versions (and why not all scripts are available in > each of them). > > Andrew > > > > On Sun, May 4, 2008 at 2:40 PM, Phillip Warner wrote: > > I think there should be something in the slackBuilds that says what > > slackware version the script was designed for. I suggest specifying the > > slackware version in the .info file and the .slackBuild file. > > > > This can be useful for two purposes. One, it can help you to use the right > > script for a certain slackware version (some differ in more than just subtle > > ways). Second, it is also possible that having the version stated can > > help you determine what slackware version the package was built for. This > > is possible if the slackware version is mentioned in the .slackBuild file, > > as it is included as a part of every SBo package. So, to determine what > > version of slackware the SBo package is intended for, you can just look at > > that file in the package. > > > > --phil > > > > > > ________________________________ > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > > now. > > > > > > _______________________________________________ > > Slackbuilds-users mailing list > > Slackbuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > > Please read the FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > ------------------------------ --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pc_warner at yahoo.com Mon May 5 15:28:04 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Mon, 5 May 2008 08:28:04 -0700 (PDT) Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms In-Reply-To: Message-ID: <174554.72387.qm@web57708.mail.re3.yahoo.com> I know it isn't a requirement, I know what's in the HowTo, and I know how to use chmod and sh. Personally, I could care less whether or not the execute perms are there because if they aren't I just use sh. The only reason I mentioned it is because there seemed to be some previous effort in getting them all to have execute perms in the 12.0 repo. I thought the consistency was good, and it is simple to change the files to keep it. --phil Message: 5 Date: Sun, 4 May 2008 14:25:16 -0700 From: "WS Grant" Subject: Re: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms To: "SlackBuilds.org Users List" Message-ID: Content-Type: text/plain; charset=ISO-8859-1 I downloaded 80 SlackBuilds and about 1/2 of them I had to chmod +x I don't think it is a requirement by the package builder to make it executable although it does save the end user a few extra keystrokes. Step 3 in the How To says "If necessary, make the script executable with chmod and then run the script:" On Sun, May 4, 2008 at 11:28 AM, Phillip Warner wrote: > The 12.1 SlackBuild scripts don't have execute permissions anymore. I don't think this was intentional, so I thought I'd mention it. > > --phil > > > > ________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > -- Wade S Grant USMC, Retired --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshuakwood at gmail.com Mon May 5 16:24:55 2008 From: joshuakwood at gmail.com (JK Wood) Date: Mon, 5 May 2008 11:24:55 -0500 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <259667.59882.qm@web57701.mail.re3.yahoo.com> References: <259667.59882.qm@web57701.mail.re3.yahoo.com> Message-ID: <6b6812630805050924j3633f92o212eaac71149b097@mail.gmail.com> That's why I use these magic things called "folders" to keep track of such things. On Mon, May 5, 2008 at 10:17 AM, Phillip Warner wrote: > Even if you do have access to the repo it would be quicker to simply check > the .info or .slackBuild file to see what slackware version it is for > instead of comparing it to what is in the repo. Either that, or people > would just download a fresh copy just to be sure (sometimes the program > version is the same in different repos), but that could waste bandwith. > > The whole point is that if you have a folder full of slackBuilds, what > version are they for? Say you have a package you want to install that was > built with a slackBuild. What version was it built for? Having the > slackware version information would be helpful in these cases. > > --phil > > Message: 4 > Date: Sun, 4 May 2008 14:11:17 -0500 > From: alkos333 > Subject: Re: [Slackbuilds-users] specifying slackware version in the > slackBuilds > To: "SlackBuilds.org Users List" > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Having a version number associated with a script would be helpful if > you didn't have access to SBo repo, or a mirror. > > On Sun, May 4, 2008 at 2:08 PM, Andrew Brouwers wrote: > > Hi Phil, > > > > What's the purpose, then, of segregating the repo's on > > slackbuilds.org? That's the reason why there are separate paths for > > different slackware versions (and why not all scripts are available in > > each of them). > > > > Andrew > > > > > > > > On Sun, May 4, 2008 at 2:40 PM, Phillip Warner wrote: > > > I think there should be something in the slackBuilds that says what > > > slackware version the script was designed for. I suggest specifying > the > > > slackware version in the .info file and the .slackBuild file. > > > > > > This can be useful for two purposes. One, it can help you to use the > right > > > script for a certain slackware version (some differ in more than just > subtle > > > ways). Second, it is also possible that having the version stated can > > > help you determine what slackware version the package was built for. > This > > > is possible if the slackware version is mentioned in the .slackBuild > file, > > > as it is included as a part of every SBo package. So, to determine > what > > > version of slackware the SBo package is intended for, you can just > look at > > > that file in the package. > > > > > > --phil > > > > > > > > > ________________________________ > > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try > it > > > now. > > > > > > > > > _______________________________________________ > > > Slackbuilds-users mailing list > > > Slackbuilds-users at slackbuilds.org > > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > > > > Please read the FAQ - http://slackbuilds.org/faq/ > > > > > > > > _______________________________________________ > > Slackbuilds-users mailing list > > Slackbuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > > Please read the FAQ - http://slackbuilds.org/faq/ > > > > > ------------------------------ > > > > ------------------------------ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From iskar.enev at gmail.com Mon May 5 16:40:17 2008 From: iskar.enev at gmail.com (Iskar Enev) Date: Mon, 05 May 2008 19:40:17 +0300 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <6b6812630805050924j3633f92o212eaac71149b097@mail.gmail.com> References: <259667.59882.qm@web57701.mail.re3.yahoo.com> <6b6812630805050924j3633f92o212eaac71149b097@mail.gmail.com> Message-ID: <481F3871.4090401@gmail.com> JK Wood wrote: > That's why I use these magic things called "folders" to keep track of > such things. Imagine that for *some* reason you don't have the initial information - how would you organize the folders then? I also think it's a good idea to include the slackware version in the .info file. And that wouldn't be something new - Pat already appends version number to the patches in -stable. We'll just "follow" ... ;) From bkirkp at gmail.com Mon May 5 16:45:39 2008 From: bkirkp at gmail.com (BKirkpatrick) Date: Mon, 05 May 2008 11:45:39 -0500 Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms Message-ID: <481F39B3.5030004@gmail.com> And, at least for me, that's a "good thing". I make several small changes to SBo scripts before I run them, including changing "#!/bin/sh" to "#!/bin/bash" & removing the execute bit. My data partition is set up nonexecutable & I want to keep it that way. I run the scripts with "bash prgnam.SlackBuild" Regards, Bill From listreader at lupulin.net Mon May 5 17:05:01 2008 From: listreader at lupulin.net (paul wisehart) Date: Mon, 05 May 2008 13:05:01 -0400 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <481F3871.4090401@gmail.com> References: <259667.59882.qm@web57701.mail.re3.yahoo.com> <6b6812630805050924j3633f92o212eaac71149b097@mail.gmail.com> <481F3871.4090401@gmail.com> Message-ID: <481F3E3D.7080105@lupulin.net> Iskar Enev wrote: > JK Wood wrote: >> That's why I use these magic things called "folders" to keep track of >> such things. > > Imagine that for *some* reason you don't have the initial information - > how would you organize the folders then? > > I also think it's a good idea to include the slackware version in the > .info file. > > And that wouldn't be something new - Pat already appends version number > to the patches in -stable. We'll just "follow" ... ;) I think some form of showing which version the package would was built for that lived *with* the pkg'ing system would also be helpful. How are you supposed to know which SBo packages can be upgraded? A package can potentially have all of the same meta-info, but need to be re-compiled for a new version of slackware. Also, slack's official packages are binary. So the same issue is handled automatically. Some variable in .info or in the PKGNAM itself would take care of this, with minimal extra impact. -- paul w From cnguyenminhtan at free.fr Mon May 5 19:31:47 2008 From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr) Date: Mon, 05 May 2008 21:31:47 +0200 Subject: [Slackbuilds-users] rtl-wifi on -current [was: Critical update suggestions for 12.1 repository] In-Reply-To: <481DA9C3.5020609@gmail.com> References: <1209636468.481996745a5ef@imp.free.fr> <481DA9C3.5020609@gmail.com> Message-ID: <1210015907.481f60a358a57@imp.free.fr> Hello, I succeeded in compiling the mod2.6.24 version as tipped by Mauro Giachero. Thanks again Mauro for the advise. I didn't include the compiled r8187.ko module in my package as this module is already in the kernel (rtl8187.ko) and I only needed the module for r8180 chipset. Now I will monitor performance (stability + logs) before I submit updated Slackbuild. I have a question to Slackbuid.org maintainers: Will you accept such a Slackbuild using a modified source ? I can make the file available on my site to ensure that link is not broken over time. Now here are the detailed steps I took to make it work (I will put them in my Slackbuild submission if it is accepted). 1) Moved modules mac80211.ko and ieee80211_crypt.ko files into *.bkp 2) Ran "depmod -a" (to prevent those 2 modules from being loaded at later steps) 3) Installed my package 4) Loaded modules in the following order: modprobe ieee80211_crypt-rtl modprobe ieee80211_crypt_wep-rtl modprobe ieee80211_crypt_tkip-rtl modprobe ieee80211_crypt_ccmp-rtl modprobe ieee80211-rtl modprobe r8180 5) Set up my interface as usual 6) so far so good :-) Thank you for advise regarding Slackbuild submission. Kind Regards, Christophe Selon Frederic Touboul : > Hello, > > Note that as of version 2.6.25, the rtl-wifi driver is officially part > of the kernel. Not really relevant for Slackware 12.1, but I thought > people might be interested. > > I have it working on my laptop running Slack 11.0 right now, without any > problem so far. > > Regards, > Frederic. > > cnguyenminhtan at free.fr wrote: > > Selon Mauro Giachero : > > > >> Trying to build a working driver I came across this: > >> > > > https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/31857/comments/34 > >> While I still can't confirm it actually works, it builds with the current > >> script and, once modprobed, I'm able to see the list of available wireless > >> networks. There's a bunch of scary messages in dmesg about missing > symbols, > >> but I haven't investigated them. > >> > >> With best regards > >> Mauro > >> > > > > Thank you for the link. Indeed I found the same file in the rtl-wifi forum. > I'll > > give it a try. > > > > Regards, > > > > Christophe > > _______________________________________________ > > Slackbuilds-users mailing list > > Slackbuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > > Please read the FAQ - http://slackbuilds.org/faq/ > > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > From pc_warner at yahoo.com Mon May 5 21:20:16 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Mon, 5 May 2008 14:20:16 -0700 (PDT) Subject: [Slackbuilds-users] nvidia-switch error: nvidia-driver slackBuild Message-ID: <775083.60835.qm@web57702.mail.re3.yahoo.com> "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver slackBuild. The line should look like the following instead: /sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia --phil --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From abrouwers at gmail.com Mon May 5 22:59:27 2008 From: abrouwers at gmail.com (Andrew Brouwers) Date: Mon, 5 May 2008 18:59:27 -0400 Subject: [Slackbuilds-users] nvidia-switch error: nvidia-driver slackBuild In-Reply-To: <775083.60835.qm@web57702.mail.re3.yahoo.com> References: <775083.60835.qm@web57702.mail.re3.yahoo.com> Message-ID: <196c22970805051559r1d4f8466t97058b2442b96b10@mail.gmail.com> $ grep -i maintainer nvidia-driver.info MAINTAINER="ppr:kut" More appropriate than spamming the entire list. On Mon, May 5, 2008 at 5:20 PM, Phillip Warner wrote: > "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver > slackBuild. The line should look like the following instead: > > /sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia > > --phil > > > ________________________________ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. > > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > From harmon at ksu.edu Tue May 6 00:13:44 2008 From: harmon at ksu.edu (Scott J. Harmon) Date: Mon, 05 May 2008 19:13:44 -0500 Subject: [Slackbuilds-users] nvidia-switch error: nvidia-driver slackBuild In-Reply-To: <196c22970805051559r1d4f8466t97058b2442b96b10@mail.gmail.com> References: <775083.60835.qm@web57702.mail.re3.yahoo.com> <196c22970805051559r1d4f8466t97058b2442b96b10@mail.gmail.com> Message-ID: <481FA2B8.7090200@ksu.edu> Andrew Brouwers wrote: > $ grep -i maintainer nvidia-driver.info > MAINTAINER="ppr:kut" > > More appropriate than spamming the entire list. > > Heh, and then you send that to the entire list, when Phillip's email address was right there ;-) Really, I don't see his email to the list as 'spam'. > On Mon, May 5, 2008 at 5:20 PM, Phillip Warner wrote: > >> "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver >> slackBuild. The line should look like the following instead: >> >> /sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia >> >> --phil >> >> >> ________________________________ >> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it >> now. >> >> >> _______________________________________________ >> Slackbuilds-users mailing list >> Slackbuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> >> Please read the FAQ - http://slackbuilds.org/faq/ >> >> >> > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > -- Scott J. Harmon PhD Candidate Kansas State University "Computer Science is no more about computers than astronomy is about telescopes." - Edsger Dijkstra From rworkman at slackbuilds.org Tue May 6 20:11:19 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 6 May 2008 20:11:19 +0000 Subject: [Slackbuilds-users] Updates - 20080506 Message-ID: <20080506201119.GA32623@slackbuilds.org> So much for taking a break after the release - you guys absolutely *flooded* us with pending updates. However, we're not complaining :) There are quite a few more left, so if yours isn't in this first batch, be patient... Tue May 6 20:01:07 UTC 2008 audio/cmus: Added a BSD license and minor cleanups to the build script; also moved from the Multimedia category to Audio where it belongs. audio/faac: Added a BSD license and minor cleanups to the build script. audio/orpheus: Added 2 patches (one to disable the use of the deprecated libghttp library and the other to fix a bug) from gentoo. Added a BSD license and minor cleanups to the build script. Thanks to Antonio Hern??ndez Blas. audio/scmpc: Added - scmpc is a audioscrobbler client for mpd. Thanks to Rodney Cobb. desktop/alltray: Added a BSD license and minor cleanups to the build script. desktop/alphacube: Added a BSD license and minor cleanups to the build script. desktop/blended: Added a BSD license and minor cleanups to the build script. desktop/cylonminimal: Updated for version 0.2 and added a BSD license and minor cleanups. desktop/dmenu: Updated for version 3.6 and added a BSD license and minor cleanups to the build script. desktop/domino: Added a BSD license and minor cleanups to the build script. desktop/kbfx: Added a BSD license and minor cleanups to the build script. desktop/linstasquared: Added a BSD license and minor cleanups. desktop/openbox: Updated for version 3.4.7.2. Thanks to Chess Griffin. desktop/un-fonts-core: Added - un-fonts is a set of Korean True Type fonts. Thanks to Christophe Nguyen. desktop/wmii: Updated for version 3.6 and added a BSD license and minor cleanups to the build script. development/eclipse: Updated for version 3.3.2 and added a BSD license and minor cleanups. development/netbeans: Updated for version 6.1 and added a BSD license and minor cleanups. games/openttd: Updated for version 0.6.0. Thanks to Chess Griffin. games/zsnes: Added a BSD license and minor cleanups to the build script. libraries/DirectFB: Added - DirectFB is a thin library that provides developers with hardware graphics acceleration. Thanks to Antonio Hern??ndez Blas. libraries/gsl: Added - gsl is a numerical library for C and C++ programmers. Thanks to Aleksandar Samardzic - this will be useful for kde4 ;-) libraries/libdaemon: Added - libdaemon is a lightweight C library that eases the writing of UNIX daemons. Thanks to Rodney Cobb. libraries/libixp: Updated for version 0.4 and added a BSD license and minor cleanups to the build script. multimedia/mpeg2dec: Added a BSD license and minor cleanups. network/axel: Added - axel is a download accelerator. Thanks to Antonio Hern??ndez Blas. network/bip: Update for version 0.7.2. Thanks to Chess Griffin. network/haproxy: Added - haproxy is a very fast and reliable proxy. Thanks to Cherife Li. network/kmldonkey: Added a BSD license and minor cleanups to the build script. network/nginx: Updated for version 0.6.30. Thanks to Chess Griffin. network/squid: Updated for version 3.0.STABLE5. network/varnish: Fixed an error in rc.varnishd script. Thanks to Cherife Li. office/oooqs2: Added a BSD license and minor cleanups to the build script. system/conky: Added a BSD license and minor cleanups to the build script. system/detachtty: Added - detachtty is a a screen like program. Thanks to Paul Wisehart. system/efont-unicode-bdf: Added - efont-unicode-bdf unicode bitmap fonts. Thanks to Antonio Hern??ndez Blas. system/emelfm2: Update for 0.4.0. Thanks to Chess Griffin. system/montecarlo: Added - montecarlo is a monospace font. Thanks to Antonio Hern??ndez Blas. system/plan9port: Added a BSD license and minor cleanups to the build script. system/profont: Added - profont is a small bitmap font great for programming. Thanks to Antonio Hern??ndez Blas. system/terminus-font: Updated to version 4.26 and added a BSD license and minor cleanups. system/xf86-video-openchrome: Added a BSD license and minor cleanups. From HMWiesinger at gmx.at Wed May 7 10:31:31 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Wed, 7 May 2008 12:31:31 +0200 Subject: [Slackbuilds-users] nvidia-switch error: nvidia-driver slackBuild In-Reply-To: <775083.60835.qm@web57702.mail.re3.yahoo.com> References: <775083.60835.qm@web57702.mail.re3.yahoo.com> Message-ID: <200805071231.31382.HMWiesinger@gmx.at> Phillip Warner wrote: > "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver > slackBuild. The line should look like the following instead: > > /sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia > Thanks for your report and also too all the others who reported the same issue. I've uploaded an updated version of the driver and the kernel-module to pending. Additionally it should now also work with the legacy-version as well as kernel-2.6.25. Grs, Heinz From iskar.enev at gmail.com Wed May 7 10:40:15 2008 From: iskar.enev at gmail.com (Iskar Enev) Date: Wed, 07 May 2008 13:40:15 +0300 Subject: [Slackbuilds-users] nvidia-switch error: nvidia-driver slackBuild In-Reply-To: <200805071231.31382.HMWiesinger@gmx.at> References: <775083.60835.qm@web57702.mail.re3.yahoo.com> <200805071231.31382.HMWiesinger@gmx.at> Message-ID: <4821870F.8070602@gmail.com> I tested the legacy version with your slackbuild, it builds and most important works nice:) Heinz Wiesinger wrote: > Phillip Warner wrote: >> "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver >> slackBuild. The line should look like the following instead: >> >> /sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia >> > > Thanks for your report and also too all the others who reported the same > issue. I've uploaded an updated version of the driver and the kernel-module > to pending. Additionally it should now also work with the legacy-version as > well as kernel-2.6.25. > > Grs, > Heinz > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ From rworkman at slackbuilds.org Wed May 7 20:40:44 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 07 May 2008 15:40:44 -0500 Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms In-Reply-To: <61783.89212.qm@web57707.mail.re3.yahoo.com> References: <61783.89212.qm@web57707.mail.re3.yahoo.com> Message-ID: <482213CC.10205@slackbuilds.org> Phillip Warner wrote: > The 12.1 SlackBuild scripts don't have execute permissions anymore. I > don't think this was intentional, so I thought I'd mention it. It was not intentional, but it has been corrected. Thanks, and sorry for the delay in fixing it. -RW From rworkman at slackbuilds.org Wed May 7 20:46:45 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 07 May 2008 15:46:45 -0500 Subject: [Slackbuilds-users] SBo 12.1 download errors In-Reply-To: <20080503185809.2e196686@griffin.mythic.magic> References: <20080503185809.2e196686@griffin.mythic.magic> Message-ID: <48221535.5040601@slackbuilds.org> ktabic wrote: > During a mass compilation session today, I've found the following errors in .info files > > pysetup: > The version number in http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c86.tar.gz is wrong and should be: > http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c8.tar.gz > > KDESvn have moved their downloads links > http://kdesvn.alwins-world.de/downloads/kdesvn-0.14.2.tar.bz2 has changed to: > http://kdesvn.alwins-world.de/trac.fcgi/downloads/kdesvn-0.14.2.tar.bz2 Both of these should be fixed now; thanks! -RW From rworkman at slackbuilds.org Wed May 7 20:48:16 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 07 May 2008 15:48:16 -0500 Subject: [Slackbuilds-users] rtl-wifi on -current In-Reply-To: <1210015907.481f60a358a57@imp.free.fr> References: <1209636468.481996745a5ef@imp.free.fr> <481DA9C3.5020609@gmail.com> <1210015907.481f60a358a57@imp.free.fr> Message-ID: <48221590.3080603@slackbuilds.org> cnguyenminhtan at free.fr wrote: > I have a question to Slackbuid.org maintainers: Will you accept such a > Slackbuild using a modified source ? I can make the file available on my site to > ensure that link is not broken over time. I'd have to see the whole script and such to say for sure, so feel free to submit it once you're comfortable with it. -RW From rworkman at slackbuilds.org Wed May 7 20:48:58 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 07 May 2008 15:48:58 -0500 Subject: [Slackbuilds-users] nvidia-switch error: nvidia-driver slackBuild In-Reply-To: <200805071231.31382.HMWiesinger@gmx.at> References: <775083.60835.qm@web57702.mail.re3.yahoo.com> <200805071231.31382.HMWiesinger@gmx.at> Message-ID: <482215BA.5000807@slackbuilds.org> Heinz Wiesinger wrote: > Phillip Warner wrote: >> "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver >> slackBuild. The line should look like the following instead: >> >> /sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia >> > > Thanks for your report and also too all the others who reported the same > issue. I've uploaded an updated version of the driver and the kernel-module > to pending. Additionally it should now also work with the legacy-version as > well as kernel-2.6.25. I'll try to get a look at this real soon now; thanks for the update. -RW From pc_warner at yahoo.com Wed May 7 21:04:37 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Wed, 7 May 2008 14:04:37 -0700 (PDT) Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms In-Reply-To: <482213CC.10205@slackbuilds.org> Message-ID: <775459.46687.qm@web57710.mail.re3.yahoo.com> Really a BIG thanks should go out to you and all the rest of the SBo (and Slackware) team! Y'all are working extra hard lately, so thank you. --phil Robby Workman wrote: Phillip Warner wrote: > The 12.1 SlackBuild scripts don't have execute permissions anymore. I > don't think this was intentional, so I thought I'd mention it. It was not intentional, but it has been corrected. Thanks, and sorry for the delay in fixing it. -RW _______________________________________________ Slackbuilds-users mailing list Slackbuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Please read the FAQ - http://slackbuilds.org/faq/ --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vbatts at batts.mine.nu Wed May 7 21:09:13 2008 From: vbatts at batts.mine.nu (Vincent Batts) Date: Wed, 7 May 2008 16:09:13 -0500 Subject: [Slackbuilds-users] 12.1 SlackBuilds no longer have execute perms In-Reply-To: <775459.46687.qm@web57710.mail.re3.yahoo.com> References: <775459.46687.qm@web57710.mail.re3.yahoo.com> Message-ID: <200805071609.13342.vbatts@batts.mine.nu> i'll second that one vb On Wednesday 07 May 2008, Phillip Warner wrote: > Really a BIG thanks should go out to you and all the rest of the SBo (and > Slackware) team! Y'all are working extra hard lately, so thank you. > > --phil > > Robby Workman wrote: Phillip Warner wrote: > > The 12.1 SlackBuild scripts don't have execute permissions anymore. I > > don't think this was intentional, so I thought I'd mention it. > > It was not intentional, but it has been corrected. > Thanks, and sorry for the delay in fixing it. > > -RW > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. -- Vincent Batts vbatts at batts.mine.nu From mickeytintincolle at yahoo.fr Thu May 8 13:56:53 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 8 May 2008 15:56:53 +0200 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds Message-ID: <709075.96752.bm@omp217.mail.ukl.yahoo.com> Hello Slackbuilds users : I have made a script that downloads, builds and installs automagically SlackBuilds . It would be nice that the script would be downloadable on the slackbuild site/included on extra/ slackware repositories . To use the script, just type as root:) : # slackmerge For example : # slackmerge desktop icewm Here is the script content : --BOF-- #!/bin/sh SLACKVER="12.1" SB_REPO="http://www.slackbuilds.org/slackbuilds/12.1/" # Usage : slackmerge # For example : slackmerge desktop icewm mkdir /tmp/SmGE cd /tmp/SmGE wget -c $SB_REPO$1/$2.tar.gz tar xvf $2.tar.gz cd $2 cp $2.info download echo "\ wget -c \$DOWNLOAD" >> download sh download sh $2.SlackBuild installpkg /tmp/*$2*.tgz --EOF-- The script is also attached to the e-mail . Enjoy using the script ! -------------- next part -------------- A non-text attachment was scrubbed... Name: slackmerge Type: application/x-shellscript Size: 361 bytes Desc: not available URL: From cherife at dotimes.com Thu May 8 14:20:53 2008 From: cherife at dotimes.com (Cherife Li) Date: Thu, 08 May 2008 22:20:53 +0800 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: <709075.96752.bm@omp217.mail.ukl.yahoo.com> References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> Message-ID: <48230C45.8000903@dotimes.com> On 2008-5-8 21:56, Antoine NONYME wrote: > Hello Slackbuilds users : > I have made a script that downloads, builds and installs automagically > SlackBuilds . > It would be nice that the script would be downloadable on the slackbuild > site/included on extra/ slackware repositories . > To use the script, just type as root:) : > # slackmerge > For example : > # slackmerge desktop icewm > Here is the script content : > --BOF-- > #!/bin/sh > SLACKVER="12.1" > SB_REPO="http://www.slackbuilds.org/slackbuilds/12.1/" > # Usage : slackmerge > # For example : slackmerge desktop icewm > mkdir /tmp/SmGE > cd /tmp/SmGE > wget -c $SB_REPO$1/$2.tar.gz > tar xvf $2.tar.gz > cd $2 > cp $2.info download > echo "\ > wget -c \$DOWNLOAD" >> download > sh download > sh $2.SlackBuild > installpkg /tmp/*$2*.tgz > --EOF-- > The script is also attached to the e-mail . > Enjoy using the script ! > IMHO, it's better to avoid using the . It will be convenient if SBO would maintain an full FILELIST file. > > ------------------------------------------------------------------------ > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ -- Rgds, Cherife. From rworkman at slackbuilds.org Thu May 8 14:39:08 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 08 May 2008 09:39:08 -0500 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: <48230C45.8000903@dotimes.com> References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> <48230C45.8000903@dotimes.com> Message-ID: <4823108C.9020309@slackbuilds.org> Cherife Li wrote: > IMHO, it's better to avoid using the . > It will be convenient if SBO would maintain an full FILELIST file. http://slackbuilds.org/ports/$SLACKVERSION/$APP.tar.gz -RW From rworkman at slackbuilds.org Thu May 8 14:41:36 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 08 May 2008 09:41:36 -0500 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: <709075.96752.bm@omp217.mail.ukl.yahoo.com> References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> Message-ID: <48231120.8020209@slackbuilds.org> Antoine NONYME wrote: > Hello Slackbuilds users : > I have made a script that downloads, builds and installs automagically > SlackBuilds . > It would be nice that the script would be downloadable on the slackbuild > site/included on extra/ slackware repositories . There are no plans to to host anything like this on our site, as there can be an endless number of similar tools, and we simply don't have time to test all of them to ensure that they're not doing something ugly. Another concern is that while we might prefer one of them over another, we'd need pretty compelling reasons to put one on our site and/or officially recommend it, as that opens up a whole new can of worms. -RW From boblounsbury at gmail.com Thu May 8 14:41:12 2008 From: boblounsbury at gmail.com (Bob Lounsbury) Date: Thu, 8 May 2008 08:41:12 -0600 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: <48230C45.8000903@dotimes.com> References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> <48230C45.8000903@dotimes.com> Message-ID: On Thu, May 8, 2008 at 8:20 AM, Cherife Li wrote: > On 2008-5-8 21:56, Antoine NONYME wrote: >> >> Hello Slackbuilds users : >> I have made a script that downloads, builds and installs automagically >> SlackBuilds . Have you seen http://code.google.com/p/sbopkg/? It's an ncurses bases tool that already does this. Cheers, /Bob From mickeytintincolle at yahoo.fr Thu May 8 13:56:53 2008 From: mickeytintincolle at yahoo.fr (Antoine NONYME) Date: Thu, 8 May 2008 15:56:53 +0200 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds Message-ID: <806883.95514.bm@omp215.mail.ukl.yahoo.com> Hello Slackbuilds users : I have made a script that downloads, builds and installs automagically SlackBuilds . It would be nice that the script would be downloadable on the slackbuild site/included on extra/ slackware repositories . To use the script, just type as root:) : # slackmerge For example : # slackmerge desktop icewm Here is the script content : --BOF-- #!/bin/sh SLACKVER="12.1" SB_REPO="http://www.slackbuilds.org/slackbuilds/12.1/" # Usage : slackmerge # For example : slackmerge desktop icewm mkdir /tmp/SmGE cd /tmp/SmGE wget -c $SB_REPO$1/$2.tar.gz tar xvf $2.tar.gz cd $2 cp $2.info download echo "\ wget -c \$DOWNLOAD" >> download sh download sh $2.SlackBuild installpkg /tmp/*$2*.tgz --EOF-- The script is also attached to the e-mail . Enjoy using the script ! -------------- next part -------------- A non-text attachment was scrubbed... Name: slackmerge Type: application/x-shellscript Size: 361 bytes Desc: not available URL: From chess at chessgriffin.com Thu May 8 15:07:13 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 08 May 2008 11:07:13 -0400 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> <48230C45.8000903@dotimes.com> Message-ID: <48231721.8060605@chessgriffin.com> Bob Lounsbury wrote: > On Thu, May 8, 2008 at 8:20 AM, Cherife Li wrote: >> On 2008-5-8 21:56, Antoine NONYME wrote: >>> Hello Slackbuilds users : >>> I have made a script that downloads, builds and installs automagically >>> SlackBuilds . > > Have you seen http://code.google.com/p/sbopkg/? It's an ncurses bases > tool that already does this. > > Cheers, > /Bob Which also works from the command line only. You can build a package like this: # sbopkg -b icewm You can search for packages: # sbopkg -q ice will grep for 'ice' and return a list of matches in category/name format. If you know the full name, you can use -s and it will then show all the related files, like the README, *.info, SlackBuild, etc: # sbopkg -s icewm There are lots of command line options, which can be checked out with: # sbopkg -h -Chess -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From mickeytintincolle at yahoo.fr Thu May 8 18:14:25 2008 From: mickeytintincolle at yahoo.fr (Anotine NONYME) Date: Thu, 08 May 2008 20:14:25 +0200 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: <4823108C.9020309@slackbuilds.org> References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> <48230C45.8000903@dotimes.com> <4823108C.9020309@slackbuilds.org> Message-ID: <48234301.1020209@yahoo.fr> Robby Workman wrote: >
Cherife > Li wrote: > >> IMHO, it's better to avoid using the . >> It will be convenient if SBO would maintain an full FILELIST file. > > http://slackbuilds.org/ports/$SLACKVERSION/$APP.tar.gz > > -RW > >
Lots of thanks, now I won't have to search the category in the site . Greets . From dev.akhawe at gmail.com Thu May 8 20:59:11 2008 From: dev.akhawe at gmail.com (dev) Date: Fri, 9 May 2008 02:29:11 +0530 Subject: [Slackbuilds-users] A script for automated downloads, builds and installs of Slackbuilds In-Reply-To: <48234301.1020209@yahoo.fr> References: <709075.96752.bm@omp217.mail.ukl.yahoo.com> <48230C45.8000903@dotimes.com> <4823108C.9020309@slackbuilds.org> <48234301.1020209@yahoo.fr> Message-ID: You can ofcourse also just do wget http://slackbuilds.org/result/?search=$1 and get the results and move from there ... I am not sure whether SBopkg does that . This would ensure that the script doesn't break if someday the sb.org team decides to reorder their repository etc. Regards Devdatta 2008/5/8 Anotine NONYME : > Robby Workman wrote: >> >>
Cherife Li >> wrote: >> >>> IMHO, it's better to avoid using the . >>> It will be convenient if SBO would maintain an full FILELIST file. >> >> http://slackbuilds.org/ports/$SLACKVERSION/$APP.tar.gz >> >> -RW >> >>
> > Lots of thanks, now I won't have to search the category in the site . > Greets . > > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Please read the FAQ - http://slackbuilds.org/faq/ > From lanceb at ksu.edu Sat May 10 17:20:19 2008 From: lanceb at ksu.edu (lanceb at ksu.edu) Date: Sat, 10 May 2008 12:20:19 -0500 Subject: [Slackbuilds-users] qtoctave SlackBuild doesn't work Message-ID: <1210440019.4825d9538c38d@webmail.ksu.edu> First of all, I want to thank you for the good work you are doing. The last week has been my first real use of Slackware. Now that I understand it, I wish I had tried it earlier, it's popular because it's good. SlackBuilds.org is a big part of what makes it great. I tried to build qtoctave (0.7.1) using the existing SlackBuild. While that does successfully build the package, there is unfortunately a bug that will prevent it from running: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476768 The current version of qtoctave is 0.7.4. The problem is that significant changes were made in the qtoctave source package between 0.7.1 and 0.7.4, such that the SlackBuild for 0.7.1 will quit with errors due to missing files if you try to run it with 0.7.4. After some searching and trial and error, I got it to build. I took the existing SlackBuild, updated the version to 0.7.4, then commented out the following lines ./configure \ --prefix=/usr \ --qtdir=/opt/qt4 This version of qtoctave is compiled using cmake. My qt4 came from slacky.eu, so I had to tell it where to find my qt4 installation. Following this forum post: http://lists.trolltech.com/qt-interest/2007-07/thread00441-0.html I replaced the above commented lines with cmake -DQT_QMAKE_EXECUTABLE=/opt/qt4/bin/qmake . make install INSTALL_ROOT=$PKG The SlackBuild still did not work. I had to comment out the following lines at the bottom because the files do not exist in qtoctave 0.7.4: cp -a $PRGNAM/doc LEEME.txt NEWS.txt LICENSE_GPL.txt README.txt \ $PKG/usr/doc/$PRGNAM-$VERSION ln -s /usr/share/$PRGNAM/qtoctave-doc $PKG/usr/doc/$PRGNAM-$VERSION/qtoctave-doc cp $CWD/octave-sombrero.png $PKG/usr/share/qtoctave/images It then built and ran properly. From HMWiesinger at gmx.at Sun May 11 08:21:23 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Sun, 11 May 2008 10:21:23 +0200 Subject: [Slackbuilds-users] some minor problems Message-ID: <200805111021.23632.HMWiesinger@gmx.at> Hi guys! I found some minor problems in the 12.1 repo. First, my libwpg script is not there anymore. As I could not find any note in previous changelogs of it being removed, I guess it was mistake. I have resubmitted the script already. Then there are currently two versions of eclipse in the db, both being displayed on the website, although only one is in the repo. And a really small mistake in the build-script for "R". The resulting package is missing $TAG, which leads to a package-name without "_SBo". Grs, Heinz From HMWiesinger at gmx.at Sun May 11 08:31:17 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Sun, 11 May 2008 10:31:17 +0200 Subject: [Slackbuilds-users] problem with faac.SlackBuild Message-ID: <200805111031.17636.HMWiesinger@gmx.at> Hi! I have found a problem in the build-script for faac. faac does currently build with "--with-mp4v2", which enables the build of the internal libmp4v2 library. However, this is not forced. The configure-script checks for a already existing libmp4v2 on the system, regardless of the option. So, no problem on first time builds, as faac does detect, that there's no libmp4v2 available. But if you update faac, or do a rebuild, faac detects the already installed libmp4v2 (from the previous faac-package) and builds against it. A followed upgradepkg will remove libmp4v2 from system. Actually, the situation is the same when run without the "--with-mp4v2" option. The only sane solution I could find, was running configure with "--without-mp4v2". If the external libmp4v2 (from SBo) is available, it will build against it, if not, build of the own libmp4v2 is disabled. Grs, Heinz From ajc at countingthoughts.com Sun May 11 09:07:00 2008 From: ajc at countingthoughts.com (Andrew Conway) Date: Sun, 11 May 2008 10:07:00 +0100 Subject: [Slackbuilds-users] arch question Message-ID: <4826B734.4070307@countingthoughts.com> Hi I'm just starting out making slackbuild scripts and am spending some time reading and understanding the docs, but please excuse me if this is a stupid or already-asked question on this list. Originally posted here: http://www.linuxquestions.org/questions/slackware-14/slackbuild-guidance-needed-641318/ I've succeeded in making a slackbuild for kphotoalbum but have come across conflicting advice. http://www.slackbuilds.com/guidelines/ tells me to include these lines: Code: if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" fi but the tutorial http://www.slackwiki.org/Writing_A_SlackBuild_Script says Code: if [ "$ARCH" = "i386" ]; then SLKCFLAGS="-O2 -march=i386 -mtune=i686" elif [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" fi Which is preferred? Andrew From carlos at strangeworlds.co.uk Sun May 11 09:16:31 2008 From: carlos at strangeworlds.co.uk (Carlos Corbacho) Date: Sun, 11 May 2008 10:16:31 +0100 Subject: [Slackbuilds-users] arch question In-Reply-To: <4826B734.4070307@countingthoughts.com> References: <4826B734.4070307@countingthoughts.com> Message-ID: <200805111016.32093.carlos@strangeworlds.co.uk> This is the preferred one. > if [ "$ARCH" = "i486" ]; then > SLKCFLAGS="-O2 -march=i486 -mtune=i686" This is wrong: > if [ "$ARCH" = "i386" ]; then > SLKCFLAGS="-O2 -march=i386 -mtune=i686" Current Slackware releases (i.e. 9.0 and onwards) don't support i386 as a target anymore (see source/d/gcc.SlackBuild for the reasons behind this). The above is also wrong because the last compiler that would have properly supported i386 on Slackware would have used -mcpu, not -mtune. Given SBo SlackBuild's target specific Slackware releases, it doesn't make much sense to put in an architecture target that won't build. -Carlos -- E-Mail: carlos at strangeworlds.co.uk Web: strangeworlds.co.uk GPG Key ID: 0x23EE722D From xgizzmo at slackbuilds.org Sun May 11 11:16:22 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Sun, 11 May 2008 07:16:22 -0400 Subject: [Slackbuilds-users] problem with faac.SlackBuild In-Reply-To: <200805111031.17636.HMWiesinger@gmx.at> References: <200805111031.17636.HMWiesinger@gmx.at> Message-ID: <200805110716.23059.xgizzmo@slackbuilds.org> On Sunday 11 May 2008 04:31:17 Heinz Wiesinger wrote: > The only sane solution I could find, was running configure > with "--without-mp4v2". If the external libmp4v2 (from SBo) is available, it > will build against it, if not, build of the own libmp4v2 is disabled. > I think the sane solution here would be to remove the package before compiling a new one. David Somero From xgizzmo at slackbuilds.org Sun May 11 11:23:10 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Sun, 11 May 2008 07:23:10 -0400 Subject: [Slackbuilds-users] some minor problems In-Reply-To: <200805111021.23632.HMWiesinger@gmx.at> References: <200805111021.23632.HMWiesinger@gmx.at> Message-ID: <200805110723.11184.xgizzmo@slackbuilds.org> On Sunday 11 May 2008 04:21:23 Heinz Wiesinger wrote: > Hi guys! > > I found some minor problems in the 12.1 repo. > First, my libwpg script is not there anymore. As I could not find any note in > previous changelogs of it being removed, I guess it was mistake. I have > resubmitted the script already. Will try and get this in the next update. I am not sure how it was missed. > Then there are currently two versions of eclipse in the db, both being > displayed on the website, although only one is in the repo. This has now been fixed. > And a really small mistake in the build-script for "R". The resulting package > is missing $TAG, which leads to a package-name without "_SBo". > This has also been fixed, Thanks a lot for the reports. David Somero From mauro.giachero at gmail.com Sun May 11 14:38:30 2008 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Sun, 11 May 2008 16:38:30 +0200 Subject: [Slackbuilds-users] qtoctave SlackBuild doesn't work In-Reply-To: <1210440019.4825d9538c38d@webmail.ksu.edu> References: <1210440019.4825d9538c38d@webmail.ksu.edu> Message-ID: Thank you for both the report and the analysis. I'll look at these as soon as I'm back to my 12.1 box (later this week) and submit an updated script. With best regards Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauro.giachero at gmail.com Sun May 11 14:46:41 2008 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Sun, 11 May 2008 16:46:41 +0200 Subject: [Slackbuilds-users] problem with faac.SlackBuild In-Reply-To: <200805110716.23059.xgizzmo@slackbuilds.org> References: <200805111031.17636.HMWiesinger@gmx.at> <200805110716.23059.xgizzmo@slackbuilds.org> Message-ID: On Sun, May 11, 2008 at 1:16 PM, wrote: > On Sunday 11 May 2008 04:31:17 Heinz Wiesinger wrote: > > The only sane solution I could find, was running configure > > with "--without-mp4v2". If the external libmp4v2 (from SBo) is > available, it > > will build against it, if not, build of the own libmp4v2 is disabled. > > > > I think the sane solution here would be to remove the package > before compiling a new one. > > David Somero This is sane as long as the script refuses to run when there's a previous faac version installed, or at least the README clearly states that it's a required procedure. AFAIK people is not supposed to remove old packages before building newer ones, and the script as-is causes unexpected breackage on users' systems. Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sun May 11 17:08:23 2008 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 11 May 2008 12:08:23 -0500 Subject: [Slackbuilds-users] problem with faac.SlackBuild In-Reply-To: <200805110716.23059.xgizzmo@slackbuilds.org> References: <200805111031.17636.HMWiesinger@gmx.at> <200805110716.23059.xgizzmo@slackbuilds.org> Message-ID: <20080511120823.65e254c9@shaggy.scooby> On May 11, 2008, at 7:16 AM, xgizzmo at slackbuilds.org wrote: > On Sunday 11 May 2008 04:31:17 Heinz Wiesinger wrote: > > The only sane solution I could find, was running configure > > with "--without-mp4v2". If the external libmp4v2 (from SBo) is available, it > > will build against it, if not, build of the own libmp4v2 is disabled. > > > > I think the sane solution here would be to remove the package > before compiling a new one. I would change the script to use --without-mp4v2 and note in the README the optional dependency of libmp4v2, available at SBo. I've tested this and it works. This seems like the most sane thing to do. If you patch it to force building the internal libmp4v2, it will conflict with a pre- existing external. -- Erik Hanson http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From xgizzmo at slackbuilds.org Mon May 12 00:53:53 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Sun, 11 May 2008 20:53:53 -0400 Subject: [Slackbuilds-users] Updates - 20080512 Message-ID: <200805112053.53560.xgizzmo@slackbuilds.org> Mon May 12 00:31:28 UTC 2008 desktop/QtCurve-Gtk2: Updated for version 0.59.2. desktop/QtCurve-KDE3: Updated for version 0.59.1. Thanks to Michiel van Wessem for both of these. --rworkman development/boost: Updated for version 1.35.0. Thanks to Heinz Wiesinger. --Michiel development/eclipse: Fixed the /usr/bin/eclipse wrapper script to use absolute path to /opt/eclipse instead of a relative path from /usr/bin, and did a bit of other miscellaneous script cleanup. Thanks to Michael Gehring for pointing out the path problem. --rworkman development/geany: Updated for version 0.14. Thanks to Michiel. --rworkman development/netbeans: Fixed the /usr/bin/netbeans wrapper script to use absolute path to /opt/netbeans instead of a relative path from /usr/bin. Thanks to Michael Gehring for pointing out the problem. --rworkman development/source-highlight: Added - source-highlight is useful for linuxdoc-tools & asciidoc. Thanks to luoyi. --Michiel development/smake: Added - smake is a highly portable make program with automake features. Thanks to jpipkin. --rworkman games/wesnoth: Updated for version 1.4.1. Thanks to Michiel van Wessem. --Alan libraries/argtable: Added - argtable is an ANSI C library for parsing GNU style command line options. Thanks to Rodney Cobb. --David Somero libraries/barry: Updated for version 0.12. Thanks to Vincent Batts. --Alan libraries/libwpg: Added back, this one got lost in the transfer to 12.1. Thanks to Heinz Wiesinger for the report. --David Somero libraries/qt4: Updated for version 4.4.0. Thanks to Aleksandar Samardzic. --Michiel multimedia/kmplayer: Updated for version 0.10.0c. Thanks to Antonio Hern?ndez Blas. --David Somero network/fcgi: Added - fast cgi is a language independent, scalable, open extension to CGI that provides high perfomance without the limitations of server specific API's. Thanks to Vincent Batts. --rworkman network/ipcalc: Added - ipcalc is a console application that displays subnets in an easy and informative format. Thanks to Vincent Batts. --Alan network/mldonkey: Updated - miscellaneous script cleanup. Thanks to Antonio Hern?ndez Blas. --Michiel office/homebank: Updated for version 3.8. Thanks to Erik Hanson. --Michiel. office/gnumeric: Added - gnumeric is a standalone spreadsheet application. Thanks to Alex Lysenka. --rworkman system/rxvt-unicode: Updated for version 9.02. Thanks to Dugan Chen. --Michiel system/star: Added - star is a very fast tar(1) like tape archiver with improved functionality. Thanks to jpipkin. --rworkman From sleistinger at verizon.net Mon May 12 00:54:34 2008 From: sleistinger at verizon.net (Steve) Date: Sun, 11 May 2008 20:54:34 -0400 Subject: [Slackbuilds-users] kaffeine version Message-ID: <200805112054.35070.sleistinger@verizon.net> Hi everyone, The version of kaffeine that Slackbuilds.org currently points to (0.8.4) has a nasty bug that causes the application to crash when to try to rip/encode. The latest release (0.8.6) fixes this bug and builds nicely using the kaffeine.SlackBuild script with only a version number edit. I'm using Slackware 12.1. I would suggest the version change if it isn't being done as we speak. Thanks, Steve From michiel at slackbuilds.org Mon May 12 01:11:23 2008 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Mon, 12 May 2008 02:11:23 +0100 Subject: [Slackbuilds-users] kaffeine version In-Reply-To: <200805112054.35070.sleistinger@verizon.net> References: <200805112054.35070.sleistinger@verizon.net> Message-ID: <200805120211.30123.michiel@slackbuilds.org> On Monday 12 May 2008 01:54:34 Steve wrote: > I would suggest the version change if it isn't being done as we speak. kaffeine 0.8.6 was submitted by me to the pending queue on 20080506 M. -- http://slackbuilds.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From rworkman at slackbuilds.org Mon May 12 04:04:32 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 11 May 2008 23:04:32 -0500 Subject: [Slackbuilds-users] problem with faac.SlackBuild In-Reply-To: <20080511120823.65e254c9@shaggy.scooby> References: <200805111031.17636.HMWiesinger@gmx.at> <200805110716.23059.xgizzmo@slackbuilds.org> <20080511120823.65e254c9@shaggy.scooby> Message-ID: <4827C1D0.5060207@slackbuilds.org> Erik Hanson wrote: > On May 11, 2008, at 7:16 AM, xgizzmo at slackbuilds.org wrote: > >> On Sunday 11 May 2008 04:31:17 Heinz Wiesinger wrote: >>> The only sane solution I could find, was running configure >>> with "--without-mp4v2". If the external libmp4v2 (from SBo) is available, it >>> will build against it, if not, build of the own libmp4v2 is disabled. >>> >> I think the sane solution here would be to remove the package >> before compiling a new one. > > I would change the script to use --without-mp4v2 and note in the README > the optional dependency of libmp4v2, available at SBo. I've tested this > and it works. This seems like the most sane thing to do. If you patch it > to force building the internal libmp4v2, it will conflict with a pre- > existing external. I think this is the optimal solution. If the maintainer (or anyone, really) can submit an update to faac which does this, that will ensure we don't forget about it. -RW From rworkman at slackbuilds.org Mon May 12 04:05:24 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 11 May 2008 23:05:24 -0500 Subject: [Slackbuilds-users] qtoctave SlackBuild doesn't work In-Reply-To: References: <1210440019.4825d9538c38d@webmail.ksu.edu> Message-ID: <4827C204.8080803@slackbuilds.org> Mauro Giachero wrote: > Thank you for both the report and the analysis. I'll look at these as > soon as I'm back to my 12.1 box (later this week) and submit an updated > script. Thanks; I had made a note to look at this, but since you're going to handle it and push it our way, I'll be sure not to forget about it :) -RW From rworkman at slackbuilds.org Mon May 12 04:10:44 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 11 May 2008 23:10:44 -0500 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <327535.21231.qm@web57706.mail.re3.yahoo.com> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> Message-ID: <4827C344.50505@slackbuilds.org> Phillip Warner wrote: > I think there should be something in the slackBuilds that says what > slackware version the script was designed for. I suggest specifying the > slackware version in the .info file and the .slackBuild file. > > This can be useful for two purposes. One, it can help you to use the > right script for a certain slackware version (some differ in more than > just subtle ways). Second, it is also possible that having the > version stated can help you determine what slackware version the package > was built for. This is possible if the slackware version is mentioned > in the .slackBuild file, as it is included as a part of every SBo > package. So, to determine what version of slackware the SBo package is > intended for, you can just look at that file in the package. Quite frankly, I don't see how this addition would help *us* (that is, the admins). While it's not a huge effort to implement once the initial addition is done, the initial change of adding the relevant line to *.info files to the entire repository *is* a huge amount of work, so here's the verdict: Unless someone can point out how this change will help *us* - we're not going to do it. Other than that, there's not really any objection to the feature, as it's nonintrusive otherwise, so if someone else not affiliated with the project thinks it's worth the amount of effort required to do it and then send us a patch, maybe we'll accept it (but no promises, of course). -RW From rworkman at slackbuilds.org Mon May 12 04:22:31 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 11 May 2008 23:22:31 -0500 Subject: [Slackbuilds-users] Talking vs Doing [was: specifying slackware version in the SlackBuilds] In-Reply-To: <4827C344.50505@slackbuilds.org> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <4827C344.50505@slackbuilds.org> Message-ID: <4827C607.7070101@slackbuilds.org> Robby Workman wrote: > ... so if someone else not affiliated with the project thinks > it's worth the amount of effort required to do it and then send us > a patch, maybe we'll accept it (but no promises, of course). As an aside, maybe I'm just in a bad mood and tomorrow I'll wish I hadn't written this, but I'll take my chances. :-) Those of you who have used Slackware for at least two or three releases prior to 12.1 might have picked up on this by now, but if you think back to 10.2 going forward, there have been a lot of things that *could* be beneficial to Slackware but weren't present in the official package sets. Lots of users liked to complain that "we need $app" or "we need $library" in Slackware, and then they got frustrated when it didn't show up. In many of those cases, there were few (if any) technical reasons for their lack of inclusion in Slackware; instead, it was often a lack of time on Pat's part to work out the details required for integrating it properly. Almost without exception, when someone else took the time to work out those details and then sent the result to Pat, they were promptly added to Slackware. I won't name examples, and I'm sure there are some notable exceptions to that, but I think the point should be clear by now... :-) -RW From pc_warner at yahoo.com Mon May 12 06:58:41 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Sun, 11 May 2008 23:58:41 -0700 (PDT) Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <4827C344.50505@slackbuilds.org> Message-ID: <598463.37853.qm@web57710.mail.re3.yahoo.com> I think it would benefit users, but I don't think it would help the admins at all. Couldn't a line be added at the *end* of every .info file with minimal effort? Y'all could just set up a loop to cat the line into the file and re-tar the slackBuilds. Anyhoo, it's no big deal to me; I just thought some users might find the feature useful. --phil Robby Workman wrote: Phillip Warner wrote: > I think there should be something in the slackBuilds that says what > slackware version the script was designed for. I suggest specifying the > slackware version in the .info file and the .slackBuild file. > > This can be useful for two purposes. One, it can help you to use the > right script for a certain slackware version (some differ in more than > just subtle ways). Second, it is also possible that having the > version stated can help you determine what slackware version the package > was built for. This is possible if the slackware version is mentioned > in the .slackBuild file, as it is included as a part of every SBo > package. So, to determine what version of slackware the SBo package is > intended for, you can just look at that file in the package. Quite frankly, I don't see how this addition would help *us* (that is, the admins). While it's not a huge effort to implement once the initial addition is done, the initial change of adding the relevant line to *.info files to the entire repository *is* a huge amount of work, so here's the verdict: Unless someone can point out how this change will help *us* - we're not going to do it. Other than that, there's not really any objection to the feature, as it's nonintrusive otherwise, so if someone else not affiliated with the project thinks it's worth the amount of effort required to do it and then send us a patch, maybe we'll accept it (but no promises, of course). -RW _______________________________________________ Slackbuilds-users mailing list Slackbuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Please read the FAQ - http://slackbuilds.org/faq/ --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From listreader at lupulin.net Mon May 12 07:25:25 2008 From: listreader at lupulin.net (pkw) Date: Mon, 12 May 2008 03:25:25 -0400 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <4827C344.50505@slackbuilds.org> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <4827C344.50505@slackbuilds.org> Message-ID: <20080512072525.GA22028@hubris.lan> On Sun, May 11, 2008 at 11:10:44PM -0500, Robby Workman wrote: > Quite frankly, I don't see how this addition would help *us* (that > is, the admins). While it's not a huge effort to implement once the > initial addition is done, the initial change of adding the relevant > line to *.info files to the entire repository *is* a huge amount of > work, so here's the verdict: Unless someone can point out how this > change will help *us* - we're not going to do it. Other than that, > there's not really any objection to the feature, as it's nonintrusive > otherwise, so if someone else not affiliated with the project thinks > it's worth the amount of effort required to do it and then send us > a patch, maybe we'll accept it (but no promises, of course). > I'm potentially prepared to do the work, but I need to clarify one point. It is only important to me if the meta-info of the target slackware version lives *with* the package. [1] It would need to be in the package name itself or in the .SlackBuild.[0] -- paul w [0] Is it a hard requirement that the Slackbuild file is included in the package? ( I have a feeling it isn't.) [1] The installed package, apart from any build process. From rworkman at slackbuilds.org Mon May 12 19:08:01 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 12 May 2008 14:08:01 -0500 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <20080512072525.GA22028@hubris.lan> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <4827C344.50505@slackbuilds.org> <20080512072525.GA22028@hubris.lan> Message-ID: <48289591.8020201@slackbuilds.org> pkw wrote: > I'm potentially prepared to do the work, but I need to clarify one > point. It is only important to me if the meta-info of the target > slackware version lives *with* the package. [1] > > It would need to be in the package name itself or in the .SlackBuild.[0] Well, if that's a requirement, then I think I should go ahead and say this: I don't think we'll be adding it. I just don't see a condition where that information is needed. When doing a system upgrade, either the package still works or it doesn't. If it does, then leave it alone unless you just want a newer version. If it doesn't, then you rebuild it, ideally checking for a newer version upstream and/or at SlackBuilds.org. If you have a package lying around and it's not clear what version it was compiled for, then you need a better system of organization. -RW From xgizzmo at slackbuilds.org Mon May 12 19:36:39 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Mon, 12 May 2008 15:36:39 -0400 Subject: [Slackbuilds-users] =?iso-8859-1?q?specifying_slackware_version_i?= =?iso-8859-1?q?n_the=09slackBuilds?= In-Reply-To: <48289591.8020201@slackbuilds.org> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <20080512072525.GA22028@hubris.lan> <48289591.8020201@slackbuilds.org> Message-ID: <200805121536.39701.xgizzmo@slackbuilds.org> On Monday 12 May 2008 15:08:01 Robby Workman wrote: > If you have a package lying around and it's not clear what version > it was compiled for, then you need a better system of organization. > Now we are getting down to the crux of the problem, no matter what we did someone would say you should have done it this way or that way. Since SlackBuilds.org tries to follow Slackware style be it written or unwritten that means following Slackware's package naming style also. The _SBo tag is needed to distinguish our builds from official ones. But I mean come on guys is it really that hard for the end user to change the tag to TAG=${TAG:-_SBo12.1} or whatever if you need this "feature". Heck you can even do it at build time via: TAG="_SBo12.1" ./*.SlackBuild David Somero From rworkman at slackbuilds.org Mon May 12 20:45:07 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 12 May 2008 20:45:07 +0000 Subject: [Slackbuilds-users] Update #2 - 20080512 Message-ID: <20080512204507.GA4687@slackbuilds.org> Mon May 12 20:27:20 UTC 2008 development/kdesvn: Updated for version 0.14.3. Thanks to Michiel. --rworkman libraries/libopensync: Reverted to version 0.22 because some things that depend on it can't use the newer releases yet. Thanks to Michael Wagner for pointing out the incompatibilities and to Heinz Wiesinger for the script work. --rworkman multimedia/kaffeine: Updated for version 0.8.6; this fixes a severe crash bug in kaffeine. Thanks to Michiel van Wessem. --rworkman network/bitlbee: Updated for version 1.2. Thanks to Michiel. --rworkman office/kmymoney2: Updated for version 0.8.9. Thanks to Michiel. --rworkman system/nvidia-driver: Updated for version 169.12, added support for the legacy drivers, and miscellaneous bugfixes and cleanup. system/nvidia-kernel: Updated for version 169.12, added support for the legacy drivers, and miscellaneous bugfixes and cleanup. Thanks to Heinz Wiesinger for both of these nvidia builds, and he wishes to thank the numerous people who reported the issues to him. --rworkman system/xorg-server-xephyr: Miscellaneous script cleanup and bugfixes. Thanks to Heinz Wiesinger. --rworkman From listreader at lupulin.net Mon May 12 20:49:47 2008 From: listreader at lupulin.net (pkw) Date: Mon, 12 May 2008 16:49:47 -0400 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <200805121536.39701.xgizzmo@slackbuilds.org> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <20080512072525.GA22028@hubris.lan> <48289591.8020201@slackbuilds.org> <200805121536.39701.xgizzmo@slackbuilds.org> Message-ID: <20080512204947.GA2071@hubris.lan> On Mon, May 12, 2008 at 03:36:39PM -0400, xgizzmo at slackbuilds.org wrote: > On Monday 12 May 2008 15:08:01 Robby Workman wrote: > > If you have a package lying around and it's not clear what version > > it was compiled for, then you need a better system of organization. > > > > Now we are getting down to the crux of the problem, no matter what we > did someone would say you should have done it this way or that way. > Since SlackBuilds.org tries to follow Slackware style be it written or > unwritten that means following Slackware's package naming style also. > The _SBo tag is needed to distinguish our builds from official ones. > But I mean come on guys is it really that hard for the end user to > change the tag to TAG=${TAG:-_SBo12.1} or whatever if you need this > "feature". Heck you can even do it at build time via: > TAG="_SBo12.1" ./*.SlackBuild > Uhm ok, that's fine. Don't get upset. I didn't make the original request, but I piped in and offered to do the work, so for my part I'm just making it clear I'm not trying to make anyone's life harder. I was completely satisfied with the 1st response that it wouldn't get done. I only offered to do the work because Rob kinda put it out there that it was a way to get it done.[0] In closing, slackbuilds.org is awesome. -- paul [0] I still think it's a good idea. Meaning; I didn't offer to to do the work for altruistic reasons, but because I wanted the feature, which I thought was the point of Rob's message. From rworkman at slackbuilds.org Mon May 12 21:19:04 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 12 May 2008 16:19:04 -0500 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <20080512204947.GA2071@hubris.lan> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <20080512072525.GA22028@hubris.lan> <48289591.8020201@slackbuilds.org> <200805121536.39701.xgizzmo@slackbuilds.org> <20080512204947.GA2071@hubris.lan> Message-ID: <4828B448.1060500@slackbuilds.org> pkw wrote: > I didn't make the original request, but I piped in and offered to > do the work, so for my part I'm just making it clear I'm not trying > to make anyone's life harder. I was completely satisfied with the > 1st response that it wouldn't get done. I only offered to do the > work because Rob kinda put it out there that it was a way to get > it done.[0] > > In closing, slackbuilds.org is awesome. :) > [0] I still think it's a good idea. Meaning; I didn't offer to to > do the work for altruistic reasons, but because I wanted the > feature, which I thought was the point of Rob's message. It was, but after more consideration and discussion with other admins, we just don't see it as a truly useful addition, and there's actually some opposition to it, so it's not going to happen. It does create a "slippery slope" toward adding/doing things that don't serve any reasonable purpose, and we'd rather not take a plunge down that hill. Sorry for the (unintentional) misleading message earlier. -RW From me at alkos333.net Wed May 14 03:06:44 2008 From: me at alkos333.net (alkos333) Date: Tue, 13 May 2008 22:06:44 -0500 Subject: [Slackbuilds-users] specifying slackware version in the slackBuilds In-Reply-To: <4828B448.1060500@slackbuilds.org> References: <327535.21231.qm@web57706.mail.re3.yahoo.com> <20080512072525.GA22028@hubris.lan> <48289591.8020201@slackbuilds.org> <200805121536.39701.xgizzmo@slackbuilds.org> <20080512204947.GA2071@hubris.lan> <4828B448.1060500@slackbuilds.org> Message-ID: Robby, There will always been suggestions to change/improve things in some way. You can always just say NO like you did this time around :). Although I agree it could be useful in rare circumstances, I can never see myself making any use of such addition in the near future. On Mon, May 12, 2008 at 4:19 PM, Robby Workman wrote: > pkw wrote: > > > > I didn't make the original request, but I piped in and offered to > > do the work, so for my part I'm just making it clear I'm not trying > > to make anyone's life harder. I was completely satisfied with the > > 1st response that it wouldn't get done. I only offered to do the > > work because Rob kinda put it out there that it was a way to get > > it done.[0] > > > > In closing, slackbuilds.org is awesome. > > > > > :) > > > > > > [0] I still think it's a good idea. Meaning; I didn't offer to to > > do the work for altruistic reasons, but because I wanted the > > feature, which I thought was the point of Rob's message. > > > > > It was, but after more consideration and discussion with other admins, > we just don't see it as a truly useful addition, and there's actually > some opposition to it, so it's not going to happen. It does create > a "slippery slope" toward adding/doing things that don't serve any > reasonable purpose, and we'd rather not take a plunge down that hill. > Sorry for the (unintentional) misleading message earlier. > > -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/ > > From rworkman at slackbuilds.org Wed May 14 18:34:17 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 14 May 2008 18:34:17 +0000 Subject: [Slackbuilds-users] Updates - 20080514 Message-ID: <20080514183417.GA31219@slackbuilds.org> Wed May 14 18:29:32 UTC 2008 accessibility/jpilot: Added - J-Pilot is a desktop organizer application for PalmOS devices. Thanks to Alex Lysenka. --rworkman audio/faac: Made libmp4v2 an optional dependency to work around conflicts if the embedded library is used (don't use it). Thanks to Heinz Wiesinger for pointing out the problem and to Antonio Hern??????ndez Blas for fixing the build script. If there are still problems with this approach, blame me, because I implemented it a bit differently than the maintainer suggested. --rworkman desktop/awesome: Added - awesome is a floating and tiling window manager initially based on a rewrite of dwm. Thanks to Chess Griffin. --rworkman graphics/fontforge: Updated for version 20080429. Thanks to Robby Workman. --David Somero libraries/confuse: Renamed from libconfuse to eliminate confusion about the upstream name and what we were calling it; no pun intended. ;-) --rworkman libraries/gstreamer: Added - gstreamer is a library that allows the construction of graphs of media-handling components, ranging from simple Ogg/Vorbis playback to complex audio (mixing) and video (non-linear editing) processing. libraries/libconfuse: Removed; renamed to confuse. --rworkman libraries/liboil: Added - liboil is a library of simple functions that are optimized for various CPUs. Thanks to Michiel van Wessem --David Somero multimedia/gst-plugins-bad: Added - gst-plugins-bad are gstreamer plug-ins that aren't up to par compared to the rest. multimedia/gst-plugins-base: Added - gst-plugins-base are gstreamer plug-ins that are well-groomed and well-maintained. multimedia/gst-plugins-good: Added - gst-plugins-good are gstreamer plug-ins that the developers consider to have good quality code. multimedia/gst-plugins-ugly: Added - gst-plugins-ugly are gstreamer plug-ins that have good quality and correct functionality, but distributing them might pose problems. Thanks to Michiel van Wessem for gstreamer. --David Somero multimedia/Songbird: Added - Songbird is a desktop media player. Thanks to Michiel van Wessem. --David Somero network/skype: Added skype (version 2.0.0.68) to the repository. Thanks to Mauro Giachero, our new maintainer for skype. --rworkman network/suphp: Updated for version 0.6.3. This update fixes a privilege escalation security flaw. See the CVE entry for more details: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1614 Thanks to Menno Duursma. --rworkman system/fglrx-driver: Added - this builds a standard Slackware package of the proprietary driver from ATI. I don't have the hardware to confirm that this works correctly, but it looks right :-) Thanks to Antonio Hern??????ndez Blas. --rworkman system/fglrx-module: Added - this builds the kernel module required by the proprietary ATI driver. Same disclaimer and credit as above. --rworkman system/htop: Updated for version 0.8. Thanks to Michiel van Wessem. --David Somero system/rkhunter: Added - rkhunter is a security monitoring and analyzing tool. Thanks to Michael Johnson. --David Somero system/wine: Updated for version 1.0rc1. Thanks to Robby Workman. --David Somero system/xbindkeys: Updated for version 1.8.2. Thanks to Erik Hanson. --David Somero From neobug at tornado.ktu.lt Thu May 15 10:12:46 2008 From: neobug at tornado.ktu.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 15 May 2008 13:12:46 +0300 Subject: [Slackbuilds-users] skype.SlackBuild contains a bug Message-ID: <20080515101246.GA14402@kiras> Hi, skype.SlackBuild contains a tiny bug: --- skype.SlackBuild.orig 2008-05-14 18:03:51.000000000 +0300 +++ skype.SlackBuild 2008-05-15 12:56:33.000000000 +0300 @@ -52,7 +52,7 @@ chmod -R u+w,go+r-w,a-s . chmod 644 sounds/* -mkdir -p $PKG/bin $PKG/usr/share/{skype,pixmaps,applications} \ +mkdir -p $PKG/usr/bin $PKG/usr/share/{skype,pixmaps,applications} \ $PKG/etc/dbus-1/system.d cp -a skype $PKG/usr/bin cp -a avatars sounds lang $PKG/usr/share/skype Due to this typo skype executable was copied to /usr directory as bin. I noticed this after installing the package, so I am not sure if there was any harm done to my system. Everything seems good so far after reinstalling fixed package. -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From mauro.giachero at gmail.com Thu May 15 13:37:39 2008 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Thu, 15 May 2008 15:37:39 +0200 Subject: [Slackbuilds-users] skype.SlackBuild contains a bug In-Reply-To: <20080515101246.GA14402@kiras> References: <20080515101246.GA14402@kiras> Message-ID: On Thu, May 15, 2008 at 12:12 PM, Audrius Ka?ukauskas wrote: > Hi, > > skype.SlackBuild contains a tiny bug: > [...] You're right, we'll fix this as soon as possible. As for the possible damages to your system, I think that as long as you still have a /usr/bin folder full of files you're safe :-) Thank you for the report, and sorry about that. Mauro -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Thu May 15 14:04:51 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 14:04:51 +0000 Subject: [Slackbuilds-users] Updates - 20080515 Message-ID: <20080515140451.GA7971@slackbuilds.org> Thu May 15 13:37:28 UTC 2008 audio/pulseaudio: Added - pulseaudio is a networked sound server intended to be a replacement for esd. Thanks to Heinz Wiesinger. --rworkman development/kdbg: Updated for version 2.1.0. Thanks to Aleksandar B. Samardzic. --Michiel development/sip: Updated for version 4.7.5. Thanks to Aleksandar B. Samardzic. --rworkman development/splint: Corrected a couple of absolute path usages in doinst.sh. Thanks to Michael Gehring for pointing them out. --rworkman development/swig: Updated for version 1.3.35. Thanks to Mauro Giachero. libraries/QuantLib: Added - QuantLib is a free open-source library for modeling, trading, and risk management in real-life. Thanks to Aleksandar Samardzic. --rworkman libraries/libatomic_ops: Added - libatomic_ops provides implementations for atomic memory update operations. Thanks to Heinz Wiesinger. --rworkman libraries/libsamplerate: Miscellaneous script cleanup. --rworkman libraries/libsndfile: Miscellaneous script cleanup. --rworkman libraries/pyqt4: Updated for version 4.4. Thanks to Aleksandar Samardzic. --rworkman libraries/wvstreams: Added - wvstreams is a networking library needed by wvdial. Thanks to Vincent Batts. --rworkman misc/gcolor2: Updated - Added a .desktop file to create a menu entry. Thanks to slakmagik for the update. --Michiel multimedia/herrie: Updated for version 2.0.2 and included an optional patch (written by our maintainer and slated for inclusion in the next version of herrie) to enable autoplay functionality. We like to see our contributors also being involved with upstream work. Thanks to Phil Warner. --Michiel network/darkstat: Added - darkstat is a small packaget/data sniffer which features a builtin webserver. Thanks to Jorey Bump. --Michiel network/newsbeuter: Updated for version 0.9.1. Thanks to slagmagik. --Michiel network/skype: Fixed a bug I introduced into the build script which resulted in a non-functional package. Thanks to Audrius Ka? ??ukauskasfor pointing out my PEBKAC. :-) --rworkman network/tcptrack: Updated to version 1.3.0. Thanks to Mauro Giachero. network/wireshark: Updated for version 1.0.0, which includes fixes for several potential security vulnerabilities present. For more information, see: http://www.wireshark.org/security/wnpa-sec-2008-02.html Thanks to Mauro Giachero. --rworkman network/wvdial: Added - wvdial is a simple command line dialer for ppp connections. Thanks to Vincent Batts. --rworkman system/xtermcontrol: Added - xtermcontrol allows dynamic control of xterm windows. Thanks to Michael Gehring. --rworkman From pc_warner at yahoo.com Thu May 15 15:47:52 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Thu, 15 May 2008 08:47:52 -0700 (PDT) Subject: [Slackbuilds-users] Updates - 20080515 In-Reply-To: <20080515140451.GA7971@slackbuilds.org> Message-ID: <139727.484.qm@web57709.mail.re3.yahoo.com> The herrie slackBuild is now under the new 'Audio' section of the repository instead of 'Multimedia'. I must say that I am very impressed with the speed at which updates are checked and posted on the slackBuilds.org site! Thank you slackBuilds.org team for all your effort! --phil Robby Workman wrote: Thu May 15 13:37:28 UTC 2008 audio/pulseaudio: Added - pulseaudio is a networked sound server intended to be a replacement for esd. Thanks to Heinz Wiesinger. --rworkman development/kdbg: Updated for version 2.1.0. Thanks to Aleksandar B. Samardzic. --Michiel development/sip: Updated for version 4.7.5. Thanks to Aleksandar B. Samardzic. --rworkman development/splint: Corrected a couple of absolute path usages in doinst.sh. Thanks to Michael Gehring for pointing them out. --rworkman development/swig: Updated for version 1.3.35. Thanks to Mauro Giachero. libraries/QuantLib: Added - QuantLib is a free open-source library for modeling, trading, and risk management in real-life. Thanks to Aleksandar Samardzic. --rworkman libraries/libatomic_ops: Added - libatomic_ops provides implementations for atomic memory update operations. Thanks to Heinz Wiesinger. --rworkman libraries/libsamplerate: Miscellaneous script cleanup. --rworkman libraries/libsndfile: Miscellaneous script cleanup. --rworkman libraries/pyqt4: Updated for version 4.4. Thanks to Aleksandar Samardzic. --rworkman libraries/wvstreams: Added - wvstreams is a networking library needed by wvdial. Thanks to Vincent Batts. --rworkman misc/gcolor2: Updated - Added a .desktop file to create a menu entry. Thanks to slakmagik for the update. --Michiel multimedia/herrie: Updated for version 2.0.2 and included an optional patch (written by our maintainer and slated for inclusion in the next version of herrie) to enable autoplay functionality. We like to see our contributors also being involved with upstream work. Thanks to Phil Warner. --Michiel network/darkstat: Added - darkstat is a small packaget/data sniffer which features a builtin webserver. Thanks to Jorey Bump. --Michiel network/newsbeuter: Updated for version 0.9.1. Thanks to slagmagik. --Michiel network/skype: Fixed a bug I introduced into the build script which resulted in a non-functional package. Thanks to Audrius Ka? ??ukauskasfor pointing out my PEBKAC. :-) --rworkman network/tcptrack: Updated to version 1.3.0. Thanks to Mauro Giachero. network/wireshark: Updated for version 1.0.0, which includes fixes for several potential security vulnerabilities present. For more information, see: http://www.wireshark.org/security/wnpa-sec-2008-02.html Thanks to Mauro Giachero. --rworkman network/wvdial: Added - wvdial is a simple command line dialer for ppp connections. Thanks to Vincent Batts. --rworkman system/xtermcontrol: Added - xtermcontrol allows dynamic control of xterm windows. Thanks to Michael Gehring. --rworkman _______________________________________________ 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 15 16:01:20 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 11:01:20 -0500 Subject: [Slackbuilds-users] Updates - 20080515 In-Reply-To: <139727.484.qm@web57709.mail.re3.yahoo.com> References: <139727.484.qm@web57709.mail.re3.yahoo.com> Message-ID: <482C5E50.1090909@slackbuilds.org> Phillip Warner wrote: > The herrie slackBuild is now under the new 'Audio' section of the > repository instead of 'Multimedia'. Oops. I've made so many stupid mistakes (mostly in credits) that I think I'll do an info update. Geez :/ > I must say that I am very impressed with the speed at which updates are > checked and posted on the slackBuilds.org site! Thank you > slackBuilds.org team for all your effort! Thanks :) -RW From asamardzic at gmail.com Thu May 15 16:26:15 2008 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Thu, 15 May 2008 18:26:15 +0200 Subject: [Slackbuilds-users] "orphaned" scripts Message-ID: I found couple of "my" scripts in the repository, that I have no incentive to update further, mostly because it happened that I don't use these tools/libraries any more, so - if anyone willing to take the maintainership over, please let us know. The scripts in question are: development/bugle development/kdbg libraries/osggis libraries/gdal libraries/OpenSceneGraph office/auctex Regards, Alex From michiel at slackbuilds.org Thu May 15 16:30:57 2008 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Thu, 15 May 2008 17:30:57 +0100 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: References: Message-ID: <200805151731.02583.michiel@slackbuilds.org> On Thursday 15 May 2008 17:26:15 Aleksandar Samardzic wrote: > development/kdbg I'll have no problem taking owner ship of this one :) M. -- http://slackbuilds.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From michiel at slackbuilds.org Thu May 15 16:33:32 2008 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Thu, 15 May 2008 17:33:32 +0100 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: References: Message-ID: <200805151733.32613.michiel@slackbuilds.org> As a further notice to 'orphaned' scripts in our repository, I recently received an email from Jick Nan who has given up his scripts. This means the following scripts are up for graps: Esetroot MySQL-python SilverCity castget docutils libstroke mod_python scim-fcitx stardict xautolock xosd I myself am intersted enough to take over his wireshark build. M. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From alien at slackbuilds.org Thu May 15 17:45:19 2008 From: alien at slackbuilds.org (Eric Hameleers) Date: Thu, 15 May 2008 19:45:19 +0200 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <200805151733.32613.michiel@slackbuilds.org> References: <200805151733.32613.michiel@slackbuilds.org> Message-ID: <482C76AF.6010908@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michiel van Wessem wrote: | As a further notice to 'orphaned' scripts in our repository, I recently | received an email from Jick Nan who has given up his scripts. This means the | following scripts are up for graps: | | Esetroot | MySQL-python | SilverCity | castget | docutils | libstroke | mod_python | scim-fcitx | stardict | xautolock | xosd | | I myself am intersted enough to take over his wireshark build. | | M. I'll take over stardict and xosd, and scim-fcitx too. Eric - -- Eric Hameleers >') ICQ: 151799386 ( \ Jabber: alien at jabber.xs4all.nl ^^` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILHaqXlaqr6dcvaARAsqEAJ4koOK19NYZQjqMPM/KQFMASVgzPACfVjif UAqyS1WTd0foD7XEGzEot/M= =w198 -----END PGP SIGNATURE----- From me at alkos333.net Thu May 15 17:51:04 2008 From: me at alkos333.net (alkos333) Date: Thu, 15 May 2008 12:51:04 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C76AF.6010908@slackbuilds.org> References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> Message-ID: Well, let's slide down the "slippery slope" as Robby so eloquently puts it every time :). If anybody would like to take over desktop/3ddesktop, feel free to do so because I don't use it anymore and have no interest in maintaining the script. On Thu, May 15, 2008 at 12:45 PM, Eric Hameleers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Michiel van Wessem wrote: > | As a further notice to 'orphaned' scripts in our repository, I recently > | received an email from Jick Nan who has given up his scripts. This > means the > | following scripts are up for graps: > | > | Esetroot > | MySQL-python > | SilverCity > | castget > | docutils > | libstroke > | mod_python > | scim-fcitx > | stardict > | xautolock > | xosd > | > | I myself am intersted enough to take over his wireshark build. > | > | M. > > I'll take over stardict and xosd, and scim-fcitx too. > > Eric > > - -- > > Eric Hameleers >') > ICQ: 151799386 ( \ > Jabber: alien at jabber.xs4all.nl ^^` > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFILHaqXlaqr6dcvaARAsqEAJ4koOK19NYZQjqMPM/KQFMASVgzPACfVjif > UAqyS1WTd0foD7XEGzEot/M= > =w198 > -----END PGP SIGNATURE----- > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From alien at slackbuilds.org Thu May 15 17:53:30 2008 From: alien at slackbuilds.org (Eric Hameleers) Date: Thu, 15 May 2008 19:53:30 +0200 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> Message-ID: <482C789A.1070208@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 alkos333 wrote: | Well, let's slide down the "slippery slope" as Robby so eloquently | puts it every time :). If anybody would like to take over | desktop/3ddesktop, feel free to do so because I don't use it anymore | and have no interest in maintaining the script. Perhaps we should start offering a "social contract" for anyone uploading a submission for SBo - say, we ask you to confirm that you stay responsible for your submission for at least 2 Slackware releases. Eric - -- Eric Hameleers >') ICQ: 151799386 ( \ Jabber: alien at jabber.xs4all.nl ^^` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILHiaXlaqr6dcvaARAhvNAJ9C+K8WhPKIsrq6qQpmJo/tdkMLEgCeL/IG hSX0r4ZL2pNXs7XKkb4WGnM= =ZoFr -----END PGP SIGNATURE----- From me at alkos333.net Thu May 15 17:58:12 2008 From: me at alkos333.net (alkos333) Date: Thu, 15 May 2008 12:58:12 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C789A.1070208@slackbuilds.org> References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> <482C789A.1070208@slackbuilds.org> Message-ID: There is no way to enforce such contract though. I would like to note that I will remain responsible for every script I have uploaded until somebody else volunteers to take over. On Thu, May 15, 2008 at 12:53 PM, Eric Hameleers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > alkos333 wrote: > | Well, let's slide down the "slippery slope" as Robby so eloquently > | puts it every time :). If anybody would like to take over > | desktop/3ddesktop, feel free to do so because I don't use it anymore > | and have no interest in maintaining the script. > > Perhaps we should start offering a "social contract" for anyone > uploading a submission for SBo - say, we ask you to confirm that you > stay responsible for your submission for at least 2 Slackware releases. > > Eric > > - -- > > Eric Hameleers >') > ICQ: 151799386 ( \ > Jabber: alien at jabber.xs4all.nl ^^` > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFILHiaXlaqr6dcvaARAhvNAJ9C+K8WhPKIsrq6qQpmJo/tdkMLEgCeL/IG > hSX0r4ZL2pNXs7XKkb4WGnM= > =ZoFr > -----END PGP SIGNATURE----- > _______________________________________________ > Slackbuilds-users mailing list > Slackbuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From alien at slackbuilds.org Thu May 15 18:02:26 2008 From: alien at slackbuilds.org (Eric Hameleers) Date: Thu, 15 May 2008 20:02:26 +0200 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> <482C789A.1070208@slackbuilds.org> Message-ID: <482C7AB2.9020707@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 alkos333 wrote: | There is no way to enforce such contract though. I would like to note | that I will remain responsible for every script I have uploaded until | somebody else volunteers to take over. | | On Thu, May 15, 2008 at 12:53 PM, Eric Hameleers wrote: | alkos333 wrote: | | Well, let's slide down the "slippery slope" as Robby so eloquently | | puts it every time :). If anybody would like to take over | | desktop/3ddesktop, feel free to do so because I don't use it anymore | | and have no interest in maintaining the script. | | Perhaps we should start offering a "social contract" for anyone | uploading a submission for SBo - say, we ask you to confirm that you | stay responsible for your submission for at least 2 Slackware releases. | | Eric Only joking (but still - we have to find a way to deal with scripts that get abandoned) ... Eric - -- Eric Hameleers >') ICQ: 151799386 ( \ Jabber: alien at jabber.xs4all.nl ^^` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILHqyXlaqr6dcvaARAg1aAJ9SbRRwekkXLpbV8H9jGXGgTjQS2QCcDB8T cYSR/Z6HKyFtUWeVWh623rg= =w89Z -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Thu May 15 18:08:03 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 13:08:03 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C789A.1070208@slackbuilds.org> References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> <482C789A.1070208@slackbuilds.org> Message-ID: <482C7C03.70506@slackbuilds.org> Eric Hameleers wrote: > Perhaps we should start offering a "social contract" for anyone > uploading a submission for SBo - say, we ask you to confirm that you > stay responsible for your submission for at least 2 Slackware releases. Just be careful with the patches. ;-) -RW From harmon at ksu.edu Thu May 15 18:10:26 2008 From: harmon at ksu.edu (Scott J. Harmon) Date: Thu, 15 May 2008 13:10:26 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C7AB2.9020707@slackbuilds.org> References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> <482C789A.1070208@slackbuilds.org> <482C7AB2.9020707@slackbuilds.org> Message-ID: <482C7C92.2040105@ksu.edu> Eric Hameleers wrote: > alkos333 wrote: > | There is no way to enforce such contract though. I would like to note > | that I will remain responsible for every script I have uploaded until > | somebody else volunteers to take over. > | > | On Thu, May 15, 2008 at 12:53 PM, Eric Hameleers > wrote: > | alkos333 wrote: > | | Well, let's slide down the "slippery slope" as Robby so eloquently > | | puts it every time :). If anybody would like to take over > | | desktop/3ddesktop, feel free to do so because I don't use it anymore > | | and have no interest in maintaining the script. > | > | Perhaps we should start offering a "social contract" for anyone > | uploading a submission for SBo - say, we ask you to confirm that you > | stay responsible for your submission for at least 2 Slackware releases. > | > | Eric > > Only joking (but still - we have to find a way to deal with scripts > that get abandoned) ... > > Eric > Why? If someone is interested in the package then they will maintain the script. If no one is interested, the script will sit. Scott. From pc_warner at yahoo.com Thu May 15 18:12:33 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Thu, 15 May 2008 11:12:33 -0700 (PDT) Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C789A.1070208@slackbuilds.org> Message-ID: <595315.23265.qm@web57705.mail.re3.yahoo.com> I personally have no problem with that, but some people may and this might discourage some good submissions. Perhaps a good compromise would be to make sure it doesn't sound too harsh or if it is only for one Slackware release. If the next release comes out and the maintainer doesn't update a script that doesn't work on the newest release, then it can simply be removed. It would be nice if maintainers would let us know when they no longer can/want to maintain a slackBuild, so maybe this could be asked of the person submitting a script. Something that also might be really useful is to start an official list of orphaned and recently removed scripts. That way a person could look at that one file and then email the user list to say "Hey, I'll take it. Here's my submission." I know this could be accomplished through threads like this, but it might be more convenient to have it all in once place instead of spread through many messages. Ideally, this would be included on the site similar to the Changelog, but I understand if the admins don't want another file to maintain. --phil Eric Hameleers wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 alkos333 wrote: | Well, let's slide down the "slippery slope" as Robby so eloquently | puts it every time :). If anybody would like to take over | desktop/3ddesktop, feel free to do so because I don't use it anymore | and have no interest in maintaining the script. Perhaps we should start offering a "social contract" for anyone uploading a submission for SBo - say, we ask you to confirm that you stay responsible for your submission for at least 2 Slackware releases. Eric - -- Eric Hameleers >') ICQ: 151799386 ( \ Jabber: alien at jabber.xs4all.nl ^^` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILHiaXlaqr6dcvaARAhvNAJ9C+K8WhPKIsrq6qQpmJo/tdkMLEgCeL/IG hSX0r4ZL2pNXs7XKkb4WGnM= =ZoFr -----END PGP SIGNATURE----- _______________________________________________ Slackbuilds-users mailing list Slackbuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Thu May 15 18:21:58 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 13:21:58 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <595315.23265.qm@web57705.mail.re3.yahoo.com> References: <595315.23265.qm@web57705.mail.re3.yahoo.com> Message-ID: <482C7F46.1090801@slackbuilds.org> Phillip Warner wrote: > I personally have no problem with that, but some people may and this > might discourage some good submissions. Perhaps a good compromise would > be to make sure it doesn't sound too harsh or if it is only for one > Slackware release. If the next release comes out and the maintainer > doesn't update a script that doesn't work on the newest release, then it > can simply be removed. It would be nice if maintainers would let us > know when they no longer can/want to maintain a slackBuild, so maybe > this could be asked of the person submitting a script. > > Something that also might be really useful is to start an official list > of orphaned and recently removed scripts. That way a person could look > at that one file and then email the user list to say "Hey, I'll take > it. Here's my submission." I know this could be accomplished through > threads like this, but it might be more convenient to have it all in > once place instead of spread through many messages. Ideally, this would > be included on the site similar to the Changelog, but I understand if > the admins don't want another file to maintain. We were just talking about doing something like that - we think it will help *us* too :) -RW From pc_warner at yahoo.com Thu May 15 18:25:33 2008 From: pc_warner at yahoo.com (Phillip Warner) Date: Thu, 15 May 2008 11:25:33 -0700 (PDT) Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C7AB2.9020707@slackbuilds.org> Message-ID: <86232.7255.qm@web57710.mail.re3.yahoo.com> I would hope that all the script maintainers are a part of this mailing list, but I think that that would be a poor assumption. In light of that, perhaps it would be helpful to automatically add the maintainers email to a mailing list when they submit a script. I do not mean this list, but rather one that is to be used only occasionally. For instance, when the next version of Slackware is about to be released an email is usually sent to this list to let us know what that the repository will be rolling over soon and there are some changes to the new Slackware version that may break ___ type of scripts. This one time email per Slackware release could be sent to all the maintainers via this special mailing list. This would remind maintainers that they are maintainers, and to let them know that if they haven't done so recently they should take a look at their script to see if it is still up to date and compatible. --phil Eric Hameleers wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 alkos333 wrote: | There is no way to enforce such contract though. I would like to note | that I will remain responsible for every script I have uploaded until | somebody else volunteers to take over. | | On Thu, May 15, 2008 at 12:53 PM, Eric Hameleers wrote: | alkos333 wrote: | | Well, let's slide down the "slippery slope" as Robby so eloquently | | puts it every time :). If anybody would like to take over | | desktop/3ddesktop, feel free to do so because I don't use it anymore | | and have no interest in maintaining the script. | | Perhaps we should start offering a "social contract" for anyone | uploading a submission for SBo - say, we ask you to confirm that you | stay responsible for your submission for at least 2 Slackware releases. | | Eric Only joking (but still - we have to find a way to deal with scripts that get abandoned) ... Eric - -- Eric Hameleers >') ICQ: 151799386 ( \ Jabber: alien at jabber.xs4all.nl ^^` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILHqyXlaqr6dcvaARAg1aAJ9SbRRwekkXLpbV8H9jGXGgTjQS2QCcDB8T cYSR/Z6HKyFtUWeVWh623rg= =w89Z -----END PGP SIGNATURE----- _______________________________________________ Slackbuilds-users mailing list Slackbuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From chess at chessgriffin.com Thu May 15 18:31:28 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 15 May 2008 14:31:28 -0400 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C7F46.1090801@slackbuilds.org> References: <595315.23265.qm@web57705.mail.re3.yahoo.com> <482C7F46.1090801@slackbuilds.org> Message-ID: <482C8180.9060607@chessgriffin.com> Robby Workman wrote: > Phillip Warner wrote: >> I personally have no problem with that, but some people may and this >> might discourage some good submissions. Perhaps a good compromise >> would be to make sure it doesn't sound too harsh or if it is only for >> one Slackware release. If the next release comes out and the >> maintainer doesn't update a script that doesn't work on the newest >> release, then it can simply be removed. It would be nice if >> maintainers would let us know when they no longer can/want to maintain >> a slackBuild, so maybe this could be asked of the person submitting a >> script. >> >> Something that also might be really useful is to start an official >> list of orphaned and recently removed scripts. That way a person >> could look at that one file and then email the user list to say "Hey, >> I'll take it. Here's my submission." I know this could be >> accomplished through threads like this, but it might be more >> convenient to have it all in once place instead of spread through many >> messages. Ideally, this would be included on the site similar to the >> Changelog, but I understand if the admins don't want another file to >> maintain. > > > We were just talking about doing something like that - we think it > will help *us* too :) > > -RW If an unmaintained script still works, though, couldn't it remain in the repo until such time as it no longer works? Orphaned does not have to mean removed. Unmaintained ports in BSD's are almost always left in the ports tree and the maintainer is changed to the ports team in general. Same with Debian, where some packages are maintained by a group or team. In this case, I'm not suggesting that SBo admins maintain and update orphaned scripts. That's adding more work to the team. But, maybe changing MAINTAINER to NONE and leaving an orphaned script in the repo could be a compromise to outright removal -- so long as it works and is not a security problem. The list Phil and Robby mention could also be kept, as an easy place to search for orphaned scripts. Someone might want to help the project and taking over an unmaintained script would be a good way to do it. Just a thought. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From chess at chessgriffin.com Thu May 15 18:34:55 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 15 May 2008 14:34:55 -0400 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <86232.7255.qm@web57710.mail.re3.yahoo.com> References: <86232.7255.qm@web57710.mail.re3.yahoo.com> Message-ID: <482C824F.9080904@chessgriffin.com> Phillip Warner wrote: > I would hope that all the script maintainers are a part of this > mailing list, but I think that that would be a poor assumption. In > light of that, perhaps it would be helpful to automatically add the > maintainers email to a mailing list when they submit a script. I do > not mean this list, but rather one that is to be used only > occasionally. > > For instance, when the next version of Slackware is about to be > released an email is usually sent to this list to let us know what > that the repository will be rolling over soon and there are some > changes to the new Slackware version that may break ___ type of > scripts. This one time email per Slackware release could be sent to > all the maintainers via this special mailing list. This would remind > maintainers that they are maintainers, and to let them know that if > they haven't done so recently they should take a look at their script > to see if it is still up to date and compatible. > > --phil This is a good idea. Maybe a slackbuilds-maintainers list that can be public or private but one to which maintainers are automatically added -- something akin to Eric's 'social contract'. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Thu May 15 18:39:48 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 13:39:48 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <86232.7255.qm@web57710.mail.re3.yahoo.com> References: <86232.7255.qm@web57710.mail.re3.yahoo.com> Message-ID: <482C8374.1040000@slackbuilds.org> Phillip Warner wrote: > I would hope that all the script maintainers are a part of this mailing > list, but I think that that would be a poor assumption. In light of > that, perhaps it would be helpful to automatically add the maintainers > email to a mailing list when they submit a script. I do not mean this > list, but rather one that is to be used only occasionally. > > For instance, when the next version of Slackware is about to be released > an email is usually sent to this list to let us know what that the > repository will be rolling over soon and there are some changes to the > new Slackware version that may break ___ type of scripts. This one time > email per Slackware release could be sent to all the maintainers via > this special mailing list. This would remind maintainers that they are > maintainers, and to let them know that if they haven't done so recently > they should take a look at their script to see if it is still up to date > and compatible. Yeah, we had discussed doing that quite some time ago, but never reached a real consensus. I'm not too keen on unrequested mailing list subscriptions, so that's a point of contention, but otherwise, I agree that the idea is not a bad one. -RW From LBrabson at behr.com Thu May 15 18:40:27 2008 From: LBrabson at behr.com (LBrabson at behr.com) Date: Thu, 15 May 2008 13:40:27 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C8374.1040000@slackbuilds.org> Message-ID: take me off your mailing list! Robby Workman Sent by: slackbuilds-users-bounces at slackbuilds.org 05/15/2008 01:39 PM Please respond to "SlackBuilds.org Users List" To "SlackBuilds.org Users List" cc Subject Re: [Slackbuilds-users] "orphaned" scripts Phillip Warner wrote: > I would hope that all the script maintainers are a part of this mailing > list, but I think that that would be a poor assumption. In light of > that, perhaps it would be helpful to automatically add the maintainers > email to a mailing list when they submit a script. I do not mean this > list, but rather one that is to be used only occasionally. > > For instance, when the next version of Slackware is about to be released > an email is usually sent to this list to let us know what that the > repository will be rolling over soon and there are some changes to the > new Slackware version that may break ___ type of scripts. This one time > email per Slackware release could be sent to all the maintainers via > this special mailing list. This would remind maintainers that they are > maintainers, and to let them know that if they haven't done so recently > they should take a look at their script to see if it is still up to date > and compatible. Yeah, we had discussed doing that quite some time ago, but never reached a real consensus. I'm not too keen on unrequested mailing list subscriptions, so that's a point of contention, but otherwise, I agree that the idea is not a bad one. -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 -------------- An HTML attachment was scrubbed... URL: From LBrabson at behr.com Thu May 15 18:41:41 2008 From: LBrabson at behr.com (LBrabson at behr.com) Date: Thu, 15 May 2008 13:41:41 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: Message-ID: take me off your list -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Thu May 15 18:51:52 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 13:51:52 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: References: Message-ID: <482C8648.90507@slackbuilds.org> LBrabson at behr.com wrote: > > take me off your list Take yourself off. I didn't put you here, and I'm not removing you. -RW From rworkman at slackbuilds.org Thu May 15 19:05:30 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 14:05:30 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C8648.90507@slackbuilds.org> References: <482C8648.90507@slackbuilds.org> Message-ID: <482C897A.1090806@slackbuilds.org> Robby Workman wrote: > LBrabson at behr.com wrote: >> >> take me off your list > > > Take yourself off. I didn't put you here, and I'm not removing you. > > -RW Jeez, it's been four months and you *still* haven't figured it out? http://lists.slackbuilds.org/pipermail/slackbuilds-users/2008-January/002156.html Follow the information link at the bottom of this mail - it's *really* not difficult. -RW From chess at chessgriffin.com Thu May 15 20:27:03 2008 From: chess at chessgriffin.com (Chess Griffin) Date: Thu, 15 May 2008 16:27:03 -0400 Subject: [Slackbuilds-users] Updates - 20080515 In-Reply-To: <139727.484.qm@web57709.mail.re3.yahoo.com> References: <139727.484.qm@web57709.mail.re3.yahoo.com> Message-ID: <482C9C97.1050109@chessgriffin.com> Phillip Warner wrote: > The herrie slackBuild is now under the new 'Audio' section of the > repository instead of 'Multimedia'. > > I must say that I am very impressed with the speed at which updates > are checked and posted on the slackBuilds.org site! Thank you > slackBuilds.org team for all your effort! > > --phil > I agree, and thanks to all the maintainers and contributors for the great updates and new additions. The repo has got a lot of really, really great software for Slackware. -- Chess Griffin GPG Key: 0x0C7558C3 http://www.chessgriffin.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Thu May 15 20:45:43 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 May 2008 20:45:43 +0000 Subject: [Slackbuilds-users] Updates #2 - 20080515 Message-ID: <20080515204543.GA22793@slackbuilds.org> Thu May 15 20:34:04 UTC 2008 First, I owe a big apology to Michael Gehring, so I'll do it publicly. His "mg@" email address tricked me into thinking of Mauro Giachero on the tcptrack and wireshark builds, and I credited the maintainer of kdbg instead of him on that one. Thanks in advance for patience and understanding, Michael :-) Second, herrie is actually in Audio rather than Multimedia. Finally, here's another (small) update: audio/amrnb: Updated for version 7.0.0.1. Thanks to Heinz Wiesinger. libraries/libarchive: Updated for version 2.4.17. Thanks to Heinz Wiesinger. --rworkman libraries/libpar2: Added - libpar2 allows for the generation, modification, verification of PAR archives. Thanks to Daniel. --rworkman libraries/python-mpd: Added - python-mpd is an MPD client library. Thanks to Andrew Brouwers. --rworkman network/nginx: Updated for version 0.6.31. Thanks to Cherife Li. --rworkman system/graveman: Fixed the docs copying line in the build script. Thanks to Pierce Lopez for the bug report and to Chess Griffin for passing it along to us. --rworkman system/lapsus: Updated for version 0.0.6. Thanks to Heinz Wiesinger. From listreader at lupulin.net Thu May 15 21:21:58 2008 From: listreader at lupulin.net (pkw) Date: Thu, 15 May 2008 17:21:58 -0400 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C789A.1070208@slackbuilds.org> References: <200805151733.32613.michiel@slackbuilds.org> <482C76AF.6010908@slackbuilds.org> <482C789A.1070208@slackbuilds.org> Message-ID: <20080515212158.GA1993@hubris.lan> On Thu, May 15, 2008 at 07:53:30PM +0200, Eric Hameleers wrote: > Perhaps we should start offering a "social contract" for anyone > uploading a submission for SBo - say, we ask you to confirm that you > stay responsible for your submission for at least 2 Slackware releases. There should be something on the web page explaining what the expectations are WRT being a maintainer. -- paul w From boxcars at gmx.net Thu May 15 22:55:50 2008 From: boxcars at gmx.net (=?ISO-8859-1?B?u1Gr?=) Date: Thu, 15 May 2008 17:55:50 -0500 Subject: [Slackbuilds-users] gnubg - no sound or 3D boards Message-ID: <20080515175550.75a3bcbe@bellgrove.remarqs.net> The 12.1 slackbuild for gnubg gives me an install without sound or the 3D board options. I'm sorry I don't know enough about the build system to troubleshoot. From the output of gnubg, it looks like the sound files aren't in place. I'll be glad to post more info, but you'd have to walk me through what I need to do. (I can log the build process without hand-holding, but I'm not at the Slackware machine right now -- just let me know if posting log(s) would help.) -- ?Q? From erik at slackbuilds.org Fri May 16 00:41:37 2008 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 15 May 2008 19:41:37 -0500 Subject: [Slackbuilds-users] gnubg - no sound or 3D boards In-Reply-To: <20080515175550.75a3bcbe@bellgrove.remarqs.net> References: <20080515175550.75a3bcbe@bellgrove.remarqs.net> Message-ID: <20080515194137.103beec9@shaggy.scooby> On May 15, 2008, at 5:55 PM, ?Q? wrote: > I'll be glad to post more info, but you'd have to walk me through what > I need to do. (I can log the build process without hand-holding, but > I'm not at the Slackware machine right now -- just let me know if > posting log(s) would help.) I was just playing, 3D with sounds. Please post the build log. -- Erik Hanson http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From boxcars at gmx.net Fri May 16 05:24:37 2008 From: boxcars at gmx.net (=?ISO-8859-1?B?u1Gr?=) Date: Fri, 16 May 2008 00:24:37 -0500 Subject: [Slackbuilds-users] gnubg - no sound or 3D boards References: <20080515175550.75a3bcbe@bellgrove.remarqs.net> <20080515194137.103beec9@shaggy.scooby> Message-ID: <20080516002437.608b030f@bellgrove.remarqs.net> On Thu, 15 May 2008 19:41:37 -0500 Erik Hanson wrote: > I was just playing, 3D with sounds. Please post the build log. It looks like the 3D board stuff is being built, but I don't have those options in the Appearance settings. As for sounds, I was wrong about them not being there. The sounds are put in the right place (/usr/share/gnubg/sounds/) but they don't play. This may just be a problem with my sound setup, though the gnubg wavs play fine with noatun. From erik at slackbuilds.org Fri May 16 06:20:37 2008 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 16 May 2008 01:20:37 -0500 Subject: [Slackbuilds-users] gnubg - no sound or 3D boards In-Reply-To: <20080516002437.608b030f@bellgrove.remarqs.net> References: <20080515175550.75a3bcbe@bellgrove.remarqs.net> <20080515194137.103beec9@shaggy.scooby> <20080516002437.608b030f@bellgrove.remarqs.net> Message-ID: <20080516012037.077f72d4@shaggy.scooby> On May 16, 2008, at 12:24 AM, ?Q? wrote: > On Thu, 15 May 2008 19:41:37 -0500 > Erik Hanson wrote: > > > > It looks like the 3D board stuff is being built, but I don't have > those options in the Appearance settings. I think you are missing gtkglext, looks like I failed to mention that as an optional dep in the README. This is from your log: checking for GTKGLEXT... checking for --with-python... enabled by default checking for python... /usr/bin/python This is mine: checking for GTKGLEXT... yes checking for --with-python... enabled by default checking for python... /usr/bin/python You can grab it here: http://slackbuilds.org/repository/12.1/libraries/gtkglext/ I am submitting an update to SBo in a few moments. -- Erik Hanson http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From boxcars at gmx.net Fri May 16 07:35:11 2008 From: boxcars at gmx.net (=?ISO-8859-1?Q?=BBQ=AB?=) Date: Fri, 16 May 2008 02:35:11 -0500 Subject: [Slackbuilds-users] gnubg - no sound or 3D boards [solved] References: <20080515175550.75a3bcbe@bellgrove.remarqs.net> <20080515194137.103beec9@shaggy.scooby> <20080516002437.608b030f@bellgrove.remarqs.net> <20080516012037.077f72d4@shaggy.scooby> Message-ID: <20080516023511.24d4f3d1@prezmyra.remarqs.net> In <20080516012037.077f72d4 at shaggy.scooby>, Erik Hanson wrote: > I think you are missing gtkglext, looks like I failed to mention that > as an optional dep in the README. That was it. Thanks very much for looking into it, and so quickly! As for sound, I just needed to tell gnubg to use the command "play" for sounds, under Settings ? Options ? Sound. -- ?Q? Kleeneness is next to G?delness. From fred.galusik at gmail.com Fri May 16 08:32:53 2008 From: fred.galusik at gmail.com (Fred Galusik) Date: Fri, 16 May 2008 10:32:53 +0200 Subject: [Slackbuilds-users] tilda update Message-ID: <482D46B5.50405@gmail.com> Hi, Just to say that the tilda page needs an update : http://slackbuilds.org/repository/12.1/system/tilda/ The download link (tilda 9.4) is deprecated as tilda 9.6 is out, here is the new one : http://downloads.sourceforge.net/tilda/tilda-0.9.6.tar.gz?modtime=1209379739&big_mirror=0 The SlackBuild just needs this minor change : VERSION=0.9.6 Cheers. ++ fredg From temporal at coconutspa.com Fri May 16 10:28:23 2008 From: temporal at coconutspa.com (Jenny Atkin) Date: Fri, 16 May 2008 10:28:23 +0000 Subject: [Slackbuilds-users] quasars natatorium Message-ID: <3162568692.20080516102458@coconutspa.com> Bonjour, Real men! Millionns of people acrosss the world have already tested THIS and ARE making their girlfrriends feel brand new sexual sensaations! YOU are the best in bed, aren't you ?Girls! Deevelop your sexual relattionship and get even MORE pleasuure! Make your booyfriend a gift! http://www.google.de/pagead/iclk?sa=l&ai=afiMiH&adurl=%68%74%74%70%3A%2F%2F%6D%65%74%68%6F%64%70%72%6F%64%75%63%65%2E%63%6F%6D Pranava, always succeed in gratifying others.1171 her, and tearing her letter in pieces the governess that impulse would, he realized, place a portion head in at the door. mind you, abe, you forget arms at a crisis like the present. colonel benjamin the result of their modification. The ear, the kunti's son yudhishthira, summoning all his brothers, sun himself at midday scorching everything around with the blessings of the gospel? From what scriptural others, lord colambre was one. 'experience,' as purposes of the gods. and, o best of men, know mordicai with a degree of familiarity, which, race. Then yudhishthira once more summoned all animals. and they are engaged in hostilities with had known that miss gertrude white's awakening. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob0 at slackbuilds.org Fri May 16 13:45:41 2008 From: rob0 at slackbuilds.org (Rob McGee) Date: Fri, 16 May 2008 08:45:41 -0500 Subject: [Slackbuilds-users] list spam In-Reply-To: <3162568692.20080516102458@coconutspa.com> References: <3162568692.20080516102458@coconutspa.com> Message-ID: <200805160845.42063.rob0@slackbuilds.org> I will set about the task of getting a content filter on here ASAP, which might mean early next week. But would you Google fans get a load of (but don't go to) this, the spam URL ... > http://www.google.de/pagead/iclk?sa=l&ai=afiMiH&adurl=%68%74%74%70%3A%2F%2F%6D%65%74%68%6F%64%70%72%6F%64%75%63%65%2E%63%6F%6D What a crock. How the heck is SpamAssassin supposed to catch something like that? Yet another example of Google's clueless spam support. Want to see another one, the one that first showed me that this problem existed? http://www.send-safe.com/ Yes, go to that one. Scroll down to the bottom of the page for the MAILTO: link. It has been there for years. I personally reported it to Google's unmanned abuse at gmail.com address. Ignored. Send-safe is botnet ratware. Google makes it possible for that bastard to collect money from spammers, who in turn send us crap like the above Google link. Google is NOT your friend. From rworkman at slackbuilds.org Fri May 16 14:06:51 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 16 May 2008 09:06:51 -0500 Subject: [Slackbuilds-users] Google and spam [was: list spam] In-Reply-To: <200805160845.42063.rob0@slackbuilds.org> References: <3162568692.20080516102458@coconutspa.com> <200805160845.42063.rob0@slackbuilds.org> Message-ID: <482D94FB.3020709@slackbuilds.org> Rob McGee wrote: > I will set about the task of getting a content filter on here ASAP, > which might mean early next week. But would you Google fans get a load > of (but don't go to) this, the spam URL ... > > http://www.google.de/pagead/iclk?sa=l&ai=afiMiH&adurl=%68%74%74%70%3A%2F%2F%6D%65%74%68%6F%64%70%72%6F%64%75%63%65%2E%63%6F%6D > > What a crock. How the heck is SpamAssassin supposed to catch something > like that? Yet another example of Google's clueless spam support. > > Want to see another one, the one that first showed me that this problem > existed? > http://www.send-safe.com/ > Yes, go to that one. Scroll down to the bottom of the page for the > MAILTO: link. It has been there for years. I personally reported it to > Google's unmanned abuse at gmail.com address. Ignored. > > Send-safe is botnet ratware. Google makes it possible for that bastard > to collect money from spammers, who in turn send us crap like the above > Google link. > > Google is NOT your friend. Just to add a bit more to that last thought, here's an interesting link from the bugtraq security list: http://www.securityfocus.com/archive/1/491779/30/60/threaded There were quite a few replies, so if you can figure out how to see the rest of the thread, it's worth a read. -RW From danielsoro at gmail.com Sat May 17 00:10:54 2008 From: danielsoro at gmail.com (Daniel Victor L. Cunha) Date: Fri, 16 May 2008 21:10:54 -0300 Subject: [Slackbuilds-users] libraries/lame Message-ID: <482E228E.3010303@gmail.com> Hi, New link for source: http://ufpr.dl.sourceforge.net/sourceforge/lame/lame-3.97.tar.gz -- att; soro, Daniel Victor L. Cunha danielsoro at gmail.com From michiel at slackbuilds.org Sat May 17 00:15:40 2008 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Sat, 17 May 2008 01:15:40 +0100 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: <482E228E.3010303@gmail.com> References: <482E228E.3010303@gmail.com> Message-ID: <200805170115.46261.michiel@slackbuilds.org> On Saturday 17 May 2008 01:10:54 Daniel Victor L. Cunha wrote: > Hi, > > New link for source: > http://ufpr.dl.sourceforge.net/sourceforge/lame/lame-3.97.tar.gz Thanks, I'll update the relevant info. M. -- http://slackbuilds.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From michiel at slackbuilds.org Sat May 17 00:29:41 2008 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Sat, 17 May 2008 01:29:41 +0100 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: <200805170115.46261.michiel@slackbuilds.org> References: <482E228E.3010303@gmail.com> <200805170115.46261.michiel@slackbuilds.org> Message-ID: <200805170129.46185.michiel@slackbuilds.org> On Saturday 17 May 2008 01:15:40 Michiel van Wessem wrote: > On Saturday 17 May 2008 01:10:54 Daniel Victor L. Cunha wrote: > > Hi, > > > > New link for source: > > http://ufpr.dl.sourceforge.net/sourceforge/lame/lame-3.97.tar.gz > my bad actually for not properly looking. The link in the .info is perfectly valid. dl.sourceforge.net is the round robbin database that points to the different sourceforge mirrors. I am going to guess that you hit a bad mirror and found one that worked. this issue is already described in http://slackbuilds.org/faq/#badlink .. M. -- http://slackbuilds.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From rworkman at slackbuilds.org Sat May 17 04:00:11 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 16 May 2008 23:00:11 -0500 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: <200805170129.46185.michiel@slackbuilds.org> References: <482E228E.3010303@gmail.com> <200805170115.46261.michiel@slackbuilds.org> <200805170129.46185.michiel@slackbuilds.org> Message-ID: <482E584B.3090700@slackbuilds.org> Michiel van Wessem wrote: > my bad actually for not properly looking. The link in the .info is > perfectly valid. dl.sourceforge.net is the round robbin database that > points to the different sourceforge mirrors. > > I am going to guess that you hit a bad mirror and found one that worked. > > this issue is already described in http://slackbuilds.org/faq/#badlink .. Holy crap, what's with the html email? Was that you, or did I manage to royally screw up my mail client, or both? Anyway, I think we need an official statement about the sf mirrors. I've found that using "downloads." is always more reliable than "dl." so perhaps we should note that in our submission guidelines. -RW From abrouwers at gmail.com Sat May 17 19:08:00 2008 From: abrouwers at gmail.com (Andrew Brouwers) Date: Sat, 17 May 2008 15:08:00 -0400 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: <482E584B.3090700@slackbuilds.org> References: <482E228E.3010303@gmail.com> <200805170115.46261.michiel@slackbuilds.org> <200805170129.46185.michiel@slackbuilds.org> <482E584B.3090700@slackbuilds.org> Message-ID: <196c22970805171208n6bacbad3xc44393241576a70a@mail.gmail.com> No, HTML email here too :) Another trick for the sourceforge mirrors is to force one in /etc/hosts: 193.1.193.66 download.sourceforge.net download.sf.net dl.sourceforge.net dl.sf.net - Andrew From me at alkos333.net Sat May 17 19:22:28 2008 From: me at alkos333.net (alkos333) Date: Sat, 17 May 2008 14:22:28 -0500 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: <196c22970805171208n6bacbad3xc44393241576a70a@mail.gmail.com> References: <482E228E.3010303@gmail.com> <200805170115.46261.michiel@slackbuilds.org> <200805170129.46185.michiel@slackbuilds.org> <482E584B.3090700@slackbuilds.org> <196c22970805171208n6bacbad3xc44393241576a70a@mail.gmail.com> Message-ID: Definitely HTML :) On Sat, May 17, 2008 at 2:08 PM, Andrew Brouwers wrote: > No, HTML email here too :) > > Another trick for the sourceforge mirrors is to force one in /etc/hosts: > > 193.1.193.66 download.sourceforge.net download.sf.net > dl.sourceforge.net dl.sf.net > > - Andrew > _______________________________________________ > 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 michiel at slackbuilds.org Sat May 17 19:41:43 2008 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Sat, 17 May 2008 20:41:43 +0100 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: References: <482E228E.3010303@gmail.com> <196c22970805171208n6bacbad3xc44393241576a70a@mail.gmail.com> Message-ID: <200805172041.52318.michiel@slackbuilds.org> On Saturday 17 May 2008 20:22:28 alkos333 wrote: > Definitely HTML :) > atleast I don't toppost ;) And just to stop everyone replying that yes it was an html email. Kmail clearly decided all on his own to do $REALLY_WEIRD_STUFF. Mea culpa. M. -- http://slackbuilds.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From palatally at eparrs.com Sun May 18 08:47:29 2008 From: palatally at eparrs.com (Danielle Matsumura) Date: Sun, 18 May 2008 08:47:29 +0000 Subject: [Slackbuilds-users] hobos settling Message-ID: <3705926043.20080518084713@eparrs.com> Oi, Real men! Millioons of people accross the world have already tested THIS and ARE making their girlffriends feel brand new sexual sennsations! YOU are the best in bed, aren't you ?Girls! DDevelop your sexual relaationship and get even MORE pleasuure! Make your boyfriendd a gift! http://www.google.de/pagead/iclk?sa=l&ai=afiMiH&adurl=%68%74%74%70%3A%2F%2F%69%6E%74%65%72%65%73%74%67%65%6E%74%6C%65%2E%63%6F%6D Very pretty to set off a fresh face, had served belonged to the ancient time, to a time when there a bit thick. You're 'you lack the brains and the in a number of morning newspapers, and i was sitting just little questions that he slipped in, or comments, one almost wished one could have trembled when bent of mrs. Poyser's mind with regard to adam annoying. all those restrictions. Nevertheless, burgs. It would astonish you to know how much time the police probably know that you have come ideas come to me! What kind of ideas ? The most in the little parlour among the china dogs. You his death, has been pointed out to me by my friend was a devoted creature and she carried out his the western sky and the shadows crept down from. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at markwalling.org Mon May 19 12:47:42 2008 From: mark at markwalling.org (Mark Walling) Date: Mon, 19 May 2008 08:47:42 -0400 Subject: [Slackbuilds-users] libraries/lame In-Reply-To: <200805172041.52318.michiel@slackbuilds.org> References: <482E228E.3010303@gmail.com> <196c22970805171208n6bacbad3xc44393241576a70a@mail.gmail.com> <200805172041.52318.michiel@slackbuilds.org> Message-ID: <20080519124742.GH19152@you> On 05/17/08, Michiel van Wessem wrote: > > On Saturday 17 May 2008 20:22:28 alkos333 wrote: > > Definitely HTML :) > > > atleast I don't toppost ;) > > And just to stop everyone replying that yes it was an html email. Kmail > clearly decided all on his own to do $REALLY_WEIRD_STUFF. > > Mea culpa. > > M. > I didn't see any HTML :) ( <3 mutt ) -M -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue May 20 15:20:39 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 20 May 2008 15:20:39 +0000 Subject: [Slackbuilds-users] Updates - 20080520 Message-ID: <20080520152039.GA8724@slackbuilds.org> Tue May 20 15:18:13 UTC 2008 academic/celestia: Updated for version 1.5.1. Thanks to Heinz Wiesinger. --David Somero audio/sonata: Updated for version 1.5.1. Thanks to Andrew Brouwers. --David Somero development/yasm: Added - Yasm is a complete rewrite of the NASM assembler under the "new" BSD License. Thanks to Heinz Wiesinger. --rworkman games/ltris: Updated for version 1.0.12. Thanks to Bill Kirkpatrick. games/nethack: Added - nethack is a single player dungeon exploration game. Thanks to Wade Nelson. --David Somero games/openarena: Updated for version 0.7.6. Thanks to Chess Griffin. --David Somero libraries/sqlite: Updated for version 3.5.9. Thanks to Robby Workman. --David Somero network/cfengine: Update for version 2.2.6. Thanks to Menno E. Duursma. --David Somero office/kmymoney2: Updated for version 0.9. Thanks to Michiel van Wessem. From druiloor at zonnet.nl Tue May 20 20:34:53 2008 From: druiloor at zonnet.nl (Menno Duursma) Date: Tue, 20 May 2008 22:34:53 +0200 (CEST) Subject: [Slackbuilds-users] Updates - 20080520 In-Reply-To: <20080520152039.GA8724@slackbuilds.org> References: <20080520152039.GA8724@slackbuilds.org> Message-ID: On Tue, 20 May 2008, Robby Workman wrote: > network/cfengine: Update for version 2.2.6. > Thanks to Menno E. Duursma. --David Somero This seems to have gone wrong somehow, i didn't remember this to be in 'system' before but alas it was (and still is) ... The build does seem to work right, appart from it including some empty dirs (which, mind you, is entirely my mistake) thing is i don't really understand what the 'tags' field in the submission page does, or is supposed to do. Especially for scripts that are an update of what is in de repo already. Reason why i changed that: Cfengine can be used on systems having no network capabilities as a generic system config tool, however it is _much_ more usefull on IP networked systems, and i reckon generaly used as such ... Cheers, -Menno. From rworkman at slackbuilds.org Tue May 20 20:45:45 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 20 May 2008 15:45:45 -0500 Subject: [Slackbuilds-users] Updates - 20080520 In-Reply-To: References: <20080520152039.GA8724@slackbuilds.org> Message-ID: <48333879.3010009@slackbuilds.org> Menno Duursma wrote: > On Tue, 20 May 2008, Robby Workman wrote: > >> network/cfengine: Update for version 2.2.6. >> Thanks to Menno E. Duursma. --David Somero > > This seems to have gone wrong somehow, i didn't remember this to > be in 'system' before but alas it was (and still is) ... > > The build does seem to work right, appart from it including some > empty dirs (which, mind you, is entirely my mistake) thing is i > don't really understand what the 'tags' field in the submission > page does, or is supposed to do. Especially for scripts that > are an update of what is in de repo already. > > Reason why i changed that: > > Cfengine can be used on systems having no network capabilities > as a generic system config tool, however it is _much_ more usefull > on IP networked systems, and i reckon generaly used as such ... Ack. I fixed the ChangeLog entry (sorry for the RSS spam) :) and will leave it in System for the reasons you outlined above. The tags are search tags - things that users can type into our search field and return cfengine as one of the results. For things that are updates, it's perfectly acceptable to leave that field blank, as we'll just copy over what's already there. If you have a new tag to add, then add *only* that new tag, and we'll append it to the list of current search tags. -RW From andrew.david.45 at gmail.com Tue May 20 21:45:23 2008 From: andrew.david.45 at gmail.com (andrew) Date: Wed, 21 May 2008 07:45:23 +1000 Subject: [Slackbuilds-users] Updates - 20080520 In-Reply-To: <20080520152039.GA8724@slackbuilds.org> References: <20080520152039.GA8724@slackbuilds.org> Message-ID: <20080520214523.GA30892@ilium.andrews-corner.org> On Tue, May 20, 2008 at 03:20:39PM +0000, Robby Workman wrote: > development/yasm: Added - Yasm is a complete rewrite of the NASM assembler > under the "new" BSD License. Thanks to Heinz Wiesinger. --rworkman Doh!! I have my own script for this almost complete! I will work a little faster next time :-) Andrew -- http://www.andrews-corner.org From pierce.lopez at gmail.com Wed May 21 04:34:06 2008 From: pierce.lopez at gmail.com (Pierce Lopez) Date: Wed, 21 May 2008 00:34:06 -0400 Subject: [Slackbuilds-users] rtorrent.SlackBuild bug Message-ID: <45f48d8d0805202134y22000a5eo4b1f1646c9fdba54@mail.gmail.com> In the SlackBuild for rtorrent, on line 52, "Slackbuild" should be "SlackBuild" (with a capital B) in two places. I think it's also worth noting that there is no SlackBuild for libtorrent (requirement of rtorrent) in the 12.1 repo. The one from 12.0 worked for me. In any case thanks for the really useful SlackBuilds! Pierce From xgizzmo at gmail.com Wed May 21 09:40:07 2008 From: xgizzmo at gmail.com (xgizzmo at gmail.com) Date: Wed, 21 May 2008 05:40:07 -0400 Subject: [Slackbuilds-users] rtorrent.SlackBuild bug In-Reply-To: <45f48d8d0805202134y22000a5eo4b1f1646c9fdba54@mail.gmail.com> References: <45f48d8d0805202134y22000a5eo4b1f1646c9fdba54@mail.gmail.com> Message-ID: <200805210540.07626.xgizzmo@gmail.com> On Wednesday 21 May 2008 00:34:06 Pierce Lopez wrote: > In the SlackBuild for rtorrent, on line 52, > "Slackbuild" should be "SlackBuild" (with a capital B) > in two places. This has been fixed now. > I think it's also worth noting that there is no SlackBuild > for libtorrent (requirement of rtorrent) in the 12.1 repo. > The one from 12.0 worked for me. It was there just missing a database entry, this has also been fixed now. Thanks for the report. David Somero From disturbed1976 at gmail.com Thu May 22 06:21:04 2008 From: disturbed1976 at gmail.com (Keith Richie) Date: Thu, 22 May 2008 02:21:04 -0400 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <482C7F46.1090801@slackbuilds.org> References: <595315.23265.qm@web57705.mail.re3.yahoo.com> <482C7F46.1090801@slackbuilds.org> Message-ID: <66a22e960805212321t3f5d5d9sc97831a5b477afac@mail.gmail.com> On Thu, May 15, 2008 at 2:21 PM, Robby Workman wrote: > Phillip Warner wrote: > >> I personally have no problem with that, but some people may and this might >> discourage some good submissions. Perhaps a good compromise would be to >> make sure it doesn't sound too harsh or if it is only for one Slackware >> release. If the next release comes out and the maintainer doesn't update a >> script that doesn't work on the newest release, then it can simply be >> removed. It would be nice if maintainers would let us know when they no >> longer can/want to maintain a slackBuild, so maybe this could be asked of >> the person submitting a script. >> >> Something that also might be really useful is to start an official list of >> orphaned and recently removed scripts. That way a person could look at that >> one file and then email the user list to say "Hey, I'll take it. Here's my >> submission." I know this could be accomplished through threads like this, >> but it might be more convenient to have it all in once place instead of >> spread through many messages. Ideally, this would be included on the site >> similar to the Changelog, but I understand if the admins don't want another >> file to maintain. >> > > > We were just talking about doing something like that - we think it > will help *us* too :) > > -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/ > > This is why I never submitted any of my SlackBuilds for mjpegtools, or DVDStyler + it's other depends. I wouldn't want to submit something, and not be able to maintain it. Not exactly wise for myself to do, considering I've only just switched back to Slackware a few months back. As it stands now, I have no plans of using another distro. But that's what I said with 10.0(.1?) and Vector, and Debian, and Ubuntu, and ..... ;) Seems like the SlackBuilds team has enough work as it is. Take a look at Arch Linux's AUR to see what orphaned build scripts can cause. A bunch of unmaintained build scripts of older software missing updates/fixes and not compatible with the current release. They also run into problems with 3-4 different build scripts of the same software. -------------- next part -------------- An HTML attachment was scrubbed... URL: From korgie at gmail.com Thu May 22 08:27:17 2008 From: korgie at gmail.com (korgman) Date: Thu, 22 May 2008 11:27:17 +0300 Subject: [Slackbuilds-users] Correction on latencytop Message-ID: <48352E65.7000705@gmail.com> Hello there. I don't know if it's approved, since it requires latest kernel. My latencytop submission has error. (wrong copy of man page) I resend the tarball with the correct man page. By the way: 1. biosdisk submission is rejected? 2. I just realized the meaning of the word "maintainer" by reading the post about orphaned scripts. I submitted few scripts (nload, mysqlcc) and it was a nice surprise that automagicaly moved to 12.1 version :) Keep up the good work. -- http://korgman.is-a-geek.net Michales Michaloudes Trilofos (thirida 477)-Thessaloniki 57 500 Dimos Mikras Tel. 6974377637 Call me FREE if you have VoIP: korgman at i-call.gr or 707 001 3814 -- Instead of Microsoft Office I use the FREE http://www.OpenOffice.org Mailer: Mozilla/5.0 (X11; U; Linux i686; en-US) www.Slackware.com -------------- next part -------------- A non-text attachment was scrubbed... Name: latencytop.tar.gz Type: application/gzip Size: 1652 bytes Desc: not available URL: From chaos.proton at gmail.com Thu May 22 14:29:35 2008 From: chaos.proton at gmail.com (Grissiom) Date: Thu, 22 May 2008 22:29:35 +0800 Subject: [Slackbuilds-users] sip.SlackBuild for sip-4.7.6 Message-ID: Hi, The current sip.SlackBuild failed to build sip-4.7.6 with the following message: ... make[1]: Leaving directory `/tmp/SBo/sip-4.7.6/siplib' cp -f sipconfig.py /tmp/SBo/package-sip/usr/lib/python2.5/site-packages/sipconfig.py cp -f sipdistutils.py /tmp/SBo/package-sip/usr/lib/python2.5/site-packages/sipdistutils.py install: cannot stat "THANKS": no such file or directory the attachment is a patch to fix it. BTW, sip-4.7.6 is needed by pyqt4.4.2 -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sip.SlackBuild.patch Type: application/octet-stream Size: 595 bytes Desc: not available URL: From asamardzic at gmail.com Thu May 22 15:15:01 2008 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Thu, 22 May 2008 17:15:01 +0200 Subject: [Slackbuilds-users] sip.SlackBuild for sip-4.7.6 In-Reply-To: References: Message-ID: On Thu, May 22, 2008 at 4:29 PM, Grissiom wrote: > Hi, > > The current sip.SlackBuild failed to build sip-4.7.6 with the following > message: > > ... > make[1]: Leaving directory `/tmp/SBo/sip-4.7.6/siplib' > cp -f sipconfig.py > /tmp/SBo/package-sip/usr/lib/python2.5/site-packages/sipconfig.py > cp -f sipdistutils.py > /tmp/SBo/package-sip/usr/lib/python2.5/site-packages/sipdistutils.py > install: cannot stat "THANKS": no such file or directory > > the attachment is a patch to fix it. > > BTW, sip-4.7.6 is needed by pyqt4.4.2 I posted (as it could be checked at: http://slackbuilds.org/pending/) updates for both sip and pyqt4 earlier today. The sip SlackBuild update includes fix for THANKS file being removed in the meantime from the sip distribution. Regards, Alex From datimmay at gmail.com Thu May 22 15:50:37 2008 From: datimmay at gmail.com (Tim King) Date: Thu, 22 May 2008 10:50:37 -0500 Subject: [Slackbuilds-users] devede and mplayer Message-ID: <274801fb0805220850l65b1ec2am5516a4cfe93e30b7@mail.gmail.com> I didn't see anything about this, and it took me a bit to figure out so I thought I'd send a mail to the list to let you know about a slight problem, that I had at least, with the package created from the mplayer slackbuild from slackbuilds.org. When I'd try to run devede (also packaged from slackbuilds) it would run just fine, up until I tried to add a video file to the list (any video). The videos played just fine in smplayer/mplayer and checking output from devede showed that they just weren't being recognized as a video file. I sent a few mails to the devede developer and we talked back and forth a few times trying to figure it out, but all the problem ended up being was one of the configure options: --enable-color-console. It was adding extra output that made devede unable to parse the identification info properly is all. Removing that option from the build script got everything working fine again :) I understand that it's not really a problem with mplayer, and I mailed the devede devel again this morning to let them know what the problem on my end was. I'm not sure what they're planning on doing about it (adding support for the extra output or recommending folks to not use that option in their mplayer build) but I thought it would be nice to let other slackers using these apps about a potential problem. Anyway that's about it :) Regards, Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From rk4n3 at inbox.com Thu May 22 19:02:16 2008 From: rk4n3 at inbox.com (Ar Kane) Date: Thu, 22 May 2008 11:02:16 -0800 Subject: [Slackbuilds-users] Small problem in MOC SlackBuild Message-ID: I'm not including any supporting information with this because the problem is so small and easy to fix - I just wanted to make sure it got reported... The MOC build detects the presence of support for the plugins it knows about, and the compile is configured accordingly. A compile error occurs if the latest ffmpeg is installed, because the MOC build assumes ffmpeg headers are in a sub-directory "ffmpeg", and the ffmpeg package has changed to have its headers in "libavformat". I resolved this by running the SlackBuild after: ln -s /usr/include/libavformat /usr/include/ffmpeg I'll leave fixing the SlackBuild up to someone more familiar with the "SlackBuild" ways... ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth From michael-wagner at gmx.de Thu May 22 21:42:49 2008 From: michael-wagner at gmx.de (Michael Wagner) Date: Thu, 22 May 2008 23:42:49 +0200 Subject: [Slackbuilds-users] Small problem in MOC SlackBuild In-Reply-To: References: Message-ID: <20080522234249.42f8e651@laptop> > The MOC build detects the presence of support > for the plugins it knows about, and the compile > is configured accordingly. A compile error > occurs if the latest ffmpeg is installed, > because the MOC build assumes ffmpeg headers > are in a sub-directory "ffmpeg", and the ffmpeg > package has changed to have its headers in > "libavformat". This has already been reported upstream and it has been fixed in svn. Maybe you can try something like CFLAGS='-I/usr/include/libavformat' or libavformat_CFLAGS='-I/usr/include/libavformat'. Please note, that I can't test it at the moment, it may be wrong. Greetings, Michael From hba.nihilismus at gmail.com Fri May 23 00:36:39 2008 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Thu, 22 May 2008 19:36:39 -0500 Subject: [Slackbuilds-users] ffmpeg update - request for testers Message-ID: <39be090805221736h49351753k29b325643a96a657@mail.gmail.com> Hi all. I'm the MAINTAINER of ffmpeg and want to announce a new SlackBuild for ffmpeg(version 20080521), you can find it at: http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/ Please, read this before you screw your system ;) http://hba.nonlogic.org/projects/slackbuilds/testing/README.WARNING The main reason to make this announce is to request for persons that can/want to test it before i upload it into pending/. Please, take a look to http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/README to know the changes i've made. Also, i've updated x264(version 20080521 too): http://hba.nonlogic.org/projects/slackbuilds/testing/x264-20080521/ I tested ffmpeg with the current SlackBuild in SBo and this update too without any problem. P.S. yeah, i know my english sucks, but the fault lies with the THC ;) - Antonio Hern?ndez Blas From HMWiesinger at gmx.at Fri May 23 08:26:26 2008 From: HMWiesinger at gmx.at (Heinz Wiesinger) Date: Fri, 23 May 2008 10:26:26 +0200 Subject: [Slackbuilds-users] ffmpeg update - request for testers In-Reply-To: <39be090805221736h49351753k29b325643a96a657@mail.gmail.com> References: <39be090805221736h49351753k29b325643a96a657@mail.gmail.com> Message-ID: <200805231026.26235.HMWiesinger@gmx.at> Am Freitag, 23. Mai 2008 02:36:39 schrieb Antonio Hern?ndez Blas: > Hi all. > > I'm the MAINTAINER of ffmpeg and want to announce a new SlackBuild for > ffmpeg(version 20080521), you can find it at: > http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/ > > Please, read this before you screw your system ;) > http://hba.nonlogic.org/projects/slackbuilds/testing/README.WARNING > > The main reason to make this announce is to request for persons that > can/want to test it before i upload it into pending/. Please, take a > look to > http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/README > to know the changes i've made. > > Also, i've updated x264(version 20080521 too): > http://hba.nonlogic.org/projects/slackbuilds/testing/x264-20080521/ > I tested ffmpeg with the current SlackBuild in SBo and this update too > without any problem. > This is actually rather cool ;) I thought about that too packages a lot in the last few weeks, so now's probably the right time to share my thoughts. Both apps are rather critical, as they do not release tarballs and there are still many apps depending on them. Making sure everything does *work*, is not easy, as every app using ffmpeg or x264 has to be tested. From my point of view, those two should not be updated that often. I first thought about an update right after the release of a new Slackware-version, but I think coordinating those updates with MPlayer-releases would be much better. There are a few reasons for that. MPlayer has a similar development philosophy as ffmpeg (as those are affiliated), but at least it gets released sometimes. As MPlayer is using ffmpeg internally we can probably state that the version used by MPlayer is pretty stable. MPlayer is also adjusting the interface to x264 in svn, which means that the perfect combination of those two would be snapshots of about the same time. Updating x264 and leaving MPlayer behind would probably end up with problems on runtime. Based on that versions we can than start syncing the other apps using them, which I am not sure about how many there are currently. Anyway, this will be a huge effort and in no way be a one-an job, as there are just too many deps to be looked through. On a sidenote, I had a look at your README Antonio and want to inform you, that libamr-nb/wb ARE in the repo. You can find them in audio as amrnb/amrwb. My two cents :) Grs, Heinz From chaos.proton at gmail.com Sat May 24 01:38:34 2008 From: chaos.proton at gmail.com (Grissiom) Date: Sat, 24 May 2008 09:38:34 +0800 Subject: [Slackbuilds-users] My slackbuild for QScintilla Message-ID: Hi, This is my first SlackBuild script. There may be many things needed to be improved. Any advice or comment is strongly welcome. Thanks in advance. -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: QScintilla-gpl.SlackBuild Type: application/octet-stream Size: 2386 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: slack-desc Type: application/octet-stream Size: 1046 bytes Desc: not available URL: From mickeytintincolle at yahoo.fr Sat May 24 18:19:17 2008 From: mickeytintincolle at yahoo.fr (Anotine NONYME) Date: Sat, 24 May 2008 20:19:17 +0200 Subject: [Slackbuilds-users] Wormux SlackBuild Message-ID: <48385C25.8070108@yahoo.fr> Wormux 0.8 was released some days ago and I wanted to compile it with the 0.7.9 SlackBuild and it works with the 2 following modifications : - Replacing VERSION from 0.7.9 to 0.8 - Replacing 'tar.gz' by 'tar.bz2' - And SDL_gfx installed of course :) From xgizzmo at slackbuilds.org Sun May 25 18:29:14 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Sun, 25 May 2008 14:29:14 -0400 Subject: [Slackbuilds-users] Updates - 20080525 Message-ID: <200805251429.14327.xgizzmo@slackbuilds.org> Sun May 25 16:37:20 UTC 2008 academic/ng-spice: Added - a mixed-level/mixed-signal circuit simulator. Thanks to Kyle Guinn. --Erik Hanson academic/xoscope: Added - a digital oscilloscope that uses a sound card and/or Radio Shack ProbeScope (Cat. No. 220-0310) a.k.a osziFOX as the signal input. Thanks to Kyle Guinn. --Erik Hanson audio/audacity: Updated for version 1.3.5. Thanks to Chess Griffin. --Erik Hanson audio/rosegarden: Updated for version 1.7.0. Thanks to Heinz Wiesinger. --Erik Hanson desktop/enlightenment: Updated for DR17 0.16.999.043. Thanks to Aleksandar Samardzic. --Erik Hanson desktop/kooldock: Added - A kool dock for KDE. It attemps to resemble the Mac OSX dock. Thanks to Blase Stanek. --Erik Hanson development/Xdialog: Added - Xdialog is designed to be a drop in replacement for the "dialog" and "cdialog" programs. Thanks to slakmagik. --rworkman development/acpica: Updated for version 20080514. Thanks to Heinz Wiesinger. --Erik Hanson development/gmm: Added - a generic C++ template library for sparse, dense and skyline matrices. Thanks to Heinz Wiesinger. --Erik Hanson development/mcpp: Added - MCPP is a portable C/C++ preprocessor, supporting GCC, Visual C++, etc. Thanks to Aleksandar Samardzic. --Erik Hanson development/mod_perl: Updated for version 2.0.4. Thanks to Heinz Wiesinger. --Erik Hanson development/python-pmw: Updated for version 1.3.2. Thanks to Luken Shiro. --Erik Hanson development/scite: Updated for version 1.76. Thanks to Iskar Enev. --Erik Hanson development/splint: Updated for version 3.1.2. Thanks to Menno E. Duursma. --Erik Hanson development/uncrustify: Updated for version 0.46. Thanks to Aleksandar Samardzic. --Erik Hanson games/gnubg: Updated for the 20080516 snapshot version. Thanks to Erik Hanson. --rworkman libraries/e_dbus: Updated for version 0.5.0.043. libraries/ecore: Updated for version 0.9.9.043. libraries/edje: Updated for version 0.9.9.043. libraries/efreet: Updated for version 0.5.0.043. libraries/eet: Updated for version 1.0.1. libraries/embryo: Updated for version 0.9.9.043. libraries/evas: Updated for version 0.9.9.043. Thanks to Aleksandar Samardzic. --Erik Hanson libraries/fltk: Updated for version 1.1.9. Thanks to Luken Shiro. --Erik Hanson libraries/gnet: Updated for version 2.0.8. Thanks to Menno E. Duursma. --Erik Hanson libraries/goffice: Updated for version 0.6.4. Thanks to Alex Lysenka. --Erik Hanson libraries/openmotif: Added - the freely available Motif user interface component toolkit. Thanks to Vincent Batts. --Erik Hanson libraries/pidgin-hotkeys: Added - pidgin-hotkeys is a Pidgin plugin that allows you to define global hotkeys for various actions. Thanks to Cherife Li. --rworkman libraries/raptor: Updated for version 1.4.17. Thanks to Heinz Wiesinger. --Erik hanson libraries/xlt: Added - widgets, functions, and macros to help while programming with the Motif API. Thanks to Vincent Batts. --Erik Hanson misc/biosdisk: Added - biosdisk simplifies the process of flashing your system BIOS under Linux on Dell desktops and laptops. Thanks to Michales Michaloudes. --Erik Hanson multimedia/GoogleEarth: Updated for version 4.3.7204.836. Note that while the package itself seems to be fine, several of us have experienced problems with actually running this version of GoogleEarth; apparently it doesn't like some graphics cards and/or drivers and/or phases of the moon and causes anything from application crashes to X crashes. Your mileage may vary. Thanks to Michiel van Wessem. --rworkman multimedia/TiMidityxx: Added this back into the repository after including some patches from Debian to fix up compiles on 12.1. Thanks to Richard Hoyle and Kyle Guinn for the update. --rworkman network/dnstop: Updated for version 20080502. Thanks to Menno E. Duursma. --Erik Hanson network/mod_hosts_access: Updated to work with Slackware 12.1. Thanks to Menno E. Duursma. --Erik Hanson network/transmission: Updated for version 1.20. Thanks to Iskar Enev. network/w3m: Included a patch to fix a segfault bug. office/xmblackberry: Added - A BlackBerry backup/restore and GPRS modem access application. Thanks to Vincent Batts. --Erik Hanson system/915resolution: Updated for version 0.5.3. Thanks to Roberto Neri. --Erik Hanson system/emelfm2: Updated for version 0.4.1. Thanks to Chess Griffin. --Erik Hanson system/gammu: Updated for version 1.20. Thanks to Heinz Wiesinger. system/lshw: Updated for version B.02.13. Thanks to Iskar Enev. system/pcmanfm: Updated for version 0.4.1.1. Thanks to Chess Griffin. --Erik Hanson system/pcsc-lite: Updated for version 1.4.101. Thanks to Luken Shiro. --Erik Hanson system/rox-filer: Added - ROX-Filer is a fast and powerful graphical file manager. Thanks to slakmagik. --rworkman system/roxterm: Update for 1.12.0. Thanks to Erik Hanson. --David Somero system/xchm: Added - xchm is a CHM (MS help file) reader. Thanks to Michael Gehring. --rworkman system/xjobs: Added - xjobs reads job descriptions line by line and executes them in parallel. Thanks to Erik Hanson. --David Somero From hba.nihilismus at gmail.com Mon May 26 04:02:50 2008 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Sun, 25 May 2008 23:02:50 -0500 Subject: [Slackbuilds-users] ffmpeg update - request for testers In-Reply-To: <200805231026.26235.HMWiesinger@gmx.at> References: <39be090805221736h49351753k29b325643a96a657@mail.gmail.com> <200805231026.26235.HMWiesinger@gmx.at> Message-ID: <39be090805252102ja8e7a7eif84771fb677594e8@mail.gmail.com> Hi Heinz Wiesinger: "From my point of view, those two should not be updated that often." Hahahaha :) trust me, they are not updated "that" often, this would be their first update since 8 months ago. " I first thought about an update right after the release of a new Slackware-version," Before the release of Slackware 12.1 that was i wanted to do, also i asked to rworkman if that would be possible (if i can remember, all he said me is(more or less) "wait for the maintainer consideration") but anyway, I still have the idea that apps from svn/cvs should be updated right after a Slackware release, so we can use them like in 1 year without worry of them ;) "As MPlayer is using ffmpeg internally we can probably state that the version used by MPlayer is pretty stable." It's that, or we can state that they are pretty different too. Are the changes made by MPlayer to ffmpeg(the internal) also done in ffmpeg(the official)? "MPlayer is also adjusting the interface to x264 in svn, which means that the perfect combination of those two would be snapshots of about the same time. Updating x264 and leaving MPlayer behind would probably end up with roblems on runtime." If you take a look into their configure script (http://svn.mplayerhq.hu/mplayer/trunk/configure?view=co), you can see something like this http://pastebin.ca/1029547. They search for the value of X264_BUILD in /usr/include/x264.h(greater than 53), which in my x264 update is '#define X264_BUILD 59", so i don't see any problem here. And finally, look the version of ffmpeg in gentoo and arch: http://www.gentoo-portage.com/AJAX/Ebuild/63099 (svn revision 11878 - fmpeg-0.4.9_p20080326.ebuild) http://aur.archlinux.org/packages/ffmpeg-svn/ffmpeg-svn/PKGBUILD (svn revision 13107) Both are updated, in *this* year :) Ok, anyway, i'm not saying your ideas are wrong, i understand them but at this moment i think we can make the updates without any problem, until the next slackware release. BTW, i have execute this command to see wich could be the other apps that should take care of this update(/var/cache/slackbuilds/ is were i sync SBo repository): find /var/cache/slackbuilds/ -name "README" -exec grep ffmpeg {} \; -exec echo -e "{}\n" \; As i can see, they are: kino, transcode, ffmpegthumbnailer and motion, (MOC too) Can another SBo admin/user give an opinion about this topic? that would be nice, i don't want to get a date with Heinz Wiesinger at the end of all this threat hahahaha :) 2008/5/23, Heinz Wiesinger : > Am Freitag, 23. Mai 2008 02:36:39 schrieb Antonio Hern?ndez Blas: > > > Hi all. > > > > I'm the MAINTAINER of ffmpeg and want to announce a new SlackBuild for > > ffmpeg(version 20080521), you can find it at: > > http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/ > > > > Please, read this before you screw your system ;) > > http://hba.nonlogic.org/projects/slackbuilds/testing/README.WARNING > > > > The main reason to make this announce is to request for persons that > > can/want to test it before i upload it into pending/. Please, take a > > look to > > http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/README > > to know the changes i've made. > > > > Also, i've updated x264(version 20080521 too): > > http://hba.nonlogic.org/projects/slackbuilds/testing/x264-20080521/ > > I tested ffmpeg with the current SlackBuild in SBo and this update too > > without any problem. > > > > This is actually rather cool ;) > I thought about that too packages a lot in the last few weeks, so now's > probably the right time to share my thoughts. > > Both apps are rather critical, as they do not release tarballs and there are > still many apps depending on them. Making sure everything does *work*, is not > easy, as every app using ffmpeg or x264 has to be tested. > > From my point of view, those two should not be updated that often. I first > thought about an update right after the release of a new Slackware-version, > but I think coordinating those updates with MPlayer-releases would be much > better. There are a few reasons for that. > > MPlayer has a similar development philosophy as ffmpeg (as those are > affiliated), but at least it gets released sometimes. As MPlayer is using > ffmpeg internally we can probably state that the version used by MPlayer is > pretty stable. > MPlayer is also adjusting the interface to x264 in svn, which means that the > perfect combination of those two would be snapshots of about the same time. > Updating x264 and leaving MPlayer behind would probably end up with problems > on runtime. > > Based on that versions we can than start syncing the other apps using them, > which I am not sure about how many there are currently. Anyway, this will be > a huge effort and in no way be a one-an job, as there are just too many deps > to be looked through. > > On a sidenote, I had a look at your README Antonio and want to inform you, > that libamr-nb/wb ARE in the repo. You can find them in audio as amrnb/amrwb. > > My two cents :) > > Grs, > Heinz > _______________________________________________ > 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 slackbuilds at sisyphus.ch Mon May 26 09:57:31 2008 From: slackbuilds at sisyphus.ch (christian) Date: Mon, 26 May 2008 11:57:31 +0200 Subject: [Slackbuilds-users] apcupsd Message-ID: <20080526095730.GL30658@machine-18.sisyphus.loc> not meaning to annoy anybody - but i think the `README-SLACKWARE` could be improved a tiny bit: ;-) __cut__ --- README-SLACKWARE 2008-03-29 00:07:29.000000000 +0000 +++ README-SLACKWARE.NEW 2008-05-26 09:46:42.000000000 +0000 @@ -41,7 +41,7 @@ # of seconds (see the apcupsd.conf file). This is important for situations # where the mains power comes back before the UPS batteries are completely # dead. - if [ -f /etc/powerfail ]; then + if [ -f /etc/apcupsd/powerfail ]; then echo echo "apcupsd will now power off the UPS" echo __cut__ thanks for any feedback. -- From Amentia-ignota at web.de Wed May 28 21:34:43 2008 From: Amentia-ignota at web.de (Thiemo Herbst) Date: Wed, 28 May 2008 23:34:43 +0200 Subject: [Slackbuilds-users] bug report for -ddclient- maintained by rworkman Message-ID: <140629510@web.de> Hi there, I think I found something missing in the slackbuild script for the ddclient buildscript: ddclient wants to create the file "/var/cache/ddclient/ddclient.cache" but the program is unable to mkdir the directory "/var/cache/ddclient/" So a simple "mkdir /var/cache/ddclient" in the buildscript should do it. Nice greetings, Thiemo Herbst PS: I didn't subscribe, because I'm @web.de, sorry :-( _______________________________________________________________________ EINE F?R ALLE: die kostenlose WEB.DE-Plattform f?r Freunde und Deine Homepage mit eigenem Namen. Jetzt starten! http://unddu.de/?kid=kid at mf2 From iskar.enev at gmail.com Thu May 29 06:06:12 2008 From: iskar.enev at gmail.com (Iskar enev) Date: Thu, 29 May 2008 09:06:12 +0300 Subject: [Slackbuilds-users] bug report for -ddclient- maintained by rworkman In-Reply-To: <140629510@web.de> References: <140629510@web.de> Message-ID: <483E47D4.8090201@gmail.com> I'll fix this. Thanks for the report. Regards: Iskar Enev Thiemo Herbst wrote: > Hi there, > I think I found something missing in the slackbuild script for the ddclient buildscript: > ddclient wants to create the file "/var/cache/ddclient/ddclient.cache" > but the program is unable to mkdir the directory "/var/cache/ddclient/" > So a simple "mkdir /var/cache/ddclient" in the buildscript should do it. > > Nice greetings, > Thiemo Herbst > > PS: I didn't subscribe, because I'm @web.de, sorry :-( From rworkman at slackbuilds.org Fri May 30 00:37:33 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 29 May 2008 19:37:33 -0500 Subject: [Slackbuilds-users] bug report for -ddclient In-Reply-To: <483E47D4.8090201@gmail.com> References: <140629510@web.de> <483E47D4.8090201@gmail.com> Message-ID: <483F4C4D.8050402@slackbuilds.org> CC'ing original poster, as he's not subscribed to the list. Note to OP: I am not the maintainer for this - Iskar is; I just tested and approved it for inclusion in our repository. Iskar enev wrote: > I'll fix this. Thanks for the report. I went ahead and fixed this, incremented BUILD, and put it in the queue for next update. If there's a new version out, then go ahead and submit it, but this was an easy enough fix. :) -RW From rworkman at slackbuilds.org Fri May 30 00:46:15 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 29 May 2008 19:46:15 -0500 Subject: [Slackbuilds-users] apcupsd In-Reply-To: <20080526095730.GL30658@machine-18.sisyphus.loc> References: <20080526095730.GL30658@machine-18.sisyphus.loc> Message-ID: <483F4E57.9070503@slackbuilds.org> christian wrote: > not meaning to annoy anybody - but i think the `README-SLACKWARE` could > be improved a tiny bit: ;-) > > __cut__ > --- README-SLACKWARE 2008-03-29 00:07:29.000000000 +0000 > +++ README-SLACKWARE.NEW 2008-05-26 09:46:42.000000000 +0000 > @@ -41,7 +41,7 @@ > # of seconds (see the apcupsd.conf file). This is important for situations > # where the mains power comes back before the UPS batteries are completely > # dead. > - if [ -f /etc/powerfail ]; then > + if [ -f /etc/apcupsd/powerfail ]; then > echo > echo "apcupsd will now power off the UPS" > echo > __cut__ > > thanks for any feedback. > Good catch; I've fixed it for the next public update. Thanks! -RW From rworkman at slackbuilds.org Fri May 30 00:48:22 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 29 May 2008 19:48:22 -0500 Subject: [Slackbuilds-users] My slackbuild for QScintilla In-Reply-To: References: Message-ID: <483F4ED6.3000608@slackbuilds.org> Grissiom wrote: > Hi, > This is my first SlackBuild script. There may be many things needed to > be improved. Any advice or comment is strongly welcome. Thanks in advance. I wish I had seen this before I went and wrote one for kde4, but since I didn't, you might have a look at it and compare the two. http://kde4.rlworkman.net/sources/deps/QScintilla/ -RW From rworkman at slackbuilds.org Fri May 30 00:50:33 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 29 May 2008 19:50:33 -0500 Subject: [Slackbuilds-users] Correction on latencytop In-Reply-To: <48352E65.7000705@gmail.com> References: <48352E65.7000705@gmail.com> Message-ID: <483F4F59.5040108@slackbuilds.org> korgman wrote: > I don't know if it's approved, since it requires latest kernel. My > latencytop submission has error. (wrong copy of man page) > > I resend the tarball with the correct man page. It's still in pending; we're running behind (as usual) again. :) I overwrote the one that was in pending with the corrected build, so it should be fine once we get to it. > By the way: > > 1. biosdisk submission is rejected? No, it went out in the last update. > 2. I just realized the meaning of the word "maintainer" by reading the > post about orphaned scripts. I submitted few scripts (nload, mysqlcc) > and it was a nice surprise that automagicaly moved to 12.1 version :) :) -RW From rworkman at slackbuilds.org Fri May 30 00:52:50 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 29 May 2008 19:52:50 -0500 Subject: [Slackbuilds-users] "orphaned" scripts In-Reply-To: <66a22e960805212321t3f5d5d9sc97831a5b477afac@mail.gmail.com> References: <595315.23265.qm@web57705.mail.re3.yahoo.com> <482C7F46.1090801@slackbuilds.org> <66a22e960805212321t3f5d5d9sc97831a5b477afac@mail.gmail.com> Message-ID: <483F4FE2.4010705@slackbuilds.org> Keith Richie wrote: > This is why I never submitted any of my SlackBuilds for mjpegtools, or > DVDStyler + it's other depends. I wouldn't want to submit something, and > not be able to maintain it. Not exactly wise for myself to do, > considering I've only just switched back to Slackware a few months back. > As it stands now, I have no plans of using another distro. But that's > what I said with 10.0(.1?) and Vector, and Debian, and Ubuntu, and ..... ;) > > Seems like the SlackBuilds team has enough work as it is. > > Take a look at Arch Linux's AUR to see what orphaned build scripts can > cause. A bunch of unmaintained build scripts of older software missing > updates/fixes and not compatible with the current release. They also run > into problems with 3-4 different build scripts of the same software. Well, worst case scenario is that one of two things happens: 1. someone else who uses the software decides to take over maintaining it, and all is well. 2. it won't build by the time the next Slackware release goes out, and we'll remove it. -RW From rworkman at slackbuilds.org Fri May 30 00:56:26 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 29 May 2008 19:56:26 -0500 Subject: [Slackbuilds-users] tilda update In-Reply-To: <482D46B5.50405@gmail.com> References: <482D46B5.50405@gmail.com> Message-ID: <483F50BA.2070204@slackbuilds.org> Fred Galusik wrote: > Hi, > > Just to say that the tilda page needs an update : > http://slackbuilds.org/repository/12.1/system/tilda/ > > The download link (tilda 9.4) is deprecated as tilda 9.6 is out, here is > the new one : > http://downloads.sourceforge.net/tilda/tilda-0.9.6.tar.gz?modtime=1209379739&big_mirror=0 > > > The SlackBuild just needs this minor change : > VERSION=0.9.6 This one does need an update, and whenever it's done, we need to fix the README so that it references 'confuse' instead of 'libconfuse' - we don't want to confuse anyone... ;-) -RW From chaos.proton at gmail.com Fri May 30 05:07:20 2008 From: chaos.proton at gmail.com (Grissiom) Date: Fri, 30 May 2008 13:07:20 +0800 Subject: [Slackbuilds-users] My slackbuild for QScintilla In-Reply-To: <483F4ED6.3000608@slackbuilds.org> References: <483F4ED6.3000608@slackbuilds.org> Message-ID: On 5/30/08, Robby Workman wrote: > Grissiom wrote: > >> Hi, >> This is my first SlackBuild script. There may be many things needed to be >> improved. Any advice or comment is strongly welcome. Thanks in advance. >> > > > I wish I had seen this before I went and wrote one for kde4, but since > I didn't, you might have a look at it and compare the two. > http://kde4.rlworkman.net/sources/deps/QScintilla/ > > -RW Hmm, I see that you installed Qt4-QScinlla into the system but never uninstall it. So it may remain some rubbish in the system after building the peckage. And, what about the Qt3 part? Since there is a lot of apps based on Qt3, so it's worth to build the Qt3 part I think. I have to admit that you add more useful qmake options than I did ;) Sorry for my poor English :( -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Fri May 30 05:22:29 2008 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 30 May 2008 00:22:29 -0500 Subject: [Slackbuilds-users] My slackbuild for QScintilla In-Reply-To: References: <483F4ED6.3000608@slackbuilds.org> Message-ID: <483F8F15.8070304@slackbuilds.org> Grissiom wrote: > Hmm, I see that you installed Qt4-QScinlla into the system but never > uninstall it. So it may remain some rubbish in the system after building > the peckage. It doesn't matter in this case (although it might/would for SBo). I'm building on a dedicate dev box that gets wiped regularly, so any crap that remains has a short life ahead. Additionally, I'll be installing the package on that dev box anyway, so removing the package later will accomplish the same thing. > And, what about the Qt3 part? Since there is a lot of apps > based on Qt3, so it's worth to build the Qt3 part I think. Well, since I'm only targeting qt4 (for kde4 dev), I don't need or even want qt3 stuff. -RW From chaos.proton at gmail.com Fri May 30 12:46:32 2008 From: chaos.proton at gmail.com (Grissiom) Date: Fri, 30 May 2008 20:46:32 +0800 Subject: [Slackbuilds-users] My slackbuild for QScintilla In-Reply-To: <483F8F15.8070304@slackbuilds.org> References: <483F4ED6.3000608@slackbuilds.org> <483F8F15.8070304@slackbuilds.org> Message-ID: On Fri, May 30, 2008 at 1:22 PM, Robby Workman wrote: > Grissiom wrote: > > Hmm, I see that you installed Qt4-QScinlla into the system but never >> uninstall it. So it may remain some rubbish in the system after building the >> peckage. >> > > > It doesn't matter in this case (although it might/would for SBo). > I'm building on a dedicate dev box that gets wiped regularly, so any > crap that remains has a short life ahead. Additionally, I'll be > installing the package on that dev box anyway, so removing the package > later will accomplish the same thing. > Hmm, yes I know the SBo directory. But I still think the SBo is clean because we can delete it with no harm. But 'make install' could copy things to /usr/lib, /usr/bin,etc, it will mixed with other things. We cannot simplly delete it ;) And as far as I see, not everyone have a dedicate dev box. Yes, install the package will overwrite things you installed previously. But I think the word 'SlackBuild' is stand for 'build slack package' but not for 'mainly build slack package and install xxx at times'. It could be buggy if a function doesn't live up to its name. > > And, what about the Qt3 part? Since there is a lot of apps based on Qt3, >> so it's worth to build the Qt3 part I think. >> > > > Well, since I'm only targeting qt4 (for kde4 dev), I don't need or > even want qt3 stuff. > > > -RW > Yes, it's right if you _only_ want qt4 support. So, may be your script is specialized and not intend for general usage? -- Cheers, Grissiom -------------- next part -------------- An HTML attachment was scrubbed... URL: From iskar.enev at gmail.com Fri May 30 12:56:06 2008 From: iskar.enev at gmail.com (Iskar Enev) Date: Fri, 30 May 2008 15:56:06 +0300 Subject: [Slackbuilds-users] bug report for -ddclient In-Reply-To: <483F4C4D.8050402@slackbuilds.org> References: <140629510@web.de> <483E47D4.8090201@gmail.com> <483F4C4D.8050402@slackbuilds.org> Message-ID: <483FF966.4020906@gmail.com> No new versions since august 2007. And thanks for the fix :) Regards: Iskar Robby Workman wrote: > I went ahead and fixed this, incremented BUILD, and put it in the > queue for next update. If there's a new version out, then go ahead > and submit it, but this was an easy enough fix. :) From erectlocution at gmail.com Fri May 30 14:44:04 2008 From: erectlocution at gmail.com (Daniel Black) Date: Fri, 30 May 2008 10:44:04 -0400 Subject: [Slackbuilds-users] Note in bitlbee SBo regarding configuration Message-ID: <20080530144403.GA3466@cavalieri.google.com> Hi, folks, The configuration note for the bitlbee SBo suggests the user add the following to inetd.conf: 6667 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee I tried this, and could not connect to bitlbee. /var/log/secure logged connection refusals. I poked around bitlbee's docs, and they recommend the following: 6667 stream tcp nowait nobody /usr/sbin/bitlbee bitlbee With this, upon restarting inetd, I connected without issue. I'm running stock 12.1, so I imagine this is the case with most anyone. Is this a change that should be made in the SBo documentation? Thanks, Daniel From asamardzic at gmail.com Fri May 30 15:29:01 2008 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Fri, 30 May 2008 17:29:01 +0200 Subject: [Slackbuilds-users] Note in bitlbee SBo regarding configuration In-Reply-To: <20080530144403.GA3466@cavalieri.google.com> References: <20080530144403.GA3466@cavalieri.google.com> Message-ID: On Fri, May 30, 2008 at 4:44 PM, Daniel Black wrote: > Hi, folks, > > The configuration note for the bitlbee SBo suggests the user add the > following to inetd.conf: > > 6667 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee > > I tried this, and could not connect to bitlbee. /var/log/secure logged > connection refusals. I poked around bitlbee's docs, and they recommend > the following: > > 6667 stream tcp nowait nobody /usr/sbin/bitlbee bitlbee > > With this, upon restarting inetd, I connected without issue. I'm > running stock 12.1, so I imagine this is the case with most anyone. Is > this a change that should be made in the SBo documentation? Did you informed inetd to reload its config after installing the program and changing /etc/inetd.conf: kill -HUP $(cat /var/run/inetd.pid) Regards, Alex From mark at markwalling.org Fri May 30 16:59:14 2008 From: mark at markwalling.org (Mark Walling) Date: Fri, 30 May 2008 12:59:14 -0400 Subject: [Slackbuilds-users] Note in bitlbee SBo regarding configuration In-Reply-To: <20080530144403.GA3466@cavalieri.google.com> References: <20080530144403.GA3466@cavalieri.google.com> Message-ID: <20080530165913.GC29114@you> On 05/30/08, Daniel Black wrote: > Hi, folks, > > The configuration note for the bitlbee SBo suggests the user add the > following to inetd.conf: > > 6667 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee > > I tried this, and could not connect to bitlbee. /var/log/secure logged > connection refusals. I poked around bitlbee's docs, and they recommend > the following: > > 6667 stream tcp nowait nobody /usr/sbin/bitlbee bitlbee > > With this, upon restarting inetd, I connected without issue. I'm > running stock 12.1, so I imagine this is the case with most anyone. Is > this a change that should be made in the SBo documentation? > FWIW, I've been running Bitlbee here with tcp_wrappers with no problems: /etc/inetd.conf 6668 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee -M -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From asamardzic at gmail.com Fri May 30 17:46:46 2008 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Fri, 30 May 2008 19:46:46 +0200 Subject: [Slackbuilds-users] Note in bitlbee SBo regarding configuration In-Reply-To: <20080530165913.GC29114@you> References: <20080530144403.GA3466@cavalieri.google.com> <20080530165913.GC29114@you> Message-ID: On Fri, May 30, 2008 at 6:59 PM, Mark Walling wrote: > On 05/30/08, Daniel Black wrote: >> Hi, folks, >> >> The configuration note for the bitlbee SBo suggests the user add the >> following to inetd.conf: >> >> 6667 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee >> >> I tried this, and could not connect to bitlbee. /var/log/secure logged >> connection refusals. I poked around bitlbee's docs, and they recommend >> the following: >> >> 6667 stream tcp nowait nobody /usr/sbin/bitlbee bitlbee >> >> With this, upon restarting inetd, I connected without issue. I'm >> running stock 12.1, so I imagine this is the case with most anyone. Is >> this a change that should be made in the SBo documentation? >> > FWIW, I've been running Bitlbee here with tcp_wrappers with no problems: > > /etc/inetd.conf > 6668 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee I should have been more detailed with my previous message, and note there that I too was able to connect to the daemon using /etc/inetd.conf configuration as suggested in given SlackBuild README file. Also, I should have read OP message more carefully - indeed it looks like TCP wrappers problems (so maybe /etc/hosts.allow and /etc/hosts.deny files should be checked on given machine?)... Regards, Alex From erectlocution at gmail.com Fri May 30 19:09:00 2008 From: erectlocution at gmail.com (Daniel Black) Date: Fri, 30 May 2008 15:09:00 -0400 Subject: [Slackbuilds-users] Note in bitlbee SBo regarding configuration In-Reply-To: References: <20080530144403.GA3466@cavalieri.google.com> <20080530165913.GC29114@you> Message-ID: <20080530190900.GA4450@cavalieri.google.com> Hi, Alex & Mark, On Fri, May 30, 2008 at 07:46:46PM +0200, Aleksandar Samardzic wrote: > On Fri, May 30, 2008 at 6:59 PM, Mark Walling wrote: > > On 05/30/08, Daniel Black wrote: > >> Hi, folks, > >> > >> The configuration note for the bitlbee SBo suggests the user add the > >> following to inetd.conf: > >> > >> 6667 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee > >> > >> I tried this, and could not connect to bitlbee. /var/log/secure logged > >> connection refusals. I poked around bitlbee's docs, and they recommend > >> the following: > >> > >> 6667 stream tcp nowait nobody /usr/sbin/bitlbee bitlbee > >> > >> With this, upon restarting inetd, I connected without issue. I'm > >> running stock 12.1, so I imagine this is the case with most anyone. Is > >> this a change that should be made in the SBo documentation? > >> > > FWIW, I've been running Bitlbee here with tcp_wrappers with no problems: > > > > /etc/inetd.conf > > 6668 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee > > I should have been more detailed with my previous message, and note > there that I too was able to connect to the daemon using > /etc/inetd.conf configuration as suggested in given SlackBuild README > file. Also, I should have read OP message more carefully - indeed it > looks like TCP wrappers problems (so maybe /etc/hosts.allow and > /etc/hosts.deny files should be checked on given machine?)... Hmm. I actually had thought of some PEBKAC on hosts.allow, after looking at /var/log/secure. I suppose my attempted fixes were off. Apologies for spamming the list without confirming my configuration wasn't to blame. Thanks for the responses. Daniel From xgizzmo at slackbuilds.org Fri May 30 23:24:08 2008 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Fri, 30 May 2008 19:24:08 -0400 Subject: [Slackbuilds-users] Updates - 20080530 Message-ID: <200805301924.09045.xgizzmo@slackbuilds.org> Fri May 30 22:49:10 UTC 2008 academic/octave: Updated for version 3.0.1. Thanks to Kyle Guinn. academic/qtoctave: Updated for version 0.7.4. Thanks to 'lanceb' and Mauro Giachero for the update. --rworkman libraries/libcap: Updated for version 2.09. Thanks to Menno Duursmaa. multimedia/GoogleEarth: Fixed some ownership and permissions problems in the resulting package. Thanks to Wayne Walton for the report and fix. multimedia/kino: Fixed some ownership and permission problems in the resulting package. Thanks to Wayne Walton for the report and fix. network/ddclient: Fixed a minor bug in the build script (added creation of the /var/cache/ddclient directory). Thanks to Thiebo Herbst for the report. --rworkman system/apcupsd: Fixed an incorrect bit in README-SLACKWARE (location of the powerfail file). Thanks to Christian on the mailing list. --rworkman system/virtualbox-kernel: Added - This is the suplementary kernel driver for the VirtualBox virtualisation environment. system/virtualbox-ose: Added - VirtualBox Open Source Edition (OSE) is a general-purpose full virtualizer for x86 hardware. Thanks to Heinz Wiesinger and Mauro Giachero. --Erik Hanson system/wine: Updated for version 1.0rc2. Thanks to Robby Workman. --Erik Hanson