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 <rworkman at slackbuilds.org>:

> 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: <da3e877f0805010215v2cf9515ejdd6846d25611b6d8@mail.gmail.com>

On Thu, May 1, 2008 at 9:59 AM, <cnguyenminhtan at free.fr> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080501/9fb0a0af/attachment.htm>

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: <da3e877f0805010215v2cf9515ejdd6846d25611b6d8@mail.gmail.com>
References: <da3e877f0805010215v2cf9515ejdd6846d25611b6d8@mail.gmail.com>
Message-ID: <1209636468.481996745a5ef@imp.free.fr>

Selon Mauro Giachero <mauro.giachero at gmail.com>:

>
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080501/190a1850/attachment.sig>

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 <rworkman at 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
>  _______________________________________________
>  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.):

<wise at hubris0~/tmp> 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
<wise at hubris0~/tmp>

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 <listreader at lupulin.net> 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.):
> 
> <wise at hubris0~/tmp> 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
> <wise at hubris0~/tmp>
> 
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080502/fad047fa/attachment.asc>

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 <rworkman at slackbuilds.org> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080502/282a0d30/attachment.asc>

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: <da3e877f0805010215v2cf9515ejdd6846d25611b6d8@mail.gmail.com>
	<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 <mauro.giachero at gmail.com>:
> 
>> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080504/a4cce24d/attachment.htm>

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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080504/a480778f/attachment.htm>

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 <pc_warner at yahoo.com> 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: <a6f13f000805041211o632485eaw78df18ad29c29d09@mail.gmail.com>

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 <abrouwers at gmail.com> 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 <pc_warner at yahoo.com> 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: <b3ab647b0805041425y632f426cx67e8f38cee015225@mail.gmail.com>

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 <pc_warner at yahoo.com> 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 <pc_warner at 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.
> _______________________________________________
>  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: <a9aae8030805050611p559a64b7k67b4de88b5acfff9@mail.gmail.com>

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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/9f27ed35/attachment.htm>

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: <a9aae8030805050611p559a64b7k67b4de88b5acfff9@mail.gmail.com>
References: <a9aae8030805050611p559a64b7k67b4de88b5acfff9@mail.gmail.com>
Message-ID: <da3e877f0805050708m10b8d1eco74599f9025758c13@mail.gmail.com>

On Mon, May 5, 2008 at 3:11 PM, Ricardo Klein <klein.rfk at gmail.com> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/ff751928/attachment-0001.htm>

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: <mailman.18.1209996488.2599.slackbuilds-users@slackbuilds.org>
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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/47035ccf/attachment.htm>

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: <mailman.18.1209996488.2599.slackbuilds-users@slackbuilds.org>
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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/3674c50e/attachment.htm>

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: <mailman.18.1209996488.2599.slackbuilds-users@slackbuilds.org>
	<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 <pc_warner at yahoo.com> 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.<http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ>
>
> _______________________________________________
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/dc81a698/attachment.htm>

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: <mailman.18.1209996488.2599.slackbuilds-users@slackbuilds.org>	<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: <mailman.18.1209996488.2599.slackbuilds-users@slackbuilds.org>	<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: <da3e877f0805010215v2cf9515ejdd6846d25611b6d8@mail.gmail.com>
	<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 <frederic.touboul at 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 <mauro.giachero at gmail.com>:
> >
> >> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080505/55f36b20/attachment.htm>

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 <pc_warner at yahoo.com> 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 <pc_warner at yahoo.com> 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: <da3e877f0805010215v2cf9515ejdd6846d25611b6d8@mail.gmail.com>	<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 <rworkman at slackbuilds.org> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080507/a88f7724/attachment.htm>

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 <rworkman at slackbuilds.org> 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 <category> <package>
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 <category> <package>
# 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080508/adb86349/attachment.bin>

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 <category> <package>
> 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 <category> <package>
> # 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 <category>.
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 <category>.
> 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: <c7aebbcd0805080741u21e68708m828f79beeb325632@mail.gmail.com>

On Thu, May 8, 2008 at 8:20 AM, Cherife Li <cherife at dotimes.com> 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 <category> <package>
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 <category> <package>
# 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080508/4af03e7e/attachment.bin>

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: <c7aebbcd0805080741u21e68708m828f79beeb325632@mail.gmail.com>
References: <709075.96752.bm@omp217.mail.ukl.yahoo.com>	<48230C45.8000903@dotimes.com>
	<c7aebbcd0805080741u21e68708m828f79beeb325632@mail.gmail.com>
Message-ID: <48231721.8060605@chessgriffin.com>

Bob Lounsbury wrote:
> On Thu, May 8, 2008 at 8:20 AM, Cherife Li <cherife at dotimes.com> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080508/5461ea06/attachment.asc>

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:
> <div class="moz-text-flowed" style="font-family: -moz-fixed">Cherife 
> Li wrote:
>
>> IMHO, it's better to avoid using the <category>.
>> It will be convenient if SBO would maintain an full FILELIST file.
>
> http://slackbuilds.org/ports/$SLACKVERSION/$APP.tar.gz
>
> -RW
>
> </div>
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: <ecf35a1b0805081359m4e9fa5bbxdb2975d2a86ca22a@mail.gmail.com>

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 <mickeytintincolle at yahoo.fr>:
> Robby Workman wrote:
>>
>> <div class="moz-text-flowed" style="font-family: -moz-fixed">Cherife Li
>> wrote:
>>
>>> IMHO, it's better to avoid using the <category>.
>>> It will be convenient if SBO would maintain an full FILELIST file.
>>
>> http://slackbuilds.org/ports/$SLACKVERSION/$APP.tar.gz
>>
>> -RW
>>
>> </div>
>
> 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: <da3e877f0805110738m5606f3fen3b980e7afa9dd954@mail.gmail.com>

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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080511/8efed0e8/attachment.htm>

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: <da3e877f0805110746r5062c9f3x9cd675ee78572d7d@mail.gmail.com>

On Sun, May 11, 2008 at 1:16 PM, <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.
>
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080511/0e885cd8/attachment.htm>

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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080511/b6b7b9c6/attachment.asc>

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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080512/79adab45/attachment.sig>

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: <da3e877f0805110738m5606f3fen3b980e7afa9dd954@mail.gmail.com>
References: <1210440019.4825d9538c38d@webmail.ksu.edu>
	<da3e877f0805110738m5606f3fen3b980e7afa9dd954@mail.gmail.com>
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 <rworkman at slackbuilds.org> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080511/b45f682c/attachment.htm>

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: <a6f13f000805132006h7a3c3d91sf60bc0f8b23d689c@mail.gmail.com>

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 <rworkman at slackbuilds.org> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080515/2cb1aa10/attachment.sig>

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: <da3e877f0805150637q34763fc5kca2074a1d18fff6e@mail.gmail.com>

On Thu, May 15, 2008 at 12:12 PM, Audrius Ka?ukauskas <neobug at tornado.ktu.lt>
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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080515/880ef83e/attachment.htm>

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 <rworkman at slackbuilds.org> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080515/72fa11fe/attachment-0001.htm>

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: <d20938700805150926o7e52905cwf8d9195ba6aa3b3b@mail.gmail.com>

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: <d20938700805150926o7e52905cwf8d9195ba6aa3b3b@mail.gmail.com>
References: <d20938700805150926o7e52905cwf8d9195ba6aa3b3b@mail.gmail.com>
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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080515/5b918152/attachment.sig>

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: <d20938700805150926o7e52905cwf8d9195ba6aa3b3b@mail.gmail.com>
References: <d20938700805150926o7e52905cwf8d9195ba6aa3b3b@mail.gmail.com>
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