From crockabiscuit at gmail.com  Wed Jun  1 15:00:56 2011
From: crockabiscuit at gmail.com (crocket)
Date: Thu, 2 Jun 2011 00:00:56 +0900
Subject: [Slackbuilds-users] Hi I want to submit an update for rss2email.
In-Reply-To: <20110601012741.GA1836@canich.net>
References: <BANLkTi=rHPzGpAKp96ByLasdxOE14wfS3g@mail.gmail.com>
	<20110601012741.GA1836@canich.net>
Message-ID: <BANLkTimiCodOhGLWx3HR2O+pDQHgPgOvVw@mail.gmail.com>

Sure, I want to take over the maintenance of rss2email.

On Wed, Jun 1, 2011 at 10:27 AM, Tom Canich <tcanich at canich.net> wrote:
>> The updated slackbuild for 2.70 is attached to this email.
>>
>> Can you consider this and submit it to slackbuilds.org ?
>
> Hi Crocket,
>
> Actually, I don't use rss2email anymore. ?Would you like to take over
> maintaining it?
>
>
>
> Tom
>

From disturbed1976 at gmail.com  Wed Jun  1 21:26:22 2011
From: disturbed1976 at gmail.com (Keith Richie)
Date: Wed, 1 Jun 2011 17:26:22 -0400
Subject: [Slackbuilds-users] Bleachbit incomplete web page
Message-ID: <BANLkTim_s9Ni_apCwxXVjOKZZqAh=3OkDg@mail.gmail.com>

http://slackbuilds.org/repository/13.37/misc/bleachbit/

Searching for Bleachbit displays misc as the category, and presents an
incomplete webpage (no files) -- browsing by ftp shows bleachbit to be
under the system category with complete files

ftp://slackbuilds.org/13.37/system/bleachbit/

From luislupe at gmx.com  Thu Jun  2 22:42:01 2011
From: luislupe at gmx.com (Luis P. Mendes)
Date: Thu, 2 Jun 2011 23:42:01 +0100
Subject: [Slackbuilds-users] sbcl problem 13.37 64bits
Message-ID: <20110602224201.GE6539@localhost.lan>

Hi,

I installed slackbuild package sbcl in my Slackware64 13.37 box, but
can't run it.  Here's the output:
$ sbcl
fatal error encountered in SBCL pid 10736(tid 140737353918240):
can't find core file at /usr/local/lib/sbcl//sbcl.core

However, the file is in:
$ ll /usr/lib64/sbcl/sbcl.core 
-rw-r--r-- 1 root root 46055472 Mai 30 00:41 /usr/lib64/sbcl/sbcl.core

Is it only a problem with my installation or do you experience the
same?


Luis P. Mendes

From paul at oldcode.org  Thu Jun  2 23:32:06 2011
From: paul at oldcode.org (paul wisehart)
Date: Thu, 2 Jun 2011 19:32:06 -0400
Subject: [Slackbuilds-users] sbcl problem 13.37 64bits
In-Reply-To: <20110602224201.GE6539@localhost.lan>
References: <20110602224201.GE6539@localhost.lan>
Message-ID: <20110602233206.GJ10632@forge>

On Thu, Jun 02, 2011 at 11:42:01PM +0100, Luis P. Mendes wrote:
> $ sbcl
> fatal error encountered in SBCL pid 10736(tid 140737353918240):
> can't find core file at /usr/local/lib/sbcl//sbcl.core
> 
> However, the file is in:
> $ ll /usr/lib64/sbcl/sbcl.core 
> -rw-r--r-- 1 root root 46055472 Mai 30 00:41 /usr/lib64/sbcl/sbcl.core


Can you try using a new shell process, so the 
SBCL_HOME setting can take effect?

--pkw

From hba.nihilismus at gmail.com  Fri Jun  3 01:36:35 2011
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Thu, 2 Jun 2011 20:36:35 -0500
Subject: [Slackbuilds-users] sbcl problem 13.37 64bits
In-Reply-To: <20110602224201.GE6539@localhost.lan>
References: <20110602224201.GE6539@localhost.lan>
Message-ID: <BANLkTinYpTHn+w2-gGv+=Zb=iNZ0VCH8Cw@mail.gmail.com>

On Thu, Jun 2, 2011 at 5:42 PM, Luis P. Mendes <luislupe at gmx.com> wrote:
> Is it only a problem with my installation or do you experience the
> same?

Hi Luis.

It's the same in x86 since the profile.d scripts are *copied* (with
0644 as permission). Here's the lines in sbcl.SlackBuild:

    # scripts in profile.d that set SBCL_HOME
    mkdir -p $PKG/etc/profile.d
    cp $CWD/sbcl.csh $CWD/sbcl.sh $PKG/etc/profile.d

You can fix this just by setting execution permissions to both scripts:

   root# chmod +x /etc/profile.d/sbcl.*

And btw, sbcl.SlackBuild can be fixed with:

    - cp $CWD/sbcl.csh $CWD/sbcl.sh $PKG/etc/profile.d
    + install -m 0755 $CWD/sbcl.sh  $PKG/etc/profile.d
    + install -m 0755 $CWD/sbcl.csh $CWD/sbcl.sh $PKG/etc/profile.d

-- 
-
hba | Antonio Hern?ndez Blas | Mexico, Mx.
http://hba.dyndns.info | http://barrapunto.com/~hba/ |
irc://irc.freenode.org/hba,isnick,needpass

From rworkman at slackbuilds.org  Fri Jun  3 02:07:18 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 2 Jun 2011 21:07:18 -0500
Subject: [Slackbuilds-users] sbcl problem 13.37 64bits
In-Reply-To: <20110602224201.GE6539@localhost.lan>
References: <20110602224201.GE6539@localhost.lan>
Message-ID: <20110602210718.7274f618@liberty.rlwhome.lan>

On Thu, 2 Jun 2011 23:42:01 +0100
"Luis P. Mendes" <luislupe at gmx.com> wrote:

> I installed slackbuild package sbcl in my Slackware64 13.37 box, but
> can't run it.  Here's the output:
> $ sbcl
> fatal error encountered in SBCL pid 10736(tid 140737353918240):
> can't find core file at /usr/local/lib/sbcl//sbcl.core
> 
> However, the file is in:
> $ ll /usr/lib64/sbcl/sbcl.core 
> -rw-r--r-- 1 root root 46055472 Mai 30 00:41 /usr/lib64/sbcl/sbcl.core
> 
> Is it only a problem with my installation or do you experience the
> same?


Fixed using hba's idea in my branch: 81e92856ebfd3bf636e4e498773ec49d167f4ca4

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110602/e54eba17/attachment.asc>

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Mon Jun  6 14:53:47 2011
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Mon, 06 Jun 2011 16:53:47 +0200
Subject: [Slackbuilds-users] Flashplayer has new md5sum
Message-ID: <4DECE9FB.8080205@skmail.ikp.physik.tu-darmstadt.de>

Hello!

Just installed it and the new one is:

3676dda1f6e3d44a3d261bfdd0f2926c

(Double checked: download from the SlackBuild's link and by just 
visiting adobes website.)

Best regards,

Serban Udrea

From audrius at neutrino.lt  Tue Jun  7 17:10:23 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Tue, 7 Jun 2011 20:10:23 +0300
Subject: [Slackbuilds-users] Announcing lxc-slack
Message-ID: <20110607171023.GA25966@kiras>

Hi,

I've announced my lxc-slack script for creating Slackware LXC containers
on LQ, but thought it may be interesting to people on this mailing list,
so here's the link:

http://www.linuxquestions.org/questions/slackware-14/announcing-lxc-slack-885017/

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110607/e94e4e79/attachment.asc>

From spamered at hotmail.com  Thu Jun  9 09:19:25 2011
From: spamered at hotmail.com (Hac Er)
Date: Thu, 9 Jun 2011 11:19:25 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
Message-ID: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>

Hello.

I have discovered this piece of wisdom in the SlackBuilds site:

"If you don't trust us to check the scripts for malicious activity,
then please move along."

This has made me wonder how secure is in fact the SlackBuild software.
Sure, 99.9% of contributors are honorable people with pure motivations
who work to enchance the whole Slackware comunity, but Black Hats do
exist too out there.

The main reason I prefer compiling myself my software is because
unofficial binary packages can easily be troyanized or otherwise
infected by malware. By using build scrips, you can just get the source
code from the original author, then package it and install. However,
many appications cannot be obtained from the original author anymore.

Let's take Snort as an example. Snort upstream developers just provide
the latest version in their site. That means SlackBuilds.org cannot just
link to the original Snort x.y.z once Snort x.y.z+1 is released. This
forces the script mantainer (Niels Horn in this case) to make Snort
x.y.z availible from another location (www.nielshorn.net in this case)
and link to it from SlackBuild.org.

I trust SlackBuild's statement of them checking the scripts for evil
contents. In fact, many scripts are so simple that you can check them
quickly in a few minutes. However... what happens if Niels Horn is one
of those Black Hats who live in the shadows, slowly infecting computers
all around the world as part of his plan for conquering the Earth? What
is preventing him from patching the original Snort x.y.z and turning it
into a dangerous backdoor? If Snort x.y.z was in www.snort.org, you
could easily check if Niel's version is the same, but you only will be
able to check against x.y.z+1 version. You can still modify the build
script and build the last version of Snort from the authors website,
yes, but this would be no solution for Niel infecting thousands of
computers.

What procedure is taken in order to avoid this nightmare?
Because, knowing SlackBuild.org has a very good reputation and its
software works flawlessly most of the times, I asume you have some
method to prevent Niel and his friends from taking over Slackware
Universe.  

Niel, if you are reading this, sorry for being the bad guy of the
story. I needed an example, and Snort was the first that came to my
mind :-)


From willysr at gmail.com  Thu Jun  9 09:36:00 2011
From: willysr at gmail.com (Willy Sudiarto Raharjo)
Date: Thu, 9 Jun 2011 16:36:00 +0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
Message-ID: <BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>

> I trust SlackBuild's statement of them checking the scripts for evil
> contents. In fact, many scripts are so simple that you can check them
> quickly in a few minutes. However... what happens if Niels Horn is one
> of those Black Hats who live in the shadows, slowly infecting computers
> all around the world as part of his plan for conquering the Earth? What
> is preventing him from patching the original Snort x.y.z and turning it
> into a dangerous backdoor? If Snort x.y.z was in www.snort.org, you
> could easily check if Niel's version is the same, but you only will be
> able to check against x.y.z+1 version. You can still modify the build
> script and build the last version of Snort from the authors website,
> yes, but this would be no solution for Niel infecting thousands of
> computers.
>
> What procedure is taken in order to avoid this nightmare?
> Because, knowing SlackBuild.org has a very good reputation and its
> software works flawlessly most of the times, I asume you have some
> method to prevent Niel and his friends from taking over Slackware
> Universe.

That's why in SBo, they never give any source in the repository
you have to download the source by yourself

if you don't believe the script, you can check whether it tries to
patch or do something malicious and you can always edit the script
according to your senses.

In most cases, the script can be used to compile x.y+1, x.y+2, or even more
you only need to edit the VERSION line


-- 
Willy Sudiarto Raharjo
Personal Blog : http://willysr.blogspot.com
Linux Blog: http://slackblogs.blogspot.com

From rob0 at slackbuilds.org  Thu Jun  9 11:00:37 2011
From: rob0 at slackbuilds.org (Rob McGee)
Date: Thu, 9 Jun 2011 06:00:37 -0500
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
Message-ID: <20110609110037.GG10482@cardinal>

On Thu, Jun 09, 2011 at 11:19:25AM +0200, Hac Er wrote:
> I have discovered this piece of wisdom in the SlackBuilds site:
> 
> "If you don't trust us to check the scripts for malicious
> activity, then please move along."

Wise words indeed.

> I trust SlackBuild's statement of them checking the scripts for 
> evil contents. In fact, many scripts are so simple that you can 
> check them quickly in a few minutes. However... what happens if 
> Niels Horn is one of those Black Hats who live in the shadows, 
> slowly infecting computers all around the world as part of his
> plan for conquering the Earth?

It's not Niels. It's Michiel. We have suspected it all along, and 
have known it for quite some time. I'm afraid is is too late now. 
Relax and cooperate with him; he might not hurt you.
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From niels.horn at gmail.com  Thu Jun  9 11:04:32 2011
From: niels.horn at gmail.com (Niels Horn)
Date: Thu, 9 Jun 2011 08:04:32 -0300
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <20110609110037.GG10482@cardinal>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<20110609110037.GG10482@cardinal>
Message-ID: <BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>

On Thu, Jun 9, 2011 at 8:00 AM, Rob McGee <rob0 at slackbuilds.org> wrote:
> On Thu, Jun 09, 2011 at 11:19:25AM +0200, Hac Er wrote:
>> I have discovered this piece of wisdom in the SlackBuilds site:
>>
>> "If you don't trust us to check the scripts for malicious
>> activity, then please move along."
>
> Wise words indeed.
>
>> I trust SlackBuild's statement of them checking the scripts for
>> evil contents. In fact, many scripts are so simple that you can
>> check them quickly in a few minutes. However... what happens if
>> Niels Horn is one of those Black Hats who live in the shadows,
>> slowly infecting computers all around the world as part of his
>> plan for conquering the Earth?
>
> It's not Niels. It's Michiel. We have suspected it all along, and
> have known it for quite some time. I'm afraid is is too late now.
> Relax and cooperate with him; he might not hurt you.
> --
> ? ?Rob McGee - /dev/rob0 - rob0 at slackbuilds.org
> _______________________________________________

To all:

Please check my picture on my site: http://www.nielshorn.net/other/personal.php
That's a *brown* hat, not a black hat!

--
Niels Horn

From dave at dawoodfall.net  Thu Jun  9 11:20:32 2011
From: dave at dawoodfall.net (David Woodfall)
Date: Thu, 9 Jun 2011 12:20:32 +0100
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<20110609110037.GG10482@cardinal>
	<BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>
Message-ID: <20110609112032.GA9005@Junius>

On (08:04 09/06/11), Niels Horn <niels.horn at gmail.com> put forth the proposition:
>On Thu, Jun 9, 2011 at 8:00 AM, Rob McGee <rob0 at slackbuilds.org> wrote:
>> On Thu, Jun 09, 2011 at 11:19:25AM +0200, Hac Er wrote:
>>> I have discovered this piece of wisdom in the SlackBuilds site:
>>>
>>> "If you don't trust us to check the scripts for malicious
>>> activity, then please move along."
>>
>> Wise words indeed.
>>
>>> I trust SlackBuild's statement of them checking the scripts for
>>> evil contents. In fact, many scripts are so simple that you can
>>> check them quickly in a few minutes. However... what happens if
>>> Niels Horn is one of those Black Hats who live in the shadows,
>>> slowly infecting computers all around the world as part of his
>>> plan for conquering the Earth?
>>
>> It's not Niels. It's Michiel. We have suspected it all along, and
>> have known it for quite some time. I'm afraid is is too late now.
>> Relax and cooperate with him; he might not hurt you.
>> --
>> ? ?Rob McGee - /dev/rob0 - rob0 at slackbuilds.org
>> _______________________________________________
>
>To all:
>
>Please check my picture on my site: http://www.nielshorn.net/other/personal.php
>That's a *brown* hat, not a black hat!
>
>--
>Niels Horn

I understand the OP's point, but then someone could hack the server of
whoever provides the source and we have the same problem. I doubt
there is any realistic way of checking source, apart being vigilant
and watchful when using software.

Nice hat by the way Niels ;)

D.

From Bradley at NorthTech.US  Thu Jun  9 11:40:12 2011
From: Bradley at NorthTech.US (Bradley D. Thornton)
Date: Thu, 09 Jun 2011 04:40:12 -0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>	<20110609110037.GG10482@cardinal>
	<BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>
Message-ID: <4DF0B11C.4030308@NorthTech.US>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160



On 06/09/2011 04:04 AM, Niels Horn wrote:
> On Thu, Jun 9, 2011 at 8:00 AM, Rob McGee <rob0 at slackbuilds.org> wrote:
>> On Thu, Jun 09, 2011 at 11:19:25AM +0200, Hac Er wrote:
>>> I have discovered this piece of wisdom in the SlackBuilds site:
>>>
>>> "If you don't trust us to check the scripts for malicious
>>> activity, then please move along."
>>
>> Wise words indeed.
>>
>>> I trust SlackBuild's statement of them checking the scripts for
>>> evil contents. In fact, many scripts are so simple that you can
>>> check them quickly in a few minutes. However... what happens if
>>> Niels Horn is one of those Black Hats who live in the shadows,
>>> slowly infecting computers all around the world as part of his
>>> plan for conquering the Earth?
>>
>> It's not Niels. It's Michiel. We have suspected it all along, and
>> have known it for quite some time. I'm afraid is is too late now.
>> Relax and cooperate with him; he might not hurt you.
>> --
>>    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org
>> _______________________________________________
> 
> To all:
> 
> Please check my picture on my site: http://www.nielshorn.net/other/personal.php
> That's a *brown* hat, not a black hat!
> 
> --
> Niels Horn

I don't think a black hat would have bothered me as much as a *red* one
Niels ;)


- -- 
Bradley D. Thornton
Manager Network Services
NorthTech Computer
TEL: +1.760.666.2703  (US)
TEL: +44.203.318.2755 (UK)
http://NorthTech.US

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Find this cert at x-hkp://pool.sks-keyservers.net

iQEcBAEBAwAGBQJN8LEaAAoJEE1wgkIhr9j3ikMH/20m0bAhrHNFXdRdHrgqG876
AF3yfrMRtUR7kVIhCaOyq/RQ1qJdiwQdMXytkq+3iPxzM44qcz4IibpKcPJ5njzm
9tIqhKeuW2PqTy7gDSxmIjxhMc0llJH6vPJsoNC2RWbZdVQ10253oq8tH8FsZVBz
7OnVswG+LEUOmhPIXgC+qI9JadpcH9WlEtkOm+QIaOGR9z9XEfBt33SWNfxqy6Uz
aKJQGNOF4x9r43jWToxG2NUrxAgBAs7Om4Tf+VxaomoREOQvX4BCUtG5oqS5U9ow
AzouY/nO2mRUp3jcdyJHvTRgTu8jMQV9nqhQV765T+LKTEdXM7hMnBMl9g2aRSA=
=uJ5e
-----END PGP SIGNATURE-----

From spamered at hotmail.com  Thu Jun  9 11:45:11 2011
From: spamered at hotmail.com (Hac Er)
Date: Thu, 9 Jun 2011 13:45:11 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
Message-ID: <BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>

On Thu, 9 Jun 2011 16:36:00 +0700
Willy Sudiarto Raharjo <willysr at gmail.com> wrote:

> That's why in SBo, they never give any source in the repository
> you have to download the source by yourself
> 
> if you don't believe the script, you can check whether it tries to
> patch or do something malicious and you can always edit the script
> according to your senses.
> 
> In most cases, the script can be used to compile x.y+1, x.y+2, or
> even more you only need to edit the VERSION line
> 

I get your point. Anyways, even being true that you can track the source
by yourself, or modifiy the SlackBuild if necessary, the backgroud
question remains unanswered.

SlackBuilds.org does not host the sources itself, but provides links
to them. I wouldn't trust some of these links if I were given no
guarantee they are trustworthy. That's exactly what I am asking: How do
SBo administrators ensure they are linking to the right sources?

This is a non-trivial question. Experience shows that many sites who
trust their uploaders to play fair end up hosting some percentage of
malware. I myself use to track the original code to build my packages,
but look at this:

http://slackbuilds.org/repository/13.37/multimedia/HandBrake/

****TRACKING DOWN THIS THING IS HELL!!!******

It is understandable that many will just say "What the hell, I'm not
going to spend the whole week checking this packages one by one". They
will follow the links provided by SBo. If the mantainer (klaatu in
this case) was not as honorable as we might think, he could post a
link to a troyaniced "libass" (for example).

Paranoid? Sure. But the fact is that the link that SBo provides for
libass is:

http://libass.googlecode.com/files/libass-0.9.9.tar.bz2

when the libass needed by the upstream HandBrake is here:

http://download.m0k.org/handbrake/contrib/libass-0.9.9.tar.bz2 (I
obtained this link from the source code itself).

I have tested both of them by various checksums (it is good to use more
than one. MD5 is good for error detection, but is vulnerable when used
for security purposes). It seems klatuu is a man of honor after all.
Anyway, if he was not, and no one checked if libass is clean, klatuu
would own many computers he has not bought, if you get my point.

The question remains: How do administrators decide if the links they
post are trustworthy?






 




From spamered at hotmail.com  Thu Jun  9 11:59:49 2011
From: spamered at hotmail.com (Hac Er)
Date: Thu, 9 Jun 2011 13:59:49 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <20110609112032.GA9005@Junius>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<20110609110037.GG10482@cardinal>
	<BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>
	<20110609112032.GA9005@Junius>
Message-ID: <BLU0-SMTP13696E20C15488860538F4ED6650@phx.gbl>

On Thu, 9 Jun 2011 12:20:32 +0100
David Woodfall <dave at dawoodfall.net> wrote:

> 
> I understand the OP's point, but then someone could hack the server of
> whoever provides the source and we have the same problem. I doubt
> there is any realistic way of checking source, apart being vigilant
> and watchful when using software.
> 
> Nice hat by the way Niels ;)
> 
> D.

I know.

However, many do provide means to test if what you are downloading is
what you want to download. They could crack www.snort.org and hang
there a evil copy of Snort, with a fake signature and a fake GPG key,
but if they did, anyone who had downloaded the GPG key a week before
would know there is something wrong when checked "snort latest version"
and found the signatures mismatch.

The only way you can ensure no one is gonna break into your computer is
trashing away your machines and rejecting every shape of I.T. from your
live. For those who don't want to apply so extreme measures, there is
prudence.

From dragonwisard at gmail.com  Thu Jun  9 12:20:43 2011
From: dragonwisard at gmail.com (Ben Mendis)
Date: Thu, 9 Jun 2011 08:20:43 -0400
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
Message-ID: <BANLkTimhnhWm=hLs3MpoWwyNygAFUHTUbg@mail.gmail.com>

I'm sorry, but this is really nothing new.

More wisdom from the ancients: http://cm.bell-labs.com/who/ken/trust.html


On Thu, Jun 9, 2011 at 5:19 AM, Hac Er <spamered at hotmail.com> wrote:

> Hello.
>
> I have discovered this piece of wisdom in the SlackBuilds site:
>
> "If you don't trust us to check the scripts for malicious activity,
> then please move along."
>
> This has made me wonder how secure is in fact the SlackBuild software.
> Sure, 99.9% of contributors are honorable people with pure motivations
> who work to enchance the whole Slackware comunity, but Black Hats do
> exist too out there.
>
> The main reason I prefer compiling myself my software is because
> unofficial binary packages can easily be troyanized or otherwise
> infected by malware. By using build scrips, you can just get the source
> code from the original author, then package it and install. However,
> many appications cannot be obtained from the original author anymore.
>
> Let's take Snort as an example. Snort upstream developers just provide
> the latest version in their site. That means SlackBuilds.org cannot just
> link to the original Snort x.y.z once Snort x.y.z+1 is released. This
> forces the script mantainer (Niels Horn in this case) to make Snort
> x.y.z availible from another location (www.nielshorn.net in this case)
> and link to it from SlackBuild.org.
>
> I trust SlackBuild's statement of them checking the scripts for evil
> contents. In fact, many scripts are so simple that you can check them
> quickly in a few minutes. However... what happens if Niels Horn is one
> of those Black Hats who live in the shadows, slowly infecting computers
> all around the world as part of his plan for conquering the Earth? What
> is preventing him from patching the original Snort x.y.z and turning it
> into a dangerous backdoor? If Snort x.y.z was in www.snort.org, you
> could easily check if Niel's version is the same, but you only will be
> able to check against x.y.z+1 version. You can still modify the build
> script and build the last version of Snort from the authors website,
> yes, but this would be no solution for Niel infecting thousands of
> computers.
>
> What procedure is taken in order to avoid this nightmare?
> Because, knowing SlackBuild.org has a very good reputation and its
> software works flawlessly most of the times, I asume you have some
> method to prevent Niel and his friends from taking over Slackware
> Universe.
>
> Niel, if you are reading this, sorry for being the bad guy of the
> story. I needed an example, and Snort was the first that came to my
> mind :-)
>
> _______________________________________________
> 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/20110609/631d4929/attachment.html>

From willysr at gmail.com  Thu Jun  9 14:24:23 2011
From: willysr at gmail.com (Willy Sudiarto Raharjo)
Date: Thu, 9 Jun 2011 21:24:23 +0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
Message-ID: <BANLkTimgsfsmr8eULXQc1_4_WF_FMCJrdw@mail.gmail.com>

> I get your point. Anyways, even being true that you can track the source
> by yourself, or modifiy the SlackBuild if necessary, the backgroud
> question remains unanswered.
>
> SlackBuilds.org does not host the sources itself, but provides links
> to them. I wouldn't trust some of these links if I were given no
> guarantee they are trustworthy. That's exactly what I am asking: How do
> SBo administrators ensure they are linking to the right sources?

> The question remains: How do administrators decide if the links they
> post are trustworthy?

AFAIK, all admin (at least the one who commited the update and post it
on the list) tested all submissions before they agreed to approve it.
If it gets suspicious, i'm sure it won't pass their filter :)


-- 
Willy Sudiarto Raharjo
Personal Blog : http://willysr.blogspot.com
Linux Blog: http://slackblogs.blogspot.com

From chris.abela at maltats.com  Thu Jun  9 14:25:53 2011
From: chris.abela at maltats.com (Chris ABELA)
Date: Thu, 9 Jun 2011 16:25:53 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
Message-ID: <054537E67136489A963B616B7221F84F@maltats.com>



What procedure is taken in order to avoid this nightmare?
Because, knowing SlackBuild.org has a very good reputation and its
software works flawlessly most of the times, I asume you have some
method to prevent Niel and his friends from taking over Slackware
Universe.  

From: slackbuilds-users-bounces at slackbuilds.org
[mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Hac Er
Sent: 09 June 2011 11:19
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] Corcern about sources' precedence

My advise is the following:

1. If you can, audit the source code.
2. If you have a liability, prepare your Case (see 1).
3. If you cannot audit the code, then don't worry, because it is useless to
worry.

This holds for wherever the codes originates. As far as I know, the only
source code that comes with an audit report is xinetd-2.3.0.

Chris



From niels.horn at gmail.com  Thu Jun  9 14:43:27 2011
From: niels.horn at gmail.com (Niels Horn)
Date: Thu, 9 Jun 2011 11:43:27 -0300
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF0B11C.4030308@NorthTech.US>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<20110609110037.GG10482@cardinal>
	<BANLkTimA22WF9kpuSkWFwLV1=3RE6DSbrw@mail.gmail.com>
	<4DF0B11C.4030308@NorthTech.US>
Message-ID: <BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>

On Thu, Jun 9, 2011 at 8:40 AM, Bradley D. Thornton
<Bradley at northtech.us> wrote:
>
> I don't think a black hat would have bothered me as much as a *red* one
> Niels ;)
>

Red Hat? No I'd never use such a thing... :-)

--
Niels

From notklaatu at straightedgelinux.com  Thu Jun  9 15:11:08 2011
From: notklaatu at straightedgelinux.com (Klaatu)
Date: Thu, 9 Jun 2011 11:11:08 -0400
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF0B11C.4030308@NorthTech.US>
	<BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>
Message-ID: <201106091111.08951.notklaatu@straightedgelinux.com>

There's no need to follow links from SlackBuilds.org for anything more than 
the SlackBuild itself, which you can audit and verify manually.  Proceed to 
your trusted site for the source code, grab the source, edit the SlackBuild 
script as needed, and build. 

I guess the larger issue, really, as Ben I think is saying, how do you know 
ANY source code you download is trustworthy?  As Ken Thompson says in Ben's 
link (great article, btw, thanks for the link Ben)  "The moral is obvious. You 
can't trust code that you did not totally create yourself."

-- klaatu



On Thursday, June 09, 2011 10:43:27 am Niels Horn wrote:
> On Thu, Jun 9, 2011 at 8:40 AM, Bradley D. Thornton
> 
> <Bradley at northtech.us> wrote:
> > I don't think a black hat would have bothered me as much as a *red* one
> > Niels ;)
> 
> Red Hat? No I'd never use such a thing... :-)
> 
> --
> Niels
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/

From spamered at hotmail.com  Thu Jun  9 16:01:04 2011
From: spamered at hotmail.com (Hac Er)
Date: Thu, 9 Jun 2011 18:01:04 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <201106091111.08951.notklaatu@straightedgelinux.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF0B11C.4030308@NorthTech.US>
	<BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>
	<201106091111.08951.notklaatu@straightedgelinux.com>
Message-ID: <BLU0-SMTP106B9317FAC026D7375D479D6650@phx.gbl>

On Thu, 9 Jun 2011 11:11:08 -0400
Klaatu <notklaatu at straightedgelinux.com> wrote:
> There's no need to follow links from SlackBuilds.org for anything
> more than the SlackBuild itself, which you can audit and verify
> manually.  Proceed to your trusted site for the source code, grab the
> source, edit the SlackBuild script as needed, and build. 
> 
> I guess the larger issue, really, as Ben I think is saying, how do
> you know ANY source code you download is trustworthy?  As Ken
> Thompson says in Ben's link (great article, btw, thanks for the link
> Ben)  "The moral is obvious. You can't trust code that you did not
> totally create yourself."
> 
> -- klaatu

Hello, klaatu.

I know you don't need to follow links fron SlackBuilds, but I think
most people will follow them. After all, the links are there for
convenience, aren't them? That's why I think it is important to have
some control over them.

Regarding the trustworthy of upstream software, I must say I largely
agree with Ken Thomsom. If you want something even more paranoid, you
have to look wipe's man page to discover how goverments can take over
your hard drives implementing hiden backdoors in the hardware itself.
Anyway, you cannot even trust your own software: shall your compiler be
compromised, you are in trouble.

When you download upstream software, you do it thinking upstream
developer is a nice person, that is, you are trusting one man. When you
download a binary package, you do it thinking that both the developer
and the packager are good guys. That is, you are trusting two men. This
is pure theory of machine survival: the more components you include in
the mechanism, the higher the likeness of any of them failing. Using
upstream software is not risk free, but is less risky than using
packages or uncontrolled builds.

Auditing the code, as Chris suggests, seems nice until you realize
your window manager is twelve thousand lines of code long. Many times 
you have to deal with binary stuff for which the source is unaccesible.
The kernel itself is damn long and includes lots of blobs (unless you
take them out, of course). Most important, the average user does not
know a word of code. I know one or two only :-)

Budda says: "If you cannot fix it, don't worry, because it is useless".
I am not worrying about upstream code. I am worrying about the people
between upstream and the users.

P.D: klatuu, your HandBrake build works nice in my computer. Very kind
of you to gather all those packages!

From chris.abela at maltats.com  Thu Jun  9 16:21:08 2011
From: chris.abela at maltats.com (chris.abela at maltats.com)
Date: Thu, 9 Jun 2011 16:21:08 +0000
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP106B9317FAC026D7375D479D6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl><4DF0B11C.4030308@NorthTech.US><BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com><201106091111.08951.notklaatu@straightedgelinux.com><BLU0-SMTP106B9317FAC026D7375D479D6650@phx.gbl>
Message-ID: <1539409574-1307636455-cardhu_decombobulator_blackberry.rim.net-2063865689-@b4.c6.bise7.blackberry>

I consider this from the point of liability.

If you can employ an auditor to mitigate your liability, then just do it.

If you do not have any liabilities then you have no problems.

If you have liability and you do not afford an auditor then you are in the wrong business.

Chris
Powered by BlackBerry? from Vodafone

-----Original Message-----
From: Hac Er <spamered at hotmail.com>
Sender: slackbuilds-users-bounces at slackbuilds.orgDate: Thu, 9 Jun 2011 18:01:04 
To: <slackbuilds-users at slackbuilds.org>
Reply-To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Corcern about sources' procedence

On Thu, 9 Jun 2011 11:11:08 -0400
Klaatu <notklaatu at straightedgelinux.com> wrote:
> There's no need to follow links from SlackBuilds.org for anything
> more than the SlackBuild itself, which you can audit and verify
> manually.  Proceed to your trusted site for the source code, grab the
> source, edit the SlackBuild script as needed, and build. 
> 
> I guess the larger issue, really, as Ben I think is saying, how do
> you know ANY source code you download is trustworthy?  As Ken
> Thompson says in Ben's link (great article, btw, thanks for the link
> Ben)  "The moral is obvious. You can't trust code that you did not
> totally create yourself."
> 
> -- klaatu

Hello, klaatu.

I know you don't need to follow links fron SlackBuilds, but I think
most people will follow them. After all, the links are there for
convenience, aren't them? That's why I think it is important to have
some control over them.

Regarding the trustworthy of upstream software, I must say I largely
agree with Ken Thomsom. If you want something even more paranoid, you
have to look wipe's man page to discover how goverments can take over
your hard drives implementing hiden backdoors in the hardware itself.
Anyway, you cannot even trust your own software: shall your compiler be
compromised, you are in trouble.

When you download upstream software, you do it thinking upstream
developer is a nice person, that is, you are trusting one man. When you
download a binary package, you do it thinking that both the developer
and the packager are good guys. That is, you are trusting two men. This
is pure theory of machine survival: the more components you include in
the mechanism, the higher the likeness of any of them failing. Using
upstream software is not risk free, but is less risky than using
packages or uncontrolled builds.

Auditing the code, as Chris suggests, seems nice until you realize
your window manager is twelve thousand lines of code long. Many times 
you have to deal with binary stuff for which the source is unaccesible.
The kernel itself is damn long and includes lots of blobs (unless you
take them out, of course). Most important, the average user does not
know a word of code. I know one or two only :-)

Budda says: "If you cannot fix it, don't worry, because it is useless".
I am not worrying about upstream code. I am worrying about the people
between upstream and the users.

P.D: klatuu, your HandBrake build works nice in my computer. Very kind
of you to gather all those packages!
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/


From gmartin at gmartin.org  Thu Jun  9 16:02:36 2011
From: gmartin at gmartin.org (gmartin)
Date: Thu, 9 Jun 2011 12:02:36 -0400
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <201106091111.08951.notklaatu@straightedgelinux.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF0B11C.4030308@NorthTech.US>
	<BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>
	<201106091111.08951.notklaatu@straightedgelinux.com>
Message-ID: <BANLkTi=Q6uCCB83+jWt4Hcptv-95nF0YcA@mail.gmail.com>

On Thu, Jun 9, 2011 at 11:11 AM, Klaatu <notklaatu at straightedgelinux.com>wrote:

> There's no need to follow links from SlackBuilds.org for anything more than
> the SlackBuild itself, which you can audit and verify manually.  Proceed to
> your trusted site for the source code, grab the source, edit the SlackBuild
> script as needed, and build.
>
> I guess the larger issue, really, as Ben I think is saying, how do you know
> ANY source code you download is trustworthy?  As Ken Thompson says in Ben's
> link (great article, btw, thanks for the link Ben)  "The moral is obvious.
> You
> can't trust code that you did not totally create yourself."
>
> -- klaatu
>
To me this comes down to reputation within the community.  I don't know
anyone involved in the snort project and have no reason to trust their code
except that it is public and open and hopefully there are eyes looking for
such things.  But in the end is is a large, faceless community - to me.
 Enter Niels (thanks, btw, for lending us your reputation for this
discussion).  He is part of a much smaller and more well known to me group -
the slackbuild contributers.  While I know the slackbuild admins are only
reviewing the script, and not Niels copy of of version x.y.z, he has,
nevertheless, developed a large positive personal reputation in the
community.  He could choose to burn that trust and we likely would not
discover it right away.  But the fact that he has earned his reputation over
time is an indicator that he is less likely to harm in the future.
 For me, it is easier to trust Niels then Snort due to the size of ther SB
community and my closer connection to it.
Perhaps the thing for you to do is spot check his (and others') tar ball
against the site's published signature (assuming it is available) for that
version.  This would give both trust AND verify .

\\Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110609/bf0a1fca/attachment.html>

From alien at slackbuilds.org  Thu Jun  9 17:09:28 2011
From: alien at slackbuilds.org (Eric Hameleers (SBo))
Date: Thu, 09 Jun 2011 19:09:28 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTi=Q6uCCB83+jWt4Hcptv-95nF0YcA@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>	<4DF0B11C.4030308@NorthTech.US>	<BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>	<201106091111.08951.notklaatu@straightedgelinux.com>
	<BANLkTi=Q6uCCB83+jWt4Hcptv-95nF0YcA@mail.gmail.com>
Message-ID: <4DF0FE48.8070906@slackbuilds.org>

Op 9-6-2011 18:02, gmartin schreef:

> Enter Niels (thanks, btw, for lending us your reputation for this
> discussion).  He is part of a much smaller and more well known to me
> group - the slackbuild contributers.

Niels is one of the admins of slackbuilds.org.

If you do not trust his contributions, then there is the door ------->

Eric

From gmartin at gmartin.org  Thu Jun  9 17:26:47 2011
From: gmartin at gmartin.org (gmartin)
Date: Thu, 9 Jun 2011 13:26:47 -0400
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF0FE48.8070906@slackbuilds.org>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF0B11C.4030308@NorthTech.US>
	<BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>
	<201106091111.08951.notklaatu@straightedgelinux.com>
	<BANLkTi=Q6uCCB83+jWt4Hcptv-95nF0YcA@mail.gmail.com>
	<4DF0FE48.8070906@slackbuilds.org>
Message-ID: <BANLkTik9yFibrABqrnsSYMp1mv7kC2gF3A@mail.gmail.com>

\\Greg



On Thu, Jun 9, 2011 at 1:09 PM, Eric Hameleers (SBo)
<alien at slackbuilds.org>wrote:

> Op 9-6-2011 18:02, gmartin schreef:
>
> > Enter Niels (thanks, btw, for lending us your reputation for this
> > discussion).  He is part of a much smaller and more well known to me
> > group - the slackbuild contributers.
>
> Niels is one of the admins of slackbuilds.org.
>
> If you do not trust his contributions, then there is the door ------->
>
> Eric
>
>
>
I do trust him.  I hope nothing I said implied anyting else.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110609/732022d6/attachment-0001.html>

From spamered at hotmail.com  Thu Jun  9 17:47:07 2011
From: spamered at hotmail.com (Hac Er)
Date: Thu, 9 Jun 2011 19:47:07 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF0FE48.8070906@slackbuilds.org>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF0B11C.4030308@NorthTech.US>
	<BANLkTikwQH6eMtLZWHna_cqxGD1VA=+0sQ@mail.gmail.com>
	<201106091111.08951.notklaatu@straightedgelinux.com>
	<BANLkTi=Q6uCCB83+jWt4Hcptv-95nF0YcA@mail.gmail.com>
	<4DF0FE48.8070906@slackbuilds.org>
Message-ID: <BLU0-SMTP112D45237C25CB7785CD7DBD6650@phx.gbl>

Eric Hameleers wrote:

> Niels is one of the admins of slackbuilds.org.
> 
> If you do not trust his contributions, then there is the door ------->

I think this is another version of a piece of wisdom I have already
mentioned...

It seems I did choose a bad example with Snort and Neils. Sorry if
someone got offended.

By the way, Eric, thanks for your multilib and LibreOffice packages.

Chris wrote:

>If you do not have any liabilities then you have no problems.
>
>If you have liability and you do not afford an auditor then you are in
>the wrong business.

Not everybody can afford an auditor, but surely many hate the
idea of their computers turned into spam-sender-zombie-robots. No
matter your objetives or circunstances, the less risks you take, the
better.

Greg wrote:

>While I know the slackbuild admins are only
>reviewing the script, and not Niels copy of of version x.y.z, he has,
>nevertheless, developed a large positive personal reputation in the
>community.

That's what I wanted to know.

I'm not attacking Neils, nor anyone. I was just asking how does
SlackBuild care of a potential security issue. A threat is less
dangerous when you know its existence. Many web sites (mainly aidmed as
MS Windows users) which provide software for free do contain malware
just because nobody checks the software that is posted in them. 

In SlackBuilds you can mitigate the risks by tracking down the original
source or by following only the links provided by reputable people who
is not trashing away its reputation so easily.

That is enough for me.

Cheers.

From biolizard.mail at gmail.com  Thu Jun  9 17:53:12 2011
From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=)
Date: Thu, 09 Jun 2011 18:53:12 +0100
Subject: [Slackbuilds-users] Dropbox bug report
Message-ID: <4DF10888.4030306@gmail.com>

Hello,

The link for the dropbox source package is not working.
Moreover, I tried manually downloading the source package and it still 
didn't work. It seems the Slackbuild is expecting a different directory 
structure from the one provided by the current dropbox package.

Regards,
Jos?

From Bradley at NorthTech.US  Thu Jun  9 23:18:52 2011
From: Bradley at NorthTech.US (Bradley D. Thornton)
Date: Thu, 09 Jun 2011 16:18:52 -0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
Message-ID: <4DF154DC.6000902@NorthTech.US>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160



On 06/09/2011 04:45 AM, Hac Er wrote:

> 
> The question remains: How do administrators decide if the links they
> post are trustworthy?

Well, since you're asking, I might as well get all socratic on you too:

"How do you know that the upstream, original author/maintainer of the
software you want to run is trustworthy?

Oh, I'm sorry... That was a Rhetorical question wasn't it? (Answer:
YES). And about 10 messages back there's a link to Ken Thompson's
treatment of that same question.

The outcome of that treatment? You can't be certain at all unless you
wrote it yourself.

Let take a moment now to poke a couple of holes into the notions which
you infer *could* exist here.

First, when someone submits a SlackBuild, a member of the SBo team vets
it out. The checksum you see at SlackBuilds.org for any particular
source won't match what you download if something changes (up thar in
that cloud thingy). sbopkg does a bit of work for you toward that end
that I am certain many people just disregard performing manually
themselves, and at times, I've been in a rush to launch a new server and
have been guilty of it myself.

Second, There really isn't anything to trust here, and the site pretty
much says so too. you get a very small script, which is overwhelmingly
just a boilerplate. So if an SBo maintainer were to do anything funky...

It's all on you Bob. Read that <package_name>.SlackBuild.

Third, at some point you're going to have to go to the grocery store. I
know you wouldn't trust getting there in a Ford Pinto with Firestone
500's, but even if you walked, there are one legged crack mamas waiting
to stab you in the heart for another 20 dollar rock.

Fourth, There is indeed software that I don't personally trust. I don't
trust selinux, or anything from those bozos; I don't trust Canonical, or
Microsoft, or Skype, or yahoo, or Oracle, or many many others either -
yet I nonetheless still use some of their products.

Fifth, it simply isn't the job of an SBo maintainer, or SlackBuilds.org,
to audit upstream software - it's yours, if you choose to do so... or not.

sixth, I would be much more concerned with the sofware management
systems of "Other distros" besides Slackware - like Gentoo, FreeBSD (k.,
separate  flavour, not a distro, I know), SourceMage, Sorcerer,
LunarLinux.... Oh, gee! most of those are *source based* distributions
aren't they?

I would also be very concerned about repos like rpmforge (now
repoforge), rpmfind.net, blah blah blah - who the heck are those
packagers? And how much more dificult is it to track what is going on there?

Let's take Sorcerer Linux, for example. People here Trust Pat, we also
trust the SBo team - these are people that have been vetted out over a
long period of time. Sure, someone could go off their meds, but that's
not what we're talking about really.

I also use Sorcerer, and like Pat, Kyle doesn't stand to gain any
advantage from wheeling a trojan horse into his little city. But in
order for the end user to ascertain what you're asking us how we
ascertain with regards to SBo's, the difference in the amount of work
involved is several orders of magnitude greater for a source based
distro than it is for someone Examining a SlackBuild.

With Sorcerer, add to that the fact that in order to speed things up,
Kyle uses Delta Patching and rsync to trim bandwidth and time in
obtaining the source - how hard would that be to scrutinize compared to
a *.SlackBuild?

Seventh, even if you LFS, you're still left with the Ken Thompson
paradox mentioned above wrt the source code you didn't write the
compiler for.

We really have no idea how many easter eggs, trojans, and back doors
exist at this very moment within our respective operating environments
(Unless you use Sony products, then you know you've got rootkits) - none
of us do. Software is piled layer upon layer so deep that generations of
coders have probably passed away that left a benign backdoor in their
products - intended for tech support perhaps, yet still lurking as
tomorrows 0day exploits.

eighth, ...drat. My daughter just came in and derailed my train of
thought. But I was on a roll there for a while wasn't I?

The bottom line is: "I'm not Bill Joy. I can't write UNIX from scratch
in a single, frenzied, marathon diet dew inspired episode, come out of
my cave, and have a completed product - Trust is always something you
can lose, but not something you must necessarily be required to earn ;)

I hope that helps :)

Kindest regards,



- -- 
Bradley D. Thornton
Manager Network Services
NorthTech Computer
TEL: +1.760.666.2703  (US)
TEL: +44.203.318.2755 (UK)
http://NorthTech.US

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Find this cert at x-hkp://pool.sks-keyservers.net

iQEcBAEBAwAGBQJN8VTbAAoJEE1wgkIhr9j3PsgH/jNO9krPIBuKWcRPKtUfSXXw
2NnSl/LxN/3GFTzPpsDF0HLQ8BuuFBy8PZkhSpGE0BpGD/rLjy2PILHiPU3dDNse
Xc3Sb1Tm30EpGg9F62AW4qmmcXlyqAFpbD8vPshebdYFmLgvxXG7w8vxz80fc3ee
Sw6sHl11Yhvosyhyr7MLAOOUL1MMoAEnrwjOq0i5mwZ+cHRVefOPd2AfYlg6n4G7
k/rqvXAWrfDycnMPre61ceykpi+hrD3pcBKncrsOetBMKFcYMbVghLol5yQg+JEM
KNotLtbI2Aa/3qD3tcFEBb4YD8WI9Y7EHgtVJ9ySlDtM21+HEp0V+uxljBpuEcA=
=2wqX
-----END PGP SIGNATURE-----

From willysr at gmail.com  Thu Jun  9 23:37:01 2011
From: willysr at gmail.com (Willy Sudiarto Raharjo)
Date: Fri, 10 Jun 2011 06:37:01 +0700
Subject: [Slackbuilds-users] Dropbox bug report
In-Reply-To: <4DF10888.4030306@gmail.com>
References: <4DF10888.4030306@gmail.com>
Message-ID: <BANLkTimwUiRxfq0rJeYNv7UNg=Km=SC3iw@mail.gmail.com>

> The link for the dropbox source package is not working.
> Moreover, I tried manually downloading the source package and it still
> didn't work. It seems the Slackbuild is expecting a different directory
> structure from the one provided by the current dropbox package.

dropbox's progress is quite fast
you can get the latest version
http://dl-web.dropbox.com/u/17/dropbox-lnx.x86-1.1.35.tar.gz


-- 
Willy Sudiarto Raharjo
Personal Blog : http://willysr.blogspot.com
Linux Blog: http://slackblogs.blogspot.com

From biolizard.mail at gmail.com  Thu Jun  9 23:41:06 2011
From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=)
Date: Fri, 10 Jun 2011 00:41:06 +0100
Subject: [Slackbuilds-users] Dropbox bug report
In-Reply-To: <BANLkTimwUiRxfq0rJeYNv7UNg=Km=SC3iw@mail.gmail.com>
References: <4DF10888.4030306@gmail.com>
	<BANLkTimwUiRxfq0rJeYNv7UNg=Km=SC3iw@mail.gmail.com>
Message-ID: <4DF15A12.3000605@gmail.com>

Thank you.

On 06/10/2011 12:37 AM, Willy Sudiarto Raharjo wrote:
>> The link for the dropbox source package is not working.
>> Moreover, I tried manually downloading the source package and it still
>> didn't work. It seems the Slackbuild is expecting a different directory
>> structure from the one provided by the current dropbox package.
> dropbox's progress is quite fast
> you can get the latest version
> http://dl-web.dropbox.com/u/17/dropbox-lnx.x86-1.1.35.tar.gz
>
>

From kingbeowulf at gmail.com  Fri Jun 10 00:18:43 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 09 Jun 2011 17:18:43 -0700
Subject: [Slackbuilds-users] gecko-mediaplayer-1.0.x won't build
In-Reply-To: <915809.26966.qm@web161719.mail.bf1.yahoo.com>
References: <915809.26966.qm@web161719.mail.bf1.yahoo.com>
Message-ID: <4DF162E3.3000500@gmail.com>

On 05/28/2011 10:37 AM, Phillip Warner wrote:
> --- On Fri, 5/27/11, Ozan T?rky?lmaz<ozan.turkyilmaz at gmail.com>  wrote:
>
>> I can't seem to get gecko-mediaplayer-1.0.0 or 1.0.3 to build on stock
>> Slackware64 13.37.  A fix I saw on linuxquestions.org
>> recommended installing
>> xulrunner to fix this compile error:
>>
>> /usr/include/seamonkey-2.1b3/plugin/nscore.h:50:32:
>> fatal error:
>> mozilla/mozalloc.h: No such file or directory
> It's a lot easier to just install the 13.1 version of seamonkey (which has all the header files) instead.
>
>> So now
>> firefox and gnome-mplayer-1.0.0 (gnome-mplayer-1.0.3
>> still complains about a
>> missing schema), but the mozalloc.h error is back for
>> gecko-mediaplayer-1.0.0.
>>
>> So what's the scoop?
>>
> The schema problem is easily resolved.  An excerpt from the current doinst.sh file:
>
> if [ -x /usr/bin/glib-compile-schemas ]; then
>    /usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas/>/dev/null 2>&1
> fi
>
> As was mentioned previously we are in a waiting status right now.  One, we need the proper seamonkey headers.  Two, the current versions of gecko and gnome-mplayer still need some work before they work properly in FF4/Chrome 11.  I might switch to SVN in the meantime.  My current slackBuild is still tracking to the latest release.  I haven't had time to check on this in the last couple of weeks, however.
>
> --phillip
Thanks, Phillip.

I have gnome-mpalyer-1.04b2 running after the above schema fix (silly 
me, forgot...) and also after installing seamonkey from 13.1 it seems 
gecko-mediaplayer-1.04.b2 runs....at least in the trailers I tested so 
far in FF4.  It still has the same glitch on comcast.net voicemail audio 
from 13.1 and FF3.

It seems the new seamonkey header files reference a ferw mozilla/*.h 
files that don't exist.  These references don't exist in the Slack13.1 
version of seamonkey.

-Ed

From kingbeowulf at gmail.com  Fri Jun 10 00:10:32 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 09 Jun 2011 17:10:32 -0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
Message-ID: <4DF160F8.3080204@gmail.com>

On 06/09/2011 02:19 AM, Hac Er wrote:
> --------snip---------
> This has made me wonder how secure is in fact the SlackBuild software.
> Sure, 99.9% of contributors are honorable people with pure motivations
> who work to enchance the whole Slackware comunity, but Black Hats do
> exist too out there.
>
> ------------snip--------

There is no life without some risk.  As individuals we each have a 
personal responsibility for our own safety.  One can hide under a rock 
in fear, or, one can pay attention to what one is doing, be smart about 
it, and try to minimize the risk.

A 99.9% confidence limit is plenty good enough for me as I am quite 
capable of watching out for the 0.1% of black hats.

That does not mean I will sift through thousands of lines of code (can I 
trust PV?) but rather be part of the Slackware community.  This 
community is quite capable of weeding out the less desirable elements.

So how exactly would you expect a "black hat" to infiltrate 
Slackware.com, Slackbuilds.org, linuxquestions.org, etc., and not be 
noticed fairly quickly?

From spamered at hotmail.com  Fri Jun 10 07:13:53 2011
From: spamered at hotmail.com (Hac Er)
Date: Fri, 10 Jun 2011 09:13:53 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF154DC.6000902@NorthTech.US>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
	<4DF154DC.6000902@NorthTech.US>
Message-ID: <BLU0-SMTP180F5CC1234EB7B0470DB37D6640@phx.gbl>

> Third, at some point you're going to have to go to the grocery store.
> I know you wouldn't trust getting there in a Ford Pinto with Firestone
> 500's, but even if you walked, there are one legged crack mamas
> waiting to stab you in the heart for another 20 dollar rock.

You cannot live risk free, but you can mitigate the risks. If you are
concerned of somebody wanting to stab you, carry a short cannon gun
with you. Maybe it is not a 100% efective protection, but it is surely
harder to stab someone when your brains are spreaded on the floor.

> "How do you know that the upstream, original author/maintainer of the
> software you want to run is trustworthy?

No way you can be certain about this, but please remember the theory of
machine survival I have already explained. If you download Warmux from
www.warmux.org, you are depending on them to be as kind as they claim
to be. If you download it from a packager or third party link, you are
introducing another potential point of failure in the chaim.

> sixth, I would be much more concerned with the sofware management
> systems of "Other distros" besides Slackware

I wouldn't be much more concerned with the software management systems
of "Other distros" I do not use. Debian's security documentation even
warns the user with this alarming text:

"As a matter of fact, a Debian developer could distribute a Trojan in
a package, and there is no possible way to check it out.[...]That is
why Debian has a "no guarantees" license clause".

No good for peace of mind, but kind of them to warn us.

> Fourth, There is indeed software that I don't personally trust. I
> don't trust selinux, or anything from those bozos; I don't trust
> Canonical, or Microsoft, or Skype, or yahoo, or Oracle, or many many
> others either

Good you do not trust them. Can anyone realy think SElinux is not
plaged with backdoors from the NSA? :-)

> Fifth, it simply isn't the job of an SBo maintainer, or
> SlackBuilds.org, to audit upstream software 

Nor I have said it should be, but ensuring the software posted in the
page is in fact the unmodified upstream software could be desirable
(although is not needed, it would do no harm). Refer to theory of
machine survival.

> Second, There really isn't anything to trust here, and the site pretty
> much says so too. you get a very small script, which is overwhelmingly
> just a boilerplate. So if an SBo maintainer were to do anything
> funky...

I had already reached that conclusion. The SlackBuild comunity talking
openly about this issue tells wonders about its honorability. 

From acummingsus at gmail.com  Fri Jun 10 10:28:25 2011
From: acummingsus at gmail.com (Al)
Date: Fri, 10 Jun 2011 03:28:25 -0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP180F5CC1234EB7B0470DB37D6640@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>	<4DF154DC.6000902@NorthTech.US>
	<BLU0-SMTP180F5CC1234EB7B0470DB37D6640@phx.gbl>
Message-ID: <4DF1F1C9.4060901@gmail.com>

Not to offend.  But to have fun.  If you're serious, then stop reading 
now!!! (except for the command at #3 below **is an actual command**)

By reading any further you waive your rights to any and all seriousness.

Now I'm starting to worry about the amount of electricity consumption 
needed by all of the running boxes that I've deemed necessary just for 
me to remain secure (if y'all read that far along down below, that is)

<grin> 1. build only on a certain machine that this machine is at least 
somewhat if not more so quarantined/isolated.

<grin> I'm a good guy in a white hat.  And another or #2 part of my good 
guy bag of goodies is the "scan your lan" technique/tool/appoach (tta 
for short).

<grin>  2. scan your network regularly.  Scan it with Perl.  Scan it 
with Wireshark.  Also, scan it with the various other utilities as 
well.  Just scan that lan at all hours as well as at irregular hours.  
<grin> we're scan/watching for something new activity/protocol.  So, 
uniq and diff those results regularly too.  But, BTW, be sure to do so 
with an uncompromised uniq and diff.

<grin> To "scan your lan"  Use the various different security/forensic 
distros that exist on live cd.  Also, to do the scans: do so from an 
OpenBSD box and a NetBSD box and a FreeBSD  box and a Slackware box and 
a Debian box and a CentOS box and a RedHat box if you are able to afford 
that last one.

3.
# finds new(ly) (software installed) files
find / -xdev -ctime -1

As root, redirect that command to a file before installing a package.  
<grin> so that after a removepkg you can insure there's no files 
leftover/remaining

4. _________fill___in___the___blank_________


From acummingsus at gmail.com  Fri Jun 10 10:42:30 2011
From: acummingsus at gmail.com (Al)
Date: Fri, 10 Jun 2011 03:42:30 -0700
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BLU0-SMTP180F5CC1234EB7B0470DB37D6640@phx.gbl>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>	<4DF154DC.6000902@NorthTech.US>
	<BLU0-SMTP180F5CC1234EB7B0470DB37D6640@phx.gbl>
Message-ID: <4DF1F516.2040906@gmail.com>

find / -xdev -ctime -1

As root, redirect that command to a file before installing a package.

Correction:  "immediately after" installing a package, not before.

But, what's to say that a trojan couldn't alter a file time or time 
stamp (which, in turn, would render that find command useless)

From ml at mareichelt.com  Fri Jun 10 13:27:02 2011
From: ml at mareichelt.com (markus reichelt)
Date: Fri, 10 Jun 2011 15:27:02 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF1F1C9.4060901@gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
	<4DF154DC.6000902@NorthTech.US>
	<BLU0-SMTP180F5CC1234EB7B0470DB37D6640@phx.gbl>
	<4DF1F1C9.4060901@gmail.com>
Message-ID: <20110610132702.GA16043@pc21.mareichelt.com>

* Al <acummingsus at gmail.com> wrote:

> By reading any further you waive your rights to any and all seriousness.

:-) This thread reminds me of a great quote:

"I refuse to tiptoe through life only to arrive safely at death."
 --Tony Campolo

-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110610/678f50f3/attachment.asc>

From jens at tuxane.com  Fri Jun 10 15:05:58 2011
From: jens at tuxane.com (Jens Weber - Tuxane.com)
Date: Fri, 10 Jun 2011 17:05:58 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF154DC.6000902@NorthTech.US>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
	<4DF154DC.6000902@NorthTech.US>
Message-ID: <4DF232D6.7070005@tuxane.com>

Am 10.06.2011 01:18, schrieb Bradley D. Thornton:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>
> On 06/09/2011 04:45 AM, Hac Er wrote:
>
>> The question remains: How do administrators decide if the links they
>> post are trustworthy?
> Well, since you're asking, I might as well get all socratic on you too:
>
> "How do you know that the upstream, original author/maintainer of the
> software you want to run is trustworthy?
>
> Oh, I'm sorry... That was a Rhetorical question wasn't it? (Answer:
> YES). And about 10 messages back there's a link to Ken Thompson's
> treatment of that same question.
>
> The outcome of that treatment? You can't be certain at all unless you
> wrote it yourself.
>
> Let take a moment now to poke a couple of holes into the notions which
> you infer *could* exist here.
>
> First, when someone submits a SlackBuild, a member of the SBo team vets
> it out. The checksum you see at SlackBuilds.org for any particular
> source won't match what you download if something changes (up thar in
> that cloud thingy). sbopkg does a bit of work for you toward that end
> that I am certain many people just disregard performing manually
> themselves, and at times, I've been in a rush to launch a new server and
> have been guilty of it myself.
>
> Second, There really isn't anything to trust here, and the site pretty
> much says so too. you get a very small script, which is overwhelmingly
> just a boilerplate. So if an SBo maintainer were to do anything funky...
>
> It's all on you Bob. Read that<package_name>.SlackBuild.
>
> Third, at some point you're going to have to go to the grocery store. I
> know you wouldn't trust getting there in a Ford Pinto with Firestone
> 500's, but even if you walked, there are one legged crack mamas waiting
> to stab you in the heart for another 20 dollar rock.
>
> Fourth, There is indeed software that I don't personally trust. I don't
> trust selinux, or anything from those bozos; I don't trust Canonical, or
> Microsoft, or Skype, or yahoo, or Oracle, or many many others either -
> yet I nonetheless still use some of their products.
>
> Fifth, it simply isn't the job of an SBo maintainer, or SlackBuilds.org,
> to audit upstream software - it's yours, if you choose to do so... or not.
>
> sixth, I would be much more concerned with the sofware management
> systems of "Other distros" besides Slackware - like Gentoo, FreeBSD (k.,
> separate  flavour, not a distro, I know), SourceMage, Sorcerer,
> LunarLinux.... Oh, gee! most of those are *source based* distributions
> aren't they?
>
> I would also be very concerned about repos like rpmforge (now
> repoforge), rpmfind.net, blah blah blah - who the heck are those
> packagers? And how much more dificult is it to track what is going on there?
>
> Let's take Sorcerer Linux, for example. People here Trust Pat, we also
> trust the SBo team - these are people that have been vetted out over a
> long period of time. Sure, someone could go off their meds, but that's
> not what we're talking about really.
>
> I also use Sorcerer, and like Pat, Kyle doesn't stand to gain any
> advantage from wheeling a trojan horse into his little city. But in
> order for the end user to ascertain what you're asking us how we
> ascertain with regards to SBo's, the difference in the amount of work
> involved is several orders of magnitude greater for a source based
> distro than it is for someone Examining a SlackBuild.
>
> With Sorcerer, add to that the fact that in order to speed things up,
> Kyle uses Delta Patching and rsync to trim bandwidth and time in
> obtaining the source - how hard would that be to scrutinize compared to
> a *.SlackBuild?
>
> Seventh, even if you LFS, you're still left with the Ken Thompson
> paradox mentioned above wrt the source code you didn't write the
> compiler for.
>
> We really have no idea how many easter eggs, trojans, and back doors
> exist at this very moment within our respective operating environments
> (Unless you use Sony products, then you know you've got rootkits) - none
> of us do. Software is piled layer upon layer so deep that generations of
> coders have probably passed away that left a benign backdoor in their
> products - intended for tech support perhaps, yet still lurking as
> tomorrows 0day exploits.
>
> eighth, ...drat. My daughter just came in and derailed my train of
> thought. But I was on a roll there for a while wasn't I?
>
> The bottom line is: "I'm not Bill Joy. I can't write UNIX from scratch
> in a single, frenzied, marathon diet dew inspired episode, come out of
> my cave, and have a completed product - Trust is always something you
> can lose, but not something you must necessarily be required to earn ;)
>
> I hope that helps :)
>
> Kindest regards,
>
>
>
> - -- 
> Bradley D. Thornton
> Manager Network Services
> NorthTech Computer
> TEL: +1.760.666.2703  (US)
> TEL: +44.203.318.2755 (UK)
> http://NorthTech.US
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Find this cert at x-hkp://pool.sks-keyservers.net
>
> iQEcBAEBAwAGBQJN8VTbAAoJEE1wgkIhr9j3PsgH/jNO9krPIBuKWcRPKtUfSXXw
> 2NnSl/LxN/3GFTzPpsDF0HLQ8BuuFBy8PZkhSpGE0BpGD/rLjy2PILHiPU3dDNse
> Xc3Sb1Tm30EpGg9F62AW4qmmcXlyqAFpbD8vPshebdYFmLgvxXG7w8vxz80fc3ee
> Sw6sHl11Yhvosyhyr7MLAOOUL1MMoAEnrwjOq0i5mwZ+cHRVefOPd2AfYlg6n4G7
> k/rqvXAWrfDycnMPre61ceykpi+hrD3pcBKncrsOetBMKFcYMbVghLol5yQg+JEM
> KNotLtbI2Aa/3qD3tcFEBb4YD8WI9Y7EHgtVJ9ySlDtM21+HEp0V+uxljBpuEcA=
> =2wqX
> -----END PGP SIGNATURE-----
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
And how can I trust the intention of such a topic when it has been 
started from a HOTMAIL account ?? :)

From kingbeowulf at gmail.com  Fri Jun 10 18:38:31 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 10 Jun 2011 11:38:31 -0700
Subject: [Slackbuilds-users]  Google Earth x86_64
Message-ID: <BANLkTim_VHkyemh7hF4-XvmWFS=-R4kgmg@mail.gmail.com>

Google provides a both x86 and x86_64 deb and rpm packages. The
GoogleEarthLinux.bin script provided (version 6.0.3.2197 as of today, btw)
is 32-bit only, and I can't seem to find a corresponding 64-bit version.
(why can't Google provide a simple FTP accessible file list? Those damn
fruitcakes...). It would be spiffy to recast the slackbuild script to allow
a choice for the two flavors of Slackware.

-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110610/547f55ed/attachment.html>

From joshuakwood at gmail.com  Fri Jun 10 18:46:01 2011
From: joshuakwood at gmail.com (JK Wood)
Date: Fri, 10 Jun 2011 13:46:01 -0500
Subject: [Slackbuilds-users] Google Earth x86_64
In-Reply-To: <BANLkTim_VHkyemh7hF4-XvmWFS=-R4kgmg@mail.gmail.com>
References: <BANLkTim_VHkyemh7hF4-XvmWFS=-R4kgmg@mail.gmail.com>
Message-ID: <BANLkTikD6gB4gjvZyY-B42JyXuYxL6=i+g@mail.gmail.com>

On Fri, Jun 10, 2011 at 1:38 PM, King Beowulf <kingbeowulf at gmail.com> wrote:

> Google provides a both x86 and x86_64 deb and rpm packages. The
> GoogleEarthLinux.bin script provided (version 6.0.3.2197 as of today, btw)
> is 32-bit only, and I can't seem to find a corresponding 64-bit version.
> (why can't Google provide a simple FTP accessible file list? Those damn
> fruitcakes...). It would be spiffy to recast the slackbuild script to allow
> a choice for the two flavors of Slackware.
>
> --
> You! What PLANET is this!
>     -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
The x86_64 packages are simply 32-bit packages reorganized for a multilib
system. There is no 64-bit Google Earth client.

--JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110610/439d1d79/attachment-0001.html>

From kingbeowulf at gmail.com  Sat Jun 11 02:09:34 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 10 Jun 2011 19:09:34 -0700
Subject: [Slackbuilds-users] Google Earth x86_64
In-Reply-To: <BANLkTikD6gB4gjvZyY-B42JyXuYxL6=i+g@mail.gmail.com>
References: <BANLkTim_VHkyemh7hF4-XvmWFS=-R4kgmg@mail.gmail.com>
	<BANLkTikD6gB4gjvZyY-B42JyXuYxL6=i+g@mail.gmail.com>
Message-ID: <BANLkTin2fW6Cr_vX49qKd+j_Gez4C4E4UA@mail.gmail.com>

On Fri, Jun 10, 2011 at 11:46 AM, JK Wood <joshuakwood at gmail.com> wrote:

>
>
> On Fri, Jun 10, 2011 at 1:38 PM, King Beowulf <kingbeowulf at gmail.com>wrote:
>
>> Google provides a both x86 and x86_64 deb and rpm packages. The
>> GoogleEarthLinux.bin script provided (version 6.0.3.2197 as of today, btw)
>> is 32-bit only, and I can't seem to find a corresponding 64-bit version.
>> (why can't Google provide a simple FTP accessible file list? Those damn
>> fruitcakes...). It would be spiffy to recast the slackbuild script to allow
>> a choice for the two flavors of Slackware.
>>
>> --
>> You! What PLANET is this!
>>     -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>>
> The x86_64 packages are simply 32-bit packages reorganized for a multilib
> system. There is no 64-bit Google Earth client.
>
> --JK
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
> Well, by golly...I should have looked my closely at the rpm.  My bad.


-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110610/39ad5dac/attachment.html>

From kingbeowulf at gmail.com  Sat Jun 11 03:56:45 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 10 Jun 2011 20:56:45 -0700
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad record monitor
Message-ID: <4DF2E77D.5040909@gmail.com>

I was having some trouble with the SBo version of kdenlive and decided 
to try version and discovered that the dependency is:

kdenlive-0.8

-required to compile
mlt
qjson

-optional (run time usefullness)
ffmpeg (avformat)
libdv
lame
dvdauthor
dvgrab (firewire capture)
recordmydesktop (desktop capture)

I verified this on a clean virtualbox Slackware64 ( no multilib).

From stormtracknole at gmail.com  Sat Jun 11 15:36:41 2011
From: stormtracknole at gmail.com (stormtracknole)
Date: Sat, 11 Jun 2011 10:36:41 -0500
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad record
	monitor
In-Reply-To: <4DF2E77D.5040909@gmail.com>
References: <4DF2E77D.5040909@gmail.com>
Message-ID: <BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>

The new dependency (qjson) has been addressed on the new version of
kdenlive, which is currently sitting on the pending que.

-stn

On Fri, Jun 10, 2011 at 10:56 PM, King Beowulf <kingbeowulf at gmail.com>wrote:

> I was having some trouble with the SBo version of kdenlive and decided to
> try version and discovered that the dependency is:
>
> kdenlive-0.8
>
> -required to compile
> mlt
> qjson
>
> -optional (run time usefullness)
> ffmpeg (avformat)
> libdv
> lame
> dvdauthor
> dvgrab (firewire capture)
> recordmydesktop (desktop capture)
>
> I verified this on a clean virtualbox Slackware64 ( no multilib).
> _______________________________________________
> 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/20110611/16ae542f/attachment.html>

From nille.kungen at gmail.com  Sat Jun 11 20:59:47 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Sat, 11 Jun 2011 22:59:47 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <4DF232D6.7070005@tuxane.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<BANLkTino0BBjBn79j1m9grAZRrNTe4_UsA@mail.gmail.com>
	<BLU0-SMTP57950B88965B3AF477B827D6650@phx.gbl>
	<4DF154DC.6000902@NorthTech.US> <4DF232D6.7070005@tuxane.com>
Message-ID: <BANLkTikYCFkAoTGJCMNE4CKb2NYXf5jGXw@mail.gmail.com>

After reading some of this thread (it was a bit much to read all) i checked
the example handbrake.
And i asked myself why doesn't handbrake use the original source mirrors and
why doesn't the source have the same md5sum as the original.
I do maintain a52dec, faac, faad2 and  when i saw that the md5sum differ
from the original i thought wtf?
Now if i do an diff it seems okey and doesn't differ except for a52dec that
has the top folder named differently so i guess the sources are good.
But it still makes me wonder why does handbrake use an own mirror and why
does the md5sum diff from the original.
We can't have different md5sum for the same source on SBo and we should use
the official mirrors if possible.
And if some sources are stripped or patched i rather have the patches for
each source and run them myself against the official source so i can keep up
on whats happening.
So i really think that handbrake should be considered broken in it's current
state due to link and md5sum mismatch.

That said i trust SBo and its maintainers and if you don't then don't use
SBo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/7102adec/attachment.html>

From nille.kungen at gmail.com  Sat Jun 11 21:05:27 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Sat, 11 Jun 2011 23:05:27 +0200
Subject: [Slackbuilds-users] mplayer-codecs broken source links
Message-ID: <BANLkTim8ODHHJLGdagLd7tgYAG5mntAfyA@mail.gmail.com>

I saw that the source links for mplayer-codecs is broken.

It needs an s/www3/www

Best regards Nille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/e2d028db/attachment.html>

From nille.kungen at gmail.com  Sat Jun 11 21:12:46 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Sat, 11 Jun 2011 23:12:46 +0200
Subject: [Slackbuilds-users] wrong email adress in some of my scripts
Message-ID: <BANLkTikPyPW+YbVsAad0BisDLjBLY4j2-g@mail.gmail.com>

I looked at
http://slackbuilds.org/gitweb/?p=slackbuilds.git&a=search&h=HEAD&st=grep&s=nilleand
saw that some of my builds has the wrong email adress.
Could someone please update all to nille.kungen[AT]gmail.com

/Nille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/77bc4202/attachment.html>

From pprkut at slackbuilds.org  Sat Jun 11 21:40:30 2011
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Sat, 11 Jun 2011 23:40:30 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTikYCFkAoTGJCMNE4CKb2NYXf5jGXw@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF232D6.7070005@tuxane.com>
	<BANLkTikYCFkAoTGJCMNE4CKb2NYXf5jGXw@mail.gmail.com>
Message-ID: <201106112340.33480.pprkut@slackbuilds.org>

On Saturday 11 June 2011 22:59:47 Niklas "Nille" ?kerstr?m wrote:
> We can't have different md5sum for the same source on SBo and we should use
> the official mirrors if possible.

Actually, it's the other way around. We support multiple md5sums per download 
link, but only one download link per md5sum. That is also why there are two 
links for handbrake that do not point to the handbrake server. The md5sums of 
those match links we already have in the system for the individual SlackBuilds 
of those. The download links of handbrake got adjusted to not cause conflicts 
between those scripts.

Grs,
Heinz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/2d308b0b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/2d308b0b/attachment-0001.asc>

From kingbeowulf at gmail.com  Sat Jun 11 21:49:20 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 11 Jun 2011 14:49:20 -0700
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad record
	monitor
In-Reply-To: <BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>
References: <4DF2E77D.5040909@gmail.com>
	<BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>
Message-ID: <BANLkTi=xfz2HaMwm9eC_HrCUU0C5rF6brQ@mail.gmail.com>

Well, heck...I guess I should stop bugging you and bug the admins!  My
Nvidia drivers are just sitting there as well.  These guys have real jobs,
or what?  The lazy bums! (disclaimer:  I have been on vacation the past week
so I have been a lazy bum - when the wife allowed it!)

kdenlive-0.8 works spiffy and I edited and generated several vob and mp4
files, but I have the same issue as with Kino: the video capture preview
window is corrupted, although the captured dv files play back ok.  The clip
and project video windows play back fine. So its got to be something screwy
somewhere else.  Anyway, if you have any ideas, I have a
linuxquestions.orgthread open (beowulf999)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/37c2eb7d/attachment.html>

From nille.kungen at gmail.com  Sat Jun 11 21:56:36 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Sat, 11 Jun 2011 23:56:36 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <201106112340.33480.pprkut@slackbuilds.org>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF232D6.7070005@tuxane.com>
	<BANLkTikYCFkAoTGJCMNE4CKb2NYXf5jGXw@mail.gmail.com>
	<201106112340.33480.pprkut@slackbuilds.org>
Message-ID: <BANLkTinketZvJJfFTG146T6zhBTAMRDS=g@mail.gmail.com>

Well a source should only have one md5sum unless the change is done upstream
and not released as an new version. (it happens but is totally wrong in my
opinion)
Or how should anyone know if it's correct?
And the md5sum should match the official release.
Or do you think otherwise?
/Nille

2011/6/11 Heinz Wiesinger <pprkut at slackbuilds.org>

>  On Saturday 11 June 2011 22:59:47 Niklas "Nille" ?kerstr?m wrote:
>
> > We can't have different md5sum for the same source on SBo and we should
> use
>
> > the official mirrors if possible.
>
> Actually, it's the other way around. We support multiple md5sums per
> download link, but only one download link per md5sum. That is also why there
> arhttp://slackbuilds.org/gitweb/?p=slackbuilds.git;a=summare two links for
> handbrake that do not point to the handbrake server. The md5sums of those
> match links we already have in the system for the individual SlackBuilds of
> those. The download links of handbrake got adjusted to not cause conflicts
> between those scripts.
>
> Grs,
>
> Heinz
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110611/b29b7ef9/attachment.html>

From nille.kungen at gmail.com  Sat Jun 11 22:03:48 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Sun, 12 Jun 2011 00:03:48 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTinketZvJJfFTG146T6zhBTAMRDS=g@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF232D6.7070005@tuxane.com>
	<BANLkTikYCFkAoTGJCMNE4CKb2NYXf5jGXw@mail.gmail.com>
	<201106112340.33480.pprkut@slackbuilds.org>
	<BANLkTinketZvJJfFTG146T6zhBTAMRDS=g@mail.gmail.com>
Message-ID: <BANLkTim+4wQwXCwQOwAiMkKJGytq1ZANSg@mail.gmail.com>

Sorry for the link that not supposed to be there.
New toshiba laptop that i'm not used to so it got it to paste something
where i didn't want it.
I need to make it turn off tuchpad while i write.
Or better sell the crap and get an new thinkpad.
/Nille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110612/a6a3ccea/attachment.html>

From nille.kungen at gmail.com  Sat Jun 11 22:49:24 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Sun, 12 Jun 2011 00:49:24 +0200
Subject: [Slackbuilds-users] Corcern about sources' procedence
In-Reply-To: <BANLkTim+4wQwXCwQOwAiMkKJGytq1ZANSg@mail.gmail.com>
References: <BLU0-SMTP1815DB2B87309B54D26CC8CD6650@phx.gbl>
	<4DF232D6.7070005@tuxane.com>
	<BANLkTikYCFkAoTGJCMNE4CKb2NYXf5jGXw@mail.gmail.com>
	<201106112340.33480.pprkut@slackbuilds.org>
	<BANLkTinketZvJJfFTG146T6zhBTAMRDS=g@mail.gmail.com>
	<BANLkTim+4wQwXCwQOwAiMkKJGytq1ZANSg@mail.gmail.com>
Message-ID: <BANLkTi=bSrQZdeu48KqmrT0fiRcLbdhtUw@mail.gmail.com>

I feel stupid when i see that there's tar.bz2 and tar.gz
So faad2 and faac are fine.
a52dec is still wrong and no official release.

Sorry for my mistake.
/Nille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110612/deb76a55/attachment.html>

From stormtracknole at gmail.com  Sat Jun 11 23:31:16 2011
From: stormtracknole at gmail.com (stormtracknole)
Date: Sat, 11 Jun 2011 18:31:16 -0500
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad record
	monitor
In-Reply-To: <BANLkTi=xfz2HaMwm9eC_HrCUU0C5rF6brQ@mail.gmail.com>
References: <4DF2E77D.5040909@gmail.com>
	<BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>
	<BANLkTi=xfz2HaMwm9eC_HrCUU0C5rF6brQ@mail.gmail.com>
Message-ID: <BANLkTin97p5aes-_4dsiB3j_-6dJ5cbGig@mail.gmail.com>

:-)  I think the team has been a tad busy I think.  kdenlive has been
sitting in pending for a while.  I was surprised by the new dependency.  I
hope my previous message didn't come off the wrong way.

As for your other problem, I saw your thread.  I haven't used kino in a long
time.  I just use dvgrab straight from the command line.  Maybe I should
build it to see how it works for me.

-stn

On Sat, Jun 11, 2011 at 4:49 PM, King Beowulf <kingbeowulf at gmail.com> wrote:

>
> Well, heck...I guess I should stop bugging you and bug the admins!  My
> Nvidia drivers are just sitting there as well.  These guys have real jobs,
> or what?  The lazy bums! (disclaimer:  I have been on vacation the past week
> so I have been a lazy bum - when the wife allowed it!)
>
> kdenlive-0.8 works spiffy and I edited and generated several vob and mp4
> files, but I have the same issue as with Kino: the video capture preview
> window is corrupted, although the captured dv files play back ok.  The clip
> and project video windows play back fine. So its got to be something screwy
> somewhere else.  Anyway, if you have any ideas, I have a
> linuxquestions.org thread open (beowulf999)
>
> _______________________________________________
> 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/20110611/310f311c/attachment.html>

From kingbeowulf at gmail.com  Sun Jun 12 17:10:57 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 12 Jun 2011 10:10:57 -0700
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad
	record	monitor
In-Reply-To: <BANLkTin97p5aes-_4dsiB3j_-6dJ5cbGig@mail.gmail.com>
References: <4DF2E77D.5040909@gmail.com>	<BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>	<BANLkTi=xfz2HaMwm9eC_HrCUU0C5rF6brQ@mail.gmail.com>
	<BANLkTin97p5aes-_4dsiB3j_-6dJ5cbGig@mail.gmail.com>
Message-ID: <4DF4F321.4040603@gmail.com>

On 06/11/2011 04:31 PM, stormtracknole wrote:
> :-)? I think the team has been a tad busy I think.? kdenlive has been 
> sitting in pending for a while.? I was surprised by the new 
> dependency.? I hope my previous message didn't come off the wrong way.
>
> As for your other problem, I saw your thread.? I haven't used kino in 
> a long time.? I just use dvgrab straight from the command line.? Maybe 
> I should build it to see how it works for me.

If you can find time to check out Kino, that would be great.  Dvgrab 
works fine, and "dvgrab - |mplayer -" runs fine too.  I like Kino 
because for its simplicity and I like to preview the clip and capture 
just the bit I like.  It bugs the heck out of me that the video screen 
is garbled. Too bad its development stopped.

Your previous message was fine.  It surprised me that I didn't think to 
check pending.  I tend to give newer versions than the ones on Sbo a 
whirl, if possible, and then "yell" when I have to do real work to get 
it to work! :-D

From rworkman at slackbuilds.org  Mon Jun 13 06:59:07 2011
From: rworkman at slackbuilds.org (rworkman at slackbuilds.org)
Date: Mon, 13 Jun 2011 06:59:07 +0000
Subject: [Slackbuilds-users] Updates - 20110613.1
Message-ID: <4df5b53b.g3CapcwRZvMPmI+Q%rworkman@slackbuilds.org>

Mon Jun 13 05:36:15 UTC 2011
academic/RBio: Moved to libraries.
academic/extrema: Updated for version 4.4.5.
academic/gerbv: Updated for version 2.5.0.
academic/glpk: Updated for version 4.45.
academic/grass: Updated for version 6.4.1.
academic/maxima: Updated for version 5.24.0.
academic/metis: Updated for version 4.0.3.
accessibility/xdotool: Updated for version 2.20101012.3049.
audio/HamsiManager: Updated for version 0.9.70 (+ new category)
audio/aacgain: Adapted to upstream tarball change.
audio/easytag: Minor tweaks and info updated.
audio/gtkpod: Updated for version 0.99.16.
audio/hydrogen: Updated for version 0.9.5.
audio/mp3gain: Updated for version 1.5.2.r2.
audio/mp3splt: Updated for version 2.3a.
audio/pianobar: Updated for version 2011.04.27.
audio/portmidi: Added symlink for compatibility with older software.
audio/puddletag: Updated for version 0.10.3.
audio/pyalsaaudio: Added (Python Bindings for ALSA)
audio/python-audiotools: Updated for version 2.17.
audio/qmmp: Updated for version 0.5.0.
audio/qsynth: Updated for version 0.3.6
audio/vamp-plugin-sdk: Updated for version 2.2.1.
audio/volwheel: Updated for version 0.2.8.
business/skrooge: Updated for version 0.8.1.
desktop/ccsm: Added (CompizConfig Settings Manager)
desktop/emerald-themes: Added (Extra themes for the Emerald Decorator)
desktop/emerald: Added (Emerald Window Decorator)
desktop/fusion-icon: Added (A system tray tool for Compiz Fusion)
desktop/synergy: Removed. Succeeded by synergy-plus.
development/avr-binutils: Updated for version 2.21.
development/bacon: Updated for version 1.0_build_22.
development/erlang-otp: Updated for version 14B02.
development/glade3: Updated for version 3.8.0.
development/mtd-utils: Updated for version 1.4.4.
development/netbeans: Updated for version 7.0.
development/orc: Updated for version 0.4.14.
development/pyenchant: Updated for version 1.6.5.
development/sbcl: Fixed SBCL_HOME setting on login
development/xmlstarlet: Updated for version 1.1.0.
development/zope.interface: Updated for version 3.6.3.
games/ioquake3: Updated for version r1959.
games/liquidwar6: Updated for 0.0.9beta.
games/ltris: Updated for version 1.0.16.
games/playonlinux: Updated for version 3.8.12.
games/trackballs: Updated for version 1.1.4.
games/uqm: Fixed typo in info file and minor tweaks.
games/xcowsay: Updated for version 1.3.
games/xmoto: Updated for version 0.5.7.
graphics/SweetHome3D: Updated for version 3.2.
graphics/brlcad: Updated for version 7.18.4.
graphics/dblatex: Added (A DocBook to LaTeX Publisher)
graphics/graphviz: Updated for version 2.28.0
graphics/luminance-hdr: Updated for version 2.0.2.
graphics/simple-scan: Updated for version 2.32.0.2.
libraries/CSparse: Updated for version 2.2.5.
libraries/RBio: Updated for version 2.0.1 and moved to libraries.
libraries/UFconfig: Updated for version 3.6.1.
libraries/afflib: Updated for version 3.6.11.
libraries/compiz-bcop: Added (A BCOP code generator for Compiz Fusion)
libraries/compiz-plugins-extra: Added (Extra plugins for Compiz Fusion)
libraries/compiz-plugins-main: Added (Main supported plugins for Compiz Fusion)
libraries/compiz-plugins-unsupported: Added (Unsupported plugins for Compiz Fusion)
libraries/compizconfig-backend-kconfig4: (kconfig backend for Compiz Fusion)
libraries/compizconfig-python: Added (Python bindings for compiz config)
libraries/cryptopp: Updated for version 5.6.1.
libraries/gdal: Updated for version 1.8.0.
libraries/gsl: Updated for version 1.15.
libraries/lapack: Fixed download link
libraries/lapack: Updated for version 3.3.1.
libraries/libass: Updated for version 0.9.12.
libraries/libcompizconfig: Added (A configuration library for Compiz Fusion)
libraries/libgadu: Updated for version 1.10.1.
libraries/libgcal: Updated for version 0.9.6.
libraries/liblinebreak: Updated for version 2.1.
libraries/libmaa: Updated for version 1.2.0.
libraries/libmatroska: Updated for version 1.1.0.
libraries/libmodplug: Updated for version 0.8.8.3.
libraries/libmp3splt: Updated for version 0.6.1a
libraries/libssh: Updated for version 0.5.0.
libraries/libtorrent: Updated for version 0.12.8.
libraries/tinyxml: Updated for version 2.6.2.
libraries/tre: Updated for version 0.8.0.
libraries/xapian-core: Updated for version 1.2.5.
libraries/zope.configuration: Updated for version 3.7.4.
libraries/zope.schema: Updated for version 3.8.0.
libraries/zope.security: Updated for version 3.8.2.
misc/KeePass: Updated for version 2.15.
misc/ardesia: Updated for version 0.8.
misc/conkyforecast: Updated for version 2.20.
misc/discount: Added (Markdown text to html)
misc/fribid: Updated for version 0.3.0.
misc/gramps: Updated for version 3.2.6.
misc/heyu: Updated for version 2.9.3.
misc/protobuf: Updated for version 2.4.1.
misc/viking: Updated for version 1.1.
multimedia/flash-player-plugin: Updated for version 10.3_r181.
multimedia/media-player-info: Updated for version 14.
multimedia/mlt: Updated for version 0.7.2.
multimedia/nted: Updated for version 1.10.18.
network/GeoIP: Updated for version 1.4.7.
network/arora: Removed (abandoned by maintainer)
network/frostwire: Updated for version 4.21.7.
network/hiawatha: Updated for version 7.4.1.
network/kbluetooth: Removed (abandoned by maintainer)
network/mumble: Added (Low-latency voice chat)
network/nbd: Updated for version 2.9.21a.
network/phpmyadmin: Updated for version 3.4.1.
network/psi: Misc tweaks plus updated maintainer email
network/sic: Added (simple irc client)
network/uget: Updated for version 1.6.4_1.
network/w3m: Updated for version 0.5.3.
office/grisbi: Updated for version 0.8.5.
office/org-mode: Updated for version 7.5.
office/rednotebook: Updated for version 1.1.6.
office/sigil: Updated for version 0.3.4.
office/verbiste: Updated for version 0.1.33.
office/xmind: Added (brainstorming and mind mapping tool)
perl/perl-MIME-tools: Updated for version 1.34.
perl/perl-MIME-tools: Updated for version 5.502.
perl/perl-NetAddr-IP: Updated for version 4.044.
perl/perl-Test-Pod: Updated for version 1.45.
system/cabextract: Updated for version 1.4.
system/dar: Updated for version 2.3.11.
system/di: Updated for version 4.27.
system/fbterm: Updated for version 1.7.
system/gpsd: Updated for version 2.96.
system/krusader: Changed maintainer
system/ksh: Updated for version openbsd49.
system/luckybackup: Updated for version 0.4.5.
system/lzip: Updated for version 1.12.
system/mariadb: Updated for version 5.2.5.
system/qemu-kvm: Build only x86 and x86_64 stuff by default
system/rar: Updated for version 4.0.1b1.
system/sleuthkit: Updated for version 3.2.1.
system/terminus-font: Updated for version 4.35.
system/testdisk: Updated for version 6.12.
system/upower: Updated for version 0.9.10.
system/usbmon: Updated for version 6.
system/webcore-fonts: Removed the two files in conf.avail.
system/winetricks: Updated for version 20110429.

From stormtracknole at gmail.com  Mon Jun 13 14:15:40 2011
From: stormtracknole at gmail.com (stormtracknole)
Date: Mon, 13 Jun 2011 09:15:40 -0500
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad record
	monitor
In-Reply-To: <4DF4F321.4040603@gmail.com>
References: <4DF2E77D.5040909@gmail.com>
	<BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>
	<BANLkTi=xfz2HaMwm9eC_HrCUU0C5rF6brQ@mail.gmail.com>
	<BANLkTin97p5aes-_4dsiB3j_-6dJ5cbGig@mail.gmail.com>
	<4DF4F321.4040603@gmail.com>
Message-ID: <BANLkTinDKu83Lh9jb9Jn9WtXiVkZpaDF0g@mail.gmail.com>

Ok, did some research and I have posted my findings on your LQ thread.

-stn

On Sun, Jun 12, 2011 at 12:10 PM, King Beowulf <kingbeowulf at gmail.com>wrote:

> On 06/11/2011 04:31 PM, stormtracknole wrote:
>
>> :-)? I think the team has been a tad busy I think.? kdenlive has been
>> sitting in pending for a while.? I was surprised by the new dependency.? I
>> hope my previous message didn't come off the wrong way.
>>
>>
>> As for your other problem, I saw your thread.? I haven't used kino in a
>> long time.? I just use dvgrab straight from the command line.? Maybe I
>> should build it to see how it works for me.
>>
>
> If you can find time to check out Kino, that would be great.  Dvgrab works
> fine, and "dvgrab - |mplayer -" runs fine too.  I like Kino because for its
> simplicity and I like to preview the clip and capture just the bit I like.
>  It bugs the heck out of me that the video screen is garbled. Too bad its
> development stopped.
>
> Your previous message was fine.  It surprised me that I didn't think to
> check pending.  I tend to give newer versions than the ones on Sbo a whirl,
> if possible, and then "yell" when I have to do real work to get it to work!
> :-D
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110613/11b8e529/attachment.html>

From kingbeowulf at gmail.com  Tue Jun 14 06:35:26 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 13 Jun 2011 23:35:26 -0700
Subject: [Slackbuilds-users] kdenlive-0.8 compilation / bad record
	monitor
In-Reply-To: <BANLkTinDKu83Lh9jb9Jn9WtXiVkZpaDF0g@mail.gmail.com>
References: <4DF2E77D.5040909@gmail.com>
	<BANLkTim85CgfLveufEbewu+SDUz11Wju5w@mail.gmail.com>
	<BANLkTi=xfz2HaMwm9eC_HrCUU0C5rF6brQ@mail.gmail.com>
	<BANLkTin97p5aes-_4dsiB3j_-6dJ5cbGig@mail.gmail.com>
	<4DF4F321.4040603@gmail.com>
	<BANLkTinDKu83Lh9jb9Jn9WtXiVkZpaDF0g@mail.gmail.com>
Message-ID: <BANLkTinfJ4fz41HzSQ=TypZCb2+Z30Kb4Q@mail.gmail.com>

I upgraded ffmpeg to the newest git snapshot and now the kdenlive record
monitor video preview screen is "prefect".  Something goofy with ffmpeg and
Nvidia, I think.  So, for this part, I am a happy camper.



You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110613/4e674464/attachment.html>

From kingbeowulf at gmail.com  Tue Jun 14 06:44:48 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 13 Jun 2011 23:44:48 -0700
Subject: [Slackbuilds-users]  Kino-1.3.4 video problems
Message-ID: <BANLkTi=se01NrzPSeb5tMarrbBXx-woxKg@mail.gmail.com>

Seems like Kino is starting to "age".  Although kino captures dv video fine,
its advantage over dvgrab is the real time video preview: you can capture
just the bits you want. The problem is that the video window is corrupted
when the system wide ffmpeg is upgraded to ffmpeg-0.7-rc1 or the current git
snapshot.  See
http://www.linuxquestions.org/questions/slackware-14/kino-1-3-4-preview-video-is-corrupted-885675/

The ffmpeg-0.6 on Sbo seems to be ok, as is the internal kino-ffmeg.
Unfortunately, that means more modern export options are not accessible from
within Kino.

A note in the readme may be in order and/or changing the slackbuild
configure option to "--enable-local-ffmpeg"


-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110613/4db8a7cf/attachment.html>

From erik at slackbuilds.org  Tue Jun 14 08:59:00 2011
From: erik at slackbuilds.org (Erik Hanson)
Date: Tue, 14 Jun 2011 03:59:00 -0500
Subject: [Slackbuilds-users] Updates - 20110613.1
Message-ID: <20110614035900.51068e12@shaggy.doo>

Mon Jun 13 05:36:15 UTC 2011
academic/RBio: Moved to libraries.
academic/extrema: Updated for version 4.4.5.
academic/gerbv: Updated for version 2.5.0.
academic/glpk: Updated for version 4.45.
academic/grass: Updated for version 6.4.1.
academic/maxima: Updated for version 5.24.0.
academic/metis: Updated for version 4.0.3.
accessibility/xdotool: Updated for version 2.20101012.3049.
audio/HamsiManager: Updated for version 0.9.70 (+ new category)
audio/aacgain: Adapted to upstream tarball change.
audio/easytag: Minor tweaks and info updated.
audio/gtkpod: Updated for version 0.99.16.
audio/hydrogen: Updated for version 0.9.5.
audio/mp3gain: Updated for version 1.5.2.r2.
audio/mp3splt: Updated for version 2.3a.
audio/pianobar: Updated for version 2011.04.27.
audio/portmidi: Added symlink for compatibility with older software.
audio/puddletag: Updated for version 0.10.3.
audio/pyalsaaudio: Added (Python Bindings for ALSA)
audio/python-audiotools: Updated for version 2.17.
audio/qmmp: Updated for version 0.5.0.
audio/qsynth: Updated for version 0.3.6
audio/vamp-plugin-sdk: Updated for version 2.2.1.
audio/volwheel: Updated for version 0.2.8.
business/skrooge: Updated for version 0.8.1.
desktop/ccsm: Added (CompizConfig Settings Manager)
desktop/emerald-themes: Added (Extra themes for the Emerald Decorator)
desktop/emerald: Added (Emerald Window Decorator)
desktop/fusion-icon: Added (A system tray tool for Compiz Fusion)
desktop/synergy: Removed. Succeeded by synergy-plus.
development/avr-binutils: Updated for version 2.21.
development/bacon: Updated for version 1.0_build_22.
development/erlang-otp: Updated for version 14B02.
development/glade3: Updated for version 3.8.0.
development/mtd-utils: Updated for version 1.4.4.
development/netbeans: Updated for version 7.0.
development/orc: Updated for version 0.4.14.
development/pyenchant: Updated for version 1.6.5.
development/sbcl: Fixed SBCL_HOME setting on login
development/xmlstarlet: Updated for version 1.1.0.
development/zope.interface: Updated for version 3.6.3.
games/ioquake3: Updated for version r1959.
games/liquidwar6: Updated for 0.0.9beta.
games/ltris: Updated for version 1.0.16.
games/playonlinux: Updated for version 3.8.12.
games/trackballs: Updated for version 1.1.4.
games/uqm: Fixed typo in info file and minor tweaks.
games/xcowsay: Updated for version 1.3.
games/xmoto: Updated for version 0.5.7.
graphics/SweetHome3D: Updated for version 3.2.
graphics/brlcad: Updated for version 7.18.4.
graphics/dblatex: Added (A DocBook to LaTeX Publisher)
graphics/graphviz: Updated for version 2.28.0
graphics/luminance-hdr: Updated for version 2.0.2.
graphics/simple-scan: Updated for version 2.32.0.2.
libraries/CSparse: Updated for version 2.2.5.
libraries/RBio: Updated for version 2.0.1 and moved to libraries.
libraries/UFconfig: Updated for version 3.6.1.
libraries/afflib: Updated for version 3.6.11.
libraries/compiz-bcop: Added (A BCOP code generator for Compiz Fusion)
libraries/compiz-plugins-extra: Added (Extra plugins for Compiz Fusion)
libraries/compiz-plugins-main: Added (Main supported plugins for Compiz Fusion)
libraries/compiz-plugins-unsupported: Added (Unsupported plugins for Compiz Fusion)
libraries/compizconfig-backend-kconfig4: (kconfig backend for Compiz Fusion)
libraries/compizconfig-python: Added (Python bindings for compiz config)
libraries/cryptopp: Updated for version 5.6.1.
libraries/gdal: Updated for version 1.8.0.
libraries/gsl: Updated for version 1.15.
libraries/lapack: Fixed download link
libraries/lapack: Updated for version 3.3.1.
libraries/libass: Updated for version 0.9.12.
libraries/libcompizconfig: Added (A configuration library for Compiz Fusion)
libraries/libgadu: Updated for version 1.10.1.
libraries/libgcal: Updated for version 0.9.6.
libraries/liblinebreak: Updated for version 2.1.
libraries/libmaa: Updated for version 1.2.0.
libraries/libmatroska: Updated for version 1.1.0.
libraries/libmodplug: Updated for version 0.8.8.3.
libraries/libmp3splt: Updated for version 0.6.1a
libraries/libssh: Updated for version 0.5.0.
libraries/libtorrent: Updated for version 0.12.8.
libraries/tinyxml: Updated for version 2.6.2.
libraries/tre: Updated for version 0.8.0.
libraries/xapian-core: Updated for version 1.2.5.
libraries/zope.configuration: Updated for version 3.7.4.
libraries/zope.schema: Updated for version 3.8.0.
libraries/zope.security: Updated for version 3.8.2.
misc/KeePass: Updated for version 2.15.
misc/ardesia: Updated for version 0.8.
misc/conkyforecast: Updated for version 2.20.
misc/discount: Added (Markdown text to html)
misc/fribid: Updated for version 0.3.0.
misc/gramps: Updated for version 3.2.6.
misc/heyu: Updated for version 2.9.3.
misc/protobuf: Updated for version 2.4.1.
misc/viking: Updated for version 1.1.
multimedia/flash-player-plugin: Updated for version 10.3_r181.
multimedia/media-player-info: Updated for version 14.
multimedia/mlt: Updated for version 0.7.2.
multimedia/nted: Updated for version 1.10.18.
network/GeoIP: Updated for version 1.4.7.
network/arora: Removed (abandoned by maintainer)
network/frostwire: Updated for version 4.21.7.
network/hiawatha: Updated for version 7.4.1.
network/kbluetooth: Removed (abandoned by maintainer)
network/mumble: Added (Low-latency voice chat)
network/nbd: Updated for version 2.9.21a.
network/phpmyadmin: Updated for version 3.4.1.
network/psi: Misc tweaks plus updated maintainer email
network/sic: Added (simple irc client)
network/uget: Updated for version 1.6.4_1.
network/w3m: Updated for version 0.5.3.
office/grisbi: Updated for version 0.8.5.
office/org-mode: Updated for version 7.5.
office/rednotebook: Updated for version 1.1.6.
office/sigil: Updated for version 0.3.4.
office/verbiste: Updated for version 0.1.33.
office/xmind: Added (brainstorming and mind mapping tool)
perl/perl-MIME-tools: Updated for version 1.34.
perl/perl-MIME-tools: Updated for version 5.502.
perl/perl-NetAddr-IP: Updated for version 4.044.
perl/perl-Test-Pod: Updated for version 1.45.
system/cabextract: Updated for version 1.4.
system/dar: Updated for version 2.3.11.
system/di: Updated for version 4.27.
system/fbterm: Updated for version 1.7.
system/gpsd: Updated for version 2.96.
system/krusader: Changed maintainer
system/ksh: Updated for version openbsd49.
system/luckybackup: Updated for version 0.4.5.
system/lzip: Updated for version 1.12.
system/mariadb: Updated for version 5.2.5.
system/qemu-kvm: Build only x86 and x86_64 stuff by default
system/rar: Updated for version 4.0.1b1.
system/sleuthkit: Updated for version 3.2.1.
system/terminus-font: Updated for version 4.35.
system/testdisk: Updated for version 6.12.
system/upower: Updated for version 0.9.10.
system/usbmon: Updated for version 6.
system/webcore-fonts: Removed the two files in conf.avail.
system/winetricks: Updated for version 20110429.

From nille.kungen at gmail.com  Tue Jun 14 12:18:21 2011
From: nille.kungen at gmail.com (=?ISO-8859-1?B?TmlrbGFzICJOaWxsZSIgxWtlcnN0cvZt?=)
Date: Tue, 14 Jun 2011 14:18:21 +0200
Subject: [Slackbuilds-users] avidemux
Message-ID: <BANLkTinO1bXHTM4oKezx-Y7TM41L=SB+Gw@mail.gmail.com>

I upgraded my avidemux.SlackBuild (2.5.5) but now i think that i should
split it into avidemux and avidemux-plugins.
The pros of 2 packages is that it would be easier to upgrade and handle
media support since the support is only in avidemux-plugins.
Avidemux has internal libavcodec and that support isn't touched by plugins
package.
But external codecs would be in the avidemux-plugins which makes it easier
to add, remove or upgrade the media support.
That would move the external dependencies from avidemux to avidemux-plugins.
So upgrading x264 wouldn't need to recompile all of avidemux as of today,
instead you would only need to recompile avidemux-plugins thats is smaller
and allot faster.

Now i only did an fast read up on this but this is as i understand that it
works.

So do you agree that it would be better to split it into 2 packages?
Btw avidemux and avidemux-plugins is in the same tarball if you wonder about
that.

Best regards Nille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110614/cdf10c51/attachment.html>

From hba.nihilismus at gmail.com  Tue Jun 14 12:49:05 2011
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Tue, 14 Jun 2011 07:49:05 -0500
Subject: [Slackbuilds-users] Updates - 20110613.1
In-Reply-To: <20110614035900.51068e12@shaggy.doo>
References: <20110614035900.51068e12@shaggy.doo>
Message-ID: <BANLkTi=JEk1Ve0yjoXVk_P6s_urUaCfw1A@mail.gmail.com>

On Tue, Jun 14, 2011 at 3:59 AM, Erik Hanson <erik at slackbuilds.org> wrote:
> Mon Jun 13 05:36:15 UTC 2011
> academic/RBio: Moved to libraries.
> academic/extrema: Updated for version 4.4.5.
> academic/gerbv: Updated for version 2.5.0.
> academic/glpk: Updated for version 4.45.
> academic/grass: Updated for version 6.4.1.
> academic/maxima: Updated for version 5.24.0.
> academic/metis: Updated for version 4.0.3.
> accessibility/xdotool: Updated for version 2.20101012.3049.
> audio/HamsiManager: Updated for version 0.9.70 (+ new category)
> audio/aacgain: Adapted to upstream tarball change.
> audio/easytag: Minor tweaks and info updated.
> audio/gtkpod: Updated for version 0.99.16.
> audio/hydrogen: Updated for version 0.9.5.
> audio/mp3gain: Updated for version 1.5.2.r2.
> audio/mp3splt: Updated for version 2.3a.
> audio/pianobar: Updated for version 2011.04.27.
> audio/portmidi: Added symlink for compatibility with older software.
> audio/puddletag: Updated for version 0.10.3.
> audio/pyalsaaudio: Added (Python Bindings for ALSA)
> audio/python-audiotools: Updated for version 2.17.
> audio/qmmp: Updated for version 0.5.0.
> audio/qsynth: Updated for version 0.3.6
> audio/vamp-plugin-sdk: Updated for version 2.2.1.
> audio/volwheel: Updated for version 0.2.8.
> business/skrooge: Updated for version 0.8.1.
> desktop/ccsm: Added (CompizConfig Settings Manager)
> desktop/emerald-themes: Added (Extra themes for the Emerald Decorator)
> desktop/emerald: Added (Emerald Window Decorator)
> desktop/fusion-icon: Added (A system tray tool for Compiz Fusion)
> desktop/synergy: Removed. Succeeded by synergy-plus.
> development/avr-binutils: Updated for version 2.21.
> development/bacon: Updated for version 1.0_build_22.
> development/erlang-otp: Updated for version 14B02.
> development/glade3: Updated for version 3.8.0.
> development/mtd-utils: Updated for version 1.4.4.
> development/netbeans: Updated for version 7.0.
> development/orc: Updated for version 0.4.14.
> development/pyenchant: Updated for version 1.6.5.
> development/sbcl: Fixed SBCL_HOME setting on login
> development/xmlstarlet: Updated for version 1.1.0.
> development/zope.interface: Updated for version 3.6.3.
> games/ioquake3: Updated for version r1959.
> games/liquidwar6: Updated for 0.0.9beta.
> games/ltris: Updated for version 1.0.16.
> games/playonlinux: Updated for version 3.8.12.
> games/trackballs: Updated for version 1.1.4.
> games/uqm: Fixed typo in info file and minor tweaks.
> games/xcowsay: Updated for version 1.3.
> games/xmoto: Updated for version 0.5.7.
> graphics/SweetHome3D: Updated for version 3.2.
> graphics/brlcad: Updated for version 7.18.4.
> graphics/dblatex: Added (A DocBook to LaTeX Publisher)
> graphics/graphviz: Updated for version 2.28.0
> graphics/luminance-hdr: Updated for version 2.0.2.
> graphics/simple-scan: Updated for version 2.32.0.2.
> libraries/CSparse: Updated for version 2.2.5.
> libraries/RBio: Updated for version 2.0.1 and moved to libraries.
> libraries/UFconfig: Updated for version 3.6.1.
> libraries/afflib: Updated for version 3.6.11.
> libraries/compiz-bcop: Added (A BCOP code generator for Compiz Fusion)
> libraries/compiz-plugins-extra: Added (Extra plugins for Compiz Fusion)
> libraries/compiz-plugins-main: Added (Main supported plugins for Compiz Fusion)
> libraries/compiz-plugins-unsupported: Added (Unsupported plugins for Compiz Fusion)
> libraries/compizconfig-backend-kconfig4: (kconfig backend for Compiz Fusion)
> libraries/compizconfig-python: Added (Python bindings for compiz config)
> libraries/cryptopp: Updated for version 5.6.1.
> libraries/gdal: Updated for version 1.8.0.
> libraries/gsl: Updated for version 1.15.
> libraries/lapack: Fixed download link
> libraries/lapack: Updated for version 3.3.1.
> libraries/libass: Updated for version 0.9.12.
> libraries/libcompizconfig: Added (A configuration library for Compiz Fusion)
> libraries/libgadu: Updated for version 1.10.1.
> libraries/libgcal: Updated for version 0.9.6.
> libraries/liblinebreak: Updated for version 2.1.
> libraries/libmaa: Updated for version 1.2.0.
> libraries/libmatroska: Updated for version 1.1.0.
> libraries/libmodplug: Updated for version 0.8.8.3.
> libraries/libmp3splt: Updated for version 0.6.1a
> libraries/libssh: Updated for version 0.5.0.
> libraries/libtorrent: Updated for version 0.12.8.
> libraries/tinyxml: Updated for version 2.6.2.
> libraries/tre: Updated for version 0.8.0.
> libraries/xapian-core: Updated for version 1.2.5.
> libraries/zope.configuration: Updated for version 3.7.4.
> libraries/zope.schema: Updated for version 3.8.0.
> libraries/zope.security: Updated for version 3.8.2.
> misc/KeePass: Updated for version 2.15.
> misc/ardesia: Updated for version 0.8.
> misc/conkyforecast: Updated for version 2.20.
> misc/discount: Added (Markdown text to html)
> misc/fribid: Updated for version 0.3.0.
> misc/gramps: Updated for version 3.2.6.
> misc/heyu: Updated for version 2.9.3.
> misc/protobuf: Updated for version 2.4.1.
> misc/viking: Updated for version 1.1.
> multimedia/flash-player-plugin: Updated for version 10.3_r181.
> multimedia/media-player-info: Updated for version 14.
> multimedia/mlt: Updated for version 0.7.2.
> multimedia/nted: Updated for version 1.10.18.
> network/GeoIP: Updated for version 1.4.7.
> network/arora: Removed (abandoned by maintainer)
> network/frostwire: Updated for version 4.21.7.
> network/hiawatha: Updated for version 7.4.1.
> network/kbluetooth: Removed (abandoned by maintainer)
> network/mumble: Added (Low-latency voice chat)
> network/nbd: Updated for version 2.9.21a.
> network/phpmyadmin: Updated for version 3.4.1.
> network/psi: Misc tweaks plus updated maintainer email
> network/sic: Added (simple irc client)
> network/uget: Updated for version 1.6.4_1.
> network/w3m: Updated for version 0.5.3.
> office/grisbi: Updated for version 0.8.5.
> office/org-mode: Updated for version 7.5.
> office/rednotebook: Updated for version 1.1.6.
> office/sigil: Updated for version 0.3.4.
> office/verbiste: Updated for version 0.1.33.
> office/xmind: Added (brainstorming and mind mapping tool)
> perl/perl-MIME-tools: Updated for version 1.34.
> perl/perl-MIME-tools: Updated for version 5.502.
> perl/perl-NetAddr-IP: Updated for version 4.044.
> perl/perl-Test-Pod: Updated for version 1.45.
> system/cabextract: Updated for version 1.4.
> system/dar: Updated for version 2.3.11.
> system/di: Updated for version 4.27.
> system/fbterm: Updated for version 1.7.
> system/gpsd: Updated for version 2.96.
> system/krusader: Changed maintainer
> system/ksh: Updated for version openbsd49.
> system/luckybackup: Updated for version 0.4.5.
> system/lzip: Updated for version 1.12.
> system/mariadb: Updated for version 5.2.5.
> system/qemu-kvm: Build only x86 and x86_64 stuff by default
> system/rar: Updated for version 4.0.1b1.
> system/sleuthkit: Updated for version 3.2.1.
> system/terminus-font: Updated for version 4.35.
> system/testdisk: Updated for version 6.12.
> system/upower: Updated for version 0.9.10.
> system/usbmon: Updated for version 6.
> system/webcore-fonts: Removed the two files in conf.avail.
> system/winetricks: Updated for version 20110429.
> _______________________________________________
> 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/
>
>

D?j? vu?

-- 
-
hba | Antonio Hern?ndez Blas | Mexico, Mx.
http://hba.dyndns.info | http://barrapunto.com/~hba/ |
irc://irc.freenode.org/hba,isnick,needpass

From ozan.turkyilmaz at gmail.com  Tue Jun 14 14:45:25 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 14 Jun 2011 19:45:25 +0500
Subject: [Slackbuilds-users] avidemux
In-Reply-To: <BANLkTinO1bXHTM4oKezx-Y7TM41L=SB+Gw@mail.gmail.com>
References: <BANLkTinO1bXHTM4oKezx-Y7TM41L=SB+Gw@mail.gmail.com>
Message-ID: <BANLkTi=Oi8=E89qDfVX0NWXHTiuOAXfvAw@mail.gmail.com>

2011/6/14 Niklas "Nille" ?kerstr?m <nille.kungen at gmail.com>:
> So do you agree that it would be better to split it into 2 packages?
> Btw avidemux and avidemux-plugins is in the same tarball if you wonder about
> that.

As a avidemux user, I support the split.
-- 
Ozan, BSc, BEng

From jackmaddox at gmail.com  Tue Jun 14 14:47:44 2011
From: jackmaddox at gmail.com (Jack Maddox)
Date: Tue, 14 Jun 2011 09:47:44 -0500
Subject: [Slackbuilds-users] How do I update a submission when submission
	are closed?
Message-ID: <BANLkTikzZ29NszTcTLs6S4wGv-YXCkWsFA@mail.gmail.com>

Please forgive me if this has been addressed elsewhere and I missed it.

I submitted a slackbuild for a new package a while back and it is still in the
pending queue.  However, since then, an update has been released by upstream,
which I have incorporated into the slackbuild.  My understanding of the
preferred method for updating my submission is to delete the submission using
the code that I received in the confirmation email and then resubmit the
updated version.

I attempted to do this but I had two problems.  After I followed the link to
delete the previous submission, I realized that submissions are closed.  So,
therefore I can't submit the updated version.  Also, it appears that my old
package is still in the pending queue even though I tried to delete it (maybe
I had a typo?).

Since I am planning on submitting the updated script once submission are
reopened, I wouldn't want the administrators to have to needlessly review my
script twice.  Should I just wait until things get caught up and then
resubmit?

The submission in question is the sage mathematics program.  The upstream
update is from version 4.6.2 to 4.7.  The slackbuild submission is sage.tar.gz

Thanks,
Jack

From artourter at gmail.com  Tue Jun 14 15:05:25 2011
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Tue, 14 Jun 2011 16:05:25 +0100
Subject: [Slackbuilds-users] How do I update a submission when
 submission are closed?
In-Reply-To: <BANLkTikzZ29NszTcTLs6S4wGv-YXCkWsFA@mail.gmail.com>
References: <BANLkTikzZ29NszTcTLs6S4wGv-YXCkWsFA@mail.gmail.com>
Message-ID: <BANLkTimq1cRT8fZn9tKXLHZtKPVy8rJP2A@mail.gmail.com>

Hi Jack

At the time of submission you should have received a confirmation
email  which also includes a code to remove the submitted package from
the queue.

As your package is still in pending you should remove it using the
code and then resubmit your updated version.

If you have deleted that email, then you will have to wait for an
admin to find the time to remove it for you or wait for your old
package to be released.

Hope this helps

Greg

On 14 June 2011 15:47, Jack Maddox <jackmaddox at gmail.com> wrote:
> Please forgive me if this has been addressed elsewhere and I missed it.
>
> I submitted a slackbuild for a new package a while back and it is still in the
> pending queue. ?However, since then, an update has been released by upstream,
> which I have incorporated into the slackbuild. ?My understanding of the
> preferred method for updating my submission is to delete the submission using
> the code that I received in the confirmation email and then resubmit the
> updated version.
>
> I attempted to do this but I had two problems. ?After I followed the link to
> delete the previous submission, I realized that submissions are closed. ?So,
> therefore I can't submit the updated version. ?Also, it appears that my old
> package is still in the pending queue even though I tried to delete it (maybe
> I had a typo?).
>
> Since I am planning on submitting the updated script once submission are
> reopened, I wouldn't want the administrators to have to needlessly review my
> script twice. ?Should I just wait until things get caught up and then
> resubmit?
>
> The submission in question is the sage mathematics program. ?The upstream
> update is from version 4.6.2 to 4.7. ?The slackbuild submission is sage.tar.gz
>
> Thanks,
> Jack
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>

From kingbeowulf at gmail.com  Tue Jun 14 21:23:53 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 14 Jun 2011 14:23:53 -0700
Subject: [Slackbuilds-users] Updates - 20110613.1
In-Reply-To: <BANLkTi=JEk1Ve0yjoXVk_P6s_urUaCfw1A@mail.gmail.com>
References: <20110614035900.51068e12@shaggy.doo>
	<BANLkTi=JEk1Ve0yjoXVk_P6s_urUaCfw1A@mail.gmail.com>
Message-ID: <BANLkTinnsr2N2YPoSA0m_=TrVPb_QdCuyw@mail.gmail.com>

I got all excited there for a bit thinking that my nvidia update will
make it past pending...


On 6/14/11, Antonio Hern?ndez Blas <hba.nihilismus at gmail.com> wrote:
> On Tue, Jun 14, 2011 at 3:59 AM, Erik Hanson <erik at slackbuilds.org> wrote:
>> Mon Jun 13 05:36:15 UTC 2011
>> academic/RBio: Moved to libraries.
>> academic/extrema: Updated for version 4.4.5.
>> academic/gerbv: Updated for version 2.5.0.
>> academic/glpk: Updated for version 4.45.
>> academic/grass: Updated for version 6.4.1.
>> academic/maxima: Updated for version 5.24.0.
>> academic/metis: Updated for version 4.0.3.
>> accessibility/xdotool: Updated for version 2.20101012.3049.
>> audio/HamsiManager: Updated for version 0.9.70 (+ new category)
>> audio/aacgain: Adapted to upstream tarball change.
>> audio/easytag: Minor tweaks and info updated.
>> audio/gtkpod: Updated for version 0.99.16.
>> audio/hydrogen: Updated for version 0.9.5.
>> audio/mp3gain: Updated for version 1.5.2.r2.
>> audio/mp3splt: Updated for version 2.3a.
>> audio/pianobar: Updated for version 2011.04.27.
>> audio/portmidi: Added symlink for compatibility with older software.
>> audio/puddletag: Updated for version 0.10.3.
>> audio/pyalsaaudio: Added (Python Bindings for ALSA)
>> audio/python-audiotools: Updated for version 2.17.
>> audio/qmmp: Updated for version 0.5.0.
>> audio/qsynth: Updated for version 0.3.6
>> audio/vamp-plugin-sdk: Updated for version 2.2.1.
>> audio/volwheel: Updated for version 0.2.8.
>> business/skrooge: Updated for version 0.8.1.
>> desktop/ccsm: Added (CompizConfig Settings Manager)
>> desktop/emerald-themes: Added (Extra themes for the Emerald Decorator)
>> desktop/emerald: Added (Emerald Window Decorator)
>> desktop/fusion-icon: Added (A system tray tool for Compiz Fusion)
>> desktop/synergy: Removed. Succeeded by synergy-plus.
>> development/avr-binutils: Updated for version 2.21.
>> development/bacon: Updated for version 1.0_build_22.
>> development/erlang-otp: Updated for version 14B02.
>> development/glade3: Updated for version 3.8.0.
>> development/mtd-utils: Updated for version 1.4.4.
>> development/netbeans: Updated for version 7.0.
>> development/orc: Updated for version 0.4.14.
>> development/pyenchant: Updated for version 1.6.5.
>> development/sbcl: Fixed SBCL_HOME setting on login
>> development/xmlstarlet: Updated for version 1.1.0.
>> development/zope.interface: Updated for version 3.6.3.
>> games/ioquake3: Updated for version r1959.
>> games/liquidwar6: Updated for 0.0.9beta.
>> games/ltris: Updated for version 1.0.16.
>> games/playonlinux: Updated for version 3.8.12.
>> games/trackballs: Updated for version 1.1.4.
>> games/uqm: Fixed typo in info file and minor tweaks.
>> games/xcowsay: Updated for version 1.3.
>> games/xmoto: Updated for version 0.5.7.
>> graphics/SweetHome3D: Updated for version 3.2.
>> graphics/brlcad: Updated for version 7.18.4.
>> graphics/dblatex: Added (A DocBook to LaTeX Publisher)
>> graphics/graphviz: Updated for version 2.28.0
>> graphics/luminance-hdr: Updated for version 2.0.2.
>> graphics/simple-scan: Updated for version 2.32.0.2.
>> libraries/CSparse: Updated for version 2.2.5.
>> libraries/RBio: Updated for version 2.0.1 and moved to libraries.
>> libraries/UFconfig: Updated for version 3.6.1.
>> libraries/afflib: Updated for version 3.6.11.
>> libraries/compiz-bcop: Added (A BCOP code generator for Compiz Fusion)
>> libraries/compiz-plugins-extra: Added (Extra plugins for Compiz Fusion)
>> libraries/compiz-plugins-main: Added (Main supported plugins for Compiz
>> Fusion)
>> libraries/compiz-plugins-unsupported: Added (Unsupported plugins for
>> Compiz Fusion)
>> libraries/compizconfig-backend-kconfig4: (kconfig backend for Compiz
>> Fusion)
>> libraries/compizconfig-python: Added (Python bindings for compiz config)
>> libraries/cryptopp: Updated for version 5.6.1.
>> libraries/gdal: Updated for version 1.8.0.
>> libraries/gsl: Updated for version 1.15.
>> libraries/lapack: Fixed download link
>> libraries/lapack: Updated for version 3.3.1.
>> libraries/libass: Updated for version 0.9.12.
>> libraries/libcompizconfig: Added (A configuration library for Compiz
>> Fusion)
>> libraries/libgadu: Updated for version 1.10.1.
>> libraries/libgcal: Updated for version 0.9.6.
>> libraries/liblinebreak: Updated for version 2.1.
>> libraries/libmaa: Updated for version 1.2.0.
>> libraries/libmatroska: Updated for version 1.1.0.
>> libraries/libmodplug: Updated for version 0.8.8.3.
>> libraries/libmp3splt: Updated for version 0.6.1a
>> libraries/libssh: Updated for version 0.5.0.
>> libraries/libtorrent: Updated for version 0.12.8.
>> libraries/tinyxml: Updated for version 2.6.2.
>> libraries/tre: Updated for version 0.8.0.
>> libraries/xapian-core: Updated for version 1.2.5.
>> libraries/zope.configuration: Updated for version 3.7.4.
>> libraries/zope.schema: Updated for version 3.8.0.
>> libraries/zope.security: Updated for version 3.8.2.
>> misc/KeePass: Updated for version 2.15.
>> misc/ardesia: Updated for version 0.8.
>> misc/conkyforecast: Updated for version 2.20.
>> misc/discount: Added (Markdown text to html)
>> misc/fribid: Updated for version 0.3.0.
>> misc/gramps: Updated for version 3.2.6.
>> misc/heyu: Updated for version 2.9.3.
>> misc/protobuf: Updated for version 2.4.1.
>> misc/viking: Updated for version 1.1.
>> multimedia/flash-player-plugin: Updated for version 10.3_r181.
>> multimedia/media-player-info: Updated for version 14.
>> multimedia/mlt: Updated for version 0.7.2.
>> multimedia/nted: Updated for version 1.10.18.
>> network/GeoIP: Updated for version 1.4.7.
>> network/arora: Removed (abandoned by maintainer)
>> network/frostwire: Updated for version 4.21.7.
>> network/hiawatha: Updated for version 7.4.1.
>> network/kbluetooth: Removed (abandoned by maintainer)
>> network/mumble: Added (Low-latency voice chat)
>> network/nbd: Updated for version 2.9.21a.
>> network/phpmyadmin: Updated for version 3.4.1.
>> network/psi: Misc tweaks plus updated maintainer email
>> network/sic: Added (simple irc client)
>> network/uget: Updated for version 1.6.4_1.
>> network/w3m: Updated for version 0.5.3.
>> office/grisbi: Updated for version 0.8.5.
>> office/org-mode: Updated for version 7.5.
>> office/rednotebook: Updated for version 1.1.6.
>> office/sigil: Updated for version 0.3.4.
>> office/verbiste: Updated for version 0.1.33.
>> office/xmind: Added (brainstorming and mind mapping tool)
>> perl/perl-MIME-tools: Updated for version 1.34.
>> perl/perl-MIME-tools: Updated for version 5.502.
>> perl/perl-NetAddr-IP: Updated for version 4.044.
>> perl/perl-Test-Pod: Updated for version 1.45.
>> system/cabextract: Updated for version 1.4.
>> system/dar: Updated for version 2.3.11.
>> system/di: Updated for version 4.27.
>> system/fbterm: Updated for version 1.7.
>> system/gpsd: Updated for version 2.96.
>> system/krusader: Changed maintainer
>> system/ksh: Updated for version openbsd49.
>> system/luckybackup: Updated for version 0.4.5.
>> system/lzip: Updated for version 1.12.
>> system/mariadb: Updated for version 5.2.5.
>> system/qemu-kvm: Build only x86 and x86_64 stuff by default
>> system/rar: Updated for version 4.0.1b1.
>> system/sleuthkit: Updated for version 3.2.1.
>> system/terminus-font: Updated for version 4.35.
>> system/testdisk: Updated for version 6.12.
>> system/upower: Updated for version 0.9.10.
>> system/usbmon: Updated for version 6.
>> system/webcore-fonts: Removed the two files in conf.avail.
>> system/winetricks: Updated for version 20110429.
>> _______________________________________________
>> 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/
>>
>>
>
> D?j? vu?
>
> --
> -
> hba | Antonio Hern?ndez Blas | Mexico, Mx.
> http://hba.dyndns.info | http://barrapunto.com/~hba/ |
> irc://irc.freenode.org/hba,isnick,needpass
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>

-- 
Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

From kingbeowulf at gmail.com  Wed Jun 15 02:48:34 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 14 Jun 2011 19:48:34 -0700
Subject: [Slackbuilds-users] avidemux
In-Reply-To: <BANLkTi=Oi8=E89qDfVX0NWXHTiuOAXfvAw@mail.gmail.com>
References: <BANLkTinO1bXHTM4oKezx-Y7TM41L=SB+Gw@mail.gmail.com>
	<BANLkTi=Oi8=E89qDfVX0NWXHTiuOAXfvAw@mail.gmail.com>
Message-ID: <BANLkTi=+5mGO3p8hrzKacD6Z9MSjWd6RVA@mail.gmail.com>

2011/6/14 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>

> 2011/6/14 Niklas "Nille" ?kerstr?m <nille.kungen at gmail.com>:
> > So do you agree that it would be better to split it into 2 packages?
> > Btw avidemux and avidemux-plugins is in the same tarball if you wonder
> about
> > that.
>
> As a avidemux user, I support the split.
> --
> Ozan, BSc, BEng
> _______________________________________________
>
>
I haven't used avidemux much as yet, but the split sounds like a good idea.

-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110614/61f42a32/attachment.html>

From rshepard at appl-ecosys.com  Wed Jun 15 15:54:55 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 08:54:55 -0700 (PDT)
Subject: [Slackbuilds-users] Cannot Find R-project
Message-ID: <alpine.LNX.2.00.1106150852050.2394@salmo.appl-ecosys.com>

   I'm setting up my 13.37/64-bit portable for an upcoming trip and
rebuilding all SlackBuild packages. I cannot find R any longer; it was there
not long ago because I upgraded R on my 13.1 server/workstation from SBo.

   When I enter R in the search box I get everything in the repository with a
R or r in the name or description.

   Please point me in the proper direction.

Rich

From jbernts at broadpark.no  Wed Jun 15 16:02:31 2011
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Wed, 15 Jun 2011 18:02:31 +0200
Subject: [Slackbuilds-users] Cannot Find R-project
In-Reply-To: <alpine.LNX.2.00.1106150852050.2394@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106150852050.2394@salmo.appl-ecosys.com>
Message-ID: <20110615160231.GA24714@josteinb>

On 15.06.11,08:54, Rich Shepard wrote:
>   I'm setting up my 13.37/64-bit portable for an upcoming trip and
> rebuilding all SlackBuild packages. I cannot find R any longer; it was there
> not long ago because I upgraded R on my 13.1 server/workstation from SBo.
> 
>   When I enter R in the search box I get everything in the repository with a
> R or r in the name or description.
> 
>   Please point me in the proper direction.
> 

I would guess that this package for 13.37 is still in the pending queue 
and is not approved yet by the administrators:

http://slackbuilds.org/pending/


Jostein



From audrius at neutrino.lt  Wed Jun 15 16:06:35 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Wed, 15 Jun 2011 19:06:35 +0300
Subject: [Slackbuilds-users] Cannot Find R-project
In-Reply-To: <alpine.LNX.2.00.1106150852050.2394@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106150852050.2394@salmo.appl-ecosys.com>
Message-ID: <20110615160635.GA23235@kiras>

On Wed, 2011-06-15 at 08:54:55 -0700, Rich Shepard wrote:
>   I'm setting up my 13.37/64-bit portable for an upcoming trip and
> rebuilding all SlackBuild packages. I cannot find R any longer; it was there
> not long ago because I upgraded R on my 13.1 server/workstation from SBo.
> 
>   When I enter R in the search box I get everything in the repository with a
> R or r in the name or description.
> 
>   Please point me in the proper direction.

It was removed by the following commit:

http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=0b4a05ae9159e3a939f455ebc3835a421f54794e

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110615/179d801e/attachment.asc>

From rshepard at appl-ecosys.com  Wed Jun 15 16:21:23 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 09:21:23 -0700 (PDT)
Subject: [Slackbuilds-users] Cannot Find R-project
In-Reply-To: <20110615160231.GA24714@josteinb>
References: <alpine.LNX.2.00.1106150852050.2394@salmo.appl-ecosys.com>
	<20110615160231.GA24714@josteinb>
Message-ID: <alpine.LNX.2.00.1106150920430.2394@salmo.appl-ecosys.com>

On Wed, 15 Jun 2011, Jostein Berntsen wrote:

> I would guess that this package for 13.37 is still in the pending queue
> and is not approved yet by the administrators:

Jostein,

   OK. I'll change the ARCH in the existing script to x86_64.

Thanks,

Rich

From rshepard at appl-ecosys.com  Wed Jun 15 19:48:45 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 12:48:45 -0700 (PDT)
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
Message-ID: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>

   There seems to be a few packages I use that no longer have build scripts
in the repository. I built SWIG manually, and suppose I could run the OO.o
rpm through rpm2tgz and see if I can install it after that.

   Are these pending (or removed) scripts going to be made available some
time soon?

Rich

From joshuakwood at gmail.com  Wed Jun 15 19:51:41 2011
From: joshuakwood at gmail.com (JK Wood)
Date: Wed, 15 Jun 2011 14:51:41 -0500
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
Message-ID: <BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>

On Jun 15, 2011 2:48 PM, "Rich Shepard" <rshepard at appl-ecosys.com> wrote:
>
>  There seems to be a few packages I use that no longer have build scripts
> in the repository. I built SWIG manually, and suppose I could run the OO.o
> rpm through rpm2tgz and see if I can install it after that.
>
>  Are these pending (or removed) scripts going to be made available some
> time soon?
>
> Rich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>

If I remember correctly, SWIG is now in Slackware, and OO.o has been
deprecated in favor of LibreOffice.

-JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110615/90b70c16/attachment.html>

From erik at slackbuilds.org  Wed Jun 15 19:57:19 2011
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 15 Jun 2011 14:57:19 -0500
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
Message-ID: <20110615145719.44907c2d@shaggy.doo>

On Wed, 15 Jun 2011 12:48:45 -0700 (PDT)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

>    There seems to be a few packages I use that no longer have build
> scripts in the repository. I built SWIG manually, and suppose I could
> run the OO.o rpm through rpm2tgz and see if I can install it after
> that.

I wouldn't expect to see OOo back.. 
http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=e67ceae

Swig is included with Slackware since at least 13.0, in d/.


-- 
Erik Hanson

From rshepard at appl-ecosys.com  Wed Jun 15 19:57:17 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 12:57:17 -0700 (PDT)
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
	<BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>

On Wed, 15 Jun 2011, JK Wood wrote:

> If I remember correctly, SWIG is now in Slackware, ...

JK,

   Now that's kewel!

> ... and OO.o has been deprecated in favor of LibreOffice.

   I get this impression, too, but have been told by some who converted that
LO does not (yet) handle all the M$ formats as well as OO.o. Since this is
my main use of the suite, it's a concern.

   Regardless, I install LO and see if it works for me.

Thanks,

Rich

From rshepard at appl-ecosys.com  Wed Jun 15 19:59:51 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 12:59:51 -0700 (PDT)
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <20110615145719.44907c2d@shaggy.doo>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
	<20110615145719.44907c2d@shaggy.doo>
Message-ID: <alpine.LNX.2.00.1106151258540.2394@salmo.appl-ecosys.com>

On Wed, 15 Jun 2011, Erik Hanson wrote:

> I wouldn't expect to see OOo back..
> http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=e67ceae

   OK.

> Swig is included with Slackware since at least 13.0, in d/.

   I did not notice that before. I'll clean up the system.

Thanks, Eric,

Rich

From jbernts at broadpark.no  Wed Jun 15 20:03:18 2011
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Wed, 15 Jun 2011 22:03:18 +0200
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
	<BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>
	<alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>
Message-ID: <20110615200318.GC24714@josteinb>

On 15.06.11,12:57, Rich Shepard wrote:
> On Wed, 15 Jun 2011, JK Wood wrote:
> 
> >If I remember correctly, SWIG is now in Slackware, ...
> 
> JK,
> 
>   Now that's kewel!
> 
> >... and OO.o has been deprecated in favor of LibreOffice.
> 
>   I get this impression, too, but have been told by some who converted that
> LO does not (yet) handle all the M$ formats as well as OO.o. Since this is
> my main use of the suite, it's a concern.
> 
>   Regardless, I install LO and see if it works for me.
> 

Libreoffice packages 3.3.2 are available through SlackBuild:

http://slackbuilds.org/repository/13.37/office/libreoffice/

or you can try Alien Bob's 3.4.0 packages at his site:

http://alien.slackbook.org/blog/libreoffice-3-4-0/


Jostein



From ml at mareichelt.com  Wed Jun 15 20:46:23 2011
From: ml at mareichelt.com (markus reichelt)
Date: Wed, 15 Jun 2011 22:46:23 +0200
Subject: [Slackbuilds-users] Opera Widgets
Message-ID: <20110615204623.GC17356@pc21.mareichelt.com>

Aloha,

I maintain the Opera SlackBuild @ SBo.

Are there any users of "my" Opera.SlackBuild that also use Opera
Widgets? If so, please tell me:

a) Did you encounter any problems, had to apply kludges in order for
things to work? If so, please explain.

b) Do you use Opera Widgets on a daily basis? If so, which ones?

c) Do you have any feedback with regard to Opera Widgets?

Please reply to slackbuilds-users at slackbuilds.org, or to me directly
if you are not subscribed to that list. I am in contact with someone
from Opera, and want to make use of this chance. 

Reason I'm asking: I do not use Opera Widgets myself, at all. The
more input the better. Thanks :)

-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110615/2a7b31e2/attachment.asc>

From Bradley at NorthTech.US  Wed Jun 15 22:19:20 2011
From: Bradley at NorthTech.US (Bradley D. Thornton)
Date: Wed, 15 Jun 2011 15:19:20 -0700
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>	<BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>
	<alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>
Message-ID: <4DF92FE8.7070603@NorthTech.US>



On 06/15/2011 12:57 PM, Rich Shepard wrote:
> On Wed, 15 Jun 2011, JK Wood wrote:
>

> I get this impression, too, but have been told by some who converted that
> LO does not (yet) handle all the M$ formats as well as OO.o. Since this is
> my main use of the suite, it's a concern.
>
> Regardless, I install LO and see if it works for me.
>

I don't think you're going to have any issues. AlienBob's package works 
well, although I'm not sure if his latest one includes the dicts or not. 
I don't think the early one did when LO was first making its break with 
OOo and EllisonCo.

But as far as Microsoft compatibility, anything in OOo is in LO, while 
LO has features not able to be included in OOo - at least that's how I 
understand the licensing issues to be.

-- 
Bradley D. Thornton
Manager Network Services
NorthTech Computer
TEL: +1.760.666.2703  (US)
TEL: +44.203.318.2755 (UK)
http://NorthTech.US


From rshepard at appl-ecosys.com  Wed Jun 15 22:52:17 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 15:52:17 -0700 (PDT)
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <20110615200318.GC24714@josteinb>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
	<BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>
	<alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>
	<20110615200318.GC24714@josteinb>
Message-ID: <alpine.LNX.2.00.1106151550380.2394@salmo.appl-ecosys.com>

On Wed, 15 Jun 2011, Jostein Berntsen wrote:

> Libreoffice packages 3.3.2 are available through SlackBuild:
> http://slackbuilds.org/repository/13.37/office/libreoffice/

Jostein,

   Thank you. For some strange reason I could not initiate the download to
the /opt/slackbuilds/libreoffice/ directory. Tried a dozen times without
success. But, when I gave up and specified my ~/ directory, it started the
download. Go figure.

   Anyway, it will eventually all be here.

Thanks,

Rich

From rshepard at appl-ecosys.com  Wed Jun 15 22:54:45 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 15 Jun 2011 15:54:45 -0700 (PDT)
Subject: [Slackbuilds-users] SWIG? OpenOffice.org?
In-Reply-To: <4DF92FE8.7070603@NorthTech.US>
References: <alpine.LNX.2.00.1106151246270.2394@salmo.appl-ecosys.com>
	<BANLkTinmoDwrkoq9sfbzg=NF5acGv3rS0A@mail.gmail.com>
	<alpine.LNX.2.00.1106151254590.2394@salmo.appl-ecosys.com>
	<4DF92FE8.7070603@NorthTech.US>
Message-ID: <alpine.LNX.2.00.1106151552240.2394@salmo.appl-ecosys.com>

On Wed, 15 Jun 2011, Bradley D. Thornton wrote:

> I don't think you're going to have any issues. AlienBob's package works
> well, although I'm not sure if his latest one includes the dicts or not. I
> don't think the early one did when LO was first making its break with OOo
> and EllisonCo.

Bradley,

   AlienBob's directory had a slew of individual packages so I'm downloading
the massive tarball from the LO site. Since I use only English other
languages are of no use to me.

> But as far as Microsoft compatibility, anything in OOo is in LO, while LO
> has features not able to be included in OOo - at least that's how I
> understand the licensing issues to be.

   Thank you very much for the clarification. I've been trying to learn how
they're related but had not found anything that answered as well as you just
did.

Regards,

Rich

From chris.abela at maltats.com  Thu Jun 16 13:23:17 2011
From: chris.abela at maltats.com (Chris ABELA)
Date: Thu, 16 Jun 2011 15:23:17 +0200
Subject: [Slackbuilds-users] What packages do you upgrade?
Message-ID: <4270A46AC7934B2388CE36DE85792B57@maltats.com>

I noticed that there were some updates on some SBo packages I had already
installed on my new Slackware 13.37 installation. Given some possible
options that come to my mind, what would you consider as the best practice?

1. Ignore them unless there are some security issues.
2. Upgrade them and rebuild any packages that were built against them.
3. Upgrade them but do not bother with any other packages even if they were
built against them.

I tend to find the last option as the most sensible but I would appreciate
your opinions.

Chris



From ozan.turkyilmaz at gmail.com  Thu Jun 16 13:25:25 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Thu, 16 Jun 2011 18:25:25 +0500
Subject: [Slackbuilds-users] What packages do you upgrade?
In-Reply-To: <4270A46AC7934B2388CE36DE85792B57@maltats.com>
References: <4270A46AC7934B2388CE36DE85792B57@maltats.com>
Message-ID: <BANLkTinsNb58Kfc8--w3ebhZOwYjuAn5Zw@mail.gmail.com>

2011/6/16 Chris ABELA <chris.abela at maltats.com>:
> 3. Upgrade them but do not bother with any other packages even if they were

I got for that all the time.

-- 
Ozan, BSc, BEng

From niels.horn at gmail.com  Thu Jun 16 13:54:03 2011
From: niels.horn at gmail.com (Niels Horn)
Date: Thu, 16 Jun 2011 10:54:03 -0300
Subject: [Slackbuilds-users] What packages do you upgrade?
In-Reply-To: <BANLkTinsNb58Kfc8--w3ebhZOwYjuAn5Zw@mail.gmail.com>
References: <4270A46AC7934B2388CE36DE85792B57@maltats.com>
	<BANLkTinsNb58Kfc8--w3ebhZOwYjuAn5Zw@mail.gmail.com>
Message-ID: <BANLkTikVBC2uXNQ66E-HENFDuROBA9uovQ@mail.gmail.com>

2011/6/16 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> 2011/6/16 Chris ABELA <chris.abela at maltats.com>:
>> 3. Upgrade them but do not bother with any other packages even if they were
>
> I got for that all the time.
>
> --
> Ozan, BSc, BEng

Well, if you upgrade a library, you might need to rebuild the packages
that depend on it.
This all depends on how big the change is in the lib - and how
upstream developers took care of that...

For instance, if you upgrade libxyz for 1.2.1 to 1.2.2 and upstream
maintained compatibility, everything will be OK.
But a change from 1.2.1 to 2.0.0 sounds like a major upgrade, with a
new version of the shared object and might intruduce compatibility
problems.

My personal experience:
- read the changelog of the upgrades package from upstream to find out
why they released the new version. If they are responsible persons,
the warn about possible impacts.
- run "ldd <your_program>" after the upgrade and check for errors
- test <your_program> - especially the functionality handled by libxyz
if possible.
- try at least to build <your_program> and see if it complains about
libxyz. If it does, you might even send an e-mail to <your_program>
developers telling them what you found out, or check their forum,
mailing list etc. There might be a patch in their source repo already.

This is all a lot of fun, but it takes some time. :)

--
Niels Horn

From chris.abela at maltats.com  Thu Jun 16 14:13:41 2011
From: chris.abela at maltats.com (Chris ABELA)
Date: Thu, 16 Jun 2011 16:13:41 +0200
Subject: [Slackbuilds-users] Remove loic from pending please
Message-ID: <11B204FF9E5A417296DE36410F11BCB7@maltats.com>

Will someone from the Admins please remove my submission for loic. I made
some significant enhancements I would like to include before your review.
Unlike other submissions I had made before, I did not receive the mail with
instructions on how to do this.

Chris



From audrius at neutrino.lt  Thu Jun 16 17:33:51 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Thu, 16 Jun 2011 20:33:51 +0300
Subject: [Slackbuilds-users] Opera Widgets
In-Reply-To: <20110615204623.GC17356@pc21.mareichelt.com>
References: <20110615204623.GC17356@pc21.mareichelt.com>
Message-ID: <20110616173351.GA25010@kiras>

On Wed, 2011-06-15 at 22:46:23 +0200, markus reichelt wrote:
> Reason I'm asking: I do not use Opera Widgets myself, at all. The
> more input the better. Thanks :)

I do not use Opera widgets either, so I guess this doesn't count as
useful input.  :-)  What I do use are UserJS scripts.  I find them very
valuable.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110616/89e236e8/attachment.asc>

From rshepard at appl-ecosys.com  Thu Jun 16 19:55:41 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 12:55:41 -0700 (PDT)
Subject: [Slackbuilds-users] GoogleEarth Won't Start
Message-ID: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>

   Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for
13.37/x86_64 I'm running into a puzzling problem when trying to invoke the
application.

   What I see on the virtual terminal is:

/usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such
file or directory
/usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success

   Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the
LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail.

   What might I have done wrong here?

Rich

From joshuakwood at gmail.com  Thu Jun 16 19:59:13 2011
From: joshuakwood at gmail.com (JK Wood)
Date: Thu, 16 Jun 2011 14:59:13 -0500
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
Message-ID: <BANLkTimDmZ-EhncHrRyBV2FMeZr=oDTvHQ@mail.gmail.com>

On Thu, Jun 16, 2011 at 2:55 PM, Rich Shepard <rshepard at appl-ecosys.com>wrote:

>  Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for
> 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the
> application.
>
>  What I see on the virtual terminal is:
>
> /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such
> file or directory
> /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success
>
>  Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the
> LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail.
>
>  What might I have done wrong here?
>
> Rich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
Is /opt/GoogleEarth/googleearth-bin executable?

--JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110616/6bf975f3/attachment.html>

From audrius at neutrino.lt  Thu Jun 16 20:04:02 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Thu, 16 Jun 2011 23:04:02 +0300
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
Message-ID: <20110616200402.GA31699@kiras>

On Thu, 2011-06-16 at 12:55:41 -0700, Rich Shepard wrote:
>   Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for
> 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the
> application.
> 
>   What I see on the virtual terminal is:
> 
> /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such
> file or directory
> /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success
> 
>   Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the
> LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail.
> 
>   What might I have done wrong here?

Are you trying to run it on Slackware64?  From GoogleEarth SlackBuild
README:

 3) GoogleEarth is a 32bit application only.  You need to have the 32bit
 compatibility packages installed to have this work on a 64bit system.
 Otherwise you'll just see "no such file or directory" errors.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110616/1583abeb/attachment-0001.asc>

From rshepard at appl-ecosys.com  Thu Jun 16 20:08:41 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 13:08:41 -0700 (PDT)
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <BANLkTimDmZ-EhncHrRyBV2FMeZr=oDTvHQ@mail.gmail.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTimDmZ-EhncHrRyBV2FMeZr=oDTvHQ@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106161307431.32425@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, JK Wood wrote:

> Is /opt/GoogleEarth/googleearth-bin executable?

JK,

   I should have mentioned that it is, with 755 permissions.

Rich

From rshepard at appl-ecosys.com  Thu Jun 16 20:11:45 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 13:11:45 -0700 (PDT)
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <20110616200402.GA31699@kiras>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<20110616200402.GA31699@kiras>
Message-ID: <alpine.LNX.2.00.1106161308540.32425@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, Audrius Ka?ukauskas wrote:

> Are you trying to run it on Slackware64?  From GoogleEarth SlackBuild
> README:
>
> 3) GoogleEarth is a 32bit application only.  You need to have the 32bit
> compatibility packages installed to have this work on a 64bit system.
> Otherwise you'll just see "no such file or directory" errors.

   I installed AlienBob's compatibility libraries. There must be something I
did incorrectly, however, as I'm also finding a build problem with another
SlackBuild package (another thread).

   Acroread would not install until I added the compat32 libs; it has font
issues so I may have missed something here.

Thanks,

Rich

From rshepard at appl-ecosys.com  Thu Jun 16 20:22:09 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 13:22:09 -0700 (PDT)
Subject: [Slackbuilds-users] epdfview Build Problem
Message-ID: <alpine.LNX.2.00.1106161317280.32425@salmo.appl-ecosys.com>

   Working with a 64-bit system is new to me so I'm hitting issues that I
expect will go away with experience. I installed AlienBob's multilibs and
compat32 libraries this morning and I'm trying to get every application I
might need on the machine before I leave on a business trip this Sunday.

   The current problem is with epdview. Running the SlackBuild script
produces:

In file included from /usr/include/glib-2.0/glib/gasyncqueue.h:34:0,
                  from /usr/include/glib-2.0/glib.h:34,
                  from /usr/include/glib-2.0/gobject/gbinding.h:30,
                  from /usr/include/glib-2.0/glib-object.h:25,
                  from /usr/include/glib-2.0/gio/gioenums.h:30,
                  from /usr/include/glib-2.0/gio/giotypes.h:30,
                  from /usr/include/glib-2.0/gio/gio.h:28,
                  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
                  from /usr/include/gtk-2.0/gdk/gdk.h:32,
                  from /usr/include/gtk-2.0/gtk/gtk.h:32,
                  from FindView.cxx:21:
/usr/include/glib-2.0/glib/gthread.h: In function 'gboolean
g_once_init_enter  olatile gsize*)':
/usr/include/glib-2.0/glib/gthread.h:347:6: error: size of array is negative
make[3]: *** [libshell_gtk_a-FindView.o] Error 1
make[3]: Leaving directory /tmp/SBo/epdfview-0.1.7/src/gtk'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory /tmp/SBo/epdfview-0.1.7/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory /tmp/SBo/epdfview-0.1.7'
make: *** [all] Error 2

   This, along with the GoogleEarth issue, suggests to me that either the
multilib upgrades or the compat32 installations are incomplete. Yesterday I
downloaded all 210M of the 13.37/ subdirectory and this morning followed the
web page "Quick Start" instructions step-by-step.

   What's your recommendations to find and fix these problems?

Rich

From baildon.research at googlemail.com  Thu Jun 16 21:09:12 2011
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 16 Jun 2011 22:09:12 +0100
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
Message-ID: <BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>

> /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such
> file or directory
> /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success

That's what happens if you haven't done what's in the SlackBuild's
README, note 2:

2) Google Earth 6 is "LSB compliant" meaning it was built on a LSB system.
   Slackware however does not have that symlink which is part of the LSB 3.0
   specification. You'll need to create the symlink manually after installing
   the package:

            ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

Yes, it's the Google Earth team being silly.
-D.

From rshepard at appl-ecosys.com  Thu Jun 16 21:16:20 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 14:16:20 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
Message-ID: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>

   If I have missed something with the installation of the multilib and
compat32 libraries, how should I re-do the process to fix the errors?

   Graphviz tells me it cannot find a library which is in /usr/lib64; it's
looking in /usr/lib. Is this a build script error?

libtool: link: warning: /usr/lib/libstdc++.la' seems to be moved
/usr/lib/libpangocairo-1.0.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[3]: *** [libgvplugin_gd.la] Error 1
make[3]: Leaving directory /tmp/SBo/graphviz-2.28.0/plugin/gd'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory /tmp/SBo/graphviz-2.28.0/plugin'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory /tmp/SBo/graphviz-2.28.0'
make: *** [all] Error 2

Rich

From rshepard at appl-ecosys.com  Thu Jun 16 21:22:15 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 14:22:15 -0700 (PDT)
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, David Spencer wrote:

> That's what happens if you haven't done what's in the SlackBuild's
> README, note 2:
>
> 2) Google Earth 6 is "LSB compliant" meaning it was built on a LSB system.
>   Slackware however does not have that symlink which is part of the LSB 3.0
>   specification. You'll need to create the symlink manually after installing
>   the package:
>
>            ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

David,

   Mea culpa! You're correct that I read the notes too quickly to really pay
attention to them.

   Thank you. That fixed the Google Earth problem. One down, two to go.

Rich

From kingbeowulf at gmail.com  Thu Jun 16 21:36:16 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 16 Jun 2011 14:36:16 -0700
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
	<alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>
Message-ID: <BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>

That tidbit caught me the other day too and was especially perplexing in the
Slack32 VM until I put the beer down.  I think it would be a good idea to
put

ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

into the doinst.sh with maybe a quick check to see if the 32-bit libs are
installed.  After all why the heck not?



-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110616/70b2d25f/attachment.html>

From sid77 at slackware.it  Thu Jun 16 22:00:33 2011
From: sid77 at slackware.it (Marco Bonetti)
Date: Fri, 17 Jun 2011 00:00:33 +0200
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>	<alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>
	<BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>
Message-ID: <4DFA7D01.8000306@slackware.it>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/16/2011 11:36 PM, King Beowulf wrote:
> After all why the heck not?
THOU SHALL NOT MESS WITH LD-LINUX.SO.2 !!!

On a more serious note: I agree the link is almost armless but I don't
think install scripts should start messing around with other packages'
files. Especially with glibc stuff.
To me README and README.SLACKWARE are the standard places to look for
slackbuilds.org notes on building and installing packages, if something
is so important that has to be stressed several times, I'd suggest a
note inside slack-desc but nothing more.

Ciao!

P.S.: or, why not a LSB-compat package with symlinks for needed stuff?
Anyone up for it?

- -- 
Marco Bonetti
Tor research and other stuff: http://sid77.slackware.it/
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/

My GnuPG key id: 0x0B60BC5F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk36fQEACgkQTYvJ9gtgvF8/dwCgtciGjQ/5Y0Ty7tAQj2pxLmb7
ItAAoOvLVd7dpWKHMmE66I7nc+T/LVzm
=wUoi
-----END PGP SIGNATURE-----

From rshepard at appl-ecosys.com  Thu Jun 16 22:12:46 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 15:12:46 -0700 (PDT)
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
	<alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>
	<BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106161511470.32425@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, King Beowulf wrote:

> After all why the heck not?

   Because it would limit the opportunities for folks to make fun of me. :-)

Rich

From yalhcru at gmail.com  Thu Jun 16 22:21:01 2011
From: yalhcru at gmail.com (B Watson)
Date: Thu, 16 Jun 2011 18:21:01 -0400
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
Message-ID: <BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>

On 6/16/11, Rich Shepard <rshepard at appl-ecosys.com> wrote:

>    Graphviz tells me it cannot find a library which is in /usr/lib64; it's
> looking in /usr/lib. Is this a build script error?

Nope. The build scripts are tested & supported only on non-multilib
(pure 64-bit). This gets mentioned pretty often on this mailing list...

However, a lot of builds that have this problem (looking for libs in
/usr/lib) can be made to work by adding 'LDFLAGS=-L/usr/lib64' to the
configure command (right before the CFLAGS and CXXFLAGS stuff).

Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't
include /usr/lib/pkgconfig (if it's not set, set it to something like
/usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig
in your .bash_profile or whatever).

Worst-case scenario, you might have to hack up the Makefile or whatever
the source uses for building. Not really difficult, most of the time.

From rshepard at appl-ecosys.com  Thu Jun 16 23:03:47 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 16:03:47 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, B Watson wrote:

> Nope. The build scripts are tested & supported only on non-multilib (pure
> 64-bit). This gets mentioned pretty often on this mailing list...

   Sigh. Since I only very recently installed 64-bit Slackware-13.37 on my
Dell Latitude I've not paid attention to 64-bit issues on the mail list.

> However, a lot of builds that have this problem (looking for libs in
> /usr/lib) can be made to work by adding 'LDFLAGS=-L/usr/lib64' to the
> configure command (right before the CFLAGS and CXXFLAGS stuff).

   Unfortunately, graphviz doesn't like this any better.

> Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't
> include /usr/lib/pkgconfig (if it's not set, set it to something like
> /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig
> in your .bash_profile or whatever).

   I don't follow you here. /usr/lib/pkgconfig contains 208 files. Are you
suggesting that I add the additional paths in ~/.bash_profile?

> Worst-case scenario, you might have to hack up the Makefile or whatever
> the source uses for building. Not really difficult, most of the time.

   Well, since I've not had success building graphviz on earlier releases
either I don't know that I really need it. It looks potentially useful, but
I have no experience with it. It can wait and I won't miss what I don't
know. :-)

Thanks,

Rich

From artourter at gmail.com  Thu Jun 16 23:32:06 2011
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Fri, 17 Jun 2011 00:32:06 +0100
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
Message-ID: <BANLkTimeRf1QOhR9qTHC7cCmUb3S6EqRFA@mail.gmail.com>

Hi,

I have just compiled graphviz on a multilib system without any issues
and without modifying anything.

The only thing I can think off is that you have run the
/etc/profile.d/32dev.sh before trying to compile it which you
shouldn't if you are trying to compile a 64bit package. Make should
the script is not executable.  But apart from that I am not sure what
to advise.



On 16 June 2011 23:21, B Watson <yalhcru at gmail.com> wrote:
> On 6/16/11, Rich Shepard <rshepard at appl-ecosys.com> wrote:
>
>> ? ?Graphviz tells me it cannot find a library which is in /usr/lib64; it's
>> looking in /usr/lib. Is this a build script error?
>
> Nope. The build scripts are tested & supported only on non-multilib
> (pure 64-bit). This gets mentioned pretty often on this mailing list...
>
> However, a lot of builds that have this problem (looking for libs in
> /usr/lib) can be made to work by adding 'LDFLAGS=-L/usr/lib64' to the
> configure command (right before the CFLAGS and CXXFLAGS stuff).
>
> Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't
> include /usr/lib/pkgconfig (if it's not set, set it to something like
> /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig
> in your .bash_profile or whatever).
>
> Worst-case scenario, you might have to hack up the Makefile or whatever
> the source uses for building. Not really difficult, most of the time.
> _______________________________________________
> 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 slacker at slaphappygeeks.com  Thu Jun 16 23:31:08 2011
From: slacker at slaphappygeeks.com (Slacker build user)
Date: Thu, 16 Jun 2011 17:31:08 -0600
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
Message-ID: <4DFA923C.1020001@slaphappygeeks.com>

Rich Shepard wrote:
>   Well, since I've not had success building graphviz on earlier releases
> either I don't know that I really need it. It looks potentially useful, but
> I have no experience with it. It can wait and I won't miss what I don't
> know. :-)

I wish I could help - but no 64 bit access at the moment... I have Graphviz only 
on a couple of 12.1 boxes right now.

On the other hand, I have used Graphviz quite a bit for several years and do in 
fact find it very useful. I would encourage you to grit your teeth and get it 
running - it is worth some effort, and then you will know what you might have 
missed!

If I get access to a 64 bit build platform I'll try to build it an post back to 
the list.

Robert

From volkerdi at slackware.com  Thu Jun 16 23:36:33 2011
From: volkerdi at slackware.com (Patrick J. Volkerding)
Date: Thu, 16 Jun 2011 18:36:33 -0500
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
Message-ID: <4DFA9381.5030405@slackware.com>

On 06/16/2011 04:09 PM, David Spencer wrote:
> 2) Google Earth 6 is "LSB compliant" meaning it was built on a LSB system.
>     Slackware however does not have that symlink which is part of the LSB 3.0
>     specification. You'll need to create the symlink manually after installing
>     the package:
>
>              ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3
>
> Yes, it's the Google Earth team being silly.
> -D.

Something important finally used the LSD, I mean LSB, and it only took 
15 years!

Is there a list of the usual silly symlinks, or is this the only one 
that anything is likely to use so far?  I mean, as long as there's no 
matching .so it would be used at runtime only, so I don't see any 
obvious harm in supplying those in Slackware.

-P.

From rshepard at appl-ecosys.com  Thu Jun 16 23:43:50 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 16 Jun 2011 16:43:50 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <4DFA923C.1020001@slaphappygeeks.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<4DFA923C.1020001@slaphappygeeks.com>
Message-ID: <alpine.LNX.2.00.1106161642380.32425@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, Slacker build user wrote:

> On the other hand, I have used Graphviz quite a bit for several years and
> do in fact find it very useful. I would encourage you to grit your teeth
> and get it running - it is worth some effort, and then you will know what
> you might have missed!

Robert,

   As time permits. Right now I'm focused on using GRASS, R, and advanced
statistical models for biologic data.

> If I get access to a 64 bit build platform I'll try to build it an post
> back to the list.

   Apparently it builds and runs on pure 64-bit systems, but not on multilib
systems.

Regards,

Rich

From kingbeowulf at gmail.com  Fri Jun 17 02:35:16 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 16 Jun 2011 19:35:16 -0700
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <4DFA9381.5030405@slackware.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
	<4DFA9381.5030405@slackware.com>
Message-ID: <BANLkTinzbXLbkWaXxtpcfPuARzA5JK0ceQ@mail.gmail.com>

On Thu, Jun 16, 2011 at 4:36 PM, Patrick J. Volkerding <
volkerdi at slackware.com> wrote:

> On 06/16/2011 04:09 PM, David Spencer wrote:
>
>> 2) Google Earth 6 is "LSB compliant" meaning it was built on a LSB system.
>>    Slackware however does not have that symlink which is part of the LSB
>> 3.0
>>    specification. You'll need to create the symlink manually after
>> installing
>>    the package:
>>
>>             ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3
>>
>> Yes, it's the Google Earth team being silly.
>> -D.
>>
>
> Something important finally used the LSD, I mean LSB, and it only took 15
> years!
>
> Is there a list of the usual silly symlinks, or is this the only one that
> anything is likely to use so far?  I mean, as long as there's no matching
> .so it would be used at runtime only, so I don't see any obvious harm in
> supplying those in Slackware.
>
> -P.
>
>
Well, all I know about LSB is a few seconds or skimming the wikipedia
article.  Since only a symlink was required, that sorta indicate Slackware
is "LSB compatible" in terms of GoogleEarth.  Heck, if it doesn't bother our
Great Guru...

>On a more serious note: I agree the link is almost armless but I don't
think install scripts
>should start messing around with other packages' files. Especially with
glibc stuff.

Er, from what little I can understand, glibc is LSB compliant. So what's the
issue? There was some talk on Gentoo, Debian and elsewhere about LSB symlink
post install packages  (
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355959) and sift through
http://refspecs.freestandards.org/lsb.shtml

 ... but I tire easily and the beer won't drink itself....

The point I was trying to make was that the package built via SBo should
work like any package native to Slackware. You run the script, installpkg,
run it. If you need to do "tweaking" of symlinks, that should be set up via
the package. Sometimes some post installation configuring is needed but that
is not this case.

And while its fun to make fun of anyone, esp Rich Shepard ;-) I repeat, why
the heck not put the symlink in doinst.sh if it doesn't bother and Slackware
libs etc.?

Dammit....I burnt the pork chops during this !!!! rant !!!!   Slackware
SUCKS!!!!  =:0

-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110616/1f0c8560/attachment.html>

From yalhcru at gmail.com  Fri Jun 17 03:57:43 2011
From: yalhcru at gmail.com (B Watson)
Date: Thu, 16 Jun 2011 23:57:43 -0400
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
Message-ID: <BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>

On 6/16/11, Rich Shepard <rshepard at appl-ecosys.com> wrote:

>> Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't
>> include /usr/lib/pkgconfig (if it's not set, set it to something like
>> /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig
>> in your .bash_profile or whatever).
>
>    I don't follow you here. /usr/lib/pkgconfig contains 208 files. Are you
> suggesting that I add the additional paths in ~/.bash_profile?

Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in
your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there).

You don't have to list 200-something .pc files, the PKG_CONFIG_PATH
just contains the director(y|ies) where the .pc files are located. The
ones in /usr/lib/pkgconfig (if you even have them) are 32-bit, and will
specify things like -L/usr/lib, which you don't want.

From josiahb at gmail.com  Fri Jun 17 04:19:49 2011
From: josiahb at gmail.com (Josiah Boothby)
Date: Thu, 16 Jun 2011 21:19:49 -0700
Subject: [Slackbuilds-users] sawfish
Message-ID: <BANLkTi=fGiz62TDF+TXG6TfQKzOSj98mOg@mail.gmail.com>

I seem to recall sawfish was a problem for some previous versions of
Slackware. I found it compiled nice and easy for 13.37, though I
didn't bother writing the requisite SlackBuilds. If anybody is
interested, email me and I'll draw them up and submit them.

--Josiah

From chris.abela at maltats.com  Fri Jun 17 06:33:22 2011
From: chris.abela at maltats.com (Chris ABELA)
Date: Fri, 17 Jun 2011 08:33:22 +0200
Subject: [Slackbuilds-users] What packages do you upgrade?
In-Reply-To: <BANLkTikVBC2uXNQ66E-HENFDuROBA9uovQ@mail.gmail.com>
References: <4270A46AC7934B2388CE36DE85792B57@maltats.com><BANLkTinsNb58Kfc8--w3ebhZOwYjuAn5Zw@mail.gmail.com>
	<BANLkTikVBC2uXNQ66E-HENFDuROBA9uovQ@mail.gmail.com>
Message-ID: <E1863A3A79354253A3BAB635865C4560@maltats.com>


>> 2011/6/16 Chris ABELA <chris.abela at maltats.com>:
>>> 3. Upgrade them but do not bother with any other packages even if they
>>>were
>>
>> I got for that all the time.
>>
>> --
>> Ozan, BSc, BEng

> Well, if you upgrade a library, you might need to rebuild the packages
> that depend on it.
> This all depends on how big the change is in the lib - and how
> upstream developers took care of that...

> For instance, if you upgrade libxyz for 1.2.1 to 1.2.2 and upstream
> maintained compatibility, everything will be OK.
> But a change from 1.2.1 to 2.0.0 sounds like a major upgrade, with a
> new version of the shared object and might intruduce compatibility
> problems.

> My personal experience:
> - read the changelog of the upgrades package from upstream to find out
> why they released the new version. If they are responsible persons,
> the warn about possible impacts.
> - run "ldd <your_program>" after the upgrade and check for errors
> - test <your_program> - especially the functionality handled by libxyz
> if possible.
> - try at least to build <your_program> and see if it complains about
> libxyz. If it does, you might even send an e-mail to <your_program>
> developers telling them what you found out, or check their forum,
> mailing list etc. There might be a patch in their source repo already.

> This is all a lot of fun, but it takes some time. :)

> --
> Niels Horn

Thanks to all who replied and/or pondered on my query.


From rshepard at appl-ecosys.com  Fri Jun 17 13:38:11 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 17 Jun 2011 06:38:11 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>

On Thu, 16 Jun 2011, B Watson wrote:

> Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in
> your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there).

   Darn! I changed PKG_CONFIG_PATH in both ~/.bash_profile and
/root/.bash_profile, sourced the latter, and still get the same fatal build
error that /usr/lib/libstdc++.la has moved. With the path change to
/usr/lib64/ I expected this error to be fixed.

   What else have I missed?

Rich

From gusconrad at gmail.com  Fri Jun 17 13:32:02 2011
From: gusconrad at gmail.com (Gustavo Conrad)
Date: Fri, 17 Jun 2011 10:32:02 -0300
Subject: [Slackbuilds-users] Can't get kbluetooth slackbuild
Message-ID: <BANLkTinUJg7DDaJeqMiHZzmBXJObA4HQzQ@mail.gmail.com>

Hi all, I want to install kbluetooth on my 13.37 Slackware but it seems that
the slackbuild file is not present on the server.
Any help will be appreciated.
Thanks!

Gustavo
Patagonia
Argentina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110617/6f2916d1/attachment.html>

From audrius at neutrino.lt  Fri Jun 17 15:39:56 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Fri, 17 Jun 2011 18:39:56 +0300
Subject: [Slackbuilds-users] Can't get kbluetooth slackbuild
In-Reply-To: <BANLkTinUJg7DDaJeqMiHZzmBXJObA4HQzQ@mail.gmail.com>
References: <BANLkTinUJg7DDaJeqMiHZzmBXJObA4HQzQ@mail.gmail.com>
Message-ID: <20110617153956.GA17114@kiras>

On Fri, 2011-06-17 at 10:32:02 -0300, Gustavo Conrad wrote:
> Hi all, I want to install kbluetooth on my 13.37 Slackware but it seems that
> the slackbuild file is not present on the server.

kbluetooth was removed from the repo recently, although there seems to
be a stale DB entry on the website:
http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=cb373c32

As kbluetooth is abandoned by upstream, consider using blueman (included
in Slackware) or bluedevil (Eric has SlackBuilds for it in
<http://taper.alienbase.nl/mirrors/alien-kde/>, I'm just not sure if
that will work with KDE 4.5.5 from Slackware).

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110617/31e4e156/attachment.asc>

From audrius at neutrino.lt  Fri Jun 17 15:47:00 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Fri, 17 Jun 2011 18:47:00 +0300
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
Message-ID: <20110617154700.GB17114@kiras>

On Fri, 2011-06-17 at 06:38:11 -0700, Rich Shepard wrote:
> On Thu, 16 Jun 2011, B Watson wrote:
> 
> >Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in
> >your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there).
> 
>   Darn! I changed PKG_CONFIG_PATH in both ~/.bash_profile and
> /root/.bash_profile, sourced the latter, and still get the same fatal build
> error that /usr/lib/libstdc++.la has moved. With the path change to
> /usr/lib64/ I expected this error to be fixed.
> 
>   What else have I missed?

Rich,

Have you tried what Greg suggested?  He was successful at compiling
graphviz on a multilib system.

Unfortunately, I can't help with this issue as I'm using pure 64-bit
system myself.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110617/dbb1f2a0/attachment.asc>

From rshepard at appl-ecosys.com  Fri Jun 17 16:20:10 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 17 Jun 2011 09:20:10 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <20110617154700.GB17114@kiras>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
Message-ID: <alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>

On Fri, 17 Jun 2011, Audrius Ka?ukauskas wrote:

> Have you tried what Greg suggested?  He was successful at compiling
> graphviz on a multilib system.

   Yes, I have. /etc/profile.d/32dev.sh is not executable. All references to
'lib' are now 'lib64' in the package and library paths.

   The three applications that won't build or run properly are graphviz (low
priority as I've not used it before), acroread (builds but does not properly
display menu fonts), and epdfview (which won't build). The latter two are
rather critical and I need to get them working.

Thanks,

Rich

From rshepard at appl-ecosys.com  Fri Jun 17 16:22:20 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 17 Jun 2011 09:22:20 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <20110617154700.GB17114@kiras>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
Message-ID: <alpine.LNX.2.00.1106170920560.14634@salmo.appl-ecosys.com>

On Fri, 17 Jun 2011, Audrius Ka?ukauskas wrote:

> Have you tried what Greg suggested?  He was successful at compiling
> graphviz on a multilib system.

   Breaking news: graphviz just built when I changed LD_LIBRARY_PATH for both
user me and root to lib64 rather than lib. Hoo-ha!

   Now I need the same expert insights on acroread and epdfview (which I'll
try rebuilding now).

Much appreciated,

Rich

From rshepard at appl-ecosys.com  Fri Jun 17 16:27:46 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 17 Jun 2011 09:27:46 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
	<alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.00.1106170924440.14634@salmo.appl-ecosys.com>

On Fri, 17 Jun 2011, Rich Shepard wrote:

>  The three applications that won't build or run properly are graphviz (low
> priority as I've not used it before), acroread (builds but does not
> properly display menu fonts), and epdfview (which won't build). The latter
> two are rather critical and I need to get them working.

   Well! This has been a valuable lesson for me. Changing references in
LD_LIBRARY_PATH from 'lib' to 'lib64' made the difference for graphviz and
epdfview.

   Acroread (after re-installing) still does not display any readable text on
menus, the open file dialog, or other views. Suggestions?

Thanks,

Rich

From artourter at gmail.com  Fri Jun 17 16:34:35 2011
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Fri, 17 Jun 2011 17:34:35 +0100
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106170924440.14634@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
	<alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.1106170924440.14634@salmo.appl-ecosys.com>
Message-ID: <BANLkTimu-2o4+EKtvX6qaMSRFZHGaRD4fA@mail.gmail.com>

For acroread (which I maintain) you need to run the
/usr/bin/update-pango-querymodules script so that the module file is
created for 32bit as well as 64bit. It should do this automatically at
the next reboot but running it manually should get you going.

Hope this helps

Cheers

Greg

On 17 June 2011 17:27, Rich Shepard <rshepard at appl-ecosys.com> wrote:
> On Fri, 17 Jun 2011, Rich Shepard wrote:
>
>> ?The three applications that won't build or run properly are graphviz (low
>> priority as I've not used it before), acroread (builds but does not
>> properly display menu fonts), and epdfview (which won't build). The latter
>> two are rather critical and I need to get them working.
>
> ?Well! This has been a valuable lesson for me. Changing references in
> LD_LIBRARY_PATH from 'lib' to 'lib64' made the difference for graphviz and
> epdfview.
>
> ?Acroread (after re-installing) still does not display any readable text on
> menus, the open file dialog, or other views. Suggestions?
>
> Thanks,
>
> Rich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>

From rshepard at appl-ecosys.com  Fri Jun 17 17:00:59 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 17 Jun 2011 10:00:59 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <BANLkTimu-2o4+EKtvX6qaMSRFZHGaRD4fA@mail.gmail.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
	<alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.1106170924440.14634@salmo.appl-ecosys.com>
	<BANLkTimu-2o4+EKtvX6qaMSRFZHGaRD4fA@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106170952441.14634@salmo.appl-ecosys.com>

On Fri, 17 Jun 2011, Greg' Ar Tourter wrote:

> For acroread (which I maintain) you need to run the
> /usr/bin/update-pango-querymodules script so that the module file is
> created for 32bit as well as 64bit. It should do this automatically at
> the next reboot but running it manually should get you going.

Greg,

   Aha! Just did this.

> Hope this helps

   I had been installing acroread by direct download from Adobe's Web site. I
did not find any acroread in the repository. But, I tried adobe and found
your adobe-reader package. A difference in semantics.

   Before building your package I tried to download xulrunner (noted as a
prerequisite), but the package is not to be found with the given URL because
1.9.2.16 has been replaced with 1.9.2.17. That's downloading now. I'll build
that, then adobe-reader, and report the results.

   I'll bet updating pango-querymodules makes all the difference.

Stay tuned ...

Rich

From artourter at gmail.com  Fri Jun 17 17:07:45 2011
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Fri, 17 Jun 2011 18:07:45 +0100
Subject: [Slackbuilds-users] Graphviz Build Error
In-Reply-To: <alpine.LNX.2.00.1106170952441.14634@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
	<alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.1106170924440.14634@salmo.appl-ecosys.com>
	<BANLkTimu-2o4+EKtvX6qaMSRFZHGaRD4fA@mail.gmail.com>
	<alpine.LNX.2.00.1106170952441.14634@salmo.appl-ecosys.com>
Message-ID: <BANLkTimfw913+Fw5uGYOT0pu-_ncc0TxQA@mail.gmail.com>

Hi Rich,

I wouldn't worry too much about xulrunner. It is a dependency that was
noted when I inherited the maintenance. it works without it (it is
just that you can see an error if you call acroread from the command
line which disappears when xulrunner is installed. I still haven't
figured out what that is about.

as for the name change, adobe renamed it adobe-reader so it was
decided to follow upstream in the naming convention. I should probably
add acroread to the tags to help the search.

Cheers

Greg

On 17 June 2011 18:00, Rich Shepard <rshepard at appl-ecosys.com> wrote:
> On Fri, 17 Jun 2011, Greg' Ar Tourter wrote:
>
>> For acroread (which I maintain) you need to run the
>> /usr/bin/update-pango-querymodules script so that the module file is
>> created for 32bit as well as 64bit. It should do this automatically at
>> the next reboot but running it manually should get you going.
>
> Greg,
>
> ?Aha! Just did this.
>
>> Hope this helps
>
> ?I had been installing acroread by direct download from Adobe's Web site. I
> did not find any acroread in the repository. But, I tried adobe and found
> your adobe-reader package. A difference in semantics.
>
> ?Before building your package I tried to download xulrunner (noted as a
> prerequisite), but the package is not to be found with the given URL because
> 1.9.2.16 has been replaced with 1.9.2.17. That's downloading now. I'll build
> that, then adobe-reader, and report the results.
>
> ?I'll bet updating pango-querymodules makes all the difference.
>
> Stay tuned ...
>
> Rich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>

From rshepard at appl-ecosys.com  Fri Jun 17 17:22:07 2011
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 17 Jun 2011 10:22:07 -0700 (PDT)
Subject: [Slackbuilds-users] Graphviz Build Error -- [ALL FIXED]
In-Reply-To: <BANLkTimfw913+Fw5uGYOT0pu-_ncc0TxQA@mail.gmail.com>
References: <alpine.LNX.2.00.1106161412590.32425@salmo.appl-ecosys.com>
	<BANLkTinrw43q9C8AEL5AcUiiwbNXC-hqGQ@mail.gmail.com>
	<alpine.LNX.2.00.1106161600000.32425@salmo.appl-ecosys.com>
	<BANLkTimjxaE0Jbg_bwiZTQYnw8_MsPoW0w@mail.gmail.com>
	<alpine.LNX.2.00.1106170635510.14634@salmo.appl-ecosys.com>
	<20110617154700.GB17114@kiras>
	<alpine.LNX.2.00.1106170917370.14634@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.1106170924440.14634@salmo.appl-ecosys.com>
	<BANLkTimu-2o4+EKtvX6qaMSRFZHGaRD4fA@mail.gmail.com>
	<alpine.LNX.2.00.1106170952441.14634@salmo.appl-ecosys.com>
	<BANLkTimfw913+Fw5uGYOT0pu-_ncc0TxQA@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1106171016471.14634@salmo.appl-ecosys.com>

On Fri, 17 Jun 2011, Greg' Ar Tourter wrote:

> I wouldn't worry too much about xulrunner.

Greg,

   Then I won't, either. Stopped the download and removed the directory.

> as for the name change, adobe renamed it adobe-reader so it was decided to
> follow upstream in the naming convention. I should probably add acroread
> to the tags to help the search.

   I've known it as acroread for years and hadn't thought to look for a
SlackBuild for it. However, ... that makes all the difference! Using your
magical script it displays all fonts as it should. Whew!

   I don't know if I want to try to upgrade the BIOS with the SlackBuild
scripts now or wait until I return from my trip. It's been an intense 2+
days getting the multilib portable up and running.

   Those of us who are not linux/slackware professionals (nor hobbyists,
either) really appreciate the dedication and quality work donated by you
package creators and maintainers. I won't be presumptuous by claiming that I
lead this list, but I'm confident that I'm near the top of appreciative
users.

Much thanks,

Rich

From michiel at slackbuilds.org  Fri Jun 17 21:42:20 2011
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Fri, 17 Jun 2011 22:42:20 +0100
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <4DFA7D01.8000306@slackware.it>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
	<alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>
	<BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>
	<4DFA7D01.8000306@slackware.it>
Message-ID: <20110617224220.544b291f@hades.esn.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 17 Jun 2011 00:00:33 +0200
Marco Bonetti <sid77 at slackware.it> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 06/16/2011 11:36 PM, King Beowulf wrote:
> > After all why the heck not?
> THOU SHALL NOT MESS WITH LD-LINUX.SO.2 !!!


AMEN. We have discussed this among us way back. So no, it WILL NOT
appear in the doinst.sh. End of. :)

> To me README and README.SLACKWARE are the standard places to look for
> slackbuilds.org notes on building and installing packages, if
> something is so important that has to be stressed several times, I'd
> suggest a note inside slack-desc but nothing more.

you mean like this? [1] ;)

GoogleEarth: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
GoogleEarth: If GoogleEarth fails to run, first consult the NOTES in
the README.
GoogleEarth: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Interesting enough, 99.8% of all the question I have had in the last
couple of years regarding Google Earth are documented in the README.
Yes, Google are annoying in several ways regarding this, but such it
is, I fear. :)

M.
- -- 
Michiel van Wessem
http://slackbuilds.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk37yjwACgkQV9sst+q63XuT1gCfVWv0PBRFEmZvL2ME9r/vm2Pa
84EAn1/KeRhu7Vjm8toSI4FNPSJ2+hpk
=xzO2
-----END PGP SIGNATURE-----

From michiel at slackbuilds.org  Fri Jun 17 21:47:48 2011
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Fri, 17 Jun 2011 22:47:48 +0100
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <4DFA9381.5030405@slackware.com>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
	<4DFA9381.5030405@slackware.com>
Message-ID: <20110617224748.623c9161@hades.esn.local>

On Thu, 16 Jun 2011 18:36:33 -0500
"Patrick J. Volkerding" <volkerdi at slackware.com> wrote:
 
> Is there a list of the usual silly symlinks, or is this the only one 
> that anything is likely to use so far?

As far as I am aware, this is (so far) the only application that
actually has a need for the LSB link to be present.	

M.
-- 
Michiel van Wessem
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110617/574d380b/attachment.asc>

From grbzks at xsmail.com  Fri Jun 17 23:31:03 2011
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sat, 18 Jun 2011 02:31:03 +0300
Subject: [Slackbuilds-users] Can't get kbluetooth slackbuild
In-Reply-To: <20110617153956.GA17114@kiras>
References: <BANLkTinUJg7DDaJeqMiHZzmBXJObA4HQzQ@mail.gmail.com>
	<20110617153956.GA17114@kiras>
Message-ID: <20110617233052.GA15374@netbook>

Audrius Ka?ukauskas wrote:
>
> kbluetooth was removed from the repo recently, although there seems to
> be a stale DB entry on the website:
> http://slackbuilds.org/gitweb/?p=3Dslackbuilds.git;a=3Dcommit;h=3Dcb373c32
>
> As kbluetooth is abandoned by upstream, consider using blueman (included
> in Slackware) or bluedevil (Eric has SlackBuilds for it in
><http://taper.alienbase.nl/mirrors/alien-kde/>, I'm just not sure if
> that will work with KDE 4.5.5 from Slackware).

If you want a decent KDE bluetooth implemention use bluedevil.
I don't know if Eric's package will work with 4.5.5, but building from
source surely will. I was using bluedevil even back in 2010.
Kbluetooth is not even worth mentioning at this point.

Greg

-- 
()  against html e-mail  |  usenet & email communication netiquette
/\  www.asciiribbon.org  |  www.netmeister.org/news/learn2quote.html

From info at microlinux.fr  Sat Jun 18 07:36:02 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sat, 18 Jun 2011 09:36:02 +0200
Subject: [Slackbuilds-users] Introduction & questions about link creation
 for the 'oxygen-gtk' theme
Message-ID: <4DFC5562.1070508@microlinux.fr>

Hi,

I'm an Austrian IT consultant (big word for saying that I run a 
one-man-company specialized in installing SOHO networks for small town 
halls, schools, public libraries and the likes, based 100% on GNU/Linux 
and FOSS) living in Montpezat, a small and sunny village in South 
France. I made my first steps on Linux back on 2001 on Slackware, and 
I've been a Slackware user for a few years. For the last few years, I've 
been switching to CentOS for various reasons. About two weeks ago, I've 
decided to come back to Slackware because 1) the release policy suits 
me, 2) despite the appearances, it's enterprise class, 3) it's 
rock-solid and belongs to the category of rare Linux distributions that 
JustWork(tm), 4) it doesn't succumb to the temptation of reinventing the 
wheel every six months by desperately implementing every new technology 
on the block. 5) It's fun. But you probably know all that.

I'm currently quite busy getting my act together on Slackware, so I'm 
writing sets of tagfiles, put all my config files in nifty little 
SlackBuild scripts so I can distribute them easily, RTFM a lot, etc.

I'm using KDE as desktop, and I tried out SBo's 'oxygen-gtk' package for 
visual integration of GTK applications. It works really great, but now I 
have a - small - problem that I'd like to solve.

1) The site contains a small HOWTO on how to activate the theme, simply 
by creating a symlink like this:

$ cd
$ ln -s /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc .gtkrc-2.0

Which works nice.

2) Since I'm planning to use this configuration on machines with lots of 
users (think: schools), I'd like to integrate this in my user profiles. 
So I tried this:

# ln -s /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc /etc/skel/.gtkrc-2.0

Which works also nice: every new user is created "automagically" with 
the relevant symlink in his home directory.

3) Now here comes the point where I reach my limit of competence. I'm 
trying to package my default user profile. I'm writing a SlackBuild 
script for this, and right now, I wonder how to define that symlink. I 
know how to go about it with a simple file. Say I have a 'gtkrc' file in 
the same directory as the SlackBuild script, the solution would be 
something like this:

mkdir -p $PKG/etc/skel
cat $CWD/gtkrc > $PKG/etc/skel/.gtkrc-2.0
chmod 0644 $PKG/etc/skel/.gtkrc-2.0

But how could I have something similar with the symlink?

Any suggestions?

Niki

From audrius at neutrino.lt  Sat Jun 18 09:51:35 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Sat, 18 Jun 2011 12:51:35 +0300
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
In-Reply-To: <4DFC5562.1070508@microlinux.fr>
References: <4DFC5562.1070508@microlinux.fr>
Message-ID: <20110618095135.GA2145@kiras>

Welcome back to Slackware!

On Sat, 2011-06-18 at 09:36:02 +0200, Nicolas Kovacs wrote:
> 3) Now here comes the point where I reach my limit of competence.
> I'm trying to package my default user profile. I'm writing a
> SlackBuild script for this, and right now, I wonder how to define
> that symlink. I know how to go about it with a simple file. Say I
> have a 'gtkrc' file in the same directory as the SlackBuild script,
> the solution would be something like this:
> 
> mkdir -p $PKG/etc/skel
> cat $CWD/gtkrc > $PKG/etc/skel/.gtkrc-2.0
> chmod 0644 $PKG/etc/skel/.gtkrc-2.0
> 
> But how could I have something similar with the symlink?

Wouldn't something like this work?

  mkdir -p $PKG/etc/skel
  ln -sf /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc $PKG/etc/skel/.gtkrc-2.0

And don't forget to add -l y to makepkg, so that it will add all
symlinks to doinst.sh script.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110618/ce15fdc0/attachment.asc>

From binhnguyen at fastmail.fm  Sat Jun 18 10:05:01 2011
From: binhnguyen at fastmail.fm (Binh Nguyen)
Date: Sat, 18 Jun 2011 17:05:01 +0700
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
In-Reply-To: <4DFC5562.1070508@microlinux.fr>
References: <4DFC5562.1070508@microlinux.fr>
Message-ID: <20110618170501.304d092f@darkstar.example.net>

On Sat, 18 Jun 2011 09:36:02 +0200
Nicolas Kovacs <info at microlinux.fr> wrote:

> Hi,
> [...] 
> mkdir -p $PKG/etc/skel
> cat $CWD/gtkrc > $PKG/etc/skel/.gtkrc-2.0
> chmod 0644 $PKG/etc/skel/.gtkrc-2.0
> 
> But how could I have something similar with the symlink?
> 
> Any suggestions?
> 
> Niki

If I understand correctly, in this your package, you want to create a
symlink to gtkrc of the package oxygen-gtk.

Then this would suffice:

mkdir -p $PKG/etc/skel
cd $PKG/etc/skel
ln -s ../../usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc .gtkrc-2.0
cd -

Regards,

-- 
Binh Nguyen

From info at microlinux.fr  Sat Jun 18 12:54:09 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sat, 18 Jun 2011 14:54:09 +0200
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
In-Reply-To: <20110618170501.304d092f@darkstar.example.net>
References: <4DFC5562.1070508@microlinux.fr>
	<20110618170501.304d092f@darkstar.example.net>
Message-ID: <4DFC9FF1.1060201@microlinux.fr>

Le 18/06/2011 12:05, Binh Nguyen a ?crit :

>
> If I understand correctly, in this your package, you want to create a
> symlink to gtkrc of the package oxygen-gtk.
>
> Then this would suffice:
>
> mkdir -p $PKG/etc/skel
> cd $PKG/etc/skel
> ln -s ../../usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc .gtkrc-2.0
> cd -
>

Thanks for the quick response (also to Audrius). I tried the relative 
link as suggested, and it works fine.
One thing that puzzled me was if the solution would work independently 
of 'oxygen-gtk' installed, e. g. what would happen if my 
'user-settings-desktop' package was installed *before* 'oxygen-gtk'.

Well, I got it: the symlink is created, but broken. And as soon as
'oxygen-gtk' is installed, the broken symlink becomes valid.
The idea which got me stuck was: create a symlink on a - yet - 
nonexistent file.

Cheers,

Niki

From rworkman at slackbuilds.org  Sat Jun 18 16:11:20 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 18 Jun 2011 11:11:20 -0500
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
In-Reply-To: <20110618170501.304d092f@darkstar.example.net>
References: <4DFC5562.1070508@microlinux.fr>
	<20110618170501.304d092f@darkstar.example.net>
Message-ID: <20110618111120.163f5aa8@liberty.rlwhome.lan>

On Sat, 18 Jun 2011 17:05:01 +0700
Binh Nguyen <binhnguyen at fastmail.fm> wrote:

> On Sat, 18 Jun 2011 09:36:02 +0200
> Nicolas Kovacs <info at microlinux.fr> wrote:
> 
> > Hi,
> > [...] 
> > mkdir -p $PKG/etc/skel
> > cat $CWD/gtkrc > $PKG/etc/skel/.gtkrc-2.0
> > chmod 0644 $PKG/etc/skel/.gtkrc-2.0
> > 
> > But how could I have something similar with the symlink?
> > 
> > Any suggestions?
> > 
> > Niki
> 
> If I understand correctly, in this your package, you want to create a
> symlink to gtkrc of the package oxygen-gtk.
> 
> Then this would suffice:
> 
> mkdir -p $PKG/etc/skel
> cd $PKG/etc/skel
> ln -s ../../usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc .gtkrc-2.0
> cd -


You'll want to use the absolute path ("/usr/...") as opposed to
relative path ("../../usr/...") or else you run the risk of a
broken link.  It just happens to work in this case because
/etc/skel is the same distance away from /usr that /home/$USER
is, but if you decide to get creative (or e.g. use the root
account), that link will be broken.

I'm curious why you don't just set the systemwide gtkrc though at
/etc/gtk-2.0/gtkrc to that.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110618/e6d71e1e/attachment.asc>

From rworkman at slackbuilds.org  Sat Jun 18 16:12:22 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 18 Jun 2011 11:12:22 -0500
Subject: [Slackbuilds-users] GoogleEarth Won't Start
In-Reply-To: <4DFA7D01.8000306@slackware.it>
References: <alpine.LNX.2.00.1106161249430.32425@salmo.appl-ecosys.com>
	<BANLkTik_=Ei4ywkNfs+zc6jMasA-Furj0w@mail.gmail.com>
	<alpine.LNX.2.00.1106161418390.32425@salmo.appl-ecosys.com>
	<BANLkTin0N10s6oPy9oCnOH9nnw=Dt9ODsw@mail.gmail.com>
	<4DFA7D01.8000306@slackware.it>
Message-ID: <20110618111222.39dd73b8@liberty.rlwhome.lan>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 17 Jun 2011 00:00:33 +0200
Marco Bonetti <sid77 at slackware.it> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 06/16/2011 11:36 PM, King Beowulf wrote:
> > After all why the heck not?
> THOU SHALL NOT MESS WITH LD-LINUX.SO.2 !!!
> 
> On a more serious note: I agree the link is almost armless but I don't
> think install scripts should start messing around with other packages'
> files. Especially with glibc stuff.
> To me README and README.SLACKWARE are the standard places to look for
> slackbuilds.org notes on building and installing packages, if
> something is so important that has to be stressed several times, I'd
> suggest a note inside slack-desc but nothing more.
> 
> Ciao!
> 
> P.S.: or, why not a LSB-compat package with symlinks for needed stuff?
> Anyone up for it?


I think that's a reasonable idea.  With any luck, it could go away 
for the next release of Slackware :-)

- -RW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk38zmcACgkQvGy9tf6lsvvrjgCgkhXKy3grCCSm4X0U/IF92jSQ
+eMAmwRvCN/Q2dyYjsCriHTKwjh+cEIc
=gR08
-----END PGP SIGNATURE-----

From rworkman at slackbuilds.org  Sat Jun 18 16:20:20 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 18 Jun 2011 11:20:20 -0500
Subject: [Slackbuilds-users] Remove loic from pending please
In-Reply-To: <11B204FF9E5A417296DE36410F11BCB7@maltats.com>
References: <11B204FF9E5A417296DE36410F11BCB7@maltats.com>
Message-ID: <20110618112020.2ccf2385@liberty.rlwhome.lan>

On Thu, 16 Jun 2011 16:13:41 +0200
"Chris ABELA" <chris.abela at maltats.com> wrote:

> Will someone from the Admins please remove my submission for loic. I
> made some significant enhancements I would like to include before
> your review. Unlike other submissions I had made before, I did not
> receive the mail with instructions on how to do this.


Done.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110618/b0bb6f26/attachment.asc>

From eric at schultzter.ca  Sat Jun 18 17:31:47 2011
From: eric at schultzter.ca (Eric Schultz)
Date: Sat, 18 Jun 2011 13:31:47 -0400
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
Message-ID: <BANLkTikd0LQF8hy=5Gerhh58CvXYLcmmcg@mail.gmail.com>

From: Nicolas Kovacs <info at microlinux.fr>
To: slackbuilds-users at slackbuilds.org
Date: Sat, 18 Jun 2011 14:54:09 +0200
Subject: Re: [Slackbuilds-users] Introduction & questions about link
creation for the 'oxygen-gtk' theme
Le 18/06/2011 12:05, Binh Nguyen a ?crit :

< snip >

> Well, I got it: the symlink is created, but broken. And as soon as
> 'oxygen-gtk' is installed, the broken symlink becomes valid.
> The idea which got me stuck was: create a symlink on a - yet - nonexistent file.

It's the -s option on the ln command that lets you get away with
creating links to non-existent files!

From info at microlinux.fr  Sat Jun 18 17:37:30 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sat, 18 Jun 2011 19:37:30 +0200
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
In-Reply-To: <20110618111120.163f5aa8@liberty.rlwhome.lan>
References: <4DFC5562.1070508@microlinux.fr>	<20110618170501.304d092f@darkstar.example.net>
	<20110618111120.163f5aa8@liberty.rlwhome.lan>
Message-ID: <4DFCE25A.1000307@microlinux.fr>

Le 18/06/2011 18:11, Robby Workman a ?crit :

>
> I'm curious why you don't just set the systemwide gtkrc though at
> /etc/gtk-2.0/gtkrc to that.
>

Hi Robbie!

Short answer: because I didn't know I could do it :o)
Thanks for the precious bit of information, I'll change my script 
accordingly. Also duly noted the info about absolute vs. relative link 
paths. And no, I wouldn't dream of logging into KDE as root.

Cheers,

Niki

From binhnguyen at fastmail.fm  Sun Jun 19 11:00:25 2011
From: binhnguyen at fastmail.fm (Binh Nguyen)
Date: Sun, 19 Jun 2011 18:00:25 +0700
Subject: [Slackbuilds-users] Introduction & questions about link
 creation for the 'oxygen-gtk' theme
In-Reply-To: <20110618111120.163f5aa8@liberty.rlwhome.lan>
References: <4DFC5562.1070508@microlinux.fr>
	<20110618170501.304d092f@darkstar.example.net>
	<20110618111120.163f5aa8@liberty.rlwhome.lan>
Message-ID: <20110619180025.4b2138c0@darkstar.example.net>

On Sat, 18 Jun 2011 11:11:20 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> On Sat, 18 Jun 2011 17:05:01 +0700
> Binh Nguyen <binhnguyen at fastmail.fm> wrote:
> 
> > On Sat, 18 Jun 2011 09:36:02 +0200
> > Nicolas Kovacs <info at microlinux.fr> wrote:
> > 
> > > Hi,
> > > [...] 
> > > mkdir -p $PKG/etc/skel
> > > cat $CWD/gtkrc > $PKG/etc/skel/.gtkrc-2.0
> > > chmod 0644 $PKG/etc/skel/.gtkrc-2.0
> > > 
> > > But how could I have something similar with the symlink?
> > > 
> > > Any suggestions?
> > > 
> > > Niki
> > 
> > If I understand correctly, in this your package, you want to create
> > a symlink to gtkrc of the package oxygen-gtk.
> > 
> > Then this would suffice:
> > 
> > mkdir -p $PKG/etc/skel
> > cd $PKG/etc/skel
> > ln -s ../../usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc .gtkrc-2.0
> > cd -
> 
> 
> You'll want to use the absolute path ("/usr/...") as opposed to
> relative path ("../../usr/...") or else you run the risk of a
> broken link.  It just happens to work in this case because
> /etc/skel is the same distance away from /usr that /home/$USER
> is, but if you decide to get creative (or e.g. use the root
> account), that link will be broken.
> 

Oh yes, I forgot that this file only becomes effective when a new user
is created.

-- 
Binh Nguyen

From rworkman at slackbuilds.org  Mon Jun 20 04:43:56 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 20 Jun 2011 04:43:56 +0000
Subject: [Slackbuilds-users] Updates - 20110620.1
Message-ID: <20110620044353.GA27584@slackbuilds.org>

Mon Jun 20 04:18:29 UTC 2011
academic/octave: Updated for version 3.4.0.
accessibility/espeak: Updated for version 1.45.04.
accessibility/wgetpaste: Updated for version 2.18.
audio/a52dec: Updated maintainer information.
audio/aften: Updated maintainer information.
audio/fluid-soundfont: Added (Fluid General MIDI SoundFont)
audio/volti: Added (gtk+ alsa volume control applet)
desktop/rootactions_servicemenu: Updated for version 2.7.1.
development/Pygments: Updated for version 1.4.
development/acpica: Updated for version 20110527.
development/autogen: Updated for version 5.11.9.
development/avr-gcc: Updated for version 4.5.3.
development/bpython: Updated for version 0.9.7.1.
development/gaphor: Updated for version 0.17.0.
development/gsoap: Updated for version 2.8.2.
development/open-cobol: Added (open-source COBOL compiler)
development/pcc-libs: Added (C Library for the Portable C Compiler)
development/pcc: Added (Portable C Compiler)
development/pychecker: Updated for version 0.8.19.
games/bsnes: Updated for version 0.079.
games/hatari: Updated for version 1.4.0.
games/warsow: Updated for version 0.62.
games/wesnoth: Updated for version 1.8.6.
graphics/dcraw: Updated for version 9.08.
haskell-haskell-regex-compat: Updated for version 0.95.1.
haskell/ghc: Updated for version 7.0.3.
haskell/haskell-MonadCatchIO-mtl: Updated for version 0.3.0.2.
haskell/haskell-QuickCheck: Updated for version 2.4.1.1.
haskell/haskell-dataenc: Updated for version 0.14.
haskell/haskell-hashed-storage: Updated for version 0.5.7.
haskell/haskell-haskeline: Updated for version 0.6.4.0.
haskell/haskell-network: Updated for version 2.3.0.3.
haskell/haskell-parsec: Updated for version 3.1.1.
haskell/haskell-regex-posix: Updated for version 0.95.1.
haskell/haskell-syb: Updated for version 0.3.2.
haskell/haskell-test-framework-quickcheck2: Updated for version 0.2.10.
haskell/haskell-test-framework: Updated for version 0.4.0.
haskell/haskell-text: Updated for version 0.11.0.8.
haskell/haskell-zip-archive: Updated for version 0.1.1.7.
haskell/haskell-zlib: Updated for version 0.5.3.1.
libraries/AMD: Updated for version 2.2.2.
libraries/BTF: Updated for version 1.1.2.
libraries/CAMD: Updated for version 2.2.2.
libraries/CCOLAMD: Updated for version 2.7.3.
libraries/CHOLMOD: Updated for version 1.7.3.
libraries/COLAMD: Updated for version 2.7.3.
libraries/CXSparse: Updated for version 2.2.5.
libraries/FormEncode: Updated for version 1.2.4.
libraries/GConf: Updated for version 2.32.4.
libraries/KLU: Updated for version 1.1.2.
libraries/LDL: Updated for version 2.0.3.
libraries/SPQR: Updated for version 1.2.2.
libraries/UMFPACK: Updated for version 5.5.1.
libraries/ZConfig: Updated for version 2.9.0.
libraries/ZODB3: Updated for version 3.10.3.
libraries/barry: Updated for version 0.17.1.
libraries/blas: Updated for version 20110419.
libraries/decorator: Updated for version 3.3.1.
libraries/e_dbus: Updated for version 1.0.1.
libraries/ecore: Updated for version 1.0.1.
libraries/edje: Updated for version 1.0.1.
libraries/eet: Updated for version 1.4.1.
libraries/eeze: Updated for version 1.0.1.
libraries/efreet: Updated for version 1.0.1.
libraries/eina: Updated for version 1.0.1.
libraries/evas: Updated for version 1.0.1.
libraries/ftgl: Updated maintainer information.
libraries/glibmm: Updated for version 2.28.2.
libraries/hdf5: Updated for version 1.8.7.
libraries/libdca: Updated maintainer information.
libraries/libedit: Updated for version 20110227_3.0.
libraries/simplejson: Moved to python.
libraries/simplejson: Updated for version 2.1.6.
libraries/virtualenv: Updated for version 1.6.1.
misc/cups-windows: Updated maintainer email
multimedia/GoogleEarth: Updated for version 6.0.3.2197.
multimedia/flash-player-plugin: Updated for version 10.3_r181.
multimedia/mplayer-codecs: Fixed download links
network/NetworkManager: Noted startup info in README
network/NetworkManager-openvpn: Noted gnome-keyring dep in README
network/arm: Updated for version 1.4.2.3.
network/efax-gtk: Updated for version 3.2.8.
network/leafnode: Included upstream patch for texpire
network/psi: Updated for version 0.14.
network/quvi: Updated for version 0.2.16.
network/rtorrent: Updated for version 0.8.8.
network/shorewall6: Updated for version 4.4.19.4.
network/shorewall: Updated for version 4.4.19.4.
network/skype: Updated for version 2.2.0.35.
network/surfraw: Fixed gzipx2 of man pages
system/dosemu: Updated maintainer information.
system/nvidia-driver: Updated for version 270.41.19.
system/nvidia-kernel: Updated for version 270.41.19.
system/virtualbox-addons: Updated for version 4.0.8.
system/virtualbox-kernel-addons: Updated for version 4.0.8.
system/virtualbox-kernel: Updated for version 4.0.8.
system/virtualbox: Updated for version 4.0.8.

From rworkman at slackbuilds.org  Mon Jun 20 04:48:56 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 19 Jun 2011 23:48:56 -0500
Subject: [Slackbuilds-users] wrong email adress in some of my scripts
In-Reply-To: <BANLkTikPyPW+YbVsAad0BisDLjBLY4j2-g@mail.gmail.com>
References: <BANLkTikPyPW+YbVsAad0BisDLjBLY4j2-g@mail.gmail.com>
Message-ID: <20110619234856.426dcf1d@liberty.rlwhome.lan>

On Sat, 11 Jun 2011 23:12:46 +0200
Niklas "Nille" ?kerstr?m <nille.kungen at gmail.com> wrote:

> I looked at
> http://slackbuilds.org/gitweb/?p=slackbuilds.git&a=search&h=HEAD&st=grep&s=nilleand
> saw that some of my builds has the wrong email adress.
> Could someone please update all to nille.kungen[AT]gmail.com


Send me a diff (one big diff will be fine) or a git pull 
request, please, and I'll apply it.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110619/9c305a96/attachment.asc>

From rworkman at slackbuilds.org  Mon Jun 20 04:50:00 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 19 Jun 2011 23:50:00 -0500
Subject: [Slackbuilds-users] mplayer-codecs broken source links
In-Reply-To: <BANLkTim8ODHHJLGdagLd7tgYAG5mntAfyA@mail.gmail.com>
References: <BANLkTim8ODHHJLGdagLd7tgYAG5mntAfyA@mail.gmail.com>
Message-ID: <20110619235000.26b4c44d@liberty.rlwhome.lan>

On Sat, 11 Jun 2011 23:05:27 +0200
Niklas "Nille" ?kerstr?m <nille.kungen at gmail.com> wrote:

> I saw that the source links for mplayer-codecs is broken.
> 
> It needs an s/www3/www


Thanks for this and the dozens of other mails I got about 
this - it's nice to know that there are people actually
using the stuff  :-)  Anyway, I fixed it in the latest
public update.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110619/bddd9d3f/attachment-0001.asc>

From rworkman at slackbuilds.org  Mon Jun 20 04:51:28 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 19 Jun 2011 23:51:28 -0500
Subject: [Slackbuilds-users] nvidia
In-Reply-To: <4DDD2C66.20905@gmail.com>
References: <4DDD2C66.20905@gmail.com>
Message-ID: <20110619235128.135c8bf9@liberty.rlwhome.lan>

On Wed, 25 May 2011 09:20:54 -0700
King Beowulf <kingbeowulf at gmail.com> wrote:

> Just an FYI to the list.  I submitted new nvidia-driver and nvidia 
> kernel for 270.41.06 (no changes to the earlier script) and just
> noticed 270.41.19 was released a few days ago that fixes a few bugs.
> I have not encountered those issues yet with 270.41.06 on my GT430.
> Also, the 270.xx.xx series has a few libs that I did not capture -
> nothing critical.  I plan on updating the script "real soon now" and
> fixing a few niggles.  I have therefore submitted queue removal
> requests via the submission email link.  BTW, the 270.xx.xx drivers
> are one hell of a lot faster....
> 
> Also, the legacy drivers are on hold for a bit.  If anyone needs them 
> updated, let me know.
> 
> If anyone catches any errors in the slackbuilds, or has
> recommendations, let me know and I'll add then add them to the to-do
> list.


I fixed what was likely a thinko in the nvidia-driver script.
It wouldn't build at all on 32bit due to the multilib stuff. 
Have a look - it just got shoved out to public.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110619/285c7c35/attachment.asc>

From rworkman at slackbuilds.org  Mon Jun 20 04:52:49 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 19 Jun 2011 23:52:49 -0500
Subject: [Slackbuilds-users] MD5SUM errors in "blas"
In-Reply-To: <4DDA7A32.5000505@hushmail.com>
References: <4DDA7A32.5000505@hushmail.com>
Message-ID: <20110619235249.69eeb239@liberty.rlwhome.lan>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 23 May 2011 11:16:02 -0400
Ric Foust <auto327094 at hushmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> The MD5SUM's provided by Slackbuilds differ from the MD5SUMS derived
> from the downloaded files.
> 
> #####################################
> 
> Slackbuilds: Blas
> 
> Source Downloads:
>     blas.tgz (7e6af7022440d8688d16be86d55fb358)
> 
> 
> Md5sum from downloaded source file:
> 5e99e975f7a1e3ea6abcad7c6e7e42e6  blas.tgz
> 
> #####################################


This should be fixed now.

- -RW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk3+0iIACgkQvGy9tf6lsvtBSgCeNH324vgclStgwbx5QKyJdbAn
DxwAoKnMKcbrJmxQRwcrxyDbM1Www6Rd
=RdEp
-----END PGP SIGNATURE-----

From pprkut at slackbuilds.org  Mon Jun 20 05:45:35 2011
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Mon, 20 Jun 2011 07:45:35 +0200
Subject: [Slackbuilds-users] wrong email adress in some of my scripts
In-Reply-To: <20110619234856.426dcf1d@liberty.rlwhome.lan>
References: <BANLkTikPyPW+YbVsAad0BisDLjBLY4j2-g@mail.gmail.com>
	<20110619234856.426dcf1d@liberty.rlwhome.lan>
Message-ID: <201106200745.44512.pprkut@slackbuilds.org>

On Monday 20 June 2011 06:48:56 Robby Workman wrote:
> On Sat, 11 Jun 2011 23:12:46 +0200
> 
> Niklas "Nille" ?kerstr?m <nille.kungen at gmail.com> wrote:
> > I looked at
> > http://slackbuilds.org/gitweb/?p=slackbuilds.git&a=search&h=HEAD&st=grep&
> > s=nilleand saw that some of my builds has the wrong email adress.
> > Could someone please update all to nille.kungen[AT]gmail.com
> 
> Send me a diff (one big diff will be fine) or a git pull
> request, please, and I'll apply it.

Oops, sorry, forgot to reply to this :)
It was already part of the last push and is hence fixed!

Grs,
Heinz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/06dffba1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/06dffba1/attachment.asc>

From rworkman at slackbuilds.org  Mon Jun 20 05:55:29 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 20 Jun 2011 00:55:29 -0500
Subject: [Slackbuilds-users] wrong email adress in some of my scripts
In-Reply-To: <201106200745.44512.pprkut@slackbuilds.org>
References: <BANLkTikPyPW+YbVsAad0BisDLjBLY4j2-g@mail.gmail.com>
	<20110619234856.426dcf1d@liberty.rlwhome.lan>
	<201106200745.44512.pprkut@slackbuilds.org>
Message-ID: <20110620005529.28c28ef4@liberty.rlwhome.lan>

On Mon, 20 Jun 2011 07:45:35 +0200
Heinz Wiesinger <pprkut at slackbuilds.org> wrote:

> On Monday 20 June 2011 06:48:56 Robby Workman wrote:
> > On Sat, 11 Jun 2011 23:12:46 +0200
> > 
> > Niklas "Nille" ?kerstr?m <nille.kungen at gmail.com> wrote:
> > > I looked at
> > > http://slackbuilds.org/gitweb/?p=slackbuilds.git&a=search&h=HEAD&st=grep&
> > > s=nilleand saw that some of my builds has the wrong email adress.
> > > Could someone please update all to nille.kungen[AT]gmail.com
> > 
> > Send me a diff (one big diff will be fine) or a git pull
> > request, please, and I'll apply it.
> 
> Oops, sorry, forgot to reply to this :)
> It was already part of the last push and is hence fixed!


Oh, cool, that makes it easy :-) 

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/5285da43/attachment.asc>

From kingbeowulf at gmail.com  Mon Jun 20 19:32:12 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 20 Jun 2011 12:32:12 -0700
Subject: [Slackbuilds-users] nvidia
In-Reply-To: <20110619235128.135c8bf9@liberty.rlwhome.lan>
References: <4DDD2C66.20905@gmail.com>
	<20110619235128.135c8bf9@liberty.rlwhome.lan>
Message-ID: <BANLkTikRUME2DV5Jc0OF5Yhuxggu9cRfpw@mail.gmail.com>

>
> I fixed what was likely a thinko in the nvidia-driver script.
> It wouldn't build at all on 32bit due to the multilib stuff.
> Have a look - it just got shoved out to public.
>
> -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/
>
>
> Wow....I shouldn't try fixing scripts in the middle of the night!  Thanks.
I could have sworn I fired up the 32-bit VM but maybe it was the 64-bit
one....

Anyway,  gotta go to Montana so I'll test it again soonest.

Also, Roberto caught a typo. Diff attached

-Ed


-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/2b89057d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nvidia-driver.SlackBuild.diff
Type: application/octet-stream
Size: 753 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/2b89057d/attachment.obj>

From audrius at neutrino.lt  Mon Jun 20 19:49:01 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Mon, 20 Jun 2011 22:49:01 +0300
Subject: [Slackbuilds-users] Updates - 20110620.1
In-Reply-To: <20110620044353.GA27584@slackbuilds.org>
References: <20110620044353.GA27584@slackbuilds.org>
Message-ID: <20110620194901.GA27356@kiras>

On Mon, 2011-06-20 at 04:43:56 +0000, Robby Workman wrote:
> libraries/virtualenv: Updated for version 1.6.1.

There's something wrong with this.  On the website it's in python
category, but files are missing.  In git repo it's in libraries.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/7f5d427e/attachment.asc>

From rworkman at slackbuilds.org  Mon Jun 20 20:04:39 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 20 Jun 2011 15:04:39 -0500
Subject: [Slackbuilds-users] Updates - 20110620.1
In-Reply-To: <20110620194901.GA27356@kiras>
References: <20110620044353.GA27584@slackbuilds.org>
	<20110620194901.GA27356@kiras>
Message-ID: <20110620150439.4f612d59@liberty.rlwhome.lan>

On Mon, 20 Jun 2011 22:49:01 +0300
Audrius Ka?ukauskas <audrius at neutrino.lt> wrote:

> On Mon, 2011-06-20 at 04:43:56 +0000, Robby Workman wrote:
> > libraries/virtualenv: Updated for version 1.6.1.
> 
> There's something wrong with this.  On the website it's in python
> category, but files are missing.  In git repo it's in libraries.


Is it supposed to be in python/ ?

I'm going to "fix" it by putting it back in libraries/ (wrt the
db), but if it should be in python, then I'll do that in the 
next update.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/8c8c8a28/attachment.asc>

From audrius at neutrino.lt  Mon Jun 20 20:10:21 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Mon, 20 Jun 2011 23:10:21 +0300
Subject: [Slackbuilds-users] Updates - 20110620.1
In-Reply-To: <20110620150439.4f612d59@liberty.rlwhome.lan>
References: <20110620044353.GA27584@slackbuilds.org>
	<20110620194901.GA27356@kiras>
	<20110620150439.4f612d59@liberty.rlwhome.lan>
Message-ID: <20110620201021.GA28396@kiras>

On Mon, 2011-06-20 at 15:04:39 -0500, Robby Workman wrote:
> Is it supposed to be in python/ ?

I've sent an email to Larry a couple of weeks ago suggesting to move
this to python/, and he agreed, so I guess that it should...

> I'm going to "fix" it by putting it back in libraries/ (wrt the
> db), but if it should be in python, then I'll do that in the 
> next update.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110620/c2977f39/attachment-0001.asc>

From kingbeowulf at gmail.com  Tue Jun 21 15:31:38 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 21 Jun 2011 08:31:38 -0700
Subject: [Slackbuilds-users]  nvidia-driver, nvidia-kernel
Message-ID: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>

Roberto brought to my attention that for both nvidia-driver and
nvidia-kernel scripts the default should be

SRCSUFFIX="nocompat32"

That way, pure x86-64 users don't have to download both tarballs! For
nvidia-kerrnel this is just better bookkeeping.

Sorry for the confusion. I have reprimanded the QC department.  *sound
of whip cracking*

Admins, please fix and let me know if you want me to send a diff, etc.

Ed

-- 
Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

From rworkman at slackbuilds.org  Tue Jun 21 15:36:59 2011
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 21 Jun 2011 10:36:59 -0500
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
Message-ID: <20110621103659.4094cbd6@liberty.rlwhome.lan>

On Tue, 21 Jun 2011 08:31:38 -0700
King Beowulf <kingbeowulf at gmail.com> wrote:

> Roberto brought to my attention that for both nvidia-driver and
> nvidia-kernel scripts the default should be
> 
> SRCSUFFIX="nocompat32"
> 
> That way, pure x86-64 users don't have to download both tarballs! For
> nvidia-kerrnel this is just better bookkeeping.
> 
> Sorry for the confusion. I have reprimanded the QC department.  *sound
> of whip cracking*
> 
> Admins, please fix and let me know if you want me to send a diff, etc.


Please do.  

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110621/9f6526ee/attachment.asc>

From info at microlinux.fr  Tue Jun 21 23:28:02 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Wed, 22 Jun 2011 01:28:02 +0200
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
Message-ID: <4E012902.2090707@microlinux.fr>

Le 21/06/2011 17:31, King Beowulf a ?crit :
> Roberto brought to my attention that for both nvidia-driver and
> nvidia-kernel scripts the default should be
>
> SRCSUFFIX="nocompat32"
>
> That way, pure x86-64 users don't have to download both tarballs! For
> nvidia-kerrnel this is just better bookkeeping.
>

I was indeed puzzled today, because I installed an Athlon machine with 
an NVidia Geforce 6500 card, and I saw that the nvidia-driver kernel 
downloaded two quite huge tarballs.

cheers,

Niki

From kingbeowulf at gmail.com  Wed Jun 22 00:59:32 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 21 Jun 2011 17:59:32 -0700
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <4E012902.2090707@microlinux.fr>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<4E012902.2090707@microlinux.fr>
Message-ID: <BANLkTim2MPMRRw_hSNv8unejNNcrk9nBQA@mail.gmail.com>

On Tue, Jun 21, 2011 at 4:28 PM, Nicolas Kovacs <info at microlinux.fr> wrote:

>
> I was indeed puzzled today, because I installed an Athlon machine with an
> NVidia Geforce 6500 card, and I saw that the nvidia-driver kernel downloaded
> two quite huge tarballs.
>
> cheers,
>
> Niki
> ______________________________**_________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.**org <SlackBuilds-users at slackbuilds.org>
> http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**users<http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> Archives - http://lists.slackbuilds.org/**pipermail/slackbuilds-users/<http://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> FAQ - http://slackbuilds.org/faq/
>
>
Niki,
Are you perhaps using an automated tool to grab Sbo scripts (e.g. sbopkg)?
If so, you will need to specify which tarballs you want.  I am not sure if
tyat can be encoded on slackbuilds.org.

For pure Slackware64, you need only download
NVIDIA-Linux-x86_64-xxx.yy.zz-no-compat32.run version and for multilib only
the NVIDIA-Linux-x86_64-xxx.yy.zz.run version.  I am fixing the default to
-no-compat32 but either one will work to get the nvidia kernal module for
either system.

-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110621/08706020/attachment.html>

From kingbeowulf at gmail.com  Wed Jun 22 01:13:29 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 21 Jun 2011 18:13:29 -0700
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <20110621103659.4094cbd6@liberty.rlwhome.lan>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
Message-ID: <BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>

On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman <rworkman at slackbuilds.org>wrote:

> On Tue, 21 Jun 2011 08:31:38 -0700
> King Beowulf <kingbeowulf at gmail.com> wrote:
>
> > Roberto brought to my attention that for both nvidia-driver and
> > nvidia-kernel scripts the default should be
> >
> > SRCSUFFIX="nocompat32"
> >
>
> Please do.
>
> -RW
>
>
nvidia-kernel.diff attached.  This should clear up some confusion.
Hopefully...

I sent in a spelling error diff for nvidia-driver yesterday.  Also,
275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
interest to the community, I will hop right on it when I get home from this
business trip.


-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110621/943ad1f9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nvidia-kernel.diff
Type: text/x-patch
Size: 1698 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110621/943ad1f9/attachment.bin>

From joshuakwood at gmail.com  Wed Jun 22 01:47:20 2011
From: joshuakwood at gmail.com (JK Wood)
Date: Tue, 21 Jun 2011 20:47:20 -0500
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
Message-ID: <BANLkTim8vYEpWhwz9XakbUsJ3CP4sN0pPA@mail.gmail.com>

On Tue, Jun 21, 2011 at 8:13 PM, King Beowulf <kingbeowulf at gmail.com> wrote:

>
>
> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman <rworkman at slackbuilds.org>wrote:
>
>> On Tue, 21 Jun 2011 08:31:38 -0700
>> King Beowulf <kingbeowulf at gmail.com> wrote:
>>
>> > Roberto brought to my attention that for both nvidia-driver and
>> > nvidia-kernel scripts the default should be
>> >
>> > SRCSUFFIX="nocompat32"
>> >
>>
>> Please do.
>>
>> -RW
>>
>>
> nvidia-kernel.diff attached.  This should clear up some confusion.
> Hopefully...
>
> I sent in a spelling error diff for nvidia-driver yesterday.  Also,
> 275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
> interest to the community, I will hop right on it when I get home from this
> business trip.
>
>
> --
> You! What PLANET is this!
>     -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
I've always been under the impression that you can install with either
tarball, it's just a difference of whether you install the compat32 stuff.
When I run the installer manually, it specifically asks if you want to
install it. Perhaps there's a command-line flag that can be passed? This
would simplify things considerably.

--JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110621/e5fb4bd7/attachment.html>

From artourter at gmail.com  Wed Jun 22 02:01:56 2011
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Wed, 22 Jun 2011 03:01:56 +0100
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
Message-ID: <BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>

Thanks for providing these packages.

However there is a problem when trying to compile the 64bit driver
with the 32bit compatibility on both -driver and -kernel, even with
the latest diff.

The code in the script goes:

SRCSUFFIX=${SRCSUFFIX:--no-compat32}
with the added note to set SRCSUFFIX="" in order to have the 32bit layer.

This doesn't actually work since setting $SRCSUFFIX to "" means that
the code above will consider the variable empty and therefore set it
to -no-compat32.

A possible fix is included in the attached diff (applies to
nvidia-driver but the same thing can be done for -kernel).

hope this helps

Cheers

ArTourter

On 22 June 2011 02:13, King Beowulf <kingbeowulf at gmail.com> wrote:
>
>
> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman <rworkman at slackbuilds.org>
> wrote:
>>
>> On Tue, 21 Jun 2011 08:31:38 -0700
>> King Beowulf <kingbeowulf at gmail.com> wrote:
>>
>> > Roberto brought to my attention that for both nvidia-driver and
>> > nvidia-kernel scripts the default should be
>> >
>> > SRCSUFFIX="nocompat32"
>> >
>>
>> Please do.
>>
>> -RW
>>
>
> nvidia-kernel.diff attached.? This should clear up some confusion.
> Hopefully...
>
> I sent in a spelling error diff for nvidia-driver yesterday.? Also,
> 275.09.07 is out with new GPU support and KDE4 fixes.? If this is of
> interest to the community, I will hop right on it when I get home from this
> business trip.
>
>
> --
> You! What PLANET is this!
> ? ? -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nvidia-driver.diff
Type: application/octet-stream
Size: 953 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110622/7b2896a8/attachment-0001.obj>

From kingbeowulf at gmail.com  Wed Jun 22 02:23:02 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 21 Jun 2011 19:23:02 -0700
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTim8vYEpWhwz9XakbUsJ3CP4sN0pPA@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
	<BANLkTim8vYEpWhwz9XakbUsJ3CP4sN0pPA@mail.gmail.com>
Message-ID: <BANLkTikzHSn6BX1j9LQ+p6ibrrk9yQsWng@mail.gmail.com>

I am curious as to why niki said both tarballs downloaded. Yes, for
Slack64 it doesn't matter which one you use for nvidia-kernel.
However, I put a switch in for nividia-driver to default to looking
for "-no-compat32" for the 64 bit purists. The default was the
opposite in nvidia-kernel and should have been the same (see readme).
That way you d/l just the one you want and not both.

What I might do, is just set up the script to require the full package
(64+32 bit) and a switch fo allow the choice during package creation.
That might be a lot simpler that having decide which one to download.

Ok thumbs tired on this blackberry. Back to chicken wings and beer...

-Ed



On 6/21/11, JK Wood <joshuakwood at gmail.com> wrote:
> On Tue, Jun 21, 2011 at 8:13 PM, King Beowulf <kingbeowulf at gmail.com> wrote:
>
>>
>>
>> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman
>> <rworkman at slackbuilds.org>wrote:
>>
>>> On Tue, 21 Jun 2011 08:31:38 -0700
>>> King Beowulf <kingbeowulf at gmail.com> wrote:
>>>
>>> > Roberto brought to my attention that for both nvidia-driver and
>>> > nvidia-kernel scripts the default should be
>>> >
>>> > SRCSUFFIX="nocompat32"
>>> >
>>>
>>> Please do.
>>>
>>> -RW
>>>
>>>
>> nvidia-kernel.diff attached.  This should clear up some confusion.
>> Hopefully...
>>
>> I sent in a spelling error diff for nvidia-driver yesterday.  Also,
>> 275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
>> interest to the community, I will hop right on it when I get home from
>> this
>> business trip.
>>
>>
>> --
>> You! What PLANET is this!
>>     -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>>
> I've always been under the impression that you can install with either
> tarball, it's just a difference of whether you install the compat32 stuff.
> When I run the installer manually, it specifically asks if you want to
> install it. Perhaps there's a command-line flag that can be passed? This
> would simplify things considerably.
>
> --JK
>

-- 
Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

From kingbeowulf at gmail.com  Wed Jun 22 02:34:16 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 21 Jun 2011 19:34:16 -0700
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
	<BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>
Message-ID: <BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>

Well just slap me for the noob I am. I really need to pay more
attention. I'm about a 900 miles away from my box and I forgot to open
ssh before I left.  It shouldn't be "" but " ". Anyway, a new nvidia
version is out and I will rejigger the script to get rid of
"no-compat32" download with a simpler selection scheme - ie yes/no
using the full nvidia package. Its just a few libs after all.

Anyway, thanks to all for pointing out the error my ways.

-Ed


On 6/21/11, Greg' Ar Tourter <artourter at gmail.com> wrote:
> Thanks for providing these packages.
>
> However there is a problem when trying to compile the 64bit driver
> with the 32bit compatibility on both -driver and -kernel, even with
> the latest diff.
>
> The code in the script goes:
>
> SRCSUFFIX=${SRCSUFFIX:--no-compat32}
> with the added note to set SRCSUFFIX="" in order to have the 32bit layer.
>
> This doesn't actually work since setting $SRCSUFFIX to "" means that
> the code above will consider the variable empty and therefore set it
> to -no-compat32.
>
> A possible fix is included in the attached diff (applies to
> nvidia-driver but the same thing can be done for -kernel).
>
> hope this helps
>
> Cheers
>
> ArTourter
>
> On 22 June 2011 02:13, King Beowulf <kingbeowulf at gmail.com> wrote:
>>
>>
>> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman <rworkman at slackbuilds.org>
>> wrote:
>>>
>>> On Tue, 21 Jun 2011 08:31:38 -0700
>>> King Beowulf <kingbeowulf at gmail.com> wrote:
>>>
>>> > Roberto brought to my attention that for both nvidia-driver and
>>> > nvidia-kernel scripts the default should be
>>> >
>>> > SRCSUFFIX="nocompat32"
>>> >
>>>
>>> Please do.
>>>
>>> -RW
>>>
>>
>> nvidia-kernel.diff attached.? This should clear up some confusion.
>> Hopefully...
>>
>> I sent in a spelling error diff for nvidia-driver yesterday.? Also,
>> 275.09.07 is out with new GPU support and KDE4 fixes.? If this is of
>> interest to the community, I will hop right on it when I get home from
>> this
>> business trip.
>>
>>
>> --
>> You! What PLANET is this!
>> ? ? -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>>
>

-- 
Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

From mpagnan at acanac.net  Wed Jun 22 02:53:37 2011
From: mpagnan at acanac.net (Martin Pagnan)
Date: Tue, 21 Jun 2011 22:53:37 -0400
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>	<20110621103659.4094cbd6@liberty.rlwhome.lan>	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>	<BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>
	<BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>
Message-ID: <4E015931.2060007@acanac.net>

Hi, I am a bit confused by this thread. I installed the nvidia drivers 
with the Linux installer available from the nvidia site over a year ago. 
As I recall, one just has to unpack the tar ball and run the script. It 
finds your card and kernel, asks for confirmation and proceeds to 
complete the installation for 64 bit or 32 bit - you chose. I have 
experienced no problems since installing it. So what has happened. Does 
nvidia no longer provide this utility? Why is a slackbuild needed?

On 21/06/2011 10:34 PM, King Beowulf wrote:
> Well just slap me for the noob I am. I really need to pay more
> attention. I'm about a 900 miles away from my box and I forgot to open
> ssh before I left.  It shouldn't be "" but " ". Anyway, a new nvidia
> version is out and I will rejigger the script to get rid of
> "no-compat32" download with a simpler selection scheme - ie yes/no
> using the full nvidia package. Its just a few libs after all.
>
> Anyway, thanks to all for pointing out the error my ways.
>
> -Ed
>
>
> On 6/21/11, Greg' Ar Tourter<artourter at gmail.com>  wrote:
>> Thanks for providing these packages.
>>
>> However there is a problem when trying to compile the 64bit driver
>> with the 32bit compatibility on both -driver and -kernel, even with
>> the latest diff.
>>
>> The code in the script goes:
>>
>> SRCSUFFIX=${SRCSUFFIX:--no-compat32}
>> with the added note to set SRCSUFFIX="" in order to have the 32bit layer.
>>
>> This doesn't actually work since setting $SRCSUFFIX to "" means that
>> the code above will consider the variable empty and therefore set it
>> to -no-compat32.
>>
>> A possible fix is included in the attached diff (applies to
>> nvidia-driver but the same thing can be done for -kernel).
>>
>> hope this helps
>>
>> Cheers
>>
>> ArTourter
>>
>> On 22 June 2011 02:13, King Beowulf<kingbeowulf at gmail.com>  wrote:
>>>
>>> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman<rworkman at slackbuilds.org>
>>> wrote:
>>>> On Tue, 21 Jun 2011 08:31:38 -0700
>>>> King Beowulf<kingbeowulf at gmail.com>  wrote:
>>>>
>>>>> Roberto brought to my attention that for both nvidia-driver and
>>>>> nvidia-kernel scripts the default should be
>>>>>
>>>>> SRCSUFFIX="nocompat32"
>>>>>
>>>> Please do.
>>>>
>>>> -RW
>>>>
>>> nvidia-kernel.diff attached.  This should clear up some confusion.
>>> Hopefully...
>>>
>>> I sent in a spelling error diff for nvidia-driver yesterday.  Also,
>>> 275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
>>> interest to the community, I will hop right on it when I get home from
>>> this
>>> business trip.
>>>
>>>
>>> --
>>> You! What PLANET is this!
>>>      -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>>>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - http://slackbuilds.org/faq/
>>>
>>>
>>>

From kingbeowulf at gmail.com  Wed Jun 22 03:12:35 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 21 Jun 2011 20:12:35 -0700
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <4E015931.2060007@acanac.net>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
	<BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>
	<BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>
	<4E015931.2060007@acanac.net>
Message-ID: <BANLkTin0Aav+Vuv=Gzdo2ispFkkxEyDPtA@mail.gmail.com>

Martin,
The Sbo slackbuild scripts builds a standard slackware package. I used
the nvidia*.run as well for ages. But it does dump files all over the
place that the pkgtool doesn't know about. What happens when you
update mesa, xorg etc? With the packages, you can revert, update,
install a bit easier without recompling (assuming constant kernel).

Its a matter of personal preference, ultimately.

Or, its the Slackware way, or the highway!!

-Ed


On 6/21/11, Martin Pagnan <mpagnan at acanac.net> wrote:
> Hi, I am a bit confused by this thread. I installed the nvidia drivers
> with the Linux installer available from the nvidia site over a year ago.
> As I recall, one just has to unpack the tar ball and run the script. It
> finds your card and kernel, asks for confirmation and proceeds to
> complete the installation for 64 bit or 32 bit - you chose. I have
> experienced no problems since installing it. So what has happened. Does
> nvidia no longer provide this utility? Why is a slackbuild needed?
>
> On 21/06/2011 10:34 PM, King Beowulf wrote:
>> Well just slap me for the noob I am. I really need to pay more
>> attention. I'm about a 900 miles away from my box and I forgot to open
>> ssh before I left.  It shouldn't be "" but " ". Anyway, a new nvidia
>> version is out and I will rejigger the script to get rid of
>> "no-compat32" download with a simpler selection scheme - ie yes/no
>> using the full nvidia package. Its just a few libs after all.
>>
>> Anyway, thanks to all for pointing out the error my ways.
>>
>> -Ed
>>
>>
>> On 6/21/11, Greg' Ar Tourter<artourter at gmail.com>  wrote:
>>> Thanks for providing these packages.
>>>
>>> However there is a problem when trying to compile the 64bit driver
>>> with the 32bit compatibility on both -driver and -kernel, even with
>>> the latest diff.
>>>
>>> The code in the script goes:
>>>
>>> SRCSUFFIX=${SRCSUFFIX:--no-compat32}
>>> with the added note to set SRCSUFFIX="" in order to have the 32bit layer.
>>>
>>> This doesn't actually work since setting $SRCSUFFIX to "" means that
>>> the code above will consider the variable empty and therefore set it
>>> to -no-compat32.
>>>
>>> A possible fix is included in the attached diff (applies to
>>> nvidia-driver but the same thing can be done for -kernel).
>>>
>>> hope this helps
>>>
>>> Cheers
>>>
>>> ArTourter
>>>
>>> On 22 June 2011 02:13, King Beowulf<kingbeowulf at gmail.com>  wrote:
>>>>
>>>> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman<rworkman at slackbuilds.org>
>>>> wrote:
>>>>> On Tue, 21 Jun 2011 08:31:38 -0700
>>>>> King Beowulf<kingbeowulf at gmail.com>  wrote:
>>>>>
>>>>>> Roberto brought to my attention that for both nvidia-driver and
>>>>>> nvidia-kernel scripts the default should be
>>>>>>
>>>>>> SRCSUFFIX="nocompat32"
>>>>>>
>>>>> Please do.
>>>>>
>>>>> -RW
>>>>>
>>>> nvidia-kernel.diff attached.  This should clear up some confusion.
>>>> Hopefully...
>>>>
>>>> I sent in a spelling error diff for nvidia-driver yesterday.  Also,
>>>> 275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
>>>> interest to the community, I will hop right on it when I get home from
>>>> this
>>>> business trip.
>>>>
>>>>
>>>> --
>>>> You! What PLANET is this!
>>>>      -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>>>>
>>>>
>>>> _______________________________________________
>>>> SlackBuilds-users mailing list
>>>> SlackBuilds-users at slackbuilds.org
>>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>> FAQ - http://slackbuilds.org/faq/
>>>>
>>>>
>>>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>

-- 
Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

From mpagnan at acanac.net  Wed Jun 22 12:51:23 2011
From: mpagnan at acanac.net (Martin Pagnan)
Date: Wed, 22 Jun 2011 08:51:23 -0400
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTin0Aav+Vuv=Gzdo2ispFkkxEyDPtA@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>	<20110621103659.4094cbd6@liberty.rlwhome.lan>	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>	<BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>	<BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>	<4E015931.2060007@acanac.net>
	<BANLkTin0Aav+Vuv=Gzdo2ispFkkxEyDPtA@mail.gmail.com>
Message-ID: <4E01E54B.3040604@acanac.net>

Thanks. Good point. But, now that I have been warned, what are these 
garbage files that I must have on my system? Do you remember? Thanks.

On 21/06/2011 11:12 PM, King Beowulf wrote:
> Martin,
> The Sbo slackbuild scripts builds a standard slackware package. I used
> the nvidia*.run as well for ages. But it does dump files all over the
> place that the pkgtool doesn't know about. What happens when you
> update mesa, xorg etc? With the packages, you can revert, update,
> install a bit easier without recompling (assuming constant kernel).
>
> Its a matter of personal preference, ultimately.
>
> Or, its the Slackware way, or the highway!!
>
> -Ed
>
>
> On 6/21/11, Martin Pagnan<mpagnan at acanac.net>  wrote:
>> Hi, I am a bit confused by this thread. I installed the nvidia drivers
>> with the Linux installer available from the nvidia site over a year ago.
>> As I recall, one just has to unpack the tar ball and run the script. It
>> finds your card and kernel, asks for confirmation and proceeds to
>> complete the installation for 64 bit or 32 bit - you chose. I have
>> experienced no problems since installing it. So what has happened. Does
>> nvidia no longer provide this utility? Why is a slackbuild needed?
>>
>> On 21/06/2011 10:34 PM, King Beowulf wrote:
>>> Well just slap me for the noob I am. I really need to pay more
>>> attention. I'm about a 900 miles away from my box and I forgot to open
>>> ssh before I left.  It shouldn't be "" but " ". Anyway, a new nvidia
>>> version is out and I will rejigger the script to get rid of
>>> "no-compat32" download with a simpler selection scheme - ie yes/no
>>> using the full nvidia package. Its just a few libs after all.
>>>
>>> Anyway, thanks to all for pointing out the error my ways.
>>>
>>> -Ed
>>>
>>>
>>> On 6/21/11, Greg' Ar Tourter<artourter at gmail.com>   wrote:
>>>> Thanks for providing these packages.
>>>>
>>>> However there is a problem when trying to compile the 64bit driver
>>>> with the 32bit compatibility on both -driver and -kernel, even with
>>>> the latest diff.
>>>>
>>>> The code in the script goes:
>>>>
>>>> SRCSUFFIX=${SRCSUFFIX:--no-compat32}
>>>> with the added note to set SRCSUFFIX="" in order to have the 32bit layer.
>>>>
>>>> This doesn't actually work since setting $SRCSUFFIX to "" means that
>>>> the code above will consider the variable empty and therefore set it
>>>> to -no-compat32.
>>>>
>>>> A possible fix is included in the attached diff (applies to
>>>> nvidia-driver but the same thing can be done for -kernel).
>>>>
>>>> hope this helps
>>>>
>>>> Cheers
>>>>
>>>> ArTourter
>>>>
>>>> On 22 June 2011 02:13, King Beowulf<kingbeowulf at gmail.com>   wrote:
>>>>> On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman<rworkman at slackbuilds.org>
>>>>> wrote:
>>>>>> On Tue, 21 Jun 2011 08:31:38 -0700
>>>>>> King Beowulf<kingbeowulf at gmail.com>   wrote:
>>>>>>
>>>>>>> Roberto brought to my attention that for both nvidia-driver and
>>>>>>> nvidia-kernel scripts the default should be
>>>>>>>
>>>>>>> SRCSUFFIX="nocompat32"
>>>>>>>
>>>>>> Please do.
>>>>>>
>>>>>> -RW
>>>>>>
>>>>> nvidia-kernel.diff attached.  This should clear up some confusion.
>>>>> Hopefully...
>>>>>
>>>>> I sent in a spelling error diff for nvidia-driver yesterday.  Also,
>>>>> 275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
>>>>> interest to the community, I will hop right on it when I get home from
>>>>> this
>>>>> business trip.
>>>>>
>>>>>
>>>>> --
>>>>> You! What PLANET is this!
>>>>>       -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> SlackBuilds-users mailing list
>>>>> SlackBuilds-users at slackbuilds.org
>>>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>>> FAQ - http://slackbuilds.org/faq/
>>>>>
>>>>>
>>>>>
>> _______________________________________________
>> 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 erik at slackbuilds.org  Wed Jun 22 13:06:37 2011
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 22 Jun 2011 08:06:37 -0500
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <4E01E54B.3040604@acanac.net>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
	<BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>
	<BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>
	<4E015931.2060007@acanac.net>
	<BANLkTin0Aav+Vuv=Gzdo2ispFkkxEyDPtA@mail.gmail.com>
	<4E01E54B.3040604@acanac.net>
Message-ID: <20110622080637.549ef077@shaggy.doo>

On Wed, 22 Jun 2011 08:51:23 -0400
Martin Pagnan <mpagnan at acanac.net> wrote:

> Thanks. Good point. But, now that I have been warned, what are these 
> garbage files that I must have on my system? Do you remember? Thanks.

Nothing that can't be cleaned up with ./NVIDIA-... --uninstall


-- 
Erik Hanson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110622/f05188bc/attachment-0001.asc>

From info at microlinux.fr  Wed Jun 22 13:25:45 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Wed, 22 Jun 2011 15:25:45 +0200
Subject: [Slackbuilds-users] libmpcdec is missing
Message-ID: <4E01ED59.5090109@microlinux.fr>

Hi,

 From the 'mpc123' page

mpc123 (console Musepack audio player)

mpc123 is your handy Musepack audio player!
It uses libmpcdec to decode Musepack streams and its features are:
* plain file playing - that's easy ;)
* playlists
* random, shuffle
* output to file (wav, cdr, au)
* and more...

Requires libmpcdec available at SlackBuilds.org

But libmpcdec is nowhere to be found.

Cheers,

Niki

From niels.horn at gmail.com  Wed Jun 22 13:41:23 2011
From: niels.horn at gmail.com (Niels Horn)
Date: Wed, 22 Jun 2011 10:41:23 -0300
Subject: [Slackbuilds-users] libmpcdec is missing
In-Reply-To: <4E01ED59.5090109@microlinux.fr>
References: <4E01ED59.5090109@microlinux.fr>
Message-ID: <BANLkTikpPpgYYm4gnqaNh+emOFGVUKTxqQ@mail.gmail.com>

On Wed, Jun 22, 2011 at 10:25 AM, Nicolas Kovacs <info at microlinux.fr> wrote:
> Hi,
>
> From the 'mpc123' page
>
> mpc123 (console Musepack audio player)
>
> mpc123 is your handy Musepack audio player!
> It uses libmpcdec to decode Musepack streams and its features are:
> * plain file playing - that's easy ;)
> * playlists
> * random, shuffle
> * output to file (wav, cdr, au)
> * and more...
>
> Requires libmpcdec available at SlackBuilds.org
>
> But libmpcdec is nowhere to be found.
>
> Cheers,
>
> Niki

It was removed as "unmaintained" with the change to 13.37.

--
Niels Horn

From kingbeowulf at gmail.com  Wed Jun 22 19:06:38 2011
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 22 Jun 2011 12:06:38 -0700
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <20110622080637.549ef077@shaggy.doo>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110621103659.4094cbd6@liberty.rlwhome.lan>
	<BANLkTik7dYBZ6KNECAd+u+JdLcP90PcrkQ@mail.gmail.com>
	<BANLkTi=R-SBtunNFn5EWCMSMf0ecZ40o1Q@mail.gmail.com>
	<BANLkTimGotPGVsmVBrkRwk9cKRj2xQ7EPA@mail.gmail.com>
	<4E015931.2060007@acanac.net>
	<BANLkTin0Aav+Vuv=Gzdo2ispFkkxEyDPtA@mail.gmail.com>
	<4E01E54B.3040604@acanac.net> <20110622080637.549ef077@shaggy.doo>
Message-ID: <BANLkTinnY6zt2CMZJVSD=9+QVjO5LxMYiA@mail.gmail.com>

Not entirely true..if you upgraded xorg/mesa etc before uninstalling.

On 6/22/11, Erik Hanson <erik at slackbuilds.org> wrote:
> On Wed, 22 Jun 2011 08:51:23 -0400
> Martin Pagnan <mpagnan at acanac.net> wrote:
>
>> Thanks. Good point. But, now that I have been warned, what are these
>> garbage files that I must have on my system? Do you remember? Thanks.
>
> Nothing that can't be cleaned up with ./NVIDIA-... --uninstall
>
>
> --
> Erik Hanson
>

-- 
Sent from my mobile device

You! What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

From yalhcru at gmail.com  Wed Jun 22 21:54:22 2011
From: yalhcru at gmail.com (B Watson)
Date: Wed, 22 Jun 2011 17:54:22 -0400
Subject: [Slackbuilds-users] Fwd: xsel slackbuild
In-Reply-To: <BANLkTik7rtoGEVpNDN4PjMg5XZ+RUp_Rjg@mail.gmail.com>
References: <BANLkTi=9vbEdK_iDsXwN=maEamwuQqpPpw@mail.gmail.com>
	<BANLkTik7rtoGEVpNDN4PjMg5XZ+RUp_Rjg@mail.gmail.com>
Message-ID: <BANLkTinjL=7ZpNRDAEcq83sQ6F34YfW=aA@mail.gmail.com>

Taking over xsel, which got dropped in the move from 12.2 to 13.0:

---------- Forwarded message ----------
From: Thiago Coutinho <thiagocoutinho1 at gmail.com>
Date: Wed, 22 Jun 2011 16:01:52 -0300
Subject: Re: xsel slackbuild
To: B Watson <yalhcru at gmail.com>

Hi.

On Thu, Jun 9, 2011 at 7:23 PM, B Watson <yalhcru at gmail.com> wrote:
> Do you ever plan to re-upload your build for 13.37? If not, I'd like to
> submit it myself (with me as maintainer, if you're not interested). I've
> got some old scripts here that use xsel, so I actually do use it.

I switch to Archlinux some time ago, feel free to update it.

From kev at pulo.com.au  Thu Jun 23 01:32:11 2011
From: kev at pulo.com.au (Kevin Pulo)
Date: Thu, 23 Jun 2011 11:32:11 +1000
Subject: [Slackbuilds-users] SBo rss feed broken
Message-ID: <20110623013210.GW30964@pulo.com.au>

The RSS feed on the Slackbuilds website is currently broken.  There are
date-related php warnings being emitted at various points, resulting in invalid
xml.

$ wget -q -O - http://slackbuilds.org/rss/ChangeLog.rss | head -10

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /rss/slackbuilds.php on line 3
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>SlackBuilds.org</title>
  <description>SlackBuilds ChangeLog</description>
  <link>http://www.slackbuilds.org/</link>
  <atom:link href="http://slackbuilds.org/rss/ChangeLog.rss" rel="self" type="application/rss+xml" />
  <language>en-us</language>
$ wget -q -O - http://slackbuilds.org/rss/ChangeLog.rss | grep Warning | sort | uniq
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /rss/slackbuilds.php on line 3
Warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /rss/slackbuilds.php on line 57
$ 

Kev

-- 
Kevin Pulo
kev at pulo.com.au
http://www.kev.pulo.com.au/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110623/ab41402b/attachment.asc>

From unix_lists at airpost.net  Thu Jun 23 00:23:34 2011
From: unix_lists at airpost.net (unix_lists at airpost.net)
Date: Wed, 22 Jun 2011 19:23:34 -0500
Subject: [Slackbuilds-users] Help on creating my own local slackbuild repo
	at home
Message-ID: <4E028786.7020700@airpost.net>

I would like to have my own local version of slackbuilds on my own 
computer. I want this because I often make changes to the scripts. I 
would like to have control over how an update from slackbuilds site is 
merged with my own home repo.
I have little experience with git or other version control systems. How 
are some of you implementing this yourselves?
-- 
Regards,
2>&1

From unix_lists at airpost.net  Wed Jun 22 20:35:27 2011
From: unix_lists at airpost.net (2>&1)
Date: Wed, 22 Jun 2011 15:35:27 -0500
Subject: [Slackbuilds-users] Help on creating my own local slackbuild repo
	at home
Message-ID: <4E02520F.20600@airpost.net>

I would like to have my own local version of slackbuilds on my own 
computer. I want this because I often make changes to the scripts. I 
would like to have control over how an update from slackbuilds site is 
merged with my own home repo.
I have little experience with git or other version control systems. How 
are some of you implementing this yourselves?
-- 
Regards,
2>&1

From eugen at flevum.de  Thu Jun 23 03:34:27 2011
From: eugen at flevum.de (Eugen Wissner)
Date: Thu, 23 Jun 2011 05:34:27 +0200
Subject: [Slackbuilds-users] Help on creating my own local slackbuild
 repo at home
In-Reply-To: <4E028786.7020700@airpost.net>
References: <4E028786.7020700@airpost.net>
Message-ID: <BANLkTinJj23_7zMMBKwKHOvi=Q+yHX5thg@mail.gmail.com>

I use rsync.

2011/6/23 <unix_lists at airpost.net>

> I would like to have my own local version of slackbuilds on my own
> computer. I want this because I often make changes to the scripts. I would
> like to have control over how an update from slackbuilds site is merged with
> my own home repo.
> I have little experience with git or other version control systems. How are
> some of you implementing this yourselves?
> --
> Regards,
> 2>&1
> ______________________________**_________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.**org <SlackBuilds-users at slackbuilds.org>
> http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**users<http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> Archives - http://lists.slackbuilds.org/**pipermail/slackbuilds-users/<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/20110623/f04eff57/attachment.html>

From mfilpot at gmail.com  Thu Jun 23 03:40:20 2011
From: mfilpot at gmail.com (Matthew Fillpot)
Date: Wed, 22 Jun 2011 23:40:20 -0400
Subject: [Slackbuilds-users] Help on creating my own local slackbuild
 repo at home
In-Reply-To: <BANLkTinJj23_7zMMBKwKHOvi=Q+yHX5thg@mail.gmail.com>
References: <4E028786.7020700@airpost.net>
	<BANLkTinJj23_7zMMBKwKHOvi=Q+yHX5thg@mail.gmail.com>
Message-ID: <BANLkTi=m26eE94hqdZcBCQJeTL=sasZi5A@mail.gmail.com>

You can use git.

Run "git clone git://slackbuilds.org/slackbuilds" to clone the
original repo, then to get updates you can go into the resulting
slackbuilds directory and issue the command "git pull".  you can
change the local files are you wish and if you want to review the
differences you can issue the command "git diff".

But to retain your modified copies it would be advisable to keep them
in an alternate location.

On Wed, Jun 22, 2011 at 11:34 PM, Eugen Wissner <eugen at flevum.de> wrote:
> I use rsync.
>
> 2011/6/23 <unix_lists at airpost.net>
>>
>> I would like to have my own local version of slackbuilds on my own
>> computer. I want this because I often make changes to the scripts. I would
>> like to have control over how an update from slackbuilds site is merged with
>> my own home repo.
>> I have little experience with git or other version control systems. How
>> are some of you implementing this yourselves?
>> --
>> Regards,
>> 2>&1
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>



-- 
-Thank You,
-Matthew Fillpot

-Join us this year in celebrating the 20th Anniversary of Linux!
Watch the "Story of Linux" here:
http://www.youtube.com/watch?v=5ocq6_3-nEw

From pprkut at liwjatan.at  Thu Jun 23 05:44:13 2011
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Thu, 23 Jun 2011 07:44:13 +0200
Subject: [Slackbuilds-users] nvidia-driver, nvidia-kernel
In-Reply-To: <BANLkTinnY6zt2CMZJVSD=9+QVjO5LxMYiA@mail.gmail.com>
References: <BANLkTikGnFbQcqa8B12=sb8rE=-YU+vs2A@mail.gmail.com>
	<20110622080637.549ef077@shaggy.doo>
	<BANLkTinnY6zt2CMZJVSD=9+QVjO5LxMYiA@mail.gmail.com>
Message-ID: <201106230744.19997.pprkut@liwjatan.at>

On Wednesday 22 June 2011 21:06:38 King Beowulf wrote:
> Not entirely true..if you upgraded xorg/mesa etc before uninstalling.
> 
> On 6/22/11, Erik Hanson <erik at slackbuilds.org> wrote:
> > On Wed, 22 Jun 2011 08:51:23 -0400
> > 
> > Martin Pagnan <mpagnan at acanac.net> wrote:
> >> Thanks. Good point. But, now that I have been warned, what are these
> >> garbage files that I must have on my system? Do you remember? Thanks.
> > 
> > Nothing that can't be cleaned up with ./NVIDIA-... --uninstall
> > 

You can also mess up your system with nvidia-switch, if you want to. Cleanness 
is the wrong reason for the SlackBuilds.

My original idea behind the SlackBuilds was to have an already known 
installation procedure for the nvidia drivers, rather than having to learn 
another different one. Yes, you can largely achieve the same with both, but 
have to know which parameters of nvidia-installer to use and when. Not saying 
that's difficult either, it's just a convenience thing.
Another reason for the SlackBuilds would be that they give you slightly more 
than the .run installer, since nvidia-settings, nvidia-xconfig, etc are built 
from source. Again this adds no functionality compared to the .run installer, 
it's an ideology thing.

In the end, if you are using the SlackBuilds or the .run installer to install 
nvidia's drivers is up to your personal preferences and those only. There's no 
better and no worse among them, just a slightly different.

Grs,
Heinz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110623/df95cc28/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110623/df95cc28/attachment.asc>

From info at microlinux.fr  Thu Jun 23 06:15:38 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Thu, 23 Jun 2011 08:15:38 +0200
Subject: [Slackbuilds-users] Help on creating my own local slackbuild
 repo	at home
In-Reply-To: <4E028786.7020700@airpost.net>
References: <4E028786.7020700@airpost.net>
Message-ID: <4E02DA0A.6070505@microlinux.fr>

Le 23/06/2011 02:23, unix_lists at airpost.net a ?crit :
> I would like to have my own local version of slackbuilds on my own
> computer. I want this because I often make changes to the scripts. I
> would like to have control over how an update from slackbuilds site is
> merged with my own home repo.
> I have little experience with git or other version control systems. How
> are some of you implementing this yourselves?

SVN is a great tool, and quite simple. The documentation is very clear. 
There's a local copy of the SVN book in your Slackware box.

If you can't setup your own SVN server, you can have a free account at 
http://www.tuxfamily.org, a great site devoted to hosting free projects. 
The FAQ contains step by step information about setting up the SVN repo.

Cheers,

Niki

From ozan.turkyilmaz at gmail.com  Thu Jun 23 06:53:05 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Thu, 23 Jun 2011 11:53:05 +0500
Subject: [Slackbuilds-users] Help on creating my own local slackbuild
 repo at home
In-Reply-To: <4E02DA0A.6070505@microlinux.fr>
References: <4E028786.7020700@airpost.net>
	<4E02DA0A.6070505@microlinux.fr>
Message-ID: <BANLkTin5Q=8q5ZLF1dv3DDQrUxmi_ysrXg@mail.gmail.com>

2011/6/23 Nicolas Kovacs <info at microlinux.fr>:
> Le 23/06/2011 02:23, unix_lists at airpost.net a ?crit :
>>
>> I would like to have my own local version of slackbuilds on my own
>> computer. I want this because I often make changes to the scripts. I
>> would like to have control over how an update from slackbuilds site is
>> merged with my own home repo.
>> I have little experience with git or other version control systems. How
>> are some of you implementing this yourselves?
>
> SVN is a great tool, and quite simple. The documentation is very clear.
> There's a local copy of the SVN book in your Slackware box.
>
> If you can't setup your own SVN server, you can have a free account at
> http://www.tuxfamily.org, a great site devoted to hosting free projects. The
> FAQ contains step by step information about setting up the SVN repo.
>

With git, You have zero needs for all this.

I have my own local repo as well. I added to sbopkg as well. I can get
updates from Offical Repo and still keep my own changes.



-- 
Ozan, BSc, BEng

From mpagnan at acanac.net  Thu Jun 23 12:19:55 2011
From: mpagnan at acanac.net (Martin Pagnan)
Date: Thu, 23 Jun 2011 08:19:55 -0400
Subject: [Slackbuilds-users] Help on creating my own local slackbuild
 repo at home
In-Reply-To: <BANLkTinJj23_7zMMBKwKHOvi=Q+yHX5thg@mail.gmail.com>
References: <4E028786.7020700@airpost.net>
	<BANLkTinJj23_7zMMBKwKHOvi=Q+yHX5thg@mail.gmail.com>
Message-ID: <4E032F6B.8040707@acanac.net>

Speaking of rsync. Does anyone know how to set up iosync on Slack? Other 
distributions seem to include it as a kernel module but Slack does not, 
as far as I can tell. Whereas rsync runs on demand or as a chron job, 
iosync monitors disk changes and sync them to a backup disk. Does anyone 
know about this?

On 22/06/2011 11:34 PM, Eugen Wissner wrote:
> I use rsync.
>
> 2011/6/23 <unix_lists at airpost.net <mailto:unix_lists at airpost.net>>
>
>     I would like to have my own local version of slackbuilds on my own
>     computer. I want this because I often make changes to the scripts.
>     I would like to have control over how an update from slackbuilds
>     site is merged with my own home repo.
>     I have little experience with git or other version control
>     systems. How are some of you implementing this yourselves?
>     -- 
>     Regards,
>     2>&1
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     FAQ - http://slackbuilds.org/faq/
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110623/0be69d45/attachment.html>

From erik at slackbuilds.org  Thu Jun 23 19:57:45 2011
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 23 Jun 2011 14:57:45 -0500
Subject: [Slackbuilds-users] SBo rss feed broken
In-Reply-To: <20110623013210.GW30964@pulo.com.au>
References: <20110623013210.GW30964@pulo.com.au>
Message-ID: <20110623145745.282bceaa@shaggy.doo>

On Thu, 23 Jun 2011 11:32:11 +1000
Kevin Pulo <kev at pulo.com.au> wrote:

> The RSS feed on the Slackbuilds website is currently broken.  There
> are date-related php warnings being emitted at various points,
> resulting in invalid xml.

It should be fine now, thanks.

-- 
Erik Hanson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110623/b045673b/attachment.asc>

From smieciarski at hotmail.com  Thu Jun 23 18:34:19 2011
From: smieciarski at hotmail.com (Foo Bar)
Date: Thu, 23 Jun 2011 20:34:19 +0200
Subject: [Slackbuilds-users] Broken link to libtorrent SlackBuild archive
Message-ID: <BAY146-w121C06489CADDF167CFD7FB5530@phx.gbl>



Hi,There is a broken link to libtorrent 0.12.8 SlackBuild archive in repository.
 		 	   		  

From erik at slackbuilds.org  Fri Jun 24 00:37:36 2011
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 23 Jun 2011 19:37:36 -0500
Subject: [Slackbuilds-users] Broken link to libtorrent SlackBuild archive
In-Reply-To: <BAY146-w121C06489CADDF167CFD7FB5530@phx.gbl>
References: <BAY146-w121C06489CADDF167CFD7FB5530@phx.gbl>
Message-ID: <20110623193736.20f48eed@shaggy.doo>

On Thu, 23 Jun 2011 20:34:19 +0200
Foo Bar <smieciarski at hotmail.com> wrote:

> Hi,There is a broken link to libtorrent 0.12.8 SlackBuild archive in
> repository. 

http://slackbuilds.org/repository/13.37/libraries/libtorrent/

Fixed now, thanks


-- 
Erik Hanson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110623/6c8cd394/attachment-0001.asc>

From chaos.proton at gmail.com  Fri Jun 24 00:44:05 2011
From: chaos.proton at gmail.com (Grissiom)
Date: Fri, 24 Jun 2011 08:44:05 +0800
Subject: [Slackbuilds-users] fix Jinja2 typo
Message-ID: <BANLkTinWHscQ4oDeZ7dYE0_OgGAvybkikQ@mail.gmail.com>

This typo makes Jianja2 leave junk /usr/doc/-2.5.5 which does not make
sense to users.

Here is the patch
=================================
diff --git a/libraries/Jinja2/Jinja2.SlackBuild
b/libraries/Jinja2/Jinja2.SlackBuild
index 0a96b9d..b20307e 100644
--- a/libraries/Jinja2/Jinja2.SlackBuild
+++ b/libraries/Jinja2/Jinja2.SlackBuild
@@ -5,9 +5,9 @@
 # Written by Mikko V?rri (vmj at linuxbox.fi)
 # Public domain.

-PRGNAM=Jinja2
+PKGNAM=Jinja2
 VERSION=${VERSION:-2.5.5}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}

 if [ -z "$ARCH" ]; then
@@ -20,7 +20,7 @@ fi

 CWD=$(pwd)
 TMP=${TMP:-/tmp/SBo}
-PKG=$TMP/package-$PRGNAM
+PKG=$TMP/package-$PKGNAM
 OUTPUT=${OUTPUT:-/tmp}

 DOCS=${DOCS:-no}
@@ -30,9 +30,9 @@ set -e
 rm -rf $PKG
 mkdir -p $TMP $PKG $OUTPUT
 cd $TMP
-rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
-cd $PRGNAM-$VERSION
+rm -rf $PKGNAM-$VERSION
+tar xvf $CWD/$PKGNAM-$VERSION.tar.gz
+cd $PKGNAM-$VERSION
 chown -R root:root .
 find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
@@ -49,13 +49,13 @@ fi
 find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

-mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a AUTHORS CHANGES LICENSE ext examples $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs
$PKG/usr/doc/$PKGNAM-$VERSION
-cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
+mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
+cp -a AUTHORS CHANGES LICENSE ext examples $PKG/usr/doc/$PKGNAM-$VERSION
+cp -a docs/_build/html $PKG/usr/doc/$PKGNAM-$VERSION || cp -a docs
$PKG/usr/doc/$PKGNAM-$VERSION
+cat $CWD/$PKGNAM.SlackBuild > $PKG/usr/doc/$PKGNAM-$VERSION/$PKGNAM.SlackBuild

 mkdir -p $PKG/install
 cat $CWD/slack-desc > $PKG/install/slack-desc

 cd $PKG
-/sbin/makepkg -l y -c n
$OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
+/sbin/makepkg -l y -c n
$OUTPUT/$PKGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
===========================

-- 
Cheers,
Grissiom

From vmj at linuxbox.fi  Fri Jun 24 09:08:32 2011
From: vmj at linuxbox.fi (Mikko Varri)
Date: Fri, 24 Jun 2011 12:08:32 +0300
Subject: [Slackbuilds-users] fix Jinja2 typo
In-Reply-To: <BANLkTinWHscQ4oDeZ7dYE0_OgGAvybkikQ@mail.gmail.com>
References: <BANLkTinWHscQ4oDeZ7dYE0_OgGAvybkikQ@mail.gmail.com>
Message-ID: <20110624090832.GD30584@linuxbox.fi>

Thanks for pointing that out.

Am I missing something?  Instead of changing PRGNAM to PKGNAM
everywhere, a smaller patch would change one instance of PGKNAM to
PRGNAM.

-cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs $PKG/usr/doc/$PKGNAM-$VERSION
+cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs $PKG/usr/doc/$PRGNAM-$VERSION

PRGNAM is the right variable name for it, right?

Could one of the admins make that change?



On Fri, Jun 24, 2011 at 08:44:05AM +0800, Grissiom wrote:
> diff --git a/libraries/Jinja2/Jinja2.SlackBuild
> b/libraries/Jinja2/Jinja2.SlackBuild
> index 0a96b9d..b20307e 100644
> --- a/libraries/Jinja2/Jinja2.SlackBuild
> +++ b/libraries/Jinja2/Jinja2.SlackBuild
> @@ -49,13 +49,13 @@ fi
>  find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
> 
> -mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> -cp -a AUTHORS CHANGES LICENSE ext examples $PKG/usr/doc/$PRGNAM-$VERSION
> -cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
> +mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
> +cp -a AUTHORS CHANGES LICENSE ext examples $PKG/usr/doc/$PKGNAM-$VERSION
> +cp -a docs/_build/html $PKG/usr/doc/$PKGNAM-$VERSION || cp -a docs
> $PKG/usr/doc/$PKGNAM-$VERSION
> +cat $CWD/$PKGNAM.SlackBuild > $PKG/usr/doc/$PKGNAM-$VERSION/$PKGNAM.SlackBuild
> 
>  mkdir -p $PKG/install
>  cat $CWD/slack-desc > $PKG/install/slack-desc
> 
>  cd $PKG
> -/sbin/makepkg -l y -c n
> $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
> +/sbin/makepkg -l y -c n
> $OUTPUT/$PKGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}

From chaos.proton at gmail.com  Fri Jun 24 10:20:37 2011
From: chaos.proton at gmail.com (Grissiom)
Date: Fri, 24 Jun 2011 18:20:37 +0800
Subject: [Slackbuilds-users] fix Jinja2 typo
In-Reply-To: <20110624090832.GD30584@linuxbox.fi>
References: <BANLkTinWHscQ4oDeZ7dYE0_OgGAvybkikQ@mail.gmail.com>
	<20110624090832.GD30584@linuxbox.fi>
Message-ID: <BANLkTimrWx8c=9sNXRiHJZqAA+NNQp+9RA@mail.gmail.com>

On Fri, Jun 24, 2011 at 5:08 PM, Mikko Varri <vmj at linuxbox.fi> wrote:
> Thanks for pointing that out.
>
> Am I missing something? ?Instead of changing PRGNAM to PKGNAM
> everywhere, a smaller patch would change one instance of PGKNAM to
> PRGNAM.
>
> -cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs $PKG/usr/doc/$PKGNAM-$VERSION
> +cp -a docs/_build/html $PKG/usr/doc/$PRGNAM-$VERSION || cp -a docs $PKG/usr/doc/$PRGNAM-$VERSION
>
> PRGNAM is the right variable name for it, right?

Oops, yeah, this patch is right. I thought is stands for "PaKaGe NAMe"
at that time... Actually, it should be "PRoGram NAMe".

-- 
Cheers,
Grissiom

From biolizard.mail at gmail.com  Fri Jun 24 18:59:33 2011
From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=)
Date: Fri, 24 Jun 2011 19:59:33 +0100
Subject: [Slackbuilds-users] Libreoffice
Message-ID: <4E04DE95.3080506@gmail.com>

Hello,

Libreoffice official package has been updated to version 3.3.3, although 
there is also a version 3.4.0, which means that the Slackbuild needs to 
be updated.

Regards,
Jos?

From niels.horn at gmail.com  Fri Jun 24 19:06:07 2011
From: niels.horn at gmail.com (Niels Horn)
Date: Fri, 24 Jun 2011 16:06:07 -0300
Subject: [Slackbuilds-users] Libreoffice
In-Reply-To: <4E04DE95.3080506@gmail.com>
References: <4E04DE95.3080506@gmail.com>
Message-ID: <BANLkTi=y9MaiK_p-W6JPhe7opYxz5ELuxw@mail.gmail.com>

2011/6/24 Jos? Lopes <biolizard.mail at gmail.com>:
> Hello,
>
> Libreoffice official package has been updated to version 3.3.3, although
> there is also a version 3.4.0, which means that the Slackbuild needs to be
> updated.
>
> Regards,
> Jos?
> _______________________________________________
> 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/
>
>

Hi,

Yes I know, that's why the new version of the SlackBuild is waiting in
the pending queue :)

If you can't wait for it to be approved, you can get it from my site:
http://www.nielshorn.net/slackware/slack_pkg.php

Thanks,

--
Niels Horn

From biolizard.mail at gmail.com  Fri Jun 24 19:07:23 2011
From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=)
Date: Fri, 24 Jun 2011 20:07:23 +0100
Subject: [Slackbuilds-users] Libreoffice
In-Reply-To: <BANLkTi=y9MaiK_p-W6JPhe7opYxz5ELuxw@mail.gmail.com>
References: <4E04DE95.3080506@gmail.com>
	<BANLkTi=y9MaiK_p-W6JPhe7opYxz5ELuxw@mail.gmail.com>
Message-ID: <4E04E06B.6090707@gmail.com>

Hi,

Oh, sorry, I forgot to check the pending queue.

Thanks,
Jos?

On 06/24/2011 08:06 PM, Niels Horn wrote:
> 2011/6/24 Jos? Lopes<biolizard.mail at gmail.com>:
>> Hello,
>>
>> Libreoffice official package has been updated to version 3.3.3, although
>> there is also a version 3.4.0, which means that the Slackbuild needs to be
>> updated.
>>
>> Regards,
>> Jos?
>> _______________________________________________
>> 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/
>>
>>
> Hi,
>
> Yes I know, that's why the new version of the SlackBuild is waiting in
> the pending queue :)
>
> If you can't wait for it to be approved, you can get it from my site:
> http://www.nielshorn.net/slackware/slack_pkg.php
>
> Thanks,
>
> --
> Niels Horn
> _______________________________________________
> 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 binhnguyen at fastmail.fm  Sat Jun 25 08:26:12 2011
From: binhnguyen at fastmail.fm (Binh Nguyen)
Date: Sat, 25 Jun 2011 15:26:12 +0700
Subject: [Slackbuilds-users] Libreoffice
In-Reply-To: <BANLkTi=y9MaiK_p-W6JPhe7opYxz5ELuxw@mail.gmail.com>
References: <4E04DE95.3080506@gmail.com>
	<BANLkTi=y9MaiK_p-W6JPhe7opYxz5ELuxw@mail.gmail.com>
Message-ID: <20110625152612.7b26e7b7@darkstar.example.net>

On Fri, 24 Jun 2011 16:06:07 -0300
Niels Horn <niels.horn at gmail.com> wrote:

> If you can't wait for it to be approved, you can get it from my site:
> http://www.nielshorn.net/slackware/slack_pkg.php
> 

I've just installed your package and I have to say I'm very glad that
LibreOffice with version 3.4.0 for the first time respects system font
settings.

For previous versions, I have to build it from source (for slack 13.0
so cannot get from Eric) to have a package that looks 'right' rather
than the one from provided binaries with an 'ugly' look.

Considering building 3.3.2 took up to 9GB in about 5 hours on an Core
i3 machine, this change in LO of course will save me a lot of time in
the future. I will just use the provided binaries instead of building
myself.

Now with LibreOffice respects system font settings along with Google
Chrome and Opera, I wish Firefox will soon implement this 'technique'
too in their provided binaries.

Cheers,

-- 
Binh Nguyen

From info at microlinux.fr  Sun Jun 26 09:12:46 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sun, 26 Jun 2011 11:12:46 +0200
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
Message-ID: <4E06F80E.6050600@microlinux.fr>

Hi,

The SBo repository currently holds a very ancient version of the 
excellent audio CD ripper Grip. Version 2.96 has no GNOME dependencies, 
but it's *very* old, it still relies on GTK1.

I just experimented a bit, and found that the latest (GTK2) version of 
Grip has indeed some GNOME dependencies (as well as id3lib), but it's 
only something like less than a dozen, and what's more important, 
they're all currently on offer on SBo. In fact the "only" explicit 
dependency is libgnomeui, but this package in itself relies on 
gnome-vfs, which in itself etc. you know the song with GNOME libs.

Some quirks to build the application are still the same. The Makefile 
has to be patched so as to use the internal cdparanoia (while the 
builtin cdparanoia works equally well, so it's just a matter of personal 
taste). Aside from that, the application builds OK, the *.desktop entry 
is now fixed and doesn't have to be provided.

I'm only posting this as a hint to the current package maintainer, since 
I don't want to appear as a maintenance usurpator. In my humble opinion, 
it's worth the while to upgrade the SlackBuild for Grip to the latest 
version. The application runs just fine here, and it has quite some more 
functionalities than the old version. These GTK1 apps all have this sort 
of North Korean look about them (except XMMS, which I still hold high in 
my esteem).

Cheers from the hot South of France,

Niki

From yalhcru at gmail.com  Sun Jun 26 10:48:11 2011
From: yalhcru at gmail.com (B Watson)
Date: Sun, 26 Jun 2011 06:48:11 -0400
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <4E06F80E.6050600@microlinux.fr>
References: <4E06F80E.6050600@microlinux.fr>
Message-ID: <BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>

On 6/26/11, Nicolas Kovacs <info at microlinux.fr> wrote:

> I just experimented a bit, and found that the latest (GTK2) version of
> Grip has indeed some GNOME dependencies (as well as id3lib), but it's
> only something like less than a dozen, and what's more important,
> they're all currently on offer on SBo. In fact the "only" explicit
> dependency is libgnomeui, but this package in itself relies on
> gnome-vfs, which in itself etc. you know the song with GNOME libs.

Speaking as the grip slackbuild maintainer (but not speaking for the SBo
admins)... The whole point of having grip available is to avoid the "big"
desktop libraries (both KDE and GNOME). I have a need for a GUI CD ripper
that can run well on a crappy old laptop with minimal resource usage,
and can be installed on Slackware without the KDE packages installed. It's
also nice not to have to wait a couple hours for the Gnome libs to build,
on an older/slower/smaller system. Plus, the ancient version has all
the features I need (hey, it rips CDs... and encodes mp3s/oggs, too!)

> I'm only posting this as a hint to the current package maintainer, since
> I don't want to appear as a maintenance usurpator. In my humble opinion,
> it's worth the while to upgrade the SlackBuild for Grip to the latest
> version. The application runs just fine here, and it has quite some more
> functionalities than the old version.

I can see the point of wanting the newer version. I just don't have any
interest or desire to build or maintain it myself.

If you (or anyone else) want to submit a build for the latest
Grip-with-Gnome, I'm willing to rename my grip build to "grip2"
or "grip-gtk" or something, and you can submit a "grip3" or maybe
"grip-gnome" build for the newest version.

I'd rather not call it "grip-legacy"... eh, but I don't feel all that
strongly about it.

I'd also rather not have there be a new "grip" package (with the same
name as the old one) that suddenly requires GNOME. Better to have no
package at all simply called "grip" (make sure anyone upgrading grip
will have to consciously choose to stay with 2.x or move to 3.x). For
the same reason, the two packages' READMEs ought to mention each other.

> These GTK1 apps all have this sort of North Korean look about them

Another thought: if your main complaint is GTK1 vs. GTK2, I'm willing to
patch grip-2.96 to build with GTK2, if the admins are willing to accept
it as an *optional* part of the SlackBuild (e.g. "export GTK2=yes;
./grip.SlackBuild", but the default is to use the unpatched GTK1 source).

This would probably have to be done eventually anyway. I'm willing to
bet that sometime after GTK3 makes its way into a Slackware release,
GTK1's days will be numbered.

From info at microlinux.fr  Sun Jun 26 12:54:12 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sun, 26 Jun 2011 14:54:12 +0200
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
Message-ID: <4E072BF4.80804@microlinux.fr>

Le 26/06/2011 12:48, B Watson a ?crit :
> If you (or anyone else) want to submit a build for the latest
> Grip-with-Gnome, I'm willing to rename my grip build to "grip2"
> or "grip-gtk" or something, and you can submit a "grip3" or maybe
> "grip-gnome" build for the newest version.

Yeah, grip2 vs. grip3 would be a good solution, so users would have the 
choice, similarly to libmusicbrainz vs. libmusicbrainz3.

Cheers,

Niki

From info at microlinux.fr  Sun Jun 26 12:56:40 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sun, 26 Jun 2011 14:56:40 +0200
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
Message-ID: <4E072C88.5070702@microlinux.fr>

Le 26/06/2011 12:48, B Watson a ?crit :
> It's
> also nice not to have to wait a couple hours for the Gnome libs to build,
> on an older/slower/smaller system.

Adding all the - ten or so - libs to the build queue in sbopkg and then 
download and build them takes ten to fifteen minutes on a reasonable 
recent PC. Of yourse, YMMV.

Niki

From Manuel.Spam at nurfuerspam.de  Sun Jun 26 12:52:19 2011
From: Manuel.Spam at nurfuerspam.de (Manuel Reimer)
Date: Sun, 26 Jun 2011 14:52:19 +0200
Subject: [Slackbuilds-users] How to get source hostet?
Message-ID: <iu7a9e$8vs$1@dough.gmane.org>

Hello,

I would like to create a SlackBuild for "osm2pgsql", which is a tool, required 
to import OpenStreetMap data to a PostGIS database. The SlackBuild is ready, but 
unfortunately there are no releases. The source is managed on SVN.

I found a source archive on the debian mirrors, but they drop parts of the 
source, as they split that package.

How can I request to get a tar.gz for a SVN release hosted on the 
slackbuilds.org servers, so my SlackBuild can use this as source archive? Can I 
upload this together with the SlackBuild itself in my tar.gz file? How to get 
updated? Can I request another file hosting some months later?

Thanks in advance

Yours

Manuel


From ozan.turkyilmaz at gmail.com  Sun Jun 26 13:16:50 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Sun, 26 Jun 2011 18:16:50 +0500
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <iu7a9e$8vs$1@dough.gmane.org>
References: <iu7a9e$8vs$1@dough.gmane.org>
Message-ID: <BANLkTimJ4iBJ7cJ5FWrF3-iuctLw_xaT2g@mail.gmail.com>

2011/6/26 Manuel Reimer <Manuel.Spam at nurfuerspam.de>:
> Hello,
>
> Thanks in advance

How big is the tarball? I offer free hosting up to 2MB.

-- 
Ozan, BSc, BEng

From ozan.turkyilmaz at gmail.com  Sun Jun 26 13:18:01 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Sun, 26 Jun 2011 18:18:01 +0500
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <4E072BF4.80804@microlinux.fr>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
	<4E072BF4.80804@microlinux.fr>
Message-ID: <BANLkTikGj2gBj8Ewhwcdw17pa3-8F4+4gg@mail.gmail.com>

2011/6/26 Nicolas Kovacs <info at microlinux.fr>:
> Le 26/06/2011 12:48, B Watson a ?crit :
>>
>> If you (or anyone else) want to submit a build for the latest
>> Grip-with-Gnome, I'm willing to rename my grip build to "grip2"
>> or "grip-gtk" or something, and you can submit a "grip3" or maybe
>> "grip-gnome" build for the newest version.
>
> Yeah, grip2 vs. grip3 would be a good solution, so users would have the
> choice, similarly to libmusicbrainz vs. libmusicbrainz3.
>

And if packages would interfare with each other, there should be a
explanation in the README.


-- 
Ozan, BSc, BEng

From yalhcru at gmail.com  Sun Jun 26 13:21:05 2011
From: yalhcru at gmail.com (B Watson)
Date: Sun, 26 Jun 2011 09:21:05 -0400
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <4E072C88.5070702@microlinux.fr>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
	<4E072C88.5070702@microlinux.fr>
Message-ID: <BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>

On 6/26/11, Nicolas Kovacs <info at microlinux.fr> wrote:

> Adding all the - ten or so - libs to the build queue in sbopkg and then
> download and build them takes ten to fifteen minutes on a reasonable
> recent PC. Of yourse, YMMV.

If I wanted a GUI CD ripper on a reasonably recent PC, I'd just use the
one that comes with Slackware as part of KDE (or XFCE). My grip package
is meant for old (or anyway resource-limited) systems. Think ArmedSlack
on a 66MHz processor, or an old Pentium-166 with 64 megs of RAM, rescued
from a dumpster (OK, maybe not with Slackware 13.x, but 10.0 or 11.0
would run OK on it).

So, I'll submit an updated package for grip-2.96, renamed to grip2. In its
README I'll mention that there's a much newer version called grip3. Should
work out OK for everyone.

From niels.horn at gmail.com  Sun Jun 26 14:22:01 2011
From: niels.horn at gmail.com (Niels Horn)
Date: Sun, 26 Jun 2011 11:22:01 -0300
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
	<4E072C88.5070702@microlinux.fr>
	<BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
Message-ID: <BANLkTimyQ7K4keTG37+yM7+y1_eDxxjFFg@mail.gmail.com>

On Sun, Jun 26, 2011 at 10:21 AM, B Watson <yalhcru at gmail.com> wrote:
> On 6/26/11, Nicolas Kovacs <info at microlinux.fr> wrote:
>
>> Adding all the - ten or so - libs to the build queue in sbopkg and then
>> download and build them takes ten to fifteen minutes on a reasonable
>> recent PC. Of yourse, YMMV.
>
> If I wanted a GUI CD ripper on a reasonably recent PC, I'd just use the
> one that comes with Slackware as part of KDE (or XFCE). My grip package
> is meant for old (or anyway resource-limited) systems. Think ArmedSlack
> on a 66MHz processor, or an old Pentium-166 with 64 megs of RAM, rescued
> from a dumpster (OK, maybe not with Slackware 13.x, but 10.0 or 11.0
> would run OK on it).
>
> So, I'll submit an updated package for grip-2.96, renamed to grip2. In its
> README I'll mention that there's a much newer version called grip3. Should
> work out OK for everyone.
> _______________________________________________
> 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/
>
>

On a personal note: I use grip(2) as it just does the job and has done
so for quite some time.

As an SBo admin, I have no problems with grip2 and grip3 co-existing
in the repo, as long as there is something mentioned in the README of
both that they cannot co-exist on a single system, and that it is not
possible to "upgrade" from grip2 to grip3, but that the older version
needs to be uninstalled before installing the newer release.

--
Niels Horn

From grbzks at xsmail.com  Sun Jun 26 18:39:27 2011
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sun, 26 Jun 2011 21:39:27 +0300
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
	<4E072C88.5070702@microlinux.fr>
	<BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
Message-ID: <20110626183923.GA10957@netbook>

B Watson wrote:
> <...>
>
> So, I'll submit an updated package for grip-2.96, renamed to grip2. In its
> README I'll mention that there's a much newer version called grip3. Should
> work out OK for everyone.

Since Nicolas Kovacs specifically said he isnt willing to maintain the
newer 3.y version of grip himself, i dont think it makes sense writing
that the newer version is called grip3. The application is still called
grip no matter if its grip 2.x or grip 3.y.
Just renaming the current script to grip2, along with a mention that
"This is the old version of grip that allows it to build without GNOME
dependencies" should suffice.
If someone in the future wants to submit the 3.y version let them do so
using its actual name (grip).
Even the "new" 3.x version is from 2005 is old in my book while 2.x is
from 2002.
Since this hasnt been brought up for all this time chances are most
people are using an alternative. Slackware itself provides at least two
applications that are capable of doing everything grip does, both
requiring KDE. Grip is decent but it doesnt do anything special.

Greg

-- 
()  against html e-mail  |  usenet & email communication netiquette
/\  www.asciiribbon.org  |  www.netmeister.org/news/learn2quote.html

From info at microlinux.fr  Sun Jun 26 19:01:37 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sun, 26 Jun 2011 21:01:37 +0200
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <20110626183923.GA10957@netbook>
References: <4E06F80E.6050600@microlinux.fr>	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>	<4E072C88.5070702@microlinux.fr>	<BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
	<20110626183923.GA10957@netbook>
Message-ID: <4E078211.9060405@microlinux.fr>

Le 26/06/2011 20:39, Grigorios Bouzakis a ?crit :
> Slackware itself provides at least two
> applications that are capable of doing everything grip does, both
> requiring KDE.

As an off-topic aside, I've found an interesting detail for KDE users 
while searching around for audio-ripping apps. Since it's not obvious - 
at least it doesn't seem to me - I decided to share it here.

When you insert an audio CD and open it in Dolphin, there's a short CDDB 
search going on, an you eventually see the track titles in a folder, 
along with some mysterious FLAC, OGG and MP3 folders. Now simply split 
this folder view and drag one of the folders to some other location. 
This starts an automagic ripping process.

You can also directly open the CD in Dolphin using the audiocd:/ 
kioslave protocol. One of those well-hidden easter eggs that make 
working with KDE so enjoyable.

Following Murphy's law, I only discovered this function *after* having 
built Grip successfully :o)

Cheers,

Niki

From mjjzf at syntaktisk.dk  Sun Jun 26 20:44:52 2011
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Sun, 26 Jun 2011 22:44:52 +0200
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
Message-ID: <20110626224452.009901b1@espero.syntaktisk.dk>

On Sun, 26 Jun 2011 06:48:11 -0400
B Watson <yalhcru at gmail.com> wrote:

[...]
> The whole point of having grip available is to avoid
> the "big" desktop libraries (both KDE and GNOME). I have a need for a
> GUI CD ripper that can run well on a crappy old laptop with minimal
> resource usage, and can be installed on Slackware without the KDE
> packages installed. It's also nice not to have to wait a couple hours
> for the Gnome libs to build, on an older/slower/smaller system. Plus,
> the ancient version has all the features I need (hey, it rips CDs...
> and encodes mp3s/oggs, too!)

I am surprised noone has mentioned Asunder, which is exactly a
lightweight CD ripper using GTK2 creating Ogg Vorbis, MP3s & FLAC:
http://slackbuilds.org/repository/13.37/audio/asunder/
I always install that one for my Xfce desktop if I need CD ripping.

Yours,
Morten
__
Morten Juhl-Johansen Z?lde-Fej?r
mjjzf at syntaktisk.dk * www.syntaktisk.dk

From ml at mareichelt.com  Sun Jun 26 22:11:29 2011
From: ml at mareichelt.com (markus reichelt)
Date: Mon, 27 Jun 2011 00:11:29 +0200
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <iu7a9e$8vs$1@dough.gmane.org>
References: <iu7a9e$8vs$1@dough.gmane.org>
Message-ID: <20110626221129.GC25897@pc21.mareichelt.com>

* Manuel Reimer <Manuel.Spam at nurfuerspam.de> wrote:

> The SlackBuild is ready, but unfortunately there are no releases. 
> The source is managed on SVN.

I hate that too.


> How can I request to get a tar.gz for a SVN release hosted on the
> slackbuilds.org servers, so my SlackBuild can use this as source
> archive?

One option would be to ask 'Tadgy' (on IRC - runs a mirror at
slackware.org.uk, check the site) to host it.  One would be to host
it yourself somewhere (since you are using gmx, there's some gmxhome
feature, 10MB space for free - if you are not using that already).


-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110627/da712632/attachment.asc>

From dragonwisard at gmail.com  Sun Jun 26 23:22:34 2011
From: dragonwisard at gmail.com (Ben Mendis)
Date: Sun, 26 Jun 2011 19:22:34 -0400
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <20110626221129.GC25897@pc21.mareichelt.com>
References: <iu7a9e$8vs$1@dough.gmane.org>
	<20110626221129.GC25897@pc21.mareichelt.com>
Message-ID: <BANLkTimt_4f+Tghsu1mGEsvBEEzacaW3vQ@mail.gmail.com>

Also, Github gives you 0.30 GB of disk space with a free account which you
could use for hosting.

On Sun, Jun 26, 2011 at 6:11 PM, markus reichelt <ml at mareichelt.com> wrote:

> * Manuel Reimer <Manuel.Spam at nurfuerspam.de> wrote:
>
> > The SlackBuild is ready, but unfortunately there are no releases.
> > The source is managed on SVN.
>
> I hate that too.
>
>
> > How can I request to get a tar.gz for a SVN release hosted on the
> > slackbuilds.org servers, so my SlackBuild can use this as source
> > archive?
>
> One option would be to ask 'Tadgy' (on IRC - runs a mirror at
> slackware.org.uk, check the site) to host it.  One would be to host
> it yourself somewhere (since you are using gmx, there's some gmxhome
> feature, 10MB space for free - if you are not using that already).
>
>
> --
> left blank, right bald
>
> _______________________________________________
> 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/20110626/e5e33c6c/attachment.html>

From dave at dawoodfall.net  Sun Jun 26 23:30:50 2011
From: dave at dawoodfall.net (David Woodfall)
Date: Mon, 27 Jun 2011 00:30:50 +0100
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <4E06F80E.6050600@microlinux.fr>
References: <4E06F80E.6050600@microlinux.fr>
Message-ID: <20110626233049.GB17125@Junius>

On (11:12 26/06/11), Nicolas Kovacs <info at microlinux.fr> put forth the proposition:
>Hi,
>
>The SBo repository currently holds a very ancient version of the 
>excellent audio CD ripper Grip. Version 2.96 has no GNOME 
>dependencies, but it's *very* old, it still relies on GTK1.

What does the new version do that older one doesn't?

>I just experimented a bit, and found that the latest (GTK2) version 
>of Grip has indeed some GNOME dependencies (as well as id3lib), but 
>it's only something like less than a dozen, and what's more 
>important, they're all currently on offer on SBo. In fact the "only" 
>explicit dependency is libgnomeui, but this package in itself relies 
>on gnome-vfs, which in itself etc. you know the song with GNOME libs.
>
>Some quirks to build the application are still the same. The Makefile 
>has to be patched so as to use the internal cdparanoia (while the 
>builtin cdparanoia works equally well, so it's just a matter of 
>personal taste). Aside from that, the application builds OK, the 
>*.desktop entry is now fixed and doesn't have to be provided.
>
>I'm only posting this as a hint to the current package maintainer, 
>since I don't want to appear as a maintenance usurpator. In my humble 
>opinion, it's worth the while to upgrade the SlackBuild for Grip to 
>the latest version. The application runs just fine here, and it has 
>quite some more functionalities than the old version. These GTK1 apps 
>all have this sort of North Korean look about them (except XMMS, 
>which I still hold high in my esteem).
>Cheers from the hot South of France,
>
>Niki
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - http://slackbuilds.org/faq/

-- 
Don't look back, the lemmings are gaining on you.

From dave at dawoodfall.net  Sun Jun 26 23:34:22 2011
From: dave at dawoodfall.net (David Woodfall)
Date: Mon, 27 Jun 2011 00:34:22 +0100
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <4E078211.9060405@microlinux.fr>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
	<4E072C88.5070702@microlinux.fr>
	<BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
	<20110626183923.GA10957@netbook> <4E078211.9060405@microlinux.fr>
Message-ID: <20110626233422.GC17125@Junius>

On (21:01 26/06/11), Nicolas Kovacs <info at microlinux.fr> put forth the proposition:
>Le 26/06/2011 20:39, Grigorios Bouzakis a ?crit :
>>Slackware itself provides at least two
>>applications that are capable of doing everything grip does, both
>>requiring KDE.
>
>As an off-topic aside, I've found an interesting detail for KDE users 
>while searching around for audio-ripping apps. Since it's not obvious 
>- at least it doesn't seem to me - I decided to share it here.
>
>When you insert an audio CD and open it in Dolphin, there's a short 
>CDDB search going on, an you eventually see the track titles in a 
>folder, along with some mysterious FLAC, OGG and MP3 folders. Now 
>simply split this folder view and drag one of the folders to some 
>other location. This starts an automagic ripping process.
>
>You can also directly open the CD in Dolphin using the audiocd:/ 
>kioslave protocol. One of those well-hidden easter eggs that make 
>working with KDE so enjoyable.
>
>Following Murphy's law, I only discovered this function *after* 
>having built Grip successfully :o)

This is great, but I for one use grip as a lightweight CD player more
than ripper. Since the demise of kscd there isn't really much of an
alternative.

I do use workbone though but grip can be easier to get on with on a
laptop with no numpad.

>Cheers,
>
>Niki
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - http://slackbuilds.org/faq/

-- 
Don't look back, the lemmings are gaining on you.

From info at microlinux.fr  Mon Jun 27 05:38:23 2011
From: info at microlinux.fr (Nicolas Kovacs)
Date: Mon, 27 Jun 2011 07:38:23 +0200
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <20110626233049.GB17125@Junius>
References: <4E06F80E.6050600@microlinux.fr> <20110626233049.GB17125@Junius>
Message-ID: <4E08174F.6070801@microlinux.fr>

Le 27/06/2011 01:30, David Woodfall a ?crit :
> What does the new version do that older one doesn't?

I'd say Grip3 is to Grip2 what a modern car is to a Trabant. You know, 
these light gray cars sold in the Eastern Block until the late eighties. 
My grandfather in Budapest had one, and he was very proud of it. Take a 
Jaguar, for example. It has four wheels like a Trabant, an engine, an 
odometer, seats, an ashtray. From this angle, a Jaguar does nothing more 
than a Jaguar.

:o)


From chrisretusn at bluehome.net  Mon Jun 27 06:03:17 2011
From: chrisretusn at bluehome.net (Chris)
Date: Mon, 27 Jun 2011 14:03:17 +0800
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <iu7a9e$8vs$1@dough.gmane.org>
Message-ID: <201162714317.758325@racermach>

Why not just add to the SlackBuilds script source checkout and tarball creation. 
 
== Original Message ========================
From: Manuel Reimer <Manuel.Spam at nurfuerspam.de>
Subj: [Slackbuilds-users] How to get source hostet?
Date: Sun, 26 Jun 2011 14:52:19 +0200
 
 
Hello,
 
I would like to create a SlackBuild for "osm2pgsql", which is a tool, required
to import OpenStreetMap data to a PostGIS database. The SlackBuild is ready, but
unfortunately there are no releases. The source is managed on SVN.
 
I found a source archive on the debian mirrors, but they drop parts of the
source, as they split that package.
 
How can I request to get a tar.gz for a SVN release hosted on the
slackbuilds.org servers, so my SlackBuild can use this as source archive? Can I
upload this together with the SlackBuild itself in my tar.gz file? How to get
updated? Can I request another file hosting some months later?
 
Thanks in advance
 
Yours
 
Manuel
 
_______________________________________________
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 slava18 at gmail.com  Mon Jun 27 07:13:06 2011
From: slava18 at gmail.com (V'yacheslav Stetskevych)
Date: Mon, 27 Jun 2011 10:13:06 +0300
Subject: [Slackbuilds-users] Grip update recommended -> latest version
 builds, installs and runs just fine
In-Reply-To: <20110626233422.GC17125@Junius>
References: <4E06F80E.6050600@microlinux.fr>
	<BANLkTik0u9JK_-wt1HtN9U08Hx=ycjaRCA@mail.gmail.com>
	<4E072C88.5070702@microlinux.fr>
	<BANLkTi=ypPtzmY9O5f9gghQEyQTC0=cziA@mail.gmail.com>
	<20110626183923.GA10957@netbook> <4E078211.9060405@microlinux.fr>
	<20110626233422.GC17125@Junius>
Message-ID: <BANLkTik-XAXaCQ8=XF2f8+cLQmNrCTjH5w@mail.gmail.com>

On Mon, Jun 27, 2011 at 2:34 AM, David Woodfall <dave at dawoodfall.net> wrote:
> Since the demise of kscd there isn't really much of an
> alternative.

I play audio cds in deadbeef or vlc. Try DeaDBeeF, it's actually very
decent, and it plays flac+cue and lots of other formats.

-- 
If you think of MS-DOS as mono, and Windows as stereo,
then Linux is Dolby Digital and all the music is free...
? ? ? ?http://www.linux.com

From ozan.turkyilmaz at gmail.com  Mon Jun 27 07:23:02 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Mon, 27 Jun 2011 12:23:02 +0500
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <201162714317.758325@racermach>
References: <iu7a9e$8vs$1@dough.gmane.org>
	<201162714317.758325@racermach>
Message-ID: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>

2011/6/27 Chris <chrisretusn at bluehome.net>:
> Why not just add to the SlackBuilds script source checkout and tarball creation.

That's a big NO-NO

-- 
Ozan, BSc, BEng

From eric.b.pratt at gmail.com  Mon Jun 27 09:23:15 2011
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Mon, 27 Jun 2011 05:23:15 -0400
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
References: <iu7a9e$8vs$1@dough.gmane.org> <201162714317.758325@racermach>
	<BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
Message-ID: <BANLkTimh-+G4vEGfEHf_wQd48fAZk=ZokA@mail.gmail.com>

2011/6/27 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> 2011/6/27 Chris <chrisretusn at bluehome.net>:
>> Why not just add to the SlackBuilds script source checkout and tarball creation.
>
> That's a big NO-NO

Not trying to be a jerk here, but I'm really curious about why this is a NO-NO.

Since you can check out by date or revision number, you can get the
same revision for the slackbuild each time.  Of course, you could
check for the presence of the tarball first and if it's not there,
check out the revision.  If you have to check out, recursively remove
the .svn directories, tarball it, and take an MD5 sum of the tarball.
The slackbuild could read the .info file and compare the MD5 sum in
the .info file with the MD5 sum of the tarball you just created.  (Not
quite sure why MD5 validation code isn't already required in all
slackbuilds anyway.)  If you want this check to be optional, then
enable it via variable before running the slackbuild, like
MD5VERIFY="Yes" or something like that.

So we add a few lines to a pretty standard slackbuild to get the
tarball and MD5 sum.  Once that's done, we're back to standard
slackbuild territory.  This seems like a perfectly reasonable way to
handle this and avoids hosting home-brewed tarballs.

Eric

From pwcazenave at gmail.com  Mon Jun 27 09:45:18 2011
From: pwcazenave at gmail.com (Pierre Cazenave)
Date: Mon, 27 Jun 2011 10:45:18 +0100
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <BANLkTimh-+G4vEGfEHf_wQd48fAZk=ZokA@mail.gmail.com>
References: <iu7a9e$8vs$1@dough.gmane.org>
	<201162714317.758325@racermach>	<BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
	<BANLkTimh-+G4vEGfEHf_wQd48fAZk=ZokA@mail.gmail.com>
Message-ID: <4E08512E.6080708@gmail.com>



On 27/06/2011 10:23, Eric Pratt wrote:
> 2011/6/27 Ozan T?rky?lmaz<ozan.turkyilmaz at gmail.com>:
>> 2011/6/27 Chris<chrisretusn at bluehome.net>:
>>> Why not just add to the SlackBuilds script source checkout and
>>> tarball creation.
>>
>> That's a big NO-NO
>
> Not trying to be a jerk here, but I'm really curious about why this
> is a NO-NO.
>
> Since you can check out by date or revision number, you can get the
> same revision for the slackbuild each time.  Of course, you could
> check for the presence of the tarball first and if it's not there,
> check out the revision.  If you have to check out, recursively
> remove the .svn directories, tarball it, and take an MD5 sum of the
> tarball. The slackbuild could read the .info file and compare the MD5
> sum in the .info file with the MD5 sum of the tarball you just
> created.  (Not quite sure why MD5 validation code isn't already
> required in all slackbuilds anyway.)  If you want this check to be
> optional, then enable it via variable before running the slackbuild,
> like MD5VERIFY="Yes" or something like that.
>
> So we add a few lines to a pretty standard slackbuild to get the
> tarball and MD5 sum.  Once that's done, we're back to standard
> slackbuild territory.  This seems like a perfectly reasonable way to
> handle this and avoids hosting home-brewed tarballs.
>
> Eric _______________________________________________
> 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/
>

If you want this level of automation of checking md5sums, gpg keys etc. 
then sbopkg does a wonderful job of that.

Keeping the scripts simple makes them easier to maintain and verify (the 
admins do seem to be busy enough as it is!) and easier to spot errors.

There are a few scripts in the repository that have "difficult" sources. 
For example, the TrueCrypt project doesn't make its source available 
with a static link, and as such the DOWNLOAD variable in the .info file 
merely points to the page from which the source can be downloaded.

Pierre

From audrius at neutrino.lt  Mon Jun 27 09:43:18 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Mon, 27 Jun 2011 12:43:18 +0300
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <BANLkTimt_4f+Tghsu1mGEsvBEEzacaW3vQ@mail.gmail.com>
References: <iu7a9e$8vs$1@dough.gmane.org>
	<20110626221129.GC25897@pc21.mareichelt.com>
	<BANLkTimt_4f+Tghsu1mGEsvBEEzacaW3vQ@mail.gmail.com>
Message-ID: <20110627094318.GA2141@kiras>

On Sun, 2011-06-26 at 19:22:34 -0400, Ben Mendis wrote:
> Also, Github gives you 0.30 GB of disk space with a free account which you
> could use for hosting.

And bitbucket.org gives you unlimited disk space for hosting
repositories and files.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110627/4c527ad8/attachment.asc>

From chrisretusn at bluehome.net  Tue Jun 28 02:03:45 2011
From: chrisretusn at bluehome.net (Chris)
Date: Tue, 28 Jun 2011 10:03:45 +0800
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
Message-ID: <201162810345.197072@racermach>

Well that was a fantastic answer. How about giving me a bit more. Perhaps a few specific and valid reasons why this is a no-no as you put it. 

All it would take is a few extra lines of code to checkout the source and then create a tarball excluding the svn directories.

You could also just build it off the checked out source tree. Copy it over to a build directory, and build from there, making a package off the result. 
 
== Original Message ========================
From: Ozan T??rky??lmaz <ozan.turkyilmaz at gmail.com>
Subj: Re: [Slackbuilds-users] How to get source hostet?
Date: Mon, 27 Jun 2011 12:23:02 +0500
 
 
2011/6/27 Chris <chrisretusn at bluehome.net>:
> Why not just add to the SlackBuilds script source checkout and tarball creation.
 
That's a big NO-NO
 
--
Ozan, BSc, BEng


From ozan.turkyilmaz at gmail.com  Tue Jun 28 02:35:43 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 28 Jun 2011 07:35:43 +0500
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <201162810345.197072@racermach>
References: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
	<201162810345.197072@racermach>
Message-ID: <BANLkTikfOXni=GZKTtzouSQ-a58aVhjCFg@mail.gmail.com>

2011/6/28 Chris <chrisretusn at bluehome.net>:
> Well that was a fantastic answer. How about giving me a bit more. Perhaps a few specific and valid reasons why this is a no-no as you put it.
>
> All it would take is a few extra lines of code to checkout the source and then create a tarball excluding the svn directories.
>
> You could also just build it off the checked out source tree. Copy it over to a build directory, and build from there, making a package off the result.
>

First don't top post

SlackBuilds is SBo do not donwload anything. Sources should be simply
ifentified in .info file with a direct download link (but that's not
posible always like TrueCrypto) with md5sums of the download sources,
SlackBuilds build packages automaticly. Their duty  is not downloading
source nor checking md5sums.
-- 
Ozan, BSc, BEng

From matteo.bernardini at gmail.com  Tue Jun 28 04:29:21 2011
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 28 Jun 2011 06:29:21 +0200
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <201162810345.197072@racermach>
References: <201162810345.197072@racermach>
Message-ID: <4E0958A1.6090508@gmail.com>

Il 28/06/2011 04:03, Chris ha scritto:
> Well that was a fantastic answer. How about giving me a bit more. Perhaps a few specific and valid reasons why this is a no-no as you put it. 
> 
> All it would take is a few extra lines of code to checkout the source and then create a tarball excluding the svn directories.
> 
> You could also just build it off the checked out source tree. Copy it over to a build directory, and build from there, making a package off the result. 

http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-April/005398.html

Matteo

From chrisretusn at bluehome.net  Tue Jun 28 05:31:15 2011
From: chrisretusn at bluehome.net (Chris)
Date: Tue, 28 Jun 2011 13:31:15 +0800
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <BANLkTikfOXni=GZKTtzouSQ-a58aVhjCFg@mail.gmail.com>
Message-ID: <2011628133115.485204@racermach>

 
  <ozan.turkyilmaz at gmail.com> wrote:
> First don't top post

OK, have it your way. Not that it make any difference. 

> SlackBuilds is SBo do not donwload anything. Sources should be simply
> ifentified in .info file with a direct download link (but that's not
> posible always like TrueCrypto) with md5sums of the download sources,
> SlackBuilds build packages automaticly. Their duty  is not downloading
> source nor checking md5sums.

I read the Submission Guidelines at Slackbuilds.org. I saw nothing there that disallows this. I do understand this should not be the norm, but in this case the the source is only hosted by svn, to get it you must check it out. I suppose one could provide instructions on how to checkout the source and then make a tarball out of it. Even automate it with a script and add it as part of the Slackbuild tarball. 

I suppose a case could be made "Follow our template scripts as much as possible. Deviations are fine where needed, but don't change things to be "more clever" or some such - we like consistency"; however, this is not an attempt at being clever. It is a practical solution IMHAO.

Since I am directly checking out the source an md5sum would not be needed as there is no tarball to verify. That is what the checksum is for, verifying the source tarball, correct. 

It's not really big deal to me, host it as a tarball somewhere or check it out from svn; either way, it's not hosted on SlackBuilds.org. 

I only offered a suggestion (how I would do it). At least your second answer was a wee bit better than your first. Thanks. 

From matteo.bernardini at gmail.com  Tue Jun 28 05:40:54 2011
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 28 Jun 2011 07:40:54 +0200
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <2011628133115.485204@racermach>
References: <2011628133115.485204@racermach>
Message-ID: <4E096966.4010204@gmail.com>

Il 28/06/2011 07:31, Chris ha scritto:
> Since I am directly checking out the source an md5sum would not be needed as there is no tarball to verify. That is what the checksum is for, verifying the source tarball, correct. 

I think the assumptions is that you guarantee:
- on the integrity of the tarball you prepare (you put the md5 you
calculate in the .info file);
- that you have tested that specific tarball with the slackbuild and it
works fine.

Repositories are dynamic, you can't be sure that every checkout will
build smoothly.

Matteo

From dave at dawoodfall.net  Tue Jun 28 06:25:00 2011
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 28 Jun 2011 07:25:00 +0100
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <201162810345.197072@racermach>
References: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
	<201162810345.197072@racermach>
Message-ID: <20110628062500.GA24330@Junius>

On (10:03 28/06/11), Chris <chrisretusn at bluehome.net> put forth the proposition:
>Well that was a fantastic answer. How about giving me a bit more. Perhaps a few specific and valid reasons why this is a no-no as you put it.
>
>All it would take is a few extra lines of code to checkout the source and then create a tarball excluding the svn directories.
>
>You could also just build it off the checked out source tree. Copy it over to a build directory, and build from there, making a package off the result.

It makes it very difficult to follow the flow if you top post.

But as I see it source checkouts are liable to break from time to
time. A SlackBuild IMHO should always point to a tested/working
source.

Having said that I do keep a few dynamic SlackBuilds in my own repo,
with a big warning about what they do and suggesting that users
keep a backup of the last, previously working packages.

D.

>
>== Original Message ========================
>From: Ozan T??rky??lmaz <ozan.turkyilmaz at gmail.com>
>Subj: Re: [Slackbuilds-users] How to get source hostet?
>Date: Mon, 27 Jun 2011 12:23:02 +0500
>
>
>2011/6/27 Chris <chrisretusn at bluehome.net>:
>> Why not just add to the SlackBuilds script source checkout and tarball creation.
>
>That's a big NO-NO
>
>--
>Ozan, BSc, BEng
>

>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - http://slackbuilds.org/faq/
>


-- 
Don't look back, the lemmings are gaining on you.

From ozan.turkyilmaz at gmail.com  Tue Jun 28 08:39:26 2011
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 28 Jun 2011 13:39:26 +0500
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <20110628062500.GA24330@Junius>
References: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
	<201162810345.197072@racermach> <20110628062500.GA24330@Junius>
Message-ID: <BANLkTimHYzy-EBVgwan3oEKPK8pycHGbTA@mail.gmail.com>

2011/6/28 David Woodfall <dave at dawoodfall.net>:
> On (10:03 28/06/11), Chris <chrisretusn at bluehome.net> put forth the
> proposition:
>>
>> Well that was a fantastic answer. How about giving me a bit more. Perhaps
>> a few specific and valid reasons why this is a no-no as you put it.
>>
>> All it would take is a few extra lines of code to checkout the source and
>> then create a tarball excluding the svn directories.
>>
>> You could also just build it off the checked out source tree. Copy it over
>> to a build directory, and build from there, making a package off the result.
>
> It makes it very difficult to follow the flow if you top post.
>
> But as I see it source checkouts are liable to break from time to
> time. A SlackBuild IMHO should always point to a tested/working
> source.
>
> Having said that I do keep a few dynamic SlackBuilds in my own repo,
> with a big warning about what they do and suggesting that users
> keep a backup of the last, previously working packages.

I have set of scripts for building wine from a git tree (or any source tree).

-- 
Ozan, BSc, BEng

From pwcazenave at gmail.com  Tue Jun 28 09:14:14 2011
From: pwcazenave at gmail.com (Pierre Cazenave)
Date: Tue, 28 Jun 2011 10:14:14 +0100
Subject: [Slackbuilds-users] ORBit2 and GConf
Message-ID: <4E099B66.7000909@gmail.com>

I'm trying to build gksu and I note it (eventually) requires ORBit2 and 
GConf. These two packages have build scripts available in the 
SlackBuilds.org repository, but there are also packages available from 
the official Slackware mirrors in /extra/google-chrome.

Are they the same? Should the SBo ones be removed?

Pierre

From matteo.bernardini at gmail.com  Tue Jun 28 09:22:16 2011
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 28 Jun 2011 11:22:16 +0200
Subject: [Slackbuilds-users] ORBit2 and GConf
In-Reply-To: <4E099B66.7000909@gmail.com>
References: <4E099B66.7000909@gmail.com>
Message-ID: <4E099D48.505@gmail.com>

On 28/06/2011 11:14, Pierre Cazenave wrote:
> I'm trying to build gksu and I note it (eventually) requires ORBit2 and
> GConf. These two packages have build scripts available in the
> SlackBuilds.org repository, but there are also packages available from
> the official Slackware mirrors in /extra/google-chrome.
> 
> Are they the same? Should the SBo ones be removed?

I think they are equivalent: ORBit2 should be pretty much the same and
the GConf version on slackbuilds.org is update to the latest 2.32.x version

ftp://ftp.gnome.org/pub/GNOME/sources/GConf/2.32/GConf-2.32.3.news
ftp://ftp.gnome.org/pub/GNOME/sources/GConf/2.32/GConf-2.32.4.news

btw and fyi, I'm using now gksu-polkit

http://cgit.ponce.cc/slackbuilds/tree/system/gksu-polkit?h=gksu-polkit

that depends "only" on vala and libgee (but no GConf ;) ).

Matteo

From ml at mareichelt.com  Tue Jun 28 12:44:54 2011
From: ml at mareichelt.com (markus reichelt)
Date: Tue, 28 Jun 2011 14:44:54 +0200
Subject: [Slackbuilds-users] opera buildscript needs a new maintainer
Message-ID: <20110628124454.GA31339@pc21.mareichelt.com>

subject says all

-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110628/44399bc6/attachment.asc>

From audrius at neutrino.lt  Tue Jun 28 13:04:22 2011
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Tue, 28 Jun 2011 16:04:22 +0300
Subject: [Slackbuilds-users] opera buildscript needs a new maintainer
In-Reply-To: <20110628124454.GA31339@pc21.mareichelt.com>
References: <20110628124454.GA31339@pc21.mareichelt.com>
Message-ID: <20110628130422.GA14198@kiras>

On Tue, 2011-06-28 at 14:44:54 +0200, markus reichelt wrote:
> subject says all

Long time Opera user here, so I'll be glad to take it.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110628/a1f9cef7/attachment.asc>

From eric at schultzter.ca  Tue Jun 28 13:40:34 2011
From: eric at schultzter.ca (Eric Schultz)
Date: Tue, 28 Jun 2011 09:40:34 -0400
Subject: [Slackbuilds-users] How to get source hostet?
Message-ID: <BANLkTinBtirLkUcJjkaey5C=5+z1XwA6fw@mail.gmail.com>

Here's my $0.02

From: Chris <chrisretusn at bluehome.net>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Date: Tue, 28 Jun 2011 13:31:15 +0800
> Subject: Re: [Slackbuilds-users] How to get source hostet?


> I suppose one could provide instructions on how to checkout the source and
> then make a tarball out of it. Even automate it with a script and add it as
> part of the Slackbuild tarball.


I would think this is the way to do it.  SlackBuilds should build the
package from a locally available source, pure and simple. What if you want
to recompile when a dependency changes, there's no need to checkout the
source again.

It would be very nice of you, though not absolutely necessary, to provide an
additional script that checks-out and tarballs the source.  But that script
would have additional dependencies not directly related to the package (ie.:
the source code control system and a network connection - neither of which
may be available on my system but that shouldn't stop me from building the
package).

Obviously it must be clearly stated that your download link identifies where
to get the source - not a direct link to a tarball. And there's a few extra
manual steps required (getting the source code, tarballing it, generating
the MD5SUM).

But that's just me!

<http://about.me/schultzter>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110628/635818a0/attachment.html>

From wxj.g.sh at gmail.com  Tue Jun 28 12:48:46 2011
From: wxj.g.sh at gmail.com (vvoody)
Date: Tue, 28 Jun 2011 20:48:46 +0800 (CST)
Subject: [Slackbuilds-users] opera buildscript needs a new maintainer
In-Reply-To: <20110628124454.GA31339@pc21.mareichelt.com>
References: <20110628124454.GA31339@pc21.mareichelt.com>
Message-ID: <20110628.204846.360652458.wxj.g.sh@gmail.com>

I'd like to take that. And what should I do next?

On Tue, 28 Jun 2011 14:44:54 +0200, markus reichelt <ml at mareichelt.com> wrote:
> subject says all
> 
> -- 
> left blank, right bald

From korgie at gmail.com  Tue Jun 28 19:43:34 2011
From: korgie at gmail.com (korgman)
Date: Tue, 28 Jun 2011 22:43:34 +0300
Subject: [Slackbuilds-users] pd new maintainer
Message-ID: <4E0A2EE6.1020502@gmail.com>

Old maintainer is not using anymore pd on slackware.

New maintainer data:

MAINTAINER="Michales Michaloudes"
EMAIL="korgie at gmail.com"

New update submission to follow maybe in this week.

Thanks.
-- 
http://clavisound.dyndns-server.com
Michales Michaloudes

From mjjzf at syntaktisk.dk  Wed Jun 29 08:34:53 2011
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Wed, 29 Jun 2011 10:34:53 +0200
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <20110628062500.GA24330@Junius>
References: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
	<201162810345.197072@racermach> <20110628062500.GA24330@Junius>
Message-ID: <20110629103453.2894d7bc@espero.syntaktisk.dk>

On Tue, 28 Jun 2011 07:25:00 +0100
David Woodfall <dave at dawoodfall.net> wrote:

> But as I see it source checkouts are liable to break from time to
> time. A SlackBuild IMHO should always point to a tested/working
> source.

Which is why checking out a specific revision would yield the same
result at pointing at a tarball over HTTP/FTP? I fail to see the
difference in anything but ports and agent. I was considering it for
Umplayer as well.
Much worse with a package like Chrome where 'latest' is a moving target
to say the least.

> Having said that I do keep a few dynamic SlackBuilds in my own repo,
> with a big warning about what they do and suggesting that users
> keep a backup of the last, previously working packages.

I have often thought that if one has builds that do not entirely follow
SlackBuild requirements but otherwise follow the conventions, it would
be nice to be able to search for. But of course, while having
such a database would be a godsend, keeping it current would be a slice
of purgatory...

> D.

All the best,
Morten
__
Morten Juhl-Johansen Z?lde-Fej?r
mjjzf at syntaktisk.dk * www.syntaktisk.dk

From dragonwisard at gmail.com  Wed Jun 29 12:29:15 2011
From: dragonwisard at gmail.com (Ben Mendis)
Date: Wed, 29 Jun 2011 08:29:15 -0400
Subject: [Slackbuilds-users] How to get source hostet?
In-Reply-To: <20110629103453.2894d7bc@espero.syntaktisk.dk>
References: <BANLkTin5JR7TNLniRT80aPWNy86oLyBPGw@mail.gmail.com>
	<201162810345.197072@racermach> <20110628062500.GA24330@Junius>
	<20110629103453.2894d7bc@espero.syntaktisk.dk>
Message-ID: <BANLkTinv-D65P2pR4xFOq0cyqO8Ep13hkg@mail.gmail.com>

On Wed, Jun 29, 2011 at 4:34 AM, Morten Juhl-Johansen Z?lde-Fej?r <
mjjzf at syntaktisk.dk> wrote:

> On Tue, 28 Jun 2011 07:25:00 +0100
> David Woodfall <dave at dawoodfall.net> wrote:
>
> > But as I see it source checkouts are liable to break from time to
> > time. A SlackBuild IMHO should always point to a tested/working
> > source.
>
> Which is why checking out a specific revision would yield the same
> result at pointing at a tarball over HTTP/FTP? I fail to see the
> difference in anything but ports and agent. I was considering it for
> Umplayer as well.
> Much worse with a package like Chrome where 'latest' is a moving target
> to say the least.
>

That's not necessarily true. History in a repository can be re-written so
even a specific revision could change over time.


>
> > Having said that I do keep a few dynamic SlackBuilds in my own repo,
> > with a big warning about what they do and suggesting that users
> > keep a backup of the last, previously working packages.
>
> I have often thought that if one has builds that do not entirely follow
> SlackBuild requirements but otherwise follow the conventions, it would
> be nice to be able to search for. But of course, while having
> such a database would be a godsend, keeping it current would be a slice
> of purgatory...
>
> > D.
>
> All the best,
> Morten
> __
> Morten Juhl-Johansen Z?lde-Fej?r
> mjjzf at syntaktisk.dk * www.syntaktisk.dk
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110629/f1e55f50/attachment.html>

From mjjzf at syntaktisk.dk  Thu Jun 30 12:05:55 2011
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Thu, 30 Jun 2011 14:05:55 +0200
Subject: [Slackbuilds-users] Chromium, or actually Chromium
Message-ID: <20110630140555.38a4e0bc@espero.syntaktisk.dk>

Looks like the keywords for
http://slackbuilds.org/repository/13.37/network/chromium/ 
have been mixed between the browser and the shooter.

Sincerely,
Morten
__
Morten Juhl-Johansen Z?lde-Fej?r
mjjzf at syntaktisk.dk * www.syntaktisk.dk

From erik at slackbuilds.org  Thu Jun 30 12:34:34 2011
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 30 Jun 2011 07:34:34 -0500
Subject: [Slackbuilds-users] Chromium, or actually Chromium
In-Reply-To: <20110630140555.38a4e0bc@espero.syntaktisk.dk>
References: <20110630140555.38a4e0bc@espero.syntaktisk.dk>
Message-ID: <20110630073434.781ae8ee@shaggy.doo>

On Thu, 30 Jun 2011 14:05:55 +0200
Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:

> Looks like the keywords for
> http://slackbuilds.org/repository/13.37/network/chromium/ 
> have been mixed between the browser and the shooter.

I made them more sensible, thanks.

-- 
Erik Hanson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110630/90c444a8/attachment.asc>