From rw at rlworkman.net  Sun Mar  2 03:33:20 2008
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 02 Mar 2008 02:33:20 -0600
Subject: [Slackbuilds-users] Test Message
Message-ID: <47CA6650.10007@rlworkman.net>

If you receive this, well, that's a good thing.
Details to follow.  ;-)

-RW

From andrew.david.45 at gmail.com  Sun Mar  2 04:38:57 2008
From: andrew.david.45 at gmail.com (andrew)
Date: Sun, 2 Mar 2008 20:38:57 +1100
Subject: [Slackbuilds-users] Test Message
In-Reply-To: <47CA6650.10007@rlworkman.net>
References: <47CA6650.10007@rlworkman.net>
Message-ID: <20080302093857.GA4222@ilium.lan>

On Sun, Mar 02, 2008 at 02:33:20AM -0600, Robby Workman wrote:
> If you receive this, well, that's a good thing.
> Details to follow.  ;-)

Good to see things back online :-)

    Andrew

-- 
http://www.andrews-corner.org

From chess at chessgriffin.com  Sun Mar  2 08:09:35 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Sun, 2 Mar 2008 08:09:35 -0500
Subject: [Slackbuilds-users] Test Message
In-Reply-To: <47CA6650.10007@rlworkman.net>
References: <47CA6650.10007@rlworkman.net>
Message-ID: <20080302080935.538cab3d@bsdbob.localdomain>

On Sun, 02 Mar 2008 02:33:20 -0600
Robby Workman <rw at rlworkman.net> wrote:

> If you receive this, well, that's a good thing.
> Details to follow.  ;-)
> 
> -RW

Check.

-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080302/09b86410/attachment.bin 

From me at alkos333.net  Sun Mar  2 08:10:15 2008
From: me at alkos333.net (alkos333)
Date: Sun, 2 Mar 2008 07:10:15 -0600
Subject: [Slackbuilds-users] Test Message
In-Reply-To: <20080302080935.538cab3d@bsdbob.localdomain>
References: <47CA6650.10007@rlworkman.net>
	<20080302080935.538cab3d@bsdbob.localdomain>
Message-ID: <a6f13f000803020510o588f0254u4402f6106b058da5@mail.gmail.com>

1 2 check :)

On Sun, Mar 2, 2008 at 7:09 AM, Chess Griffin <chess at chessgriffin.com> wrote:
> On Sun, 02 Mar 2008 02:33:20 -0600
>  Robby Workman <rw at rlworkman.net> wrote:
>
>  > If you receive this, well, that's a good thing.
>  > Details to follow.  ;-)
>  >
>  > -RW
>
>  Check.
>
>  --
>  Chess Griffin
>  GPG Public Key:  0x0C7558C3
>  http://www.chessgriffin.com
>
> _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>
>

From sebastien.serre33 at laposte.net  Sun Mar  2 08:16:43 2008
From: sebastien.serre33 at laposte.net (seb)
Date: Sun, 2 Mar 2008 14:16:43 +0100
Subject: [Slackbuilds-users] Test Message
In-Reply-To: <a6f13f000803020510o588f0254u4402f6106b058da5@mail.gmail.com>
References: <47CA6650.10007@rlworkman.net>
	<20080302080935.538cab3d@bsdbob.localdomain>
	<a6f13f000803020510o588f0254u4402f6106b058da5@mail.gmail.com>
Message-ID: <20080302141643.1dbfaae6@tangram.loonet.net>

On Sun, 2 Mar 2008 07:10:15 -0600
alkos333 <me at alkos333.net> wrote:

> 1 2 check :)
> 
> On Sun, Mar 2, 2008 at 7:09 AM, Chess Griffin
> <chess at chessgriffin.com> wrote:
> > On Sun, 02 Mar 2008 02:33:20 -0600
> >  Robby Workman <rw at rlworkman.net> wrote:
> >
> >  > If you receive this, well, that's a good thing.
> >  > Details to follow.  ;-)
> >  >
> >  > -RW
> >
> >  Check.
> >
> >  --
> >  Chess Griffin
> >  GPG Public Key:  0x0C7558C3
> >  http://www.chessgriffin.com
> >
> > _______________________________________________
> >  Slackbuilds-users mailing list
> >  Slackbuilds-users at slackbuilds.org
> >  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >
> >  Please read the FAQ - http://slackbuilds.org/faq/
> >
> >
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> 
> Please read the FAQ - http://slackbuilds.org/faq/
> 
check to 5/5


From ciol13 at gmail.com  Sun Mar  2 08:50:38 2008
From: ciol13 at gmail.com (ciol)
Date: Sun, 02 Mar 2008 14:50:38 +0100
Subject: [Slackbuilds-users] Test Message
In-Reply-To: <20080302141643.1dbfaae6@tangram.loonet.net>
References: <47CA6650.10007@rlworkman.net>	<20080302080935.538cab3d@bsdbob.localdomain>	<a6f13f000803020510o588f0254u4402f6106b058da5@mail.gmail.com>
	<20080302141643.1dbfaae6@tangram.loonet.net>
Message-ID: <47CAB0AE.5080503@gmail.com>

__Hitek__ d?ban moi du forum stp

seb wrote:
> On Sun, 2 Mar 2008 07:10:15 -0600
> alkos333 <me at alkos333.net> wrote:
> 
>> 1 2 check :)
>>
>> On Sun, Mar 2, 2008 at 7:09 AM, Chess Griffin
>> <chess at chessgriffin.com> wrote:
>>> On Sun, 02 Mar 2008 02:33:20 -0600
>>>  Robby Workman <rw at rlworkman.net> wrote:
>>>
>>>  > If you receive this, well, that's a good thing.
>>>  > Details to follow.  ;-)
>>>  >
>>>  > -RW
>>>
>>>  Check.
>>>
>>>  --
>>>  Chess Griffin
>>>  GPG Public Key:  0x0C7558C3
>>>  http://www.chessgriffin.com
>>>
>>> _______________________________________________
>>>  Slackbuilds-users mailing list
>>>  Slackbuilds-users at slackbuilds.org
>>>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>
>>>  Please read the FAQ - http://slackbuilds.org/faq/
>>>
>>>
>> _______________________________________________
>> Slackbuilds-users mailing list
>> Slackbuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>
>> Please read the FAQ - http://slackbuilds.org/faq/
>>
> check to 5/5
> 
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> 
> Please read the FAQ - http://slackbuilds.org/faq/
> 


From rworkman at slackbuilds.org  Sun Mar  2 17:29:27 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 2 Mar 2008 17:29:27 -0500
Subject: [Slackbuilds-users] Updates - 20080302
Message-ID: <20080302222927.GA6755@slackbuilds.org>

Sun Mar  2 22:25:31 UTC 2008
First of all, sorry for the extended outage of our mailing list and admin
  email; cardinal.lizella.net hosts those for us, and their colocation center
  decided to close their branch in the town where it was hosted (and forgot
  to let the owners know).  If DNS changes have propagated out to everyone
  by now, lists and mail should be back up.  We're still relaying mail through
  another host while we work on getting rDNS set up for us, but for the most
  part, everything is back to normal.  Again, apologies for the inconvenience,
  but it beyond our control.  With all that said, here are some updates...
desktop/Blokkal: Added - Blokkal is a blogging client for KDE.
  Thanks to Vincent Batts.  --rworkman
development/Genshi: Added - Genshi is a Python toolkit for stream-based 
  generation of output for the web.  Thanks to Andrea Maccis.  --rworkman
development/icoutils: Added - icoutils is a set of programs for extracting and
  converting images in Microsoft Windows(R) icon and cursor files.
  Thanks to Mark Walling.  --David Somero
development/jbigkit: Noted patent information in the README; no changes to the
  build script.  Thanks to Iskar Enev.  --rworkman
development/SQLAlchemy: Updated to version 0.4.3.
  Thanks to Andrea Maccis.  --David Somero
development/Werkzeug: Updated to version 0.2.
  Thanks to Andrea Maccis.  --David Somero
libraries/barry: Fixed the build script to add the TAG to package name.
  Thanks to Amrit for spotting the oversight. :)  --rworkman
libraries/gtkglext: Bugfixes - the first strip line errors out, causing the 
  subshell to exit, so we append "|| true" to it; also, copy the build script
  into the docs directory.  Thanks to Frank Caraballo.  --rworkman
libraries/pycairo: Bugfix - same strip problem as gtkglext.
  Thanks again to Frank Caraballo.  --rworkman
libraries/qt4: Updated to version 4.3.4.
  Thanks to Aleksandar B. Samardzic.  --David Somero
misc/clawsker: Updated for version 0.4.0. Thanks to Erik Hanson. --rworkman
multimedia/fluidsynth: Added - FluidSynth is a software real-time synthesizer 
  based on the Soundfont 2 specifications.
  Thanks to Heinz Wiesinger.  --rworkman
multimedia/id3v2: Added a patch to fix a crash bug.
  Thanks to Paul Wisehart.  --David Somero
multimedia/sonata: Updated to version 1.4.2.
  Thanks to Andrew Brouwers.  --David Somero
network/frostwire: Added - FrostWire is a fork of LimeWire, a cross-platform, 
  open-source peer-to-peer filesharing client for the Gnutella and BitTorrent 
  protocols.  Thanks to Phil Warner.  --rworkman
system/apcupsd: Fixed permissions on /var/lock directory.  If you've got an
  apcupsd package build from us before today, you don't have to rebuild it -
  you can use the shortcut:  "chmod 1777 /var/lock"  --rworkman
system/aufs: Added - Aufs is a stackable unification filesystem like Unionfs.
  Thanks to Mauro Giachero.  --rworkman
system/cfengine: Updated for version 2.2.3. Thanks to Menno Duursma. --rworkman
system/isomaster: Updated to version 1.3.1.
  Thanks to Erik Hanson.  --David Somero
system/splix: Updated for version 1.1.1 and added ability to build without
  jbig support.  Thanks to Iskar Enev.  --rworkman
system/watchdog: Updated for version 5.4.  Thanks to Menno Duursma. --rworkman

From joshuakwood at gmail.com  Sun Mar  2 18:55:41 2008
From: joshuakwood at gmail.com (JK Wood)
Date: Sun, 2 Mar 2008 17:55:41 -0600
Subject: [Slackbuilds-users] Test Message
In-Reply-To: <47CA6650.10007@rlworkman.net>
References: <47CA6650.10007@rlworkman.net>
Message-ID: <6b6812630803021555j518ef3d0j56c8e807c5de4e8d@mail.gmail.com>

Works good, I think.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080302/58c0485a/attachment.html 

From rworkman at slackbuilds.org  Tue Mar  4 10:23:57 2008
From: rworkman at slackbuilds.org (rworkman at slackbuilds.org)
Date: Tue, 04 Mar 2008 10:23:57 -0500
Subject: [Slackbuilds-users] Updates - 20080304
Message-ID: <47cd698d.zZA9PMKgEQOZQb2C%rworkman@slackbuilds.org>

Tue Mar  4 15:19:51 UTC 2008
development/Jinja: Added - Jinja is a sandboxed template engine.  It provides
  a Django-like non-XML syntax and compiles templates into executable python 
  code.  Thanks to Javier Rojas.  --rworkman
development/nvi: Added - Nvi is an implementation of the ex/vi text editor
  with a very small memory footprint. Thanks to rworkman. --Michiel
games/openarena: Bugfix - Fixed some file permissions.
  Thanks to Chess Griffin and Old Fogie.  --David Somero
multimedia/kdetv: Added - Kdetv is a KDE application that allows you to 
  watch television on your GNU/Linux box running KDE. 
  Thanks to Konstantin Oshovskij. --Michiel
network/kadu: Added - kadu is Gadu-Gadu protocol compatibile IM Messenger for
  Unix-like systems. Thanks to Andrzej Telszewski. --Michiel
network/squid: Bugfixes.  Thanks to Gianluca Toso and David Somero. --rworkman
network/xrdp: Added - XRDP is a remote desktop server for Linux.  It's a fully
  functional terminal server, capable of accepting connections from rdesktop 
  and Microsoft's terminal server / remote desktop clients.
  Thanks to Phil Warner.  --rworkman 
office/eqonomize: Added - Eqonomize is a simple kde application for managing
  personal finances.  Thanks to Heinz Wiesinger.  --rworkman

From rworkman at slackbuilds.org  Thu Mar  6 10:50:58 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 6 Mar 2008 10:50:58 -0500
Subject: [Slackbuilds-users] Updates - 20080306
Message-ID: <20080306155058.GA25749@slackbuilds.org>

Thu Mar  6 15:48:40 UTC 2008
desktop/QtCurve-Gtk2: Updated for version 0.56.3.
desktop/QtCurve-KDE3: Updated for version 0.56.3. 
  Thanks to Michiel van Wessem for both of these updates.  --rworkman
games/defcon: Updated for version 1.42.  Thanks to Daniel de Kok.  --rworkman
games/micropolis: Added - micropolis is a simulation game based on the sources
  from the original SimCity.  Thanks to Chess Griffin.  --rworkman
system/emelfm2: Updated for version 0.3.6. Thanks to Chess Griffin. --rworkman
system/pcsc-lite: Updated for version 1.4.99 and fixed pidfile location.
  Thank to Petar Petkoff for the bug report and to Luken Shiro for the
  update and fix.  --rworkman
system/xorg-server-xephyr: Added - Xephyr is a nested X-Client like Xnest, 
  but with some additional features like XRender support.
  Thanks to Heinz Wiesinger.  --rworkman
system/yakuake: Updated for version 2.8.1.  Thanks to Michiel van Wessem.

From rw at rlworkman.net  Thu Mar  6 17:14:36 2008
From: rw at rlworkman.net (Robby Workman)
Date: Thu, 06 Mar 2008 16:14:36 -0600
Subject: [Slackbuilds-users] Test Message - No response needed
Message-ID: <47D06CCC.1040205@rlworkman.net>

Just upgraded Mailman to fix a security issue and confirming success
:)

-RW

From erectlocution at gmail.com  Thu Mar  6 17:42:33 2008
From: erectlocution at gmail.com (Daniel Black)
Date: Thu, 6 Mar 2008 17:42:33 -0500
Subject: [Slackbuilds-users] Test Message - No response needed
In-Reply-To: <47D06CCC.1040205@rlworkman.net>
References: <47D06CCC.1040205@rlworkman.net>
Message-ID: <20080306224232.GA5934@dirac>

Hi,

On Thu, Mar 06, 2008 at 04:14:36PM -0600, Robby Workman wrote:
> Just upgraded Mailman to fix a security issue and confirming success
> :)

Pong.

From me at alkos333.net  Thu Mar  6 17:35:02 2008
From: me at alkos333.net (alkos333)
Date: Thu, 6 Mar 2008 16:35:02 -0600
Subject: [Slackbuilds-users] Test Message - No response needed
In-Reply-To: <20080306224232.GA5934@dirac>
References: <47D06CCC.1040205@rlworkman.net> <20080306224232.GA5934@dirac>
Message-ID: <a6f13f000803061435u3ea407ccsaa76c6f76d5bac67@mail.gmail.com>

3 1 2

On Thu, Mar 6, 2008 at 4:42 PM, Daniel Black <erectlocution at gmail.com> wrote:
> Hi,
>
>
>  On Thu, Mar 06, 2008 at 04:14:36PM -0600, Robby Workman wrote:
>  > Just upgraded Mailman to fix a security issue and confirming success
>  > :)
>
>  Pong.
>
>
> _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>

From joshuakwood at gmail.com  Thu Mar  6 18:34:43 2008
From: joshuakwood at gmail.com (JK Wood)
Date: Thu, 6 Mar 2008 17:34:43 -0600
Subject: [Slackbuilds-users] Test Message - No response needed
In-Reply-To: <47D06CCC.1040205@rlworkman.net>
References: <47D06CCC.1040205@rlworkman.net>
Message-ID: <6b6812630803061534g29a4c36h15e0aed77a851dfa@mail.gmail.com>

Email?  What email?  I didn't get any email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080306/bfa63698/attachment.html>

From mark at markwalling.org  Thu Mar  6 18:35:12 2008
From: mark at markwalling.org (Mark Walling)
Date: Thu, 06 Mar 2008 18:35:12 -0500
Subject: [Slackbuilds-users] Test Message - No response needed
In-Reply-To: <a6f13f000803061435u3ea407ccsaa76c6f76d5bac67@mail.gmail.com>
References: <47D06CCC.1040205@rlworkman.net> <20080306224232.GA5934@dirac>
	<a6f13f000803061435u3ea407ccsaa76c6f76d5bac67@mail.gmail.com>
Message-ID: <47D07FB0.7020302@markwalling.org>

alkos333 wrote:
> 3 1 2
> 
> On Thu, Mar 6, 2008 at 4:42 PM, Daniel Black <erectlocution at gmail.com> wrote:
>> Hi,
>>
>>
>>  On Thu, Mar 06, 2008 at 04:14:36PM -0600, Robby Workman wrote:
>>  > Just upgraded Mailman to fix a security issue and confirming success
>>  > :)
>>
>>  Pong.

4 8 15 16 23 42

-Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080306/4c726023/attachment.bin>

From me at alkos333.net  Thu Mar  6 18:38:38 2008
From: me at alkos333.net (alkos333)
Date: Thu, 6 Mar 2008 17:38:38 -0600
Subject: [Slackbuilds-users] Test Message - No response needed
In-Reply-To: <47D07FB0.7020302@markwalling.org>
References: <47D06CCC.1040205@rlworkman.net> <20080306224232.GA5934@dirac>
	<a6f13f000803061435u3ea407ccsaa76c6f76d5bac67@mail.gmail.com>
	<47D07FB0.7020302@markwalling.org>
Message-ID: <a6f13f000803061538v1dda5d2cq6f222ac09aec164e@mail.gmail.com>

No, 312  as in beer lol :)

On Thu, Mar 6, 2008 at 5:35 PM, Mark Walling <mark at markwalling.org> wrote:
> alkos333 wrote:
>  > 3 1 2
>  >
>  > On Thu, Mar 6, 2008 at 4:42 PM, Daniel Black <erectlocution at gmail.com> wrote:
>  >> Hi,
>  >>
>  >>
>  >>  On Thu, Mar 06, 2008 at 04:14:36PM -0600, Robby Workman wrote:
>  >>  > Just upgraded Mailman to fix a security issue and confirming success
>  >>  > :)
>  >>
>  >>  Pong.
>
>  4 8 15 16 23 42
>
>  -Mark
>
>
> _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>
>

From chris.punches at gmail.com  Thu Mar  6 23:23:12 2008
From: chris.punches at gmail.com (chris punches)
Date: Thu, 6 Mar 2008 23:23:12 -0500
Subject: [Slackbuilds-users] Test Message - No response needed
In-Reply-To: <a6f13f000803061538v1dda5d2cq6f222ac09aec164e@mail.gmail.com>
References: <47D06CCC.1040205@rlworkman.net> <20080306224232.GA5934@dirac>
	<a6f13f000803061435u3ea407ccsaa76c6f76d5bac67@mail.gmail.com>
	<47D07FB0.7020302@markwalling.org>
	<a6f13f000803061538v1dda5d2cq6f222ac09aec164e@mail.gmail.com>
Message-ID: <8c0ce5b60803062023y765d7f02q6ebe18e7084e55cc@mail.gmail.com>

that should go on noobfarm lol

On Thu, Mar 6, 2008 at 6:38 PM, alkos333 <me at alkos333.net> wrote:

> No, 312  as in beer lol :)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080306/ae586c63/attachment.html>

From ciol13 at gmail.com  Fri Mar  7 04:27:57 2008
From: ciol13 at gmail.com (ciol)
Date: Fri, 07 Mar 2008 10:27:57 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
Message-ID: <47D10A9D.1090405@gmail.com>

The following files are both installed by sip (sbo) and kdeaddon 
(slackware):

usr/lib/python2.5/site-packages/sip.so
usr/include/python2.5/sip.h
usr/lib/python2.5/site-packages/sipconfig.py
usr/bin/sip

From lukenshiro at ngi.it  Fri Mar  7 05:11:19 2008
From: lukenshiro at ngi.it (LukenShiro)
Date: Fri, 7 Mar 2008 11:11:19 +0100
Subject: [Slackbuilds-users] Updates - 20080306
In-Reply-To: <20080306155058.GA25749@slackbuilds.org>
References: <20080306155058.GA25749@slackbuilds.org>
Message-ID: <200803071111.20342.lukenshiro@ngi.it>

gioved? 6 marzo 2008, Robby Workman ha scritto:
> Thu Mar  6 15:48:40 UTC 2008
[..]
> system/pcsc-lite: Updated for 
> version 1.4.99 and fixed pidfile location. Thank to Petar Petkoff for
> the bug report and to Luken Shiro for the update and fix.  --rworkman

For some onforeseeable reasons, the package scripts for pcsc-lite on 
slackbuilds.org seem to be published in incorrect (that is: previous) 
version.
So I've just resubmitted the package (as a second build).

-- 
GNU/Linux * Slackware 'current'
LU #210970 LM #98222 SU #12583
"two rights don't make a wrong, but two Wrights made an airplane."

From asamardzic at gmail.com  Fri Mar  7 05:16:12 2008
From: asamardzic at gmail.com (Aleksandar B. Samardzic)
Date: Fri, 7 Mar 2008 11:16:12 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D10A9D.1090405@gmail.com>
References: <47D10A9D.1090405@gmail.com>
Message-ID: <d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>

On Fri, Mar 7, 2008 at 10:27 AM, ciol <ciol13 at gmail.com> wrote:
> The following files are both installed by sip (sbo) and kdeaddon
>  (slackware):
>
>  usr/lib/python2.5/site-packages/sip.so
>  usr/include/python2.5/sip.h
>  usr/lib/python2.5/site-packages/sipconfig.py
>  usr/bin/sip
>

I'm sip SlackBuild maintainer, thanks for the problem report.  The
Slackware package in question seems to be kdebindings, not kdeaddons;
indeed it already contains all non-doc files that are installed
through the sip SlackBuild, and I wasn't aware of that before at all.
The simplest resolution of the problem would be just to remove sip
SlackBuild from SBo.org, and to remove statement of dependency on sip
in README file of pyqt4 SlackBuild (sip is here because it is needed
for PyQt4).  However, there is a subtle issue here: sip and PyQt4
development are intertwined, and fresh builds of PyQt4 always need
latest sip, while on the other side kdebindings doesn't seem to by
fetching in sip that often.  For example, I'm tracking
slackware-current, and at the moment I have kdebindings 3.5.9 (last
updated by Pat at 02/29) installed; however, this package contains
rather old (4.6) sip version, while sip 4.7.2 or newer is required to
build latest PyQt4.  On the other side, sip functionality needed for
generating Python bindings for Qt 3, that is the reason why sip is
included in KDE 3 kdebindings package after all, is rather stable, so
it's understandable that KDE guys feel no urge to update to recent sip
code.

So, I'm really not sure what to do here...  Obviously, I was working
with sip package overwriting kdebindings installed files, and I
encountered no problems so far, but I'm using Python Qt bindings only
for my work, not KDE bindings, so I'm not sure is there a possibility
for any harm from alike overwriting; in any case, overwriting is
definitely not something that a SlackBuild should do.  So, the best
solution that I could think of would be to suggest to have both sip
and pyqt4 SlackBuilds temporarily removed.  Since nobody complained in
the meantime about wrong link to PyQt4 source tarball from pyqt4
SlackBuild page (PyQt4 guys seems to be hosting latest version tarball
only at their site), I guess that pyqt4 saw no much use anyway, so not
much harm would be made by removing it; on the other side, I'll
probably wait until KDE 4 included in Slackware (hopefully later this
year), in which case kdebindings will have to contain fresh sip
version, and then I'll update and repost this pyqt4 SlackBuild here.

So - Robby, or someone else: any further suggestion on this?  If not,
would you have these SlackBuilds removed?

Alex

PS. Albeit am big fan of all Qt and everything related, must confess
that this practice of having same names for programs and sometimes
other stuff in both Qt 3 and Qt 4, that obviously crept into related
packages, was really a fiasco...

From ciol13 at gmail.com  Fri Mar  7 06:24:54 2008
From: ciol13 at gmail.com (ciol)
Date: Fri, 07 Mar 2008 12:24:54 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>
References: <47D10A9D.1090405@gmail.com>
	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>
Message-ID: <47D12606.5000108@gmail.com>

A solution would be to install sip in another location.

Here is what I did:

python configure.py -b /user/local/bin \
                     -d /user/local/lib/python2.5/site-packages \
                     -e /user/local/include/python2.5 \
                     -v /user/local/share/sip

Then I needed:
export PYTHONPATH=/usr/local/lib/python2.5/site-packages/

I am really not an expert of python or qt, therefore there is maybe a 
better solution.

I also installed pyqt4 this way, not sure if it was necessary.

Aleksandar B. Samardzic wrote:
> On Fri, Mar 7, 2008 at 10:27 AM, ciol <ciol13 at gmail.com> wrote:
>> The following files are both installed by sip (sbo) and kdeaddon
>>  (slackware):
>>
>>  usr/lib/python2.5/site-packages/sip.so
>>  usr/include/python2.5/sip.h
>>  usr/lib/python2.5/site-packages/sipconfig.py
>>  usr/bin/sip
>>
> 
> I'm sip SlackBuild maintainer, thanks for the problem report.  The
> Slackware package in question seems to be kdebindings, not kdeaddons;
> indeed it already contains all non-doc files that are installed
> through the sip SlackBuild, and I wasn't aware of that before at all.
> The simplest resolution of the problem would be just to remove sip
> SlackBuild from SBo.org, and to remove statement of dependency on sip
> in README file of pyqt4 SlackBuild (sip is here because it is needed
> for PyQt4).  However, there is a subtle issue here: sip and PyQt4
> development are intertwined, and fresh builds of PyQt4 always need
> latest sip, while on the other side kdebindings doesn't seem to by
> fetching in sip that often.  For example, I'm tracking
> slackware-current, and at the moment I have kdebindings 3.5.9 (last
> updated by Pat at 02/29) installed; however, this package contains
> rather old (4.6) sip version, while sip 4.7.2 or newer is required to
> build latest PyQt4.  On the other side, sip functionality needed for
> generating Python bindings for Qt 3, that is the reason why sip is
> included in KDE 3 kdebindings package after all, is rather stable, so
> it's understandable that KDE guys feel no urge to update to recent sip
> code.
> 
> So, I'm really not sure what to do here...  Obviously, I was working
> with sip package overwriting kdebindings installed files, and I
> encountered no problems so far, but I'm using Python Qt bindings only
> for my work, not KDE bindings, so I'm not sure is there a possibility
> for any harm from alike overwriting; in any case, overwriting is
> definitely not something that a SlackBuild should do.  So, the best
> solution that I could think of would be to suggest to have both sip
> and pyqt4 SlackBuilds temporarily removed.  Since nobody complained in
> the meantime about wrong link to PyQt4 source tarball from pyqt4
> SlackBuild page (PyQt4 guys seems to be hosting latest version tarball
> only at their site), I guess that pyqt4 saw no much use anyway, so not
> much harm would be made by removing it; on the other side, I'll
> probably wait until KDE 4 included in Slackware (hopefully later this
> year), in which case kdebindings will have to contain fresh sip
> version, and then I'll update and repost this pyqt4 SlackBuild here.
> 
> So - Robby, or someone else: any further suggestion on this?  If not,
> would you have these SlackBuilds removed?
> 
> Alex
> 
> PS. Albeit am big fan of all Qt and everything related, must confess
> that this practice of having same names for programs and sometimes
> other stuff in both Qt 3 and Qt 4, that obviously crept into related
> packages, was really a fiasco...
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> 
> Please read the FAQ - http://slackbuilds.org/faq/
> 


From rworkman at slackbuilds.org  Fri Mar  7 09:31:50 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 07 Mar 2008 08:31:50 -0600
Subject: [Slackbuilds-users] pcsc-lite
In-Reply-To: <200803071111.20342.lukenshiro@ngi.it>
References: <20080306155058.GA25749@slackbuilds.org>
	<200803071111.20342.lukenshiro@ngi.it>
Message-ID: <47D151D6.9080207@slackbuilds.org>

LukenShiro wrote:
> gioved? 6 marzo 2008, Robby Workman ha scritto:
>> Thu Mar  6 15:48:40 UTC 2008
> [..]
>> system/pcsc-lite: Updated for 
>> version 1.4.99 and fixed pidfile location. Thank to Petar Petkoff for
>> the bug report and to Luken Shiro for the update and fix.  --rworkman
> 
> For some onforeseeable reasons, the package scripts for pcsc-lite on 
> slackbuilds.org seem to be published in incorrect (that is: previous) 
> version.
> So I've just resubmitted the package (as a second build).
> 


I don't understand.  What exactly is not correct?
It shows version 1.4.99 in the db and in the build script, and that's
the version I tested and built, and that's the version you submitted
(both times).  Am I missing something obvious?

-RW

From lukenshiro at ngi.it  Fri Mar  7 10:20:28 2008
From: lukenshiro at ngi.it (LukenShiro)
Date: Fri, 7 Mar 2008 16:20:28 +0100
Subject: [Slackbuilds-users] pcsc-lite
In-Reply-To: <47D151D6.9080207@slackbuilds.org>
References: <20080306155058.GA25749@slackbuilds.org>
	<200803071111.20342.lukenshiro@ngi.it>
	<47D151D6.9080207@slackbuilds.org>
Message-ID: <200803071620.28862.lukenshiro@ngi.it>

venerd? 7 marzo 2008, Robby Workman ha scritto:
> > For some onforeseeable reasons, the package scripts for pcsc-lite
> > on slackbuilds.org seem to be published in incorrect (that is:
> > previous) version.
> > So I've just resubmitted the package (as a second build).
>
> I don't understand.  What exactly is not correct?
> It shows version 1.4.99 in the db and in the build script, and that's
> the version I tested and built, and that's the version you submitted
> (both times).  Am I missing something obvious?

Sorry, Robby, but in
http://slackbuilds.org/repository/12.0/system/pcsc-lite/ -  "individual 
files" pcsc-lite.SlackBuild is old one (version 1.4.4, error in .pid 
directory).
Instead in pcsc-lite.tar.gz it seems to be the correct one (version 
1.4.99).

From rworkman at slackbuilds.org  Fri Mar  7 10:29:43 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 07 Mar 2008 09:29:43 -0600
Subject: [Slackbuilds-users] pcsc-lite
In-Reply-To: <200803071620.28862.lukenshiro@ngi.it>
References: <20080306155058.GA25749@slackbuilds.org>	<200803071111.20342.lukenshiro@ngi.it>	<47D151D6.9080207@slackbuilds.org>
	<200803071620.28862.lukenshiro@ngi.it>
Message-ID: <47D15F67.7010207@slackbuilds.org>

LukenShiro wrote:
> venerd? 7 marzo 2008, Robby Workman ha scritto:
>>> For some onforeseeable reasons, the package scripts for pcsc-lite
>>> on slackbuilds.org seem to be published in incorrect (that is:
>>> previous) version.
>>> So I've just resubmitted the package (as a second build).
>> I don't understand.  What exactly is not correct?
>> It shows version 1.4.99 in the db and in the build script, and that's
>> the version I tested and built, and that's the version you submitted
>> (both times).  Am I missing something obvious?
> 
> Sorry, Robby, but in
> http://slackbuilds.org/repository/12.0/system/pcsc-lite/ -  "individual 
> files" pcsc-lite.SlackBuild is old one (version 1.4.4, error in .pid 
> directory).
> Instead in pcsc-lite.tar.gz it seems to be the correct one (version 
> 1.4.99).


Hmm, it looks right to me.

http://slackbuilds.org/slackbuilds/12.0/system/pcsc-lite/pcsc-lite.SlackBuild

I promise I didn't fix this after mail :)  Are you sure you're not
behind a caching proxy or something?

-RW

From lukenshiro at ngi.it  Fri Mar  7 11:48:58 2008
From: lukenshiro at ngi.it (LukenShiro)
Date: Fri, 7 Mar 2008 17:48:58 +0100
Subject: [Slackbuilds-users] pcsc-lite
In-Reply-To: <47D15F67.7010207@slackbuilds.org>
References: <20080306155058.GA25749@slackbuilds.org>
	<200803071620.28862.lukenshiro@ngi.it>
	<47D15F67.7010207@slackbuilds.org>
Message-ID: <200803071748.58963.lukenshiro@ngi.it>

venerd? 7 marzo 2008, Robby Workman ha scritto:
> Hmm, it looks right to me.
>
> http://slackbuilds.org/slackbuilds/12.0/system/pcsc-lite/pcsc-lite.Sl
>ackBuild
>
> I promise I didn't fix this after mail :)  Are you sure you're not
> behind a caching proxy or something?

Urgh .. yes, I'm behind a caching proxy, but I believed to have 
refreshed the entire page in order to display current/up-to-date 
contents, my fault.
I've found the problem. Sorry to bother .. :-//

From rworkman at slackbuilds.org  Fri Mar  7 12:05:10 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 07 Mar 2008 11:05:10 -0600
Subject: [Slackbuilds-users] pcsc-lite
In-Reply-To: <200803071748.58963.lukenshiro@ngi.it>
References: <20080306155058.GA25749@slackbuilds.org>	<200803071620.28862.lukenshiro@ngi.it>	<47D15F67.7010207@slackbuilds.org>
	<200803071748.58963.lukenshiro@ngi.it>
Message-ID: <47D175C6.8080107@slackbuilds.org>

LukenShiro wrote:
> venerd? 7 marzo 2008, Robby Workman ha scritto:
>> Hmm, it looks right to me.
>>
>> http://slackbuilds.org/slackbuilds/12.0/system/pcsc-lite/pcsc-lite.Sl
>> ackBuild
>>
>> I promise I didn't fix this after mail :)  Are you sure you're not
>> behind a caching proxy or something?
> 
> Urgh .. yes, I'm behind a caching proxy, but I believed to have 
> refreshed the entire page in order to display current/up-to-date 
> contents, my fault.
> I've found the problem. Sorry to bother .. :-//


No worries :)

-RW

From asamardzic at gmail.com  Fri Mar  7 13:14:14 2008
From: asamardzic at gmail.com (Aleksandar B. Samardzic)
Date: Fri, 7 Mar 2008 19:14:14 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D12606.5000108@gmail.com>
References: <47D10A9D.1090405@gmail.com>
	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>
	<47D12606.5000108@gmail.com>
Message-ID: <d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>

On Fri, Mar 7, 2008 at 12:24 PM, ciol <ciol13 at gmail.com> wrote:
> A solution would be to install sip in another location.
>
>  Here is what I did:
>
>  python configure.py -b /user/local/bin \
>                      -d /user/local/lib/python2.5/site-packages \
>                      -e /user/local/include/python2.5 \
>                      -v /user/local/share/sip
>
>  Then I needed:
>  export PYTHONPATH=/usr/local/lib/python2.5/site-packages/
>
>  I am really not an expert of python or qt, therefore there is maybe a
>  better solution.
>
>  I also installed pyqt4 this way, not sure if it was necessary.

There is a slight issue with conformance this way - having files from
a package installed into /usr/local would be against LSB, and also,
more importantly, against long standing Unix tradition to only have
software compiled locally, from the source, installed there...

Alex

From ciol13 at gmail.com  Fri Mar  7 13:47:47 2008
From: ciol13 at gmail.com (ciol)
Date: Fri, 07 Mar 2008 19:47:47 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>
	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>
Message-ID: <47D18DD3.7090109@gmail.com>

Aleksandar B. Samardzic wrote:
> On Fri, Mar 7, 2008 at 12:24 PM, ciol <ciol13 at gmail.com> wrote:
>> A solution would be to install sip in another location.
>>
>>  Here is what I did:
>>
>>  python configure.py -b /user/local/bin \
>>                      -d /user/local/lib/python2.5/site-packages \
>>                      -e /user/local/include/python2.5 \
>>                      -v /user/local/share/sip
>>
>>  Then I needed:
>>  export PYTHONPATH=/usr/local/lib/python2.5/site-packages/
>>
>>  I am really not an expert of python or qt, therefore there is maybe a
>>  better solution.
>>
>>  I also installed pyqt4 this way, not sure if it was necessary.
> 
> There is a slight issue with conformance this way - having files from
> a package installed into /usr/local would be against LSB, and also,
> more importantly, against long standing Unix tradition to only have
> software compiled locally, from the source, installed there...

Slackbuilds from SBO belong to this tradition (in my opinion), but I do 
not want to speak about this again.

Anyway, why not create a /usr/slackbuilds-conflicts for these kind of 
conflicting packages?


From rworkman at slackbuilds.org  Fri Mar  7 14:04:05 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 07 Mar 2008 13:04:05 -0600
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D18DD3.7090109@gmail.com>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>
	<47D18DD3.7090109@gmail.com>
Message-ID: <47D191A5.9030601@slackbuilds.org>

ciol wrote:
> Aleksandar B. Samardzic wrote:
>> On Fri, Mar 7, 2008 at 12:24 PM, ciol <ciol13 at gmail.com> wrote:
>>> A solution would be to install sip in another location.
>>>
>>>  Here is what I did:
>>>
>>>  python configure.py -b /user/local/bin \
>>>                      -d /user/local/lib/python2.5/site-packages \
>>>                      -e /user/local/include/python2.5 \
>>>                      -v /user/local/share/sip
>>>
>>>  Then I needed:
>>>  export PYTHONPATH=/usr/local/lib/python2.5/site-packages/
>>>
>>>  I am really not an expert of python or qt, therefore there is maybe a
>>>  better solution.
>>>
>>>  I also installed pyqt4 this way, not sure if it was necessary.
>>
>> There is a slight issue with conformance this way - having files from
>> a package installed into /usr/local would be against LSB, and also,
>> more importantly, against long standing Unix tradition to only have
>> software compiled locally, from the source, installed there...
> 
> Slackbuilds from SBO belong to this tradition (in my opinion), but I do 
> not want to speak about this again.


I would argue that the distinction comes in when the software is
packaged and installed _as_a_package_; packaged software goes to
/usr (or /opt as appropriate), while non-packaged software goes to
/usr/local (or elsewhere as deemed appropriate by the sysadmin).
However, I agree that this has already been hashed out, and our
decision stands as is, so there's no need to drag it out again.


> Anyway, why not create a /usr/slackbuilds-conflicts for these kind of 
> conflicting packages?


This sort of information belongs in the README.
I'll have to defer judgment on what is *most* appropriate here to
those individuals more familiar with the affected software, but I'm
curious as to whether packaging sip in /opt/sip (assuming the relevant
environment variables are set) would work out okay, or if the included
sip stuff in kdebindings would conflict.  Maybe there are some other
concerns too...

-RW


From alan at lizella.net  Fri Mar  7 14:18:42 2008
From: alan at lizella.net (Alan Hicks)
Date: Fri, 07 Mar 2008 14:18:42 -0500
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D191A5.9030601@slackbuilds.org>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>	<47D18DD3.7090109@gmail.com>
	<47D191A5.9030601@slackbuilds.org>
Message-ID: <47D19512.1040401@lizella.net>

Robby Workman wrote:
>> Slackbuilds from SBO belong to this tradition (in my opinion), but I 
>> do not want to speak about this again.
> 
> I would argue that the distinction comes in when the software is
> packaged and installed _as_a_package_; packaged software goes to
> /usr (or /opt as appropriate), while non-packaged software goes to
> /usr/local (or elsewhere as deemed appropriate by the sysadmin).
> However, I agree that this has already been hashed out, and our
> decision stands as is, so there's no need to drag it out again.

I'm with Robby on this one and personally, I'm tired of it being discussed 
as well.  It's a very minor issue; I really don't understand why it 
sometimes turns into a holy war.  If you don't want packages compiled from 
SBo scripts in /usr, just edit the friggin' PREFIX variable and you're done.

>> Anyway, why not create a /usr/slackbuilds-conflicts for these kind of 
>> conflicting packages?

I've thought about that myself, or rather something like a 
/usr/lib/sbo-conflicts, but that's an ugly kludge if I've ever seen one. 
I'm just not confident that it wouldn't cause more problems than it fixes.

> This sort of information belongs in the README.
> I'll have to defer judgment on what is *most* appropriate here to
> those individuals more familiar with the affected software, but I'm
> curious as to whether packaging sip in /opt/sip (assuming the relevant
> environment variables are set) would work out okay, or if the included
> sip stuff in kdebindings would conflict.  Maybe there are some other
> concerns too...

In general, when we've had a conflicting package, we simply noted such in 
the README (see dropbear in 12.0 for an example).  In this case though, I'm 
really not certain what the best course of action really is.  Noting it in 
the README and including the script in the repo might cause problems for 
users down the road, and subsequently tarnish our image.  On the other hand, 
turning down a script that some one submits with the sort of humility and 
knowledge that Aleksandar showed when the problem was first reported isn't 
exactly the kind of thing I'd like to do either.

FTR, I'm for noting the conflict in the README, perhaps in ALL CAPS or 
something so it stands out.  Also, the script itself could warn.  Something 
like...

cat EOF
This script creates a package that is known to conflict with the kdebindings 
package included in Slackware.  While it has been tested, we cannot vouch 
that problems will not occur with other software which uses sip.  If you 
believe you have encountered such a problem, please remove this package and 
re-install kdebindings, then try again before filing a bug report to the 
maintainer or the mailing list.  Press ENTER to continue:
EOF
read NOTHING


Of course this isn't a perfect solution either, and I'm as open to 
suggestions here as anyone.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080307/259fba33/attachment.bin>

From rworkman at slackbuilds.org  Fri Mar  7 14:29:14 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 07 Mar 2008 13:29:14 -0600
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D19512.1040401@lizella.net>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>	<47D18DD3.7090109@gmail.com>	<47D191A5.9030601@slackbuilds.org>
	<47D19512.1040401@lizella.net>
Message-ID: <47D1978A.7030801@slackbuilds.org>

Alan Hicks wrote:
> Robby Workman wrote:
>>> Slackbuilds from SBO belong to this tradition (in my opinion), but I 
>>> do not want to speak about this again.
>>
>> I would argue that the distinction comes in when the software is
>> packaged and installed _as_a_package_; packaged software goes to
>> /usr (or /opt as appropriate), while non-packaged software goes to
>> /usr/local (or elsewhere as deemed appropriate by the sysadmin).
>> However, I agree that this has already been hashed out, and our
>> decision stands as is, so there's no need to drag it out again.
> 
> I'm with Robby on this one and personally, I'm tired of it being 
> discussed as well.  It's a very minor issue; I really don't understand 
> why it sometimes turns into a holy war.  If you don't want packages 
> compiled from SBo scripts in /usr, just edit the friggin' PREFIX 
> variable and you're done.


Maybe, but not in all cases - quite a few things in many of the
scripts are hardcoded for /usr, and I personally have no intentions
of changing that.  If someone doesn't like the way we do things, there
are plenty of domain names available.  This comment is not directed
at ciol (really), but there are far too many people who have all sorts
of grand ideas of how to "improve" things, but only if someone else
spends the time and does the work.  The way I see, so long as we're
the ones spending the time and doing the work, the only grand ideas
that get implemented are the ones that we like  ;-)


> FTR, I'm for noting the conflict in the README, perhaps in ALL CAPS or 
> something so it stands out.  Also, the script itself could warn.  
> Something like...
> 
> cat EOF
> This script creates a package that is known to conflict with the 
> kdebindings package included in Slackware.  While it has been tested, we 
> cannot vouch that problems will not occur with other software which uses 
> sip.  If you believe you have encountered such a problem, please remove 
> this package and re-install kdebindings, then try again before filing a 
> bug report to the maintainer or the mailing list.  Press ENTER to continue:
> EOF
> read NOTHING
> 
> 
> Of course this isn't a perfect solution either, and I'm as open to 
> suggestions here as anyone.


I think it's overkill.  Put that text in the README and that's good
enough until/unless we know more.

-RW

From ciol13 at gmail.com  Fri Mar  7 14:38:06 2008
From: ciol13 at gmail.com (ciol)
Date: Fri, 07 Mar 2008 20:38:06 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D19512.1040401@lizella.net>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>	<47D18DD3.7090109@gmail.com>	<47D191A5.9030601@slackbuilds.org>
	<47D19512.1040401@lizella.net>
Message-ID: <47D1999E.3080704@gmail.com>

Alan Hicks wrote:
> Robby Workman wrote:
>>> Slackbuilds from SBO belong to this tradition (in my opinion), but I 
>>> do not want to speak about this again.
>>
>> I would argue that the distinction comes in when the software is
>> packaged and installed _as_a_package_; packaged software goes to
>> /usr (or /opt as appropriate), while non-packaged software goes to
>> /usr/local (or elsewhere as deemed appropriate by the sysadmin).
>> However, I agree that this has already been hashed out, and our
>> decision stands as is, so there's no need to drag it out again.
> 
> I'm with Robby on this one and personally, I'm tired of it being 
> discussed as well.  It's a very minor issue; I really don't understand 
> why it sometimes turns into a holy war.  If you don't want packages 
> compiled from SBo scripts in /usr, just edit the friggin' PREFIX 
> variable and you're done.
> 
>>> Anyway, why not create a /usr/slackbuilds-conflicts for these kind of 
>>> conflicting packages?
> 
> I've thought about that myself, or rather something like a 
> /usr/lib/sbo-conflicts, but that's an ugly kludge if I've ever seen one. 
> I'm just not confident that it wouldn't cause more problems than it fixes.
> 
>> This sort of information belongs in the README.
>> I'll have to defer judgment on what is *most* appropriate here to
>> those individuals more familiar with the affected software, but I'm
>> curious as to whether packaging sip in /opt/sip (assuming the relevant
>> environment variables are set) would work out okay, or if the included
>> sip stuff in kdebindings would conflict.  Maybe there are some other
>> concerns too...
> 
> In general, when we've had a conflicting package, we simply noted such 
> in the README (see dropbear in 12.0 for an example).  In this case 
> though, I'm really not certain what the best course of action really 
> is.  Noting it in the README and including the script in the repo might 
> cause problems for users down the road, and subsequently tarnish our 
> image.  On the other hand, turning down a script that some one submits 
> with the sort of humility and knowledge that Aleksandar showed when the 
> problem was first reported isn't exactly the kind of thing I'd like to 
> do either.
> 
> FTR, I'm for noting the conflict in the README, perhaps in ALL CAPS or 
> something so it stands out.  Also, the script itself could warn.  
> Something like...
> 
> cat EOF
> This script creates a package that is known to conflict with the 
> kdebindings package included in Slackware.  While it has been tested, we 
> cannot vouch that problems will not occur with other software which uses 
> sip.  If you believe you have encountered such a problem, please remove 
> this package and re-install kdebindings, then try again before filing a 
> bug report to the maintainer or the mailing list.  Press ENTER to continue:
> EOF
> read NOTHING
> 
> 
> Of course this isn't a perfect solution either, and I'm as open to 
> suggestions here as anyone.
> 

I suggest to add variables, and to write an explanation in the README:

python configure.py -b $PREFIX/bin \
                     -d $PREFIX/lib/python2.5/site-packages \
                     -e $PREFIX/include/python2.5 \
                     -v $PREFIX/share/sip

with $PREFIX by default to /usr or /opt/sip or /usr/foobar, whatever you 
want. The user will have the choice.

From asamardzic at gmail.com  Sat Mar  8 07:55:21 2008
From: asamardzic at gmail.com (Aleksandar B. Samardzic)
Date: Sat, 8 Mar 2008 13:55:21 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D1999E.3080704@gmail.com>
References: <47D10A9D.1090405@gmail.com>
	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>
	<47D12606.5000108@gmail.com>
	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>
	<47D18DD3.7090109@gmail.com> <47D191A5.9030601@slackbuilds.org>
	<47D19512.1040401@lizella.net> <47D1999E.3080704@gmail.com>
Message-ID: <d20938700803080455i442e902dnba4be5c07db62085@mail.gmail.com>

On Fri, Mar 7, 2008 at 8:38 PM, ciol <ciol13 at gmail.com> wrote:
>
>  I suggest to add variables, and to write an explanation in the README:
>
>  python configure.py -b $PREFIX/bin \
>                      -d $PREFIX/lib/python2.5/site-packages \
>                      -e $PREFIX/include/python2.5 \
>                      -v $PREFIX/share/sip
>
>  with $PREFIX by default to /usr or /opt/sip or /usr/foobar, whatever you
>  want. The user will have the choice.

Thanks for all suggestions.  I've just posted an updated version of
sip SlackBuild, with big fat warning added to README file regarding
overwriting kdebindings files, and with support for PREFIX variable as
ciol suggested above (I haven't put "-v" flag there, because seems
unneeded to me, but the rest of configure step is exactly as above,
and PREFIX is set to /usr by default); I hope/think that would be OK
solution for now.  I've also posted pyqt4 SlackBuild, updated to its
latest version.  As usual, these two could be found for now at:
  http://slackbuilds.org/pending/sip.tar.gz
  http://slackbuilds.org/pending/pyqt4.tar.gz

If any additional issue encountered with these packages, please let me know.

Alex

From tihomiroff at gmail.com  Sat Mar  8 11:47:05 2008
From: tihomiroff at gmail.com (Petar Petkoff)
Date: Sat, 8 Mar 2008 18:47:05 +0200
Subject: [Slackbuilds-users] sK1, uniconvertor and cdr_explorer
Message-ID: <27edcc460803080847k2a8b7e67j4d0bcd005b4ad5a5@mail.gmail.com>

         Hi,
Someone to have experience with building of these packages?


Regards,
Petar Petkoff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080308/c288c036/attachment.html>

From volkerdi at slackware.com  Sun Mar  9 05:21:21 2008
From: volkerdi at slackware.com (Patrick J. Volkerding)
Date: Sun, 09 Mar 2008 04:21:21 -0500
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <47D18DD3.7090109@gmail.com>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>
	<47D18DD3.7090109@gmail.com>
Message-ID: <47D3AC11.1010404@slackware.com>

ciol wrote:
> Aleksandar B. Samardzic wrote:
>> There is a slight issue with conformance this way - having files from
>> a package installed into /usr/local would be against LSB, and also,
>> more importantly, against long standing Unix tradition to only have
>> software compiled locally, from the source, installed there...
> 
> Slackbuilds from SBO belong to this tradition (in my opinion), but I do 
> not want to speak about this again.

IMO, a package built from a proper SlackBuild should not be putting 
files in /usr/local.  They are manageable packages that _could_ be 
deployed on multiple systems, and even if they aren't it's a little 
different than using "make install".

The correct solution (I think) would be for python to have a 
vendor-python directory much like perl's vendor_perl that we've started 
to use.  But there are other overlaps here, too.

> Anyway, why not create a /usr/slackbuilds-conflicts for these kind of 
> conflicting packages?

What a terrible name.  Perhaps suggest that to the LSB as an offical 
directory under /usr?  ;-)

Perhaps /opt would be a better choice.  You can decide how to arrange 
your $PATH.

My $0.02.

Pat

From rworkman at slackbuilds.org  Mon Mar 10 10:38:46 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 10 Mar 2008 10:38:46 -0400
Subject: [Slackbuilds-users] Updates - 20080310
Message-ID: <20080310143846.GA13300@slackbuilds.org>

Mon Mar 10 14:37:22 UTC 2008
development/R: Added - R is a language and environment for statistical 
  computing and graphics.  Thanks to Joel Adamson. :) --rworkman
development/esvn: Added - esvn is a QT frontend for Subversion.
  Thanks to Iskar Enev.  --David Somero
development/sip: Noted conflicts with kdebindings package in Slackware.
  Thanks to ciol for noticing it, everyone on the -users mailing list
  who contributed to the discussion, and to Alex Samardzic for sending
  the update.  --rworkman
games/gnubg: Added - gnubg is GNU Backgammon.  Thanks to Erik Hanson. 
libraries/libarchive: Updated to version 2.4.13.
  Thanks to Heinz Wiesinger.  --David Somero
libraries/pyqt4: Updated for version 4.3.3.  
  Thanks to Alex Samardzic.  --rworkman
libraries/stfl: Added - stfl is a library which implements a curses-based 
  widget set for text terminals. Thanks to slakmagik.  --David Somero
multimedia/MPlayer: Included a patch to make MPlayer build with 2.6.24.x
  kernel includes.  --rworkman
network/aircrack-ng: Added - aircrack-ng is a WLAN auditing tool.
  Thanks to Yalla-One.  --David Somero
network/ganglia: Updated for version 3.0.7.
  Thanks to Cherife Li.  --David Somero
network/LimeWire: Updated to version 4.16.3
  Thanks to Robby Workman.  --David Somero
network/madwifi-driver: Updated to version 0.9.4.
  Thanks to Robby Workman.  --David Somero
network/madwifi-tools: Updated to version 0.9.4.
  Thanks to Robby Workman.  --David Somero
network/newsbeuter: Added - newsbeuter is a rss reader.
  Thanks to slakmagik.  --David Somero
office/kmobiletools: Added - kmobiletools is a KDE application that allows 
  you to control your mobile phone. Thanks to Heinz Wiesinger. --David Somero
system/ddrescue: Updated to version 1.8.
  Thanks to Heinz Wiesinger.  --David Somero
system/fish: Added the Friendly Interactive SHell.
  Thanks to Pierre Cazenave.  --rworkman
system/preload: Added - preload is an adaptive readahead daemon for preloading
  system libraries, making applications start faster.
  Thanks to Robby Workman.  --David Somero
system/zeroinstall-injector: Added the ZeroInstall Injector.
  Thanks to Michael Dupont.  --rworkman

From ciol13 at gmail.com  Mon Mar 10 15:03:12 2008
From: ciol13 at gmail.com (ciol)
Date: Mon, 10 Mar 2008 20:03:12 +0100
Subject: [Slackbuilds-users] sip conflicts with kdeaddon
In-Reply-To: <d20938700803080455i442e902dnba4be5c07db62085@mail.gmail.com>
References: <47D10A9D.1090405@gmail.com>	<d20938700803070216v581e9fb6w36c25c5cdef18b43@mail.gmail.com>	<47D12606.5000108@gmail.com>	<d20938700803071014k1efb3c32n8a3d408e6ef0253a@mail.gmail.com>	<47D18DD3.7090109@gmail.com>
	<47D191A5.9030601@slackbuilds.org>	<47D19512.1040401@lizella.net>
	<47D1999E.3080704@gmail.com>
	<d20938700803080455i442e902dnba4be5c07db62085@mail.gmail.com>
Message-ID: <47D585F0.8000109@gmail.com>

Aleksandar B. Samardzic wrote:
> On Fri, Mar 7, 2008 at 8:38 PM, ciol <ciol13 at gmail.com> wrote:
>>  I suggest to add variables, and to write an explanation in the README:
>>
>>  python configure.py -b $PREFIX/bin \
>>                      -d $PREFIX/lib/python2.5/site-packages \
>>                      -e $PREFIX/include/python2.5 \
>>                      -v $PREFIX/share/sip
>>
>>  with $PREFIX by default to /usr or /opt/sip or /usr/foobar, whatever you
>>  want. The user will have the choice.
> 
> Thanks for all suggestions.  I've just posted an updated version of
> sip SlackBuild, with big fat warning added to README file regarding
> overwriting kdebindings files, and with support for PREFIX variable as
> ciol suggested above (I haven't put "-v" flag there, because seems
> unneeded to me, but the rest of configure step is exactly as above,
> and PREFIX is set to /usr by default); I hope/think that would be OK
> solution for now.  I've also posted pyqt4 SlackBuild, updated to its
> latest version.  As usual, these two could be found for now at:
>   http://slackbuilds.org/pending/sip.tar.gz
>   http://slackbuilds.org/pending/pyqt4.tar.gz
> 
> If any additional issue encountered with these packages, please let me know.

I don't know why, but it _seems_ the -v flag is necessary, in 
sip.Slackbuild.
I tried your new slackbuilds. I set $PREFIX to another location.
I built sip, then pyqt4 (which required to set properly $PYTHONPATH), 
but "from PyQt4 import QtGui" did not work (whereas import PyQt4 did).
Then, I have built everything again, this time with the -v flag, and 
everything is working.

As I said, I am not a python expert. Maybe this flag is not necessary, 
for a person who knows what to do.


From pc_warner at yahoo.com  Tue Mar 11 02:04:55 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Mon, 10 Mar 2008 23:04:55 -0700 (PDT)
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
Message-ID: <935370.93650.qm@web57706.mail.re3.yahoo.com>

I just installed wifi-radar via the slackBuild and I noticed that it installed /etc/wifi-radar/wifi-radar.conf with read permissions to everyone.  This is not good considering this is the file your wireless keys are stored on.  I think the read perms for group and others should be taken away just like they are on /etc/rc.d/rc.wireless.conf.

Seeing as how some people may have already used this slackBuild without fixing the perms, the easiest way to fix this would probably be to add a 'chmod go-r /etc/wifi-radar/wifi-radar.conf*' at the end of doinst.sh.  That way, even if the user did not change their config we can be sure the perms are right.

--phil

       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080310/49100e32/attachment.html>

From ferenc.deak at gmail.com  Tue Mar 11 13:04:00 2008
From: ferenc.deak at gmail.com (Deak, Ferenc)
Date: Tue, 11 Mar 2008 18:04:00 +0100
Subject: [Slackbuilds-users] error compiling lablgtk on Slack 11 using
	SlackBuild from slackbuilds.org
In-Reply-To: <47BF3154.3000003@newmexicobusinesssolutions.com>
References: <47BF1B7E.4020605@newmexicobusinesssolutions.com>
	<47BF1BDA.7030209@slackadelic.com>
	<47BF1D10.4020001@newmexicobusinesssolutions.com>
	<47BF21F6.8080804@slackbuilds.org>
	<47BF3154.3000003@newmexicobusinesssolutions.com>
Message-ID: <c87dcd030803111004h3ea6aad0o55331fd225d133b7@mail.gmail.com>

Hi!

On Fri, Feb 22, 2008 at 9:32 PM, Brian Carey
<BrianC at newmexicobusinesssolutions.com> wrote:
>  Thanks for the answers. I tried with a later version, no luck. Tried
>  downgrading gtk, no luck either. Oh well, this machine is going to be
>  upgraded anyway, so I guess I'll wait for that. By the way, this does
>  compile fine on Slack 12 with DLG.
>

I'm the maintainer of lablgtk. Sorry for the late answer.
Have you solved the problem?
If not please check the newer version I submitted today.
You can get it from the pendiing queue at
http://slackbuilds.org/pending/lablgtk.tar.bz2,
or from the official place, after it is inserted into the official tree.

feco

From BrianC at newmexicobusinesssolutions.com  Tue Mar 11 16:05:33 2008
From: BrianC at newmexicobusinesssolutions.com (Brian Carey)
Date: Tue, 11 Mar 2008 14:05:33 -0600
Subject: [Slackbuilds-users] error compiling lablgtk on Slack 11 using
 SlackBuild from slackbuilds.org
In-Reply-To: <c87dcd030803111004h3ea6aad0o55331fd225d133b7@mail.gmail.com>
References: <47BF1B7E.4020605@newmexicobusinesssolutions.com>	<47BF1BDA.7030209@slackadelic.com>	<47BF1D10.4020001@newmexicobusinesssolutions.com>	<47BF21F6.8080804@slackbuilds.org>	<47BF3154.3000003@newmexicobusinesssolutions.com>
	<c87dcd030803111004h3ea6aad0o55331fd225d133b7@mail.gmail.com>
Message-ID: <47D6E60D.20109@newmexicobusinesssolutions.com>

Hi,

I do thank you for getting back to me. In fact, I ended up upgrading the 
server and so used the build for 12.0. Everything went perfectly! Thanks 
for your work.

Brian

Deak, Ferenc wrote:
> Hi!
>
> On Fri, Feb 22, 2008 at 9:32 PM, Brian Carey
> <BrianC at newmexicobusinesssolutions.com> wrote:
>   
>>  Thanks for the answers. I tried with a later version, no luck. Tried
>>  downgrading gtk, no luck either. Oh well, this machine is going to be
>>  upgraded anyway, so I guess I'll wait for that. By the way, this does
>>  compile fine on Slack 12 with DLG.
>>
>>     
>
> I'm the maintainer of lablgtk. Sorry for the late answer.
> Have you solved the problem?
> If not please check the newer version I submitted today.
> You can get it from the pendiing queue at
> http://slackbuilds.org/pending/lablgtk.tar.bz2,
> or from the official place, after it is inserted into the official tree.
>
> feco
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
> Please read the FAQ - http://slackbuilds.org/faq/
>
>
>   


From rworkman at slackbuilds.org  Tue Mar 11 16:19:44 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 11 Mar 2008 15:19:44 -0500
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <935370.93650.qm@web57706.mail.re3.yahoo.com>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>
Message-ID: <47D6E960.8040606@slackbuilds.org>

Phillip Warner wrote:
> I just installed wifi-radar via the slackBuild and I noticed that it 
> installed /etc/wifi-radar/wifi-radar.conf with read permissions to 
> everyone.  This is not good considering this is the file your wireless 
> keys are stored on.  I think the read perms for group and others should 
> be taken away just like they are on /etc/rc.d/rc.wireless.conf.


Agreed; I'll handle that in the next update.


> Seeing as how some people may have already used this slackBuild without 
> fixing the perms, the easiest way to fix this would probably be to add a 
> 'chmod go-r /etc/wifi-radar/wifi-radar.conf*' at the end of doinst.sh.  
> That way, even if the user did not change their config we can be sure 
> the perms are right.


Well, I'm not sure that's the right approach - there may very well be
some cases where the admin has assigned group permissions to be
readable or even writable, and we don't want to blow that away.
That being said, it is somewhat of a corner case, and I guess that,
all things considered, it's probably better for the admin to have to
reset those permissions than to have compromised private key.

-RW



From ciol13 at gmail.com  Tue Mar 11 16:55:34 2008
From: ciol13 at gmail.com (ciol)
Date: Tue, 11 Mar 2008 21:55:34 +0100
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <47D6E960.8040606@slackbuilds.org>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>
	<47D6E960.8040606@slackbuilds.org>
Message-ID: <47D6F1C6.8050806@gmail.com>

Robby Workman wrote:
> Phillip Warner wrote:
>> I just installed wifi-radar via the slackBuild and I noticed that it 
>> installed /etc/wifi-radar/wifi-radar.conf with read permissions to 
>> everyone.  This is not good considering this is the file your wireless 
>> keys are stored on.  I think the read perms for group and others 
>> should be taken away just like they are on /etc/rc.d/rc.wireless.conf.
> 
> 
> Agreed; I'll handle that in the next update.
> 
> 
>> Seeing as how some people may have already used this slackBuild 
>> without fixing the perms, the easiest way to fix this would probably 
>> be to add a 'chmod go-r /etc/wifi-radar/wifi-radar.conf*' at the end 
>> of doinst.sh.  That way, even if the user did not change their config 
>> we can be sure the perms are right.
> 
> 
> Well, I'm not sure that's the right approach - there may very well be
> some cases where the admin has assigned group permissions to be
> readable or even writable, and we don't want to blow that away.
> That being said, it is somewhat of a corner case, and I guess that,
> all things considered, it's probably better for the admin to have to
> reset those permissions than to have compromised private key.
> 
> -RW
> 

echo "WARNING: you should do a chmod -r [...]"

No?

From rworkman at slackbuilds.org  Tue Mar 11 17:21:08 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 11 Mar 2008 16:21:08 -0500
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <47D6F1C6.8050806@gmail.com>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>	<47D6E960.8040606@slackbuilds.org>
	<47D6F1C6.8050806@gmail.com>
Message-ID: <47D6F7C4.5020102@slackbuilds.org>

ciol wrote:
> Robby Workman wrote:
>> Well, I'm not sure that's the right approach - there may very well be
>> some cases where the admin has assigned group permissions to be
>> readable or even writable, and we don't want to blow that away.
>> That being said, it is somewhat of a corner case, and I guess that,
>> all things considered, it's probably better for the admin to have to
>> reset those permissions than to have compromised private key.
>>
> 
> echo "WARNING: you should do a chmod -r [...]"
> 
> No?


Well, that's an option, but there's no guarantee that it will be
seen (of course, there never it, but in this case especially).
If the package is installed as part of a large group, the message
will scroll past way too quickly to read...

I've got another idea, but I'll have to test - more later...

-RW

From joshuakwood at gmail.com  Tue Mar 11 18:58:40 2008
From: joshuakwood at gmail.com (JK Wood)
Date: Tue, 11 Mar 2008 17:58:40 -0500
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <47D6F7C4.5020102@slackbuilds.org>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>
	<47D6E960.8040606@slackbuilds.org> <47D6F1C6.8050806@gmail.com>
	<47D6F7C4.5020102@slackbuilds.org>
Message-ID: <6b6812630803111558l54d0dea7ie196bdb648530592@mail.gmail.com>

Erm... in the readme?

That's the usual thing,  as I understand it.  If you don't read the
documentation, that's your problem.

Just my two cents.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080311/d1634cf6/attachment.html>

From ciol13 at gmail.com  Wed Mar 12 04:56:03 2008
From: ciol13 at gmail.com (ciol)
Date: Wed, 12 Mar 2008 09:56:03 +0100
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <47D6F7C4.5020102@slackbuilds.org>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>
	<47D6E960.8040606@slackbuilds.org> <47D6F1C6.8050806@gmail.com>
	<47D6F7C4.5020102@slackbuilds.org>
Message-ID: <809f7dd60803120156p1d2b084fg86d85d5b30ba6ad5@mail.gmail.com>

2008/3/11, Robby Workman <rworkman at slackbuilds.org>:
>
> ciol wrote:
>
> > Robby Workman wrote:
> >> Well, I'm not sure that's the right approach - there may very well be
> >> some cases where the admin has assigned group permissions to be
> >> readable or even writable, and we don't want to blow that away.
> >> That being said, it is somewhat of a corner case, and I guess that,
> >> all things considered, it's probably better for the admin to have to
> >> reset those permissions than to have compromised private key.
> >>
> >
>
> > echo "WARNING: you should do a chmod -r [...]"
> >
> > No?
>
>
>
> Well, that's an option, but there's no guarantee that it will be
> seen (of course, there never it, but in this case especially).
> If the package is installed as part of a large group, the message
> will scroll past way too quickly to read...
>
> I've got another idea, but I'll have to test - more later...



slackbuilds-security at slackbuilds.org :o)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080312/4c8e499f/attachment.html>

From andrea.maccis at gmail.com  Wed Mar 12 07:45:17 2008
From: andrea.maccis at gmail.com (Andrea Maccis)
Date: Wed, 12 Mar 2008 12:45:17 +0100
Subject: [Slackbuilds-users] Is there something like slackpkg for
	slackbuilds?
In-Reply-To: <47D6F7C4.5020102@slackbuilds.org>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>	<47D6E960.8040606@slackbuilds.org>
	<47D6F1C6.8050806@gmail.com>	<47D6F7C4.5020102@slackbuilds.org>
Message-ID: <47D7C24D.3060205@gmail.com>

Is there something like slackpkg, for (automatic) search and download of 
slackbuilds archives, build and install|upgrade packages (via 
slackduilds.org repository)?
On google I don't found yet anything.
If you have already written of this, I apologize for the question, but I 
haven't yet read all mailing list archives :-)

Regards,
Andrea Maccis

From chess at chessgriffin.com  Wed Mar 12 08:48:48 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 12 Mar 2008 08:48:48 -0400
Subject: [Slackbuilds-users] Is there something like slackpkg
	for	slackbuilds?
In-Reply-To: <47D7C24D.3060205@gmail.com>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>	<47D6E960.8040606@slackbuilds.org>	<47D6F1C6.8050806@gmail.com>	<47D6F7C4.5020102@slackbuilds.org>
	<47D7C24D.3060205@gmail.com>
Message-ID: <47D7D130.8090405@chessgriffin.com>

Andrea Maccis wrote:
> Is there something like slackpkg, for (automatic) search and download of 
> slackbuilds archives, build and install|upgrade packages (via 
> slackduilds.org repository)?
> On google I don't found yet anything.
> If you have already written of this, I apologize for the question, but I 
> haven't yet read all mailing list archives :-)
> 
> Regards,
> Andrea Maccis

I am not sure if this is exactly what you are looking for, I but I've 
created a small script that will sync with the SBo repository and then 
automatically build packages from the repo.  It will download the 
source, check the md5sum, and compile the package.  It is located here:

http://chessgriffin.com/files/scripts/buildsbo/

I am in the process of rewriting it and renaming it "sbopkg" and it will 
be an ncurses (dialog) based tool like pkgtool that will sync with the 
repo, let you browse your local copy of repo, allow you to read the 
README of the packages in the repo etc., and then similarly download the 
source, check the md5sum, and build a package.  When I have it ready for 
testing, I'll post to the list.

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080312/c57d14cf/attachment.bin>

From mwalling at dstar.org  Wed Mar 12 08:50:38 2008
From: mwalling at dstar.org (Mark Walling)
Date: Wed, 12 Mar 2008 08:50:38 -0400
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <809f7dd60803120156p1d2b084fg86d85d5b30ba6ad5@mail.gmail.com>
References: <935370.93650.qm@web57706.mail.re3.yahoo.com>
	<47D6E960.8040606@slackbuilds.org> <47D6F1C6.8050806@gmail.com>
	<47D6F7C4.5020102@slackbuilds.org>
	<809f7dd60803120156p1d2b084fg86d85d5b30ba6ad5@mail.gmail.com>
Message-ID: <20080312125038.GB9404@you>

On 03/12/08, ciol wrote:
> 2008/3/11, Robby Workman <rworkman at slackbuilds.org>:
> >
> > ciol wrote:
> >
> > > Robby Workman wrote:
> > >> Well, I'm not sure that's the right approach - there may very well be
> > >> some cases where the admin has assigned group permissions to be
> > >> readable or even writable, and we don't want to blow that away.
> > >> That being said, it is somewhat of a corner case, and I guess that,
> > >> all things considered, it's probably better for the admin to have to
> > >> reset those permissions than to have compromised private key.
> > >>
> > >
> >
> > > echo "WARNING: you should do a chmod -r [...]"
> > >
> > > No?
> >
> >
> >
> > Well, that's an option, but there's no guarantee that it will be
> > seen (of course, there never it, but in this case especially).
> > If the package is installed as part of a large group, the message
> > will scroll past way too quickly to read...
> >
> > I've got another idea, but I'll have to test - more later...
> 
> 
> 
> slackbuilds-security at slackbuilds.org :o)

Mar 12 08:49:20 you postfix/smtp[9459]: 48ADC21BA0:
to=<slackbuilds-security-requests at slackbuilds.org>,
relay=cardinal.slackbuilds.org[216.23.247.24]:25, delay=0.77,
delays=0.14/0.02/0.44/0.17, dsn=4.1.1, status=deferred (host
cardinal.slackbuilds.org[216.23.247.24] said: 450 4.1.1
<slackbuilds-security-requests at slackbuilds.org>: Recipient address
rejected: User unknown in virtual alias table (in reply to RCPT TO
command))


-M

-------------- 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/20080312/d70cbb76/attachment-0001.bin>

From pc_warner at yahoo.com  Wed Mar 12 16:17:08 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Wed, 12 Mar 2008 13:17:08 -0700 (PDT)
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <mailman.33.1205326240.2026.slackbuilds-users@slackbuilds.org>
Message-ID: <900609.1127.qm@web57702.mail.re3.yahoo.com>


Robby Workman wrote:



Agreed; I'll handle that in the next update.


> Seeing as how some people may have already used this slackBuild without 
> fixing the perms, the easiest way to fix this would probably be to add a 
> 'chmod go-r /etc/wifi-radar/wifi-radar.conf*' at the end of doinst.sh.  
> That way, even if the user did not change their config we can be sure 
> the perms are right.


Well, I'm not sure that's the right approach - there may very well be
some cases where the admin has assigned group permissions to be
readable or even writable, and we don't want to blow that away.
That being said, it is somewhat of a corner case, and I guess that,
all things considered, it's probably better for the admin to have to
reset those permissions than to have compromised private key.

-RW

When it is updated could you also add keywords so that someone searching for "wifi radar" could find it easily.  I imagine some people would not realize slackBuilds.org has it if they forget the hyphen in the name or chose not to search for simply "wifi".


Perhaps, as a compromise, the solution for this slackBuild would be to add an option that would allow the perms to be left alone (say NOFIXPERMS=true ./wifi-radar.SlackBuild).  If the option was not specified or not set to true then the slackBuild would cat the appropriate line into the doinst.sh in order to fix the perms.  Some note about this should be added to the README.

--phil
       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080312/a3665b7d/attachment.html>

From joshuakwood at gmail.com  Wed Mar 12 17:22:02 2008
From: joshuakwood at gmail.com (JK Wood)
Date: Wed, 12 Mar 2008 16:22:02 -0500
Subject: [Slackbuilds-users] rtorrent has incorrect link
Message-ID: <6b6812630803121422u562b5b7di27ca49ed4ecebf2@mail.gmail.com>

On the rtorrent 0.8.0 page, the source link points to 0.7.6.  As you may
imagine, this will break the SlackBuild.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080312/cd851801/attachment.html>

From rworkman at slackbuilds.org  Wed Mar 12 17:41:34 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 12 Mar 2008 16:41:34 -0500
Subject: [Slackbuilds-users] rtorrent has incorrect link
In-Reply-To: <6b6812630803121422u562b5b7di27ca49ed4ecebf2@mail.gmail.com>
References: <6b6812630803121422u562b5b7di27ca49ed4ecebf2@mail.gmail.com>
Message-ID: <47D84E0E.7020601@slackbuilds.org>

JK Wood wrote:
> On the rtorrent 0.8.0 page, the source link points to 0.7.6.  As you may 
> imagine, this will break the SlackBuild.


Easy fix. Thanks!

-RW

From rworkman at slackbuilds.org  Thu Mar 13 00:54:03 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 12 Mar 2008 23:54:03 -0500
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <900609.1127.qm@web57702.mail.re3.yahoo.com>
References: <900609.1127.qm@web57702.mail.re3.yahoo.com>
Message-ID: <47D8B36B.2080602@slackbuilds.org>

Phillip Warner wrote:
> 
> When it is updated could you also add keywords so that someone searching 
> for "wifi radar" could find it easily.  I imagine some people would not 
> realize slackBuilds.org has it if they forget the hyphen in the name or 
> chose not to search for simply "wifi".


I will - good idea.  Double check it after the update goes public just
to make sure I didn't forget.


> Perhaps, as a compromise, the solution for this slackBuild would be to 
> add an option that would allow the perms to be left alone (say 
> NOFIXPERMS=true ./wifi-radar.SlackBuild).  If the option was not 
> specified or not set to true then the slackBuild would cat the 
> appropriate line into the doinst.sh in order to fix the perms.  Some 
> note about this should be added to the README.


After some thought, I decided to fix it in the script, put a note in
the README, and leave it at that.  For most people using this, they're
on a single-user box where it's not an issue anyway, and for those
people managing multi-user boxes (laptops - are there such creatures?)
:) well, they should be checking that sort of thing anyway.

-RW

From rshepard at appl-ecosys.com  Fri Mar 14 19:02:51 2008
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 14 Mar 2008 16:02:51 -0700 (PDT)
Subject: [Slackbuilds-users] Building libdv?
Message-ID: <Pine.LNX.4.64.0803141602320.30007@salmo.appl-ecosys.com>

   To view videos made with Apple's .mov format using mplayer requires
libdv.so,4. That's apparently not a library supplied with Slackware, so I
downloaded the source for libdv-1.0.0 then looked for a libdv.Slackware
script.

   I find scripts for libdvbpsi, libdvdcss, libdvdplay, and libdvdread, but
nothing for plain ol' libdv.

   Is there such a script, or should I use one of the *read and/or *play
libraries instead?

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From xgizzmo at gmail.com  Fri Mar 14 19:52:06 2008
From: xgizzmo at gmail.com (xgizzmo at gmail.com)
Date: Fri, 14 Mar 2008 19:52:06 -0400
Subject: [Slackbuilds-users] Building libdv?
In-Reply-To: <Pine.LNX.4.64.0803141602320.30007@salmo.appl-ecosys.com>
References: <Pine.LNX.4.64.0803141602320.30007@salmo.appl-ecosys.com>
Message-ID: <200803141952.06491.xgizzmo@gmail.com>

On Friday 14 March 2008 19:02:51 Rich Shepard wrote:
>    To view videos made with Apple's .mov format using mplayer requires
> libdv.so,4. That's apparently not a library supplied with Slackware, so I
> downloaded the source for libdv-1.0.0 then looked for a libdv.Slackware
> script.
> 
>    I find scripts for libdvbpsi, libdvdcss, libdvdplay, and libdvdread, but
> nothing for plain ol' libdv.
> 
>    Is there such a script, or should I use one of the *read and/or *play
> libraries instead?
> 
> Rich
> 

libdv is a software CODEC for DV (digital video) not DVD related.
There is a slackbuild for it on slackbuilds.org  

http://slackbuilds.org/repository/12.0/libraries/libdv/

From rshepard at appl-ecosys.com  Fri Mar 14 20:13:20 2008
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 14 Mar 2008 17:13:20 -0700 (PDT)
Subject: [Slackbuilds-users] Building libdv?
In-Reply-To: <200803141952.06491.xgizzmo@gmail.com>
References: <Pine.LNX.4.64.0803141602320.30007@salmo.appl-ecosys.com>
	<200803141952.06491.xgizzmo@gmail.com>
Message-ID: <Pine.LNX.4.64.0803141712170.30007@salmo.appl-ecosys.com>

On Fri, 14 Mar 2008, xgizzmo at gmail.com wrote:

> libdv is a software CODEC for DV (digital video) not DVD related.
> There is a slackbuild for it on slackbuilds.org
>
> http://slackbuilds.org/repository/12.0/libraries/libdv/

   Thank you. I was looking in the 11.0 section and didn't see it. (I cannot
upgrade my main workstation/server until an issue of matplotlib and
python-2.5 is resolved.)

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From me at alkos333.net  Sat Mar 15 08:10:22 2008
From: me at alkos333.net (alkos333)
Date: Sat, 15 Mar 2008 07:10:22 -0500
Subject: [Slackbuilds-users] libevent 1.3e Breaks tor
Message-ID: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>

I noticed that after updating to 1.3e, whenever I try to start tor, I
get the following:

Starting tor: /usr/bin/tor: error while loading shared libraries:
libevent-1.2a.so.1: cannot open shared object file: No such file or
directory

From me at alkos333.net  Sat Mar 15 08:13:24 2008
From: me at alkos333.net (alkos333)
Date: Sat, 15 Mar 2008 07:13:24 -0500
Subject: [Slackbuilds-users] libevent 1.3e Breaks tor
In-Reply-To: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>
References: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>
Message-ID: <a6f13f000803150513y76174e5dlb67341cff0df83b5@mail.gmail.com>

Creating a symlink seems to solve the problem though:

ln -s libevent-1.3e.so.1 libevent-1.2a.so.1

On Sat, Mar 15, 2008 at 7:10 AM, alkos333 <me at alkos333.net> wrote:
> I noticed that after updating to 1.3e, whenever I try to start tor, I
>  get the following:
>
>  Starting tor: /usr/bin/tor: error while loading shared libraries:
>  libevent-1.2a.so.1: cannot open shared object file: No such file or
>  directory
>

From ciol13 at gmail.com  Sat Mar 15 08:22:39 2008
From: ciol13 at gmail.com (ciol)
Date: Sat, 15 Mar 2008 13:22:39 +0100
Subject: [Slackbuilds-users] libevent 1.3e Breaks tor
In-Reply-To: <a6f13f000803150513y76174e5dlb67341cff0df83b5@mail.gmail.com>
References: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>
	<a6f13f000803150513y76174e5dlb67341cff0df83b5@mail.gmail.com>
Message-ID: <47DBBF8F.8050606@gmail.com>

alkos333 wrote:
> Creating a symlink seems to solve the problem though:
> 
> ln -s libevent-1.3e.so.1 libevent-1.2a.so.1
> 
> On Sat, Mar 15, 2008 at 7:10 AM, alkos333 <me at alkos333.net> wrote:
>> I noticed that after updating to 1.3e, whenever I try to start tor, I
>>  get the following:
>>
>>  Starting tor: /usr/bin/tor: error while loading shared libraries:
>>  libevent-1.2a.so.1: cannot open shared object file: No such file or
>>  directory
>>

Maybe you should recompile tor.

From me at alkos333.net  Sat Mar 15 08:25:35 2008
From: me at alkos333.net (alkos333)
Date: Sat, 15 Mar 2008 07:25:35 -0500
Subject: [Slackbuilds-users] libevent 1.3e Breaks tor
In-Reply-To: <47DBBF8F.8050606@gmail.com>
References: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>
	<a6f13f000803150513y76174e5dlb67341cff0df83b5@mail.gmail.com>
	<47DBBF8F.8050606@gmail.com>
Message-ID: <a6f13f000803150525r7643332atc1ab9542f7c707dd@mail.gmail.com>

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

That helped.  However, if this is the layout:

lrwxrwxrwx 1 root root    22 2008-03-15 06:01 libevent-1.3e.so.1 ->
libevent-1.3e.so.1.0.3*
- -rwxr-xr-x 1 root root 84472 2008-03-14 13:58 libevent-1.3e.so.1.0.3*
- -rwxr-xr-x 1 root root   818 2008-03-14 13:58 libevent.la*
lrwxrwxrwx 1 root root    22 2008-03-15 06:01 libevent.so ->
libevent-1.3e.so.1.0.3*


I don't know why tor wouldn't use libevent.so as suppose to libevent-1.2a.so.1

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

iD8DBQFH27G/R+OWhEg1RV8RAtSuAJ4lsW/00EGItJV71Hauo4ubaAkPowCaAk8L
vYbA0UXjOhTc+J60NAAe/wU=
=hvYZ
-----END PGP SIGNATURE-----

On Sat, Mar 15, 2008 at 7:22 AM, ciol <ciol13 at gmail.com> wrote:
>
> alkos333 wrote:
>  > Creating a symlink seems to solve the problem though:
>  >
>  > ln -s libevent-1.3e.so.1 libevent-1.2a.so.1
>  >
>  > On Sat, Mar 15, 2008 at 7:10 AM, alkos333 <me at alkos333.net> wrote:
>  >> I noticed that after updating to 1.3e, whenever I try to start tor, I
>  >>  get the following:
>  >>
>  >>  Starting tor: /usr/bin/tor: error while loading shared libraries:
>  >>  libevent-1.2a.so.1: cannot open shared object file: No such file or
>  >>  directory
>  >>
>
>  Maybe you should recompile tor.
>  _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>

From xgizzmo at gmail.com  Sat Mar 15 08:26:03 2008
From: xgizzmo at gmail.com (xgizzmo at gmail.com)
Date: Sat, 15 Mar 2008 08:26:03 -0400
Subject: [Slackbuilds-users] libevent 1.3e Breaks tor
In-Reply-To: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>
References: <a6f13f000803150510p651cadc4k750beff75e216e26@mail.gmail.com>
Message-ID: <200803150826.03298.xgizzmo@gmail.com>

On Saturday 15 March 2008 08:10:22 alkos333 wrote:
> I noticed that after updating to 1.3e, whenever I try to start tor, I
> get the following:
> 
> Starting tor: /usr/bin/tor: error while loading shared libraries:
> libevent-1.2a.so.1: cannot open shared object file: No such file or
> directory

Did you recompile tor after you updated  libevent?
Creating a symlink to a different libevent version is allmost sure to
 cause problems.



From donniepennington at mac.com  Sun Mar 16 11:29:14 2008
From: donniepennington at mac.com (Donnie Pennington)
Date: Sun, 16 Mar 2008 10:29:14 -0500
Subject: [Slackbuilds-users] ttf-sil-gentium
Message-ID: <20080316152913.GB27125@macslack.purdigital.net>

I encountered a problem with the ttf-sil-gentium SlackBuild.  The source
download link gives me this error message in firefox:

The URL is incorrect: no Site ID provided (cannot continue).

I went to the homepage directly and successfully downloaded the
GNU/Linux source tarball but then encountered a problem with the name of
the tarball as downloaded vs what the script expects.  When I manually
changed the name of the tarball, the SlackBuild worked.

Actual name of the downloaded tarball:
ttf-sil-gentium_1.0.2.tar.gz

Name SlackBuild script expects:
ttf-gentium_1.02.orig.tar.gz

-- 
Donnie Pennington


From elyk03 at gmail.com  Sun Mar 16 15:18:58 2008
From: elyk03 at gmail.com (Kyle Guinn)
Date: Sun, 16 Mar 2008 14:18:58 -0500
Subject: [Slackbuilds-users] ttf-sil-gentium
In-Reply-To: <20080316152913.GB27125@macslack.purdigital.net>
References: <20080316152913.GB27125@macslack.purdigital.net>
Message-ID: <2dcaacad0803161218p10b59836o92d85d61d036998f@mail.gmail.com>

I remember we've had problems with that download link before -- the
script has been modified a few times to compensate for it.  Rather
than providing a direct link to the file, the SIL website links to a
script named render_download.php.  The script takes an argument
representing the file to retrieve.  Here is the correct link:
http://scripts.sil.org/cms/scripts/render_download.php?site_id=nrsi&format=file&media_id=Gentium_102_L_tar&filename=%2Fttf-sil-gentium_1.0.2.tar.gz

There is no problem when saving this link with some browsers, but wget
does not approve.  The link must be quoted, and even then wget will
save it with the filename
"render_download.php?site_id\=nrsi&format\=file&media_id\=Gentium_102_L_tar&filename\=ttf-sil-gentium_1.0.2.tar.gz".
  This is not useful for those who install packages from SBo using a
script.

I propose that we save the file ttf-sil-gentium_1.0.2.tar.gz on SBo
similar to how we save some CVS snapshots.  Would this be a problem?

-Kyle

From rworkman at slackbuilds.org  Mon Mar 17 12:38:28 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 17 Mar 2008 11:38:28 -0500
Subject: [Slackbuilds-users] ttf-sil-gentium
In-Reply-To: <2dcaacad0803161218p10b59836o92d85d61d036998f@mail.gmail.com>
References: <20080316152913.GB27125@macslack.purdigital.net>
	<2dcaacad0803161218p10b59836o92d85d61d036998f@mail.gmail.com>
Message-ID: <47DE9E84.5070608@slackbuilds.org>

Kyle Guinn wrote:
> I remember we've had problems with that download link before -- the
> script has been modified a few times to compensate for it.  Rather
> than providing a direct link to the file, the SIL website links to a
> script named render_download.php.  The script takes an argument
> representing the file to retrieve.  Here is the correct link:
> http://scripts.sil.org/cms/scripts/render_download.php?site_id=nrsi&format=file&media_id=Gentium_102_L_tar&filename=%2Fttf-sil-gentium_1.0.2.tar.gz
> 
> There is no problem when saving this link with some browsers, but wget
> does not approve.  The link must be quoted, and even then wget will
> save it with the filename
> "render_download.php?site_id\=nrsi&format\=file&media_id\=Gentium_102_L_tar&filename\=ttf-sil-gentium_1.0.2.tar.gz".
>   This is not useful for those who install packages from SBo using a
> script.
> 
> I propose that we save the file ttf-sil-gentium_1.0.2.tar.gz on SBo
> similar to how we save some CVS snapshots.  Would this be a problem?


Well, the .info file has a link to the sources from a debian mirror,
but the db entry wasn't updated.  I don't know if I did that when I
approved it, or if someone has fixed it since then, but it's correct
now.

Just in case the debian mirror goes dark, I do have a copy of it on
the SBo server, but we won't use it unless it becomes necessary.

Thanks!

-RW

From rworkman at slackbuilds.org  Mon Mar 17 00:14:30 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 17 Mar 2008 00:14:30 -0400
Subject: [Slackbuilds-users] Updates - 20080317
Message-ID: <20080317041430.GA1203@slackbuilds.org>

For those of you who keep a local rsync mirror, hang on a few minutes
before you start it.  I'm going to be regenerating all of the tarballs
and gpg signatures so that the build scripts are mode 0755 inside the
tarballs.  I'll post a note here when I'm finished.  --rworkman

Mon Mar 17 17:08:04 UTC 2008
desktop/QtCurve-Gtk2: Updated to version 0.57.1.
  Thanks to Michiel van Wessem.  --David Somero
desktop/QtCurve-KDE3: Updated to version 0.57.1.
  Thanks to Michiel van Wessem.  --David Somero
desktop/industrial-cursor-theme: Added - industrial-cursor-theme is a
  flat-looking cursor theme for X. Thanks to "slakmagik".  --David Somero
desktop/root-tail: Added - Displays a given file anywhere on your X11 root 
  window.  Thanks to "slakmagik".  --David Somero
development/gc: Updated to version 7.0.
  Thanks to Robby Workman.  --David Somero
development/yaml: Added - YAML.pm implements a YAML Loader and Dumper based
  on the YAML 1.0 specification. Thanks to Heinz Wiesinger.  --David Somero
libraries/libopensync: Added - libopensync is a plugin-based application
  that basically provides a framework for syncing groups.
  Thanks to Heinz Wiesinger.  --David Somero
libraries/libsndfile: Included a patch to allow compilation against versions
  of flac newer than 1.1.2.  Thanks to Eric Hameleers.
multimedia/shntool: Added - shntool is a multi-purpose WAVE data processing 
  and reporting utility. Thanks to "slakmagik".  --David Somero
multimedia/shorten: Added - shorten reduces the size of waveform files.
  Thanks to "slakmagik".  --David Somero
network/fail2ban: Updated to version 0.8.2.
  Thanks to Nishant Limbachia.  --David Somero
network/openrdate: Added - openrdate is an alternative to netdate and 
  ntpd / ntpdate.  Thanks to "slakmagik".  --David Somero
network/opera: Updated to version 9.26.
  Thanks to Martin Lefebvre.  --David Somero
network/w3m: Added - w3m is a light weight text-mode web browser.
  Thanks to "slakmagik".  --David Somero
network/wicd: Updated to version 1.4.2.
  Thanks to Robby Workman.  --David Somero
office/tellico: Updated to version 1.3.1.
  Thanks to Michiel van Wessem.  --David Somero
system/qdu: Added - QDU is a graphical disk usage tool.
  Thanks to Rodney Cobb.  --David Somero
system/treesize: Added - treesize is a disk consumption analyzing tool.
  Thanks to Rodney Cobb.  --David Somero
system/wine: Updated to version 0.9.57.
  Thanks to Robby Workman.  --David Somero

From rworkman at slackbuilds.org  Mon Mar 17 13:25:27 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 17 Mar 2008 12:25:27 -0500
Subject: [Slackbuilds-users] Updates - 20080317
In-Reply-To: <20080317041430.GA1203@slackbuilds.org>
References: <20080317041430.GA1203@slackbuilds.org>
Message-ID: <47DEA987.8070606@slackbuilds.org>

Robby Workman wrote:
> For those of you who keep a local rsync mirror, hang on a few minutes
> before you start it.  I'm going to be regenerating all of the tarballs
> and gpg signatures so that the build scripts are mode 0755 inside the
> tarballs.  I'll post a note here when I'm finished.  --rworkman


Done. Commence rsync. :)

From rworkman at slackbuilds.org  Mon Mar 17 13:41:27 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 17 Mar 2008 12:41:27 -0500
Subject: [Slackbuilds-users] ATTN Maintainers: Perl stuff
Message-ID: <47DEAD47.10306@slackbuilds.org>

For those of you who are listed as MAINTAINERS for scripts building
perl stuff, you should probably go ahead and be looking into making
them work with the new vender_perl changes in -current.

Don't submit new builds to us just yet - we'll let you know when
we're ready - but it's probably best to go ahead and be looking into
what's needed.

Thanks!

-RW

From sleistinger at verizon.net  Mon Mar 17 19:16:44 2008
From: sleistinger at verizon.net (Steve)
Date: Mon, 17 Mar 2008 19:16:44 -0400
Subject: [Slackbuilds-users] ATTN Maintainers: Perl stuff
In-Reply-To: <47DEAD47.10306@slackbuilds.org>
References: <47DEAD47.10306@slackbuilds.org>
Message-ID: <200803171916.45034.sleistinger@verizon.net>

On Monday 17 March 2008 01:41:27 pm Robby Workman wrote:
> For those of you who are listed as MAINTAINERS for scripts building
> perl stuff, you should probably go ahead and be looking into making
> them work with the new vender_perl changes in -current.
>
> Don't submit new builds to us just yet - we'll let you know when
> we're ready - but it's probably best to go ahead and be looking into
> what's needed.
>
> Thanks!
>
> -RW

Out of curiosity ...

Is there an accepted means of notifying responsible parties as to whether a 
script for 12.0 fails to build without error in -current?  I suspect a note 
with a fix to the maintainer would be helpful, but to do so too soon and 
uninvited could turn a well intentioned act into an annoyance.

Apologies if this has been discussed in an earlier thread.

Steve





From pc_warner at yahoo.com  Tue Mar 18 02:38:30 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Mon, 17 Mar 2008 23:38:30 -0700 (PDT)
Subject: [Slackbuilds-users] wifi-radar.conf need better perms
In-Reply-To: <mailman.4.1205536743.2549.slackbuilds-users@slackbuilds.org>
Message-ID: <278337.22988.qm@web57712.mail.re3.yahoo.com>



Date: Wed, 12 Mar 2008 23:54:03 -0500
From: Robby Workman 
Subject: Re: [Slackbuilds-users] wifi-radar.conf need better perms
To: "SlackBuilds.org Users List" 
Message-ID: <47D8B36B.2080602 at slackbuilds.org>
Content-Type: text/plain; charset=UTF-8; format=flowed

Phillip Warner wrote:
> 
> When it is updated could you also add keywords so that someone searching 
> for "wifi radar" could find it easily.  I imagine some people would not 
> realize slackBuilds.org has it if they forget the hyphen in the name or 
> chose not to search for simply "wifi".


I will - good idea.  Double check it after the update goes public just
to make sure I didn't forget.


> Perhaps, as a compromise, the solution for this slackBuild would be to 
> add an option that would allow the perms to be left alone (say 
> NOFIXPERMS=true ./wifi-radar.SlackBuild).  If the option was not 
> specified or not set to true then the slackBuild would cat the 
> appropriate line into the doinst.sh in order to fix the perms.  Some 
> note about this should be added to the README.


After some thought, I decided to fix it in the script, put a note in
the README, and leave it at that.  For most people using this, they're
on a single-user box where it's not an issue anyway, and for those
people managing multi-user boxes (laptops - are there such creatures?)
:) well, they should be checking that sort of thing anyway.

-RW


The search tags and the slackBuild look much better.  Thank you.

--phil





       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080317/79bc9131/attachment-0001.html>

From pc_warner at yahoo.com  Tue Mar 18 03:13:15 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Tue, 18 Mar 2008 00:13:15 -0700 (PDT)
Subject: [Slackbuilds-users] Problem building WINE 0.9.57 with fontforge
Message-ID: <732442.4014.qm@web57714.mail.re3.yahoo.com>

WINE failed to build for me when I had fontforge-20080302 installed (via the slackBuild).  I was building for i686 with no OpenGL.  Here is the error I received:

Missing glyph for char 0e5b
../tools/fnt2fon system-874-96-16.fnt vgas874.fon
System 10 pts 96x96 dpi
fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
Copyright (c) 2000-2008 by George Williams.
 Executable based on sources from 21:54 GMT 2-Mar-2008.
  Library based on sources from 21:54 GMT 2-Mar-2008.
  make[1]: *** [marlett.ttf] Segmentation fault
  make[1]: *** Deleting file `marlett.ttf'
  make[1]: Leaving directory `/tmp/SBo/wine-0.9.57/fonts'
  make: *** [fonts] Error 2

Normally, I have built WINE without fontforge and have never had any problems (including this version if fontforge is not installed).  I decided to try it since the slackBuild README suggested it.

It should be noted that I did this before the updated slackBuild for 0.9.57 was released, but there were not any significant changes to the script that I saw (except for the fact that the docs are now copied to $PKG/usr/doc/$PRGNAM-$VERSION/$DOC and I have no idea what $DOC is).

Thank you in advance for any help.

--phil
       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080318/5a854683/attachment.htm>

From alien at slackbuilds.org  Tue Mar 18 17:34:09 2008
From: alien at slackbuilds.org (Eric Hameleers)
Date: Tue, 18 Mar 2008 22:34:09 +0100
Subject: [Slackbuilds-users] Problem building WINE 0.9.57 with fontforge
In-Reply-To: <732442.4014.qm@web57714.mail.re3.yahoo.com>
References: <732442.4014.qm@web57714.mail.re3.yahoo.com>
Message-ID: <47E03551.2040902@slackbuilds.org>

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

Phillip Warner wrote:
| WINE failed to build for me when I had fontforge-20080302 installed
(via
| the slackBuild).  I was building for i686 with no OpenGL.  Here is the
| error I received:
|
| Missing glyph for char 0e5b
| ../tools/fnt2fon system-874-96-16.fnt vgas874.fon
| System 10 pts 96x96 dpi
| fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
| Copyright (c) 2000-2008 by George Williams.
|  Executable based on sources from 21:54 GMT 2-Mar-2008.
|   Library based on sources from 21:54 GMT 2-Mar-2008.
|   make[1]: *** [marlett.ttf] Segmentation fault
|   make[1]: *** Deleting file `marlett.ttf'
|   make[1]: Leaving directory `/tmp/SBo/wine-0.9.57/fonts'
|   make: *** [fonts] Error 2

I rebuilt my own Wine to check on that error - on a fresh install of
Slackware 12.0 and fontforge-20080203 installed I get:

Missing glyph for char 0e5b
../tools/fnt2fon system-874-96-16.fnt vgas874.fon
System 10 pts 96x96 dpi
fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahoma.sfd tahoma.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahomabd.sfd tahomabd.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
make[1]: Leaving directory `/tmp/build/tmp-wine/wine-0.9.57/fonts'

To be sure I also ran the SBo script for Wine and got similar results:

Missing glyph for char 0e5b
../tools/fnt2fon system-874-96-16.fnt vgas874.fon
System 10 pts 96x96 dpi
fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahoma.sfd tahoma.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahomabd.sfd tahomabd.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
make[1]: Leaving directory `/tmp/SBo/wine-0.9.57/fonts'

I have zero errors.
Note that I use a fontforge from 3 feb 2008 while you have fonforge of
~ 2 march 2008.

I seriously doubt that the fontforge difference is the cause of your
segfaults though.

Cheers, Eric

- --

Eric Hameleers                     >')
ICQ: 151799386                     ( \
Jabber: alien at jabber.xs4all.nl      ^^`
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH4DVCXlaqr6dcvaARAp9VAJ9h7OE4WYVkGkiJLLrL+15zgw7X4QCfUtmE
B9tIGhZXZTBcx2CJYK6PjeY=
=I031
-----END PGP SIGNATURE-----

From rworkman at slackbuilds.org  Wed Mar 19 00:46:18 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 18 Mar 2008 23:46:18 -0500
Subject: [Slackbuilds-users] Problem building WINE 0.9.57 with fontforge
In-Reply-To: <47E03551.2040902@slackbuilds.org>
References: <732442.4014.qm@web57714.mail.re3.yahoo.com>
	<47E03551.2040902@slackbuilds.org>
Message-ID: <47E09A9A.7020200@slackbuilds.org>

Eric Hameleers wrote:
> Phillip Warner wrote:
> | WINE failed to build for me when I had fontforge-20080302 installed
> (via
> | the slackBuild).  I was building for i686 with no OpenGL.  Here is the
> | error I received:
> |
> | Missing glyph for char 0e5b
> | ../tools/fnt2fon system-874-96-16.fnt vgas874.fon
> | System 10 pts 96x96 dpi
> | fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
> | Copyright (c) 2000-2008 by George Williams.
> |  Executable based on sources from 21:54 GMT 2-Mar-2008.
> |   Library based on sources from 21:54 GMT 2-Mar-2008.
> |   make[1]: *** [marlett.ttf] Segmentation fault
> |   make[1]: *** Deleting file `marlett.ttf'
> |   make[1]: Leaving directory `/tmp/SBo/wine-0.9.57/fonts'
> |   make: *** [fonts] Error 2
> 
> I rebuilt my own Wine to check on that error - on a fresh install of
> Slackware 12.0 and fontforge-20080203 installed I get: [SNIPPED]
> 
> I have zero errors.
> Note that I use a fontforge from 3 feb 2008 while you have fonforge of
> ~ 2 march 2008.
> 
> I seriously doubt that the fontforge difference is the cause of your
> segfaults though.


I've just built wine-0.9.57 against fontforge-20070808 (last night) on
both 12.0 and -current, and I didn't get any errors.  I'll make a note
here to try and get latest fontforge tomorrow to see how things go
with them...

-RW

From rworkman at slackbuilds.org  Wed Mar 19 00:52:31 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 18 Mar 2008 23:52:31 -0500
Subject: [Slackbuilds-users] ATTN Maintainers: Perl stuff
In-Reply-To: <200803171916.45034.sleistinger@verizon.net>
References: <47DEAD47.10306@slackbuilds.org>
	<200803171916.45034.sleistinger@verizon.net>
Message-ID: <47E09C0F.8000006@slackbuilds.org>

Steve wrote:
> On Monday 17 March 2008 01:41:27 pm Robby Workman wrote:
>> For those of you who are listed as MAINTAINERS for scripts building
>> perl stuff, you should probably go ahead and be looking into making
>> them work with the new vender_perl changes in -current.
>>
>> Don't submit new builds to us just yet - we'll let you know when
>> we're ready - but it's probably best to go ahead and be looking into
>> what's needed.
>>
> 
> Is there an accepted means of notifying responsible parties as to whether a 
> script for 12.0 fails to build without error in -current?  I suspect a note 
> with a fix to the maintainer would be helpful, but to do so too soon and 
> uninvited could turn a well intentioned act into an annoyance.


It's probably about the right time to start looking into that, so...
sure, feel free.  If you do, please advise them that we're not ready
for the -current (12.1) submissions, but that now is a good time to
be testing and/or updating them.

That being said, I've handled glibmm, cairomm, and gtkmm here (as I
needed them for something else), and also synaptics.  There are a few
things we'll need to remove from the repo (fuse, ntfs-3g, pygtk, and
so on), and there's the perl changes to consider.  Other than those
things, all of the stuff in the 12.0 repo should transition over to
12.1 with very little difficulty.

-RW


From yallaone at gmail.com  Wed Mar 19 16:56:45 2008
From: yallaone at gmail.com (Halim Issa)
Date: Wed, 19 Mar 2008 21:56:45 +0100
Subject: [Slackbuilds-users] digikam slackbuild updated for v0.9.3 fails -
	anyone know why?
Message-ID: <200803192156.45850.yallaone@gmail.com>

Hello,

I'm trying to build digikam with the slackbuilds from SBo, updated for the 
latest versions to get 0.9.3 to build. I now see why perhaps the SBo version 
has stayed with 0.9.2, as building the latest version fails spectacularly

I'm building on slackware-current with the following dependencies:
kipi-plugins 0.1.5, 
libkipi 0.1.5
libkexif 0.2.5
libkexiv2 0.1.6
libkdcraw 0.1.4

All are built with SBo SlackBuilds with only version numbers updated. 
Everything else left as-is.

Here's where it fails:

CII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE  -MT 
editorwindow.lo -MD -MP -MF ".deps/editorwindow.Tpo" -c -o editorwindow.lo 
editorwindow.cpp; \
        then mv -f ".deps/editorwindow.Tpo" ".deps/editorwindow.Plo"; else 
rm -f ".deps/editorwindow.Tpo"; exit 1; fi
editorwindow.cpp: In member function 'void 
Digikam::EditorWindow::applyStandardSettings()':
editorwindow.cpp:888: error: 'class KDcrawIface::RawDecodingSettings' has no 
member named 'automaticColorBalance'
editorwindow.cpp:889: error: 'class KDcrawIface::RawDecodingSettings' has no 
member named 'cameraColorBalance'
make[5]: *** [editorwindow.lo] Error 1
make[5]: Leaving directory 
`/tmp/SBo/digikam-0.9.3/digikam/utilities/imageeditor/editor'

Does anyone have any hints on how to get 0.9.3 with the timeline to build?

(I also tried 0.9.4-beta1, but it depends on various yet-to-be-released 
library-versions and is as such not a realistic target)

 -y1

From fecaraballo at gmail.com  Wed Mar 19 18:21:25 2008
From: fecaraballo at gmail.com (Frank Caraballo)
Date: Wed, 19 Mar 2008 15:21:25 -0700
Subject: [Slackbuilds-users] digikam slackbuild updated for v0.9.3 fails
 -	anyone know why?
In-Reply-To: <200803192156.45850.yallaone@gmail.com>
References: <200803192156.45850.yallaone@gmail.com>
Message-ID: <47E191E5.7030607@gmail.com>

Halim Issa wrote:
> Hello,
>
> I'm trying to build digikam with the slackbuilds from SBo, updated for the 
> latest versions to get 0.9.3 to build. I now see why perhaps the SBo version 
> has stayed with 0.9.2, as building the latest version fails spectacularly
>
> I'm building on slackware-current with the following dependencies:
> kipi-plugins 0.1.5, 
> libkipi 0.1.5
> libkexif 0.2.5
> libkexiv2 0.1.6
> libkdcraw 0.1.4
>
> All are built with SBo SlackBuilds with only version numbers updated. 
> Everything else left as-is.
>
> Here's where it fails:
>
> CII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE  -MT 
> editorwindow.lo -MD -MP -MF ".deps/editorwindow.Tpo" -c -o editorwindow.lo 
> editorwindow.cpp; \
>         then mv -f ".deps/editorwindow.Tpo" ".deps/editorwindow.Plo"; else 
> rm -f ".deps/editorwindow.Tpo"; exit 1; fi
> editorwindow.cpp: In member function 'void 
> Digikam::EditorWindow::applyStandardSettings()':
> editorwindow.cpp:888: error: 'class KDcrawIface::RawDecodingSettings' has no 
> member named 'automaticColorBalance'
> editorwindow.cpp:889: error: 'class KDcrawIface::RawDecodingSettings' has no 
> member named 'cameraColorBalance'
> make[5]: *** [editorwindow.lo] Error 1
> make[5]: Leaving directory 
> `/tmp/SBo/digikam-0.9.3/digikam/utilities/imageeditor/editor'
>
> Does anyone have any hints on how to get 0.9.3 with the timeline to build?
>
> (I also tried 0.9.4-beta1, but it depends on various yet-to-be-released 
> library-versions and is as such not a realistic target)
>
>  -y1
>
>   
I was actually waiting on updating all of the digiKam related scripts 
until the next version of kipi-plugins had came out. Wouldn't you know 
it, kipi-plugins 0.1.5 will not compile without libkdcraw 0.1.4 and 
digiKam 0.9.3 will not compile with it. I would suggest installing 
libkdcraw 0.1.3 and kipi-plugins 0.1.4 (or 0.1.5-rc2) for now to get 
digiKam 0.9.3 to compile.

Once digiKam 0.9.4 and its dependencies are released, I will update the 
scripts again.

Frank

FYI, I just uploaded the digiKam 0.9.3 updates today. They are currently 
in pending and should be approved shortly.


From pc_warner at yahoo.com  Wed Mar 19 20:57:04 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Wed, 19 Mar 2008 17:57:04 -0700 (PDT)
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and suggestions
	for xinit scripts
Message-ID: <585981.24577.qm@web57707.mail.re3.yahoo.com>

The xinitrc.openbox file included with the SlackBuild should be modified at the end so that it says:
exec openbox-session

instead of:
exec openbox

With the way it is, the autostart.sh file is not executed when starting openbox.  This is important for setting up a stand alone openbox session.  The file's output is slightly noisy out of the box, however, as it does not redirect stderror and it checks for some things that slackware does not have out of the box.  If this bothers people sed can fix that easily.  This doesn't affect any functionality.

Also, since openbox includes scripts for starting KDE or GNOME sessions with openbox as the windows manager, it would be nice to have some xinitrc files for them as well.  I propose that there be an option to include each of their respective xinitrc scripts.  They could be called xinitrc.kde-openbox and xinitrc.gnome-openbox, and the kde one could be included by default.  The files would be the same as the xinitrc.openbox file with the exception of the last line:

exec openbox-kde-session
- or -
exec openbox-gnome-session

I do not have GNOME, so I did not test the proposed xinitrc file for it.  However, I did test xinitrc.kde-openbox in both runlevels 3 and 4 and everything ran well.

Having these xinitrc scripts will make it easier for the user to select them as their default session (with xwmconfig), and it will make it so the sessions are an option in KDM/GDM/XDM.

With these changes I think the openbox slackBuild would be improved and the resultant behavior would be more in line with the expectations based on the openbox documentation:
http://icculus.org/openbox/index.php/Help:Getting_started#Using_Openbox_without_a_desktop_environment_.28The_lightweight_approach.29

--phil

       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080319/5967a7d8/attachment-0001.htm>

From chess at chessgriffin.com  Wed Mar 19 23:28:26 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 19 Mar 2008 23:28:26 -0400
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
	suggestions for xinit scripts
In-Reply-To: <585981.24577.qm@web57707.mail.re3.yahoo.com>
References: <585981.24577.qm@web57707.mail.re3.yahoo.com>
Message-ID: <20080319232826.33231faf@bsdbob.localdomain>

On Wed, 19 Mar 2008 17:57:04 -0700 (PDT)
Phillip Warner <pc_warner at yahoo.com> wrote:

> The xinitrc.openbox file included with the SlackBuild should be
> modified at the end so that it says: exec openbox-session
> 
> instead of:
> exec openbox
> 
> With the way it is, the autostart.sh file is not executed when
> starting openbox.  This is important for setting up a stand alone
> openbox session.  The file's output is slightly noisy out of the box,
> however, as it does not redirect stderror and it checks for some
> things that slackware does not have out of the box.  If this bothers
> people sed can fix that easily.  This doesn't affect any
> functionality.
> 
> Also, since openbox includes scripts for starting KDE or GNOME
> sessions with openbox as the windows manager, it would be nice to
> have some xinitrc files for them as well.  I propose that there be an
> option to include each of their respective xinitrc scripts.  They
> could be called xinitrc.kde-openbox and xinitrc.gnome-openbox, and
> the kde one could be included by default.  The files would be the
> same as the xinitrc.openbox file with the exception of the last line:
> 
> exec openbox-kde-session
> - or -
> exec openbox-gnome-session
> 
> I do not have GNOME, so I did not test the proposed xinitrc file for
> it.  However, I did test xinitrc.kde-openbox in both runlevels 3 and
> 4 and everything ran well.
> 
> Having these xinitrc scripts will make it easier for the user to
> select them as their default session (with xwmconfig), and it will
> make it so the sessions are an option in KDM/GDM/XDM.
> 
> With these changes I think the openbox slackBuild would be improved
> and the resultant behavior would be more in line with the
> expectations based on the openbox documentation:
> http://icculus.org/openbox/index.php/Help:Getting_started#Using_Openbox_without_a_desktop_environment_.28The_lightweight_approach.29
> 
> --phil
> 

Without having looked into this yet, I am inclined to agree with you on
the first point.  As to the second point, it seems that maybe this is
more of a user-configurable option and not actually necessary for the
stand-alone usage of Openbox?  Couldn't the user do what you say
manually instead of crowding xwmconfig with a bunch of Openbox
choices?  Or by option do you mean an option that can be enabled in the
SlackBuild?  I don't use Openbox within KDE or GNOME so maybe I'm
missing something.  In any event, I'm just throwing out some thoughts.


-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080319/c04753d6/attachment.asc>

From dosnlinux at gmail.com  Thu Mar 20 00:25:29 2008
From: dosnlinux at gmail.com (Lehman Black)
Date: Wed, 19 Mar 2008 23:25:29 -0500
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
	suggestions for xinit scripts
In-Reply-To: <20080319232826.33231faf@bsdbob.localdomain>
References: <585981.24577.qm@web57707.mail.re3.yahoo.com>
	<20080319232826.33231faf@bsdbob.localdomain>
Message-ID: <cc3ba8ff0803192125x3f6ebc37maa53f07c29d1ad02@mail.gmail.com>

The extra xinit scripts are not essential for the functioning of the
package, so I would put them in /usr/doc/ and put a note in README.
Including them by default would be like including xinit scripts for using
Xfwm4 with KDE and GNOME.


On 3/19/08, Chess Griffin <chess at chessgriffin.com> wrote:
>
> On Wed, 19 Mar 2008 17:57:04 -0700 (PDT)
> Phillip Warner <pc_warner at yahoo.com> wrote:
>
> > The xinitrc.openbox file included with the SlackBuild should be
> > modified at the end so that it says: exec openbox-session
> >
> > instead of:
> > exec openbox
> >
> > With the way it is, the autostart.sh file is not executed when
> > starting openbox.  This is important for setting up a stand alone
> > openbox session.  The file's output is slightly noisy out of the box,
> > however, as it does not redirect stderror and it checks for some
> > things that slackware does not have out of the box.  If this bothers
> > people sed can fix that easily.  This doesn't affect any
> > functionality.
> >
> > Also, since openbox includes scripts for starting KDE or GNOME
> > sessions with openbox as the windows manager, it would be nice to
> > have some xinitrc files for them as well.  I propose that there be an
> > option to include each of their respective xinitrc scripts.  They
> > could be called xinitrc.kde-openbox and xinitrc.gnome-openbox, and
> > the kde one could be included by default.  The files would be the
> > same as the xinitrc.openbox file with the exception of the last line:
> >
> > exec openbox-kde-session
> > - or -
> > exec openbox-gnome-session
> >
> > I do not have GNOME, so I did not test the proposed xinitrc file for
> > it.  However, I did test xinitrc.kde-openbox in both runlevels 3 and
> > 4 and everything ran well.
> >
> > Having these xinitrc scripts will make it easier for the user to
> > select them as their default session (with xwmconfig), and it will
> > make it so the sessions are an option in KDM/GDM/XDM.
> >
> > With these changes I think the openbox slackBuild would be improved
> > and the resultant behavior would be more in line with the
> > expectations based on the openbox documentation:
> >
> http://icculus.org/openbox/index.php/Help:Getting_started#Using_Openbox_without_a_desktop_environment_.28The_lightweight_approach.29
> >
> > --phil
> >
>
>
> Without having looked into this yet, I am inclined to agree with you on
> the first point.  As to the second point, it seems that maybe this is
> more of a user-configurable option and not actually necessary for the
> stand-alone usage of Openbox?  Couldn't the user do what you say
> manually instead of crowding xwmconfig with a bunch of Openbox
> choices?  Or by option do you mean an option that can be enabled in the
> SlackBuild?  I don't use Openbox within KDE or GNOME so maybe I'm
> missing something.  In any event, I'm just throwing out some thoughts.
>
>
>
> --
> Chess Griffin
> GPG Public Key:  0x0C7558C3
> http://www.chessgriffin.com
>
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
> Please read the FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080319/0a1e7df5/attachment.htm>

From pc_warner at yahoo.com  Thu Mar 20 00:38:15 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Wed, 19 Mar 2008 21:38:15 -0700 (PDT)
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
	suggestions for xinit scripts
In-Reply-To: <20080319232826.33231faf@bsdbob.localdomain>
Message-ID: <236570.31976.qm@web57712.mail.re3.yahoo.com>

I was suggesting that it should be an option in the SlackBuild script so that, if selected, the user can easily have the KDE-openbox and/or GNOME-openbox option in xwmconfig and XDM/KDM/GDM.  So, for instance, if someone using the slackBuild wanted the  xinitrc script for GNOME, but not for KDE, then they could execute

GXINIT=yes KXINIT=no ./openbox.SlackBuild

or just modify the slackBuild accordingly.  By default, I think the option for the GNOME-openbox .xinitrc should be disabled and the KDE-openbox .xinitrc should be enabled since GNOME is not on stock Slackware but KDE is.

If someone thinks this will give them too many options then they can easily disable it, but I think a lot of Slackware users who use KDE or GNOME may only want Openbox to replace their DE's window manager.  Plus, the openbox online documentation talks about running openbox within KDE from KDM, and I think the slackBuild would be nicer if it could set that up.

--phil

Chess Griffin <chess at chessgriffin.com> wrote: On Wed, 19 Mar 2008 17:57:04 -0700 (PDT)
Phillip Warner 
 wrote:

> The xinitrc.openbox file included with the SlackBuild should be
> modified at the end so that it says: exec openbox-session
> 
> instead of:
> exec openbox
> 
> With the way it is, the autostart.sh file is not executed when
> starting openbox.  This is important for setting up a stand alone
> openbox session.  The file's output is slightly noisy out of the box,
> however, as it does not redirect stderror and it checks for some
> things that slackware does not have out of the box.  If this bothers
> people sed can fix that easily.  This doesn't affect any
> functionality.
> 
> Also, since openbox includes scripts for starting KDE or GNOME
> sessions with openbox as the windows manager, it would be nice to
> have some xinitrc files for them as well.  I propose that there be an
> option to include each of their respective xinitrc scripts.  They
> could be called xinitrc.kde-openbox and xinitrc.gnome-openbox, and
> the kde one could be included by default.  The files would be the
> same as the xinitrc.openbox file with the exception of the last line:
> 
> exec openbox-kde-session
> - or -
> exec openbox-gnome-session
> 
> I do not have GNOME, so I did not test the proposed xinitrc file for
> it.  However, I did test xinitrc.kde-openbox in both runlevels 3 and
> 4 and everything ran well.
> 
> Having these xinitrc scripts will make it easier for the user to
> select them as their default session (with xwmconfig), and it will
> make it so the sessions are an option in KDM/GDM/XDM.
> 
> With these changes I think the openbox slackBuild would be improved
> and the resultant behavior would be more in line with the
> expectations based on the openbox documentation:
> http://icculus.org/openbox/index.php/Help:Getting_started#Using_Openbox_without_a_desktop_environment_.28The_lightweight_approach.29
> 
> --phil
> 

Without having looked into this yet, I am inclined to agree with you on
the first point.  As to the second point, it seems that maybe this is
more of a user-configurable option and not actually necessary for the
stand-alone usage of Openbox?  Couldn't the user do what you say
manually instead of crowding xwmconfig with a bunch of Openbox
choices?  Or by option do you mean an option that can be enabled in the
SlackBuild?  I don't use Openbox within KDE or GNOME so maybe I'm
missing something.  In any event, I'm just throwing out some thoughts.


-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com



       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080319/43564a3b/attachment.htm>

From pc_warner at yahoo.com  Thu Mar 20 03:15:32 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Thu, 20 Mar 2008 00:15:32 -0700 (PDT)
Subject: [Slackbuilds-users] Problem building WINE 0.9.57 with fontforge
In-Reply-To: <mailman.18.1205974626.2549.slackbuilds-users@slackbuilds.org>
Message-ID: <534036.51687.qm@web57710.mail.re3.yahoo.com>

The problem is fontforge.  I just downgraded fontforge to the 20080203 release and everything compiled fine.

--phil

Date: Tue, 18 Mar 2008 22:34:09 +0100
From: Eric Hameleers 
Subject: Re: [Slackbuilds-users] Problem building WINE 0.9.57 with
 fontforge
To: "SlackBuilds.org Users List" 
Message-ID: <47E03551.2040902 at slackbuilds.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

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

Phillip Warner wrote:
| WINE failed to build for me when I had fontforge-20080302 installed
(via
| the slackBuild).  I was building for i686 with no OpenGL.  Here is the
| error I received:
|
| Missing glyph for char 0e5b
| ../tools/fnt2fon system-874-96-16.fnt vgas874.fon
| System 10 pts 96x96 dpi
| fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
| Copyright (c) 2000-2008 by George Williams.
|  Executable based on sources from 21:54 GMT 2-Mar-2008.
|   Library based on sources from 21:54 GMT 2-Mar-2008.
|   make[1]: *** [marlett.ttf] Segmentation fault
|   make[1]: *** Deleting file `marlett.ttf'
|   make[1]: Leaving directory `/tmp/SBo/wine-0.9.57/fonts'
|   make: *** [fonts] Error 2

I rebuilt my own Wine to check on that error - on a fresh install of
Slackware 12.0 and fontforge-20080203 installed I get:

Missing glyph for char 0e5b
../tools/fnt2fon system-874-96-16.fnt vgas874.fon
System 10 pts 96x96 dpi
fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahoma.sfd tahoma.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahomabd.sfd tahomabd.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
make[1]: Leaving directory `/tmp/build/tmp-wine/wine-0.9.57/fonts'

To be sure I also ran the SBo script for Wine and got similar results:

Missing glyph for char 0e5b
../tools/fnt2fon system-874-96-16.fnt vgas874.fon
System 10 pts 96x96 dpi
fontforge -script ../fonts/genttf.ff marlett.sfd marlett.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahoma.sfd tahoma.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
fontforge -script ../fonts/genttf.ff tahomabd.sfd tahomabd.ttf
Copyright (c) 2000-2008 by George Williams.
~ Executable based on sources from 20:25 GMT 3-Feb-2008.
~ Library based on sources from 03:08 GMT 3-Feb-2008.
make[1]: Leaving directory `/tmp/SBo/wine-0.9.57/fonts'

I have zero errors.
Note that I use a fontforge from 3 feb 2008 while you have fonforge of
~ 2 march 2008.

I seriously doubt that the fontforge difference is the cause of your
segfaults though.

Cheers, Eric

- --

Eric Hameleers                     >')
ICQ: 151799386                     ( \
Jabber: alien at jabber.xs4all.nl      ^^`
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH4DVCXlaqr6dcvaARAp9VAJ9h7OE4WYVkGkiJLLrL+15zgw7X4QCfUtmE
B9tIGhZXZTBcx2CJYK6PjeY=
=I031
-----END PGP SIGNATURE-----



       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080320/a27f3e51/attachment-0001.htm>

From yallaone at gmail.com  Thu Mar 20 13:31:22 2008
From: yallaone at gmail.com (Halim Issa)
Date: Thu, 20 Mar 2008 18:31:22 +0100
Subject: [Slackbuilds-users]
	=?iso-8859-1?q?digikam_slackbuild_updated_for?=
	=?iso-8859-1?q?_v0=2E9=2E3_fails_-=09anyone_know_why=3F?=
In-Reply-To: <47E191E5.7030607@gmail.com>
References: <200803192156.45850.yallaone@gmail.com>
	<47E191E5.7030607@gmail.com>
Message-ID: <200803201831.22391.yallaone@gmail.com>

On Wednesday 19 March 2008 23:21:25 Frank Caraballo wrote:
> kipi-plugins 0.1.5 will not compile without libkdcraw 0.1.4 and
> digiKam 0.9.3 will not compile with it. I would suggest installing
> libkdcraw 0.1.3 and kipi-plugins 0.1.4 (or 0.1.5-rc2) for now to get
> digiKam 0.9.3 to compile.

Thanks - a downgrade to libkdcraw and kipi-plugins 0.1.4 does the trick just 
fine just as you say. 

> Once digiKam 0.9.4 and its dependencies are released, I will update the
> scripts again.

Supposedly beta2 will come out next week with slightly more realistic 
dependencies... Fingers crossed...

Thanks for the quick and to-the-point response.


From pc_warner at yahoo.com  Thu Mar 20 16:23:52 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Thu, 20 Mar 2008 13:23:52 -0700 (PDT)
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
	suggestions for xinit scripts
In-Reply-To: <mailman.20.1205997335.2549.slackbuilds-users@slackbuilds.org>
Message-ID: <683107.60805.qm@web57705.mail.re3.yahoo.com>

True.  However, Openbox installs extra scripts by default to /usr/bin to facilitate running with a KDE or GNOME session while the Xfce package does not.  So, if the extra xinit scripts aren't there the extra scripts under /usr/bin probably shouldn't be there either.
 
Xfwm4 is probably not the best example, though, as it is part of a DE package.  Comparing this situation to fluxbox would be better.  Fluxbox does not include an extra script for running under KDE or GNOME either.  Fluxbox's site also doesn't advertise running it in KDE or GNOME like Openbox's site does.

I don't really think of the xinitrc.kde-openbox script as being any different than the xinitrc.openbox script.  Neither are created by the vanilla package.  Both can be easily created manually by the admin, but the slackware package should include them as a convenience.  Both are needed if the user is to make full use of the package "out of the box", which is one of the purposes of slackBuilds.  Otherwise, slackBuilds would never set up things like rc scripts.

This is just my opinion, and obviously some people disagree.  For those that do agree, they might like having the option built in the slackBuild so they don't have to take care of it manually (and possibly remember to delete all those extras when they remove the package).

--phil
 

Date: Wed, 19 Mar 2008 23:25:29 -0500
From: "Lehman Black" 
Subject: Re: [Slackbuilds-users] openbox slackBuild: minor fix and
 suggestions for xinit scripts
To: "SlackBuilds.org Users List" 
Message-ID:
 
Content-Type: text/plain; charset="iso-8859-1"

The extra xinit scripts are not essential for the functioning of the
package, so I would put them in /usr/doc/ and put a note in README.
Including them by default would be like including xinit scripts for using
Xfwm4 with KDE and GNOME.








       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080320/60d4e307/attachment.htm>

From chess at chessgriffin.com  Thu Mar 20 17:41:03 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 20 Mar 2008 17:41:03 -0400
Subject: [Slackbuilds-users] openbox slackBuild: minor fix
	and	suggestions for xinit scripts
In-Reply-To: <683107.60805.qm@web57705.mail.re3.yahoo.com>
References: <mailman.20.1205997335.2549.slackbuilds-users@slackbuilds.org>
	<683107.60805.qm@web57705.mail.re3.yahoo.com>
Message-ID: <20080320214103.GA35237@localhost>

* Phillip Warner <pc_warner at yahoo.com> [2008-03-20 13:23:52]:

> True.  However, Openbox installs extra scripts by default to
> /usr/bin to facilitate running with a KDE or GNOME session while the
> Xfce package does not.  So, if the extra xinit scripts aren't there
> the extra scripts under /usr/bin probably shouldn't be there either.
>  

Ok, if you will send me a diff or a tarball with the revised
SlackBuild and related files, I'll check it out and test it.  I ask
that you have this functionality disabled by default in the SlackBuild
by commenting out the lines that would enable it.  You can add a
comment in the SlackBuild and the REAMDE informing folks that they can
enable the functionality if they choose to do so.  It's not a bad idea
to have this in the SlackBuild, but I just like to keep things as
simple and vanilla as possible.  I think having folks voluntarily
enable this extra funtionality would be a fair compromise.  Sound
good?

Thanks for the bug report and for the suggestions.

-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080320/c40074ba/attachment.sig>

From asamardzic at gmail.com  Sun Mar 23 07:34:57 2008
From: asamardzic at gmail.com (Aleksandar Samardzic)
Date: Sun, 23 Mar 2008 12:34:57 +0100
Subject: [Slackbuilds-users] JOBS variable support,
	and Slamd64 patches handling
Message-ID: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>

Just received patches for my qt4, sip and pyqt4 SlackBuilds from
Carlos Corbacho (thanks, Carlos!), adding support for JOBS variable in
these scripts, and extending them to work for Slamd64.  Am not sure
how to handle these, though, so I'd like to hear some opinions:

1. As for JOBS variable support, the idea is to have variable defined
at the start of SlackBuild as follows:
  JOBS=${JOBS:1}
and then to change "make" invocation to:
  make -j ${JOBS}
with the intention to allow to users having multi-core machines to
speed-up compilation times significally. This is actually something
that I intended to suggest to adding to SlackBuild script template
long time ago, so - any opinions?

2. I was thinking that no direct support for Slamd64 is offered here
at SBo, however while searching to find is there any other SlackBuild
employing above described JOBS mechanism, I found that for example
wine SlackBuild supports both this mechanism and Slamd64...  So I
guess it may be OK to apply Carlos patches to my SlackBuilds; on the
other side, I don't have any Slamd64 installation accessible, and
don't have plans for making one on my own machine, thus I would prefer
not to take maintainership  for something alike.  Again - any
suggestion here: to not include patches, to include them and state
directly that other person is responsible regarding all Slamd64
related issues, to have them hosted separately (maybe also here at
SBo) and only point to them from README files,... ?

Regards,
Alex

From carlos at strangeworlds.co.uk  Sun Mar 23 08:11:36 2008
From: carlos at strangeworlds.co.uk (Carlos Corbacho)
Date: Sun, 23 Mar 2008 12:11:36 +0000
Subject: [Slackbuilds-users] JOBS variable support,
	and Slamd64 patches handling
In-Reply-To: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>
References: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>
Message-ID: <200803231211.36314.carlos@strangeworlds.co.uk>

On Sunday 23 March 2008 11:34:57 Aleksandar Samardzic wrote:
> 1. As for JOBS variable support, the idea is to have variable defined
> at the start of SlackBuild as follows:
>   JOBS=${JOBS:1}
> and then to change "make" invocation to:
>   make -j ${JOBS}
> with the intention to allow to users having multi-core machines to
> speed-up compilation times significally. This is actually something
> that I intended to suggest to adding to SlackBuild script template
> long time ago, so - any opinions?

Obviously, I'm in favour of this :). (In cases where this breaks things, I'd 
like to see the maintainers put a note in the SlackBuild that this is the 
case so that they don't get plagued by helpful souls trying to keep adding 
multiple job support to a given SlackBuild, but that should only be for a 
minority of cases).

> to include them and state 
> directly that other person is responsible regarding all Slamd64
> related issues, 

I'm happy with this kind of arrangement - after all, I don't expect the 
maintainer of a given SlackBuild to have to take responsibility for my 
additions (and SBo only guarantees a given SlackBuild will work for a given 
Slackware release on x86; anything on top of that is an added bonus/ optional 
extra).

Something making it clear in the SlackBuild itself that support for X, Y, Z 
etc is the responsibility of someone else would be fine by me.

> to have them hosted separately (maybe also here at 
> SBo) and only point to them from README files,... ?

This would end up with needless duplication, since 99% of such SlackBuild's 
would otherwise be identical.

-Carlos
-- 
E-Mail: carlos at strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D

From volkerdi at slackware.com  Sun Mar 23 12:02:33 2008
From: volkerdi at slackware.com (Patrick J. Volkerding)
Date: Sun, 23 Mar 2008 11:02:33 -0500
Subject: [Slackbuilds-users] JOBS variable support,
 and Slamd64 patches handling
In-Reply-To: <200803231211.36314.carlos@strangeworlds.co.uk>
References: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>
	<200803231211.36314.carlos@strangeworlds.co.uk>
Message-ID: <47E67F19.2090801@slackware.com>

Carlos Corbacho wrote:
> On Sunday 23 March 2008 11:34:57 Aleksandar Samardzic wrote:
>> 1. As for JOBS variable support, the idea is to have variable defined
>> at the start of SlackBuild as follows:
>>   JOBS=${JOBS:1}
>> and then to change "make" invocation to:
>>   make -j ${JOBS}
>> with the intention to allow to users having multi-core machines to
>> speed-up compilation times significally. This is actually something
>> that I intended to suggest to adding to SlackBuild script template
>> long time ago, so - any opinions?
> 
> Obviously, I'm in favour of this :). (In cases where this breaks things, I'd 
> like to see the maintainers put a note in the SlackBuild that this is the 
> case so that they don't get plagued by helpful souls trying to keep adding 
> multiple job support to a given SlackBuild, but that should only be for a 
> minority of cases).

If $JOBS support is added, I think 3 is a more reasonable default than 
1.  It's probably going to be slightly faster even on a single core box.

Take care,

Pat


From alan at lizella.net  Sun Mar 23 15:30:59 2008
From: alan at lizella.net (Alan Hicks)
Date: Sun, 23 Mar 2008 15:30:59 -0400
Subject: [Slackbuilds-users] JOBS variable support,
 and Slamd64 patches handling
In-Reply-To: <47E67F19.2090801@slackware.com>
References: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>	<200803231211.36314.carlos@strangeworlds.co.uk>
	<47E67F19.2090801@slackware.com>
Message-ID: <47E6AFF3.6020405@lizella.net>

Patrick J. Volkerding wrote:
> Carlos Corbacho wrote:
>> On Sunday 23 March 2008 11:34:57 Aleksandar Samardzic wrote:
>>> 1. As for JOBS variable support, the idea is to have variable defined
>>> at the start of SlackBuild as follows:
>>>   JOBS=${JOBS:1}
>>> and then to change "make" invocation to:
>>>   make -j ${JOBS}
>>> with the intention to allow to users having multi-core machines to
>>> speed-up compilation times significally. This is actually something
>>> that I intended to suggest to adding to SlackBuild script template
>>> long time ago, so - any opinions?

I can see this being a worthy addition.

>> Obviously, I'm in favour of this :). (In cases where this breaks 
>> things, I'd like to see the maintainers put a note in the SlackBuild 
>> that this is the case so that they don't get plagued by helpful souls 
>> trying to keep adding multiple job support to a given SlackBuild, but 
>> that should only be for a minority of cases).
> 
> If $JOBS support is added, I think 3 is a more reasonable default than 
> 1.  It's probably going to be slightly faster even on a single core box.

I've nothing blocking the addition of JOBS support, and agree 3 is probably 
a more reasonable alternative.  It's been awhile since I read this, but some 
where some time ago the kernel devs advocated -j 4 on single processor 
machines as this let gcc continue to build some things while others were 
waiting on disk I/O.  Still, there might be some code out there that 
completely bombs with a forked make, and for many things (python scripts and 
the like) it's entirely unnecessary.

I think this is something that should certainly be discussed on the -devel 
mailing list with the possibility of including it into our template file and 
faq.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080323/6614c04e/attachment-0001.asc>

From pc_warner at yahoo.com  Sun Mar 23 21:27:33 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Sun, 23 Mar 2008 18:27:33 -0700 (PDT)
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
	suggestions for xinit scripts
In-Reply-To: <mailman.24.1206300669.2549.slackbuilds-users@slackbuilds.org>
Message-ID: <229395.10816.qm@web57701.mail.re3.yahoo.com>

Sounds great.  I just sent you an updated tarball.

I attached a diff to this email so everyone can see the changes I made and take part in tweaking them if desired.

*) The extra xinit scripts are not installed by default and can be selected for install in the script or in the commandline.
*) All the xinit scripts are now copied to /usr/doc/openbox
*) The openbox-kde-session and openbox-gnome-session mini scripts in /usr/bin are moved to /usr/doc/openbox if their respective xinit script is not installed.

Sorry about the slow response.  I just received the digest tonight.

--phil

Date: Thu, 20 Mar 2008 17:41:03 -0400
From: Chess Griffin 
Subject: Re: [Slackbuilds-users] openbox slackBuild: minor fix and
 suggestions for xinit scripts
To: "SlackBuilds.org Users List" 
Message-ID: <20080320214103.GA35237 at localhost>
Content-Type: text/plain; charset="iso-8859-1"

* Phillip Warner 
 [2008-03-20 13:23:52]:

> True.  However, Openbox installs extra scripts by default to
> /usr/bin to facilitate running with a KDE or GNOME session while the
> Xfce package does not.  So, if the extra xinit scripts aren't there
> the extra scripts under /usr/bin probably shouldn't be there either.
>  

Ok, if you will send me a diff or a tarball with the revised
SlackBuild and related files, I'll check it out and test it.  I ask
that you have this functionality disabled by default in the SlackBuild
by commenting out the lines that would enable it.  You can add a
comment in the SlackBuild and the REAMDE informing folks that they can
enable the functionality if they choose to do so.  It's not a bad idea
to have this in the SlackBuild, but I just like to keep things as
simple and vanilla as possible.  I think having folks voluntarily
enable this extra funtionality would be a fair compromise.  Sound
good?

Thanks for the bug report and for the suggestions.

-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: 

------------------------------




       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080323/3ed7bcdd/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openbox-slackBuild.diff
Type: application/octet-stream
Size: 4078 bytes
Desc: 2367563906-openbox-slackBuild.diff
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080323/3ed7bcdd/attachment.obj>

From chess at chessgriffin.com  Sun Mar 23 22:49:23 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Sun, 23 Mar 2008 22:49:23 -0400
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
 suggestions for xinit scripts
In-Reply-To: <229395.10816.qm@web57701.mail.re3.yahoo.com>
References: <mailman.24.1206300669.2549.slackbuilds-users@slackbuilds.org>
	<229395.10816.qm@web57701.mail.re3.yahoo.com>
Message-ID: <20080323224923.7d1f51d4@slackbob.localdomain>

On Sun, 23 Mar 2008 18:27:33 -0700 (PDT)
Phillip Warner <pc_warner at yahoo.com> wrote:

> Sounds great.  I just sent you an updated tarball.
> 
> I attached a diff to this email so everyone can see the changes I
> made and take part in tweaking them if desired.
> 
> *) The extra xinit scripts are not installed by default and can be
> selected for install in the script or in the commandline. *) All the
> xinit scripts are now copied to /usr/doc/openbox *) The
> openbox-kde-session and openbox-gnome-session mini scripts
> in /usr/bin are moved to /usr/doc/openbox if their respective xinit
> script is not installed.
> 
> Sorry about the slow response.  I just received the digest tonight.
> 
> --phil
 
Thanks, Phil.  I have only glanced at your changes so far, but they
look good.  Let me check it out and test over the next day or two and
get back to you.

Thanks again for working up the proposed changes.  I really appreciate
it.

Chess

-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080323/f7b6f62f/attachment.asc>

From chess at chessgriffin.com  Mon Mar 24 10:22:44 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 24 Mar 2008 10:22:44 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
Message-ID: <47E7B934.60209@chessgriffin.com>

For reasons due to personal itch scratching, I've been working on a 
little tool called 'sbopkg' to interact with a local copy of the SBo 
mirror.  It can be used via cli only or with a dialog interface similar 
to that seen in other Slackware tools.  Sbopkg will allow the user to 
rsync and browse a local copy of the SBo repository, read the SBo 
ChangeLog, and view the README, SlackBuild, .info, and slack-desc files 
for each package. Sbopkg will also allow the user to select packages to 
build and it will download the source code, check the md5sum, and build 
a Slackware package.

I have been testing it myself for awhile now and it's been working ok, 
though YMMV.  Anyway, I just uploaded the code and created a version 
0.0.1 tarball and noarch package for folks to check out.  There are two 
man pages that are installed which should explain most of the features. 
  There's still lots to do on this tool, as well as some needed 
improvements -- especially on the package building part -- and fixes 
that I plan to work on, so my TODO list is growing. 
Ideas/suggestions/patches are welcomed.  :-)  I'm also in #slackbuilds 
and ##slackware (nick _chess_ or cng) if you want to chat about it.

You can read more about sbopkg, check out the fancy screenshots, and 
download the tarball or noarch package here:

http://code.google.com/p/sbopkg/

Finally, although I spent many hours pouring over scripts written by 
Patrick, Eric Hameleers, PiterPunk, and many others, in an attempt to 
discern the Way of Scripting, I doubt I was entirely successful. 
Therefore, all errors and omissions, while unintentional, are purely my 
own.  ;-)

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/d486667b/attachment.asc>

From boblounsbury at gmail.com  Mon Mar 24 11:20:14 2008
From: boblounsbury at gmail.com (Bob Lounsbury)
Date: Mon, 24 Mar 2008 09:20:14 -0600
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7B934.60209@chessgriffin.com>
References: <47E7B934.60209@chessgriffin.com>
Message-ID: <c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>

On Mon, Mar 24, 2008 at 8:22 AM, Chess Griffin <chess at chessgriffin.com> wrote:
> For reasons due to personal itch scratching, I've been working on a
>  little tool called 'sbopkg' to interact with a local copy of the SBo
>  mirror.  It can be used via cli only or with a dialog interface similar
>  to that seen in other Slackware tools.  Sbopkg will allow the user to
>  rsync and browse a local copy of the SBo repository, read the SBo
>  ChangeLog, and view the README, SlackBuild, .info, and slack-desc files
>  for each package. Sbopkg will also allow the user to select packages to
>  build and it will download the source code, check the md5sum, and build
>  a Slackware package.
>
>  I have been testing it myself for awhile now and it's been working ok,
>  though YMMV.  Anyway, I just uploaded the code and created a version
>  0.0.1 tarball and noarch package for folks to check out.  There are two
>  man pages that are installed which should explain most of the features.
>   There's still lots to do on this tool, as well as some needed
>  improvements -- especially on the package building part -- and fixes
>  that I plan to work on, so my TODO list is growing.
>  Ideas/suggestions/patches are welcomed.  :-)  I'm also in #slackbuilds
>  and ##slackware (nick _chess_ or cng) if you want to chat about it.
>
>  You can read more about sbopkg, check out the fancy screenshots, and
>  download the tarball or noarch package here:
>
>  http://code.google.com/p/sbopkg/
>
>  Finally, although I spent many hours pouring over scripts written by
>  Patrick, Eric Hameleers, PiterPunk, and many others, in an attempt to
>  discern the Way of Scripting, I doubt I was entirely successful.
>  Therefore, all errors and omissions, while unintentional, are purely my
>  own.  ;-)
>
>  --
>  Chess Griffin
>  GPG Key:  0x0C7558C3
>  http://www.chessgriffin.com
>
>
> _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>
>

Very interesting. I like the idea and have a question. Is there any
way to make local changes to the SlackBuild script and then build the
package with your sbopkg tool? I'm assuming that rsync creates local
copies of SlackBuilds.org. I'm only asking because I also use
Slacintosh and I have modified several SlackBuild scripts to compile
successfully on powerpc. I guess this question could also relate to
changing the SlackBuild script locally for any other reason also, not
just for powerpc stuff.

Cheers,
/Bob

From rworkman at slackbuilds.org  Mon Mar 24 11:46:03 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 24 Mar 2008 10:46:03 -0500
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>
References: <47E7B934.60209@chessgriffin.com>
	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>
Message-ID: <47E7CCBB.8000203@slackbuilds.org>

Bob Lounsbury wrote:
> 
> Very interesting. I like the idea and have a question. Is there any
> way to make local changes to the SlackBuild script and then build the
> package with your sbopkg tool? I'm assuming that rsync creates local
> copies of SlackBuilds.org. I'm only asking because I also use
> Slacintosh and I have modified several SlackBuild scripts to compile
> successfully on powerpc. I guess this question could also relate to
> changing the SlackBuild script locally for any other reason also, not
> just for powerpc stuff.



Hmm... good question.

Now, I'm not going to be one of those who throws feature requests out
for SOMEONE ELSE to implement, but perhaps something to use $EDITOR
or $VISUAL from the environment would be trivial to implement... :)

-RW

From chess at chessgriffin.com  Mon Mar 24 12:00:05 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 24 Mar 2008 12:00:05 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7CCBB.8000203@slackbuilds.org>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>
	<47E7CCBB.8000203@slackbuilds.org>
Message-ID: <47E7D005.10603@chessgriffin.com>

Robby Workman wrote:
> Bob Lounsbury wrote:
>>
>> Very interesting. I like the idea and have a question. Is there any
>> way to make local changes to the SlackBuild script and then build the
>> package with your sbopkg tool? I'm assuming that rsync creates local
>> copies of SlackBuilds.org. I'm only asking because I also use
>> Slacintosh and I have modified several SlackBuild scripts to compile
>> successfully on powerpc. I guess this question could also relate to
>> changing the SlackBuild script locally for any other reason also, not
>> just for powerpc stuff.
> 
> 
> 
> Hmm... good question.
> 
> Now, I'm not going to be one of those who throws feature requests out
> for SOMEONE ELSE to implement, but perhaps something to use $EDITOR
> or $VISUAL from the environment would be trivial to implement... :)
> 
> -RW

Bob -- yes, good point.  Since this script displays the files in your 
local mirror, any manual changes you have made would be there, but as 
far as editing the files from within sbopkg, that's not there yet, 
although it's a great idea.  I like Robby's idea of using $EDITOR to 
edit the SlackBuild from within sbopkg and that should be easy to do.

I'll add it to the TODO.

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/bb449357/attachment-0001.asc>

From alan at lizella.net  Mon Mar 24 12:10:49 2008
From: alan at lizella.net (Alan Hicks)
Date: Mon, 24 Mar 2008 12:10:49 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D005.10603@chessgriffin.com>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>
	<47E7D005.10603@chessgriffin.com>
Message-ID: <47E7D289.40607@lizella.net>

Chess Griffin wrote:
> Bob -- yes, good point.  Since this script displays the files in your 
> local mirror, any manual changes you have made would be there, but as 
> far as editing the files from within sbopkg, that's not there yet, 
> although it's a great idea.  I like Robby's idea of using $EDITOR to 
> edit the SlackBuild from within sbopkg and that should be easy to do.
> 
> I'll add it to the TODO.

The hard part would be integrating properly with rsync.  You don't want your 
next rsync fetch using sbopkg to over-write your local copy changes.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/cf5c36e3/attachment.asc>

From chess at chessgriffin.com  Mon Mar 24 12:14:08 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 24 Mar 2008 12:14:08 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D289.40607@lizella.net>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>	<47E7D005.10603@chessgriffin.com>
	<47E7D289.40607@lizella.net>
Message-ID: <47E7D350.8050806@chessgriffin.com>

Alan Hicks wrote:
> Chess Griffin wrote:
>> Bob -- yes, good point.  Since this script displays the files in your 
>> local mirror, any manual changes you have made would be there, but as 
>> far as editing the files from within sbopkg, that's not there yet, 
>> although it's a great idea.  I like Robby's idea of using $EDITOR to 
>> edit the SlackBuild from within sbopkg and that should be easy to do.
>>
>> I'll add it to the TODO.
> 
> The hard part would be integrating properly with rsync.  You don't want 
> your next rsync fetch using sbopkg to over-write your local copy changes.

Yes, my thoughts exactly.  One idea would be have the sbopkg 
automatically cp the Slackbuild so it's app.SlackBuild.local or 
something like that and that's the file that is edited.  Right now, 
sbopkg uses the -avz options with rsync so local changes will get 
clobbered.  Not ideal.

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/573a8f92/attachment.asc>

From alan at lizella.net  Mon Mar 24 12:20:03 2008
From: alan at lizella.net (Alan Hicks)
Date: Mon, 24 Mar 2008 12:20:03 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D350.8050806@chessgriffin.com>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>	<47E7D005.10603@chessgriffin.com>	<47E7D289.40607@lizella.net>
	<47E7D350.8050806@chessgriffin.com>
Message-ID: <47E7D4B3.1000902@lizella.net>

Chess Griffin wrote:
>> The hard part would be integrating properly with rsync.  You don't 
>> want your next rsync fetch using sbopkg to over-write your local copy 
>> changes.
> 
> Yes, my thoughts exactly.  One idea would be have the sbopkg 
> automatically cp the Slackbuild so it's app.SlackBuild.local or 
> something like that and that's the file that is edited.  Right now, 
> sbopkg uses the -avz options with rsync so local changes will get 
> clobbered.  Not ideal.

Nope.  You need --delete as well.  After all, we occasionally remove whole 
SlackBuild scripts.  Additionally, patches that were necessary in an old 
version might not exist in a new one for example.

You *could* have sbopkg add a file into the source that would prevent it 
from clobbering anything in that source directory, but that becomes a major 
hassel because you'd have to run a while loop to construct all your 
--exclude lines.

One possibility is to create a SBo/local/ branch and --exclude local/. 
sbopkg could copy the entire source directory and structure there if a user 
decided to make any changes.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/7aa51995/attachment.asc>

From listreader at lupulin.net  Mon Mar 24 12:32:04 2008
From: listreader at lupulin.net (paul wisehart)
Date: Mon, 24 Mar 2008 12:32:04 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D4B3.1000902@lizella.net>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>	<47E7D005.10603@chessgriffin.com>	<47E7D289.40607@lizella.net>	<47E7D350.8050806@chessgriffin.com>
	<47E7D4B3.1000902@lizella.net>
Message-ID: <47E7D784.9050701@lupulin.net>

Alan Hicks wrote:
> You *could* have sbopkg add a file into the source that would prevent it 
> from clobbering anything in that source directory, but that becomes a 
> major hassel because you'd have to run a while loop to construct all 
> your --exclude lines.

I make my local edits to <pkg-name>.Slackbuilds.sbo-local , and have 
rsync exlude .-sbo-local files.

--exclude='*.sbo-local'

You could do something like that, and have sbopkg look for the 
..sbo-local slackbuild first when building packages.

--
paul w


From chess at chessgriffin.com  Mon Mar 24 12:37:30 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 24 Mar 2008 12:37:30 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D4B3.1000902@lizella.net>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>	<47E7D005.10603@chessgriffin.com>	<47E7D289.40607@lizella.net>	<47E7D350.8050806@chessgriffin.com>
	<47E7D4B3.1000902@lizella.net>
Message-ID: <47E7D8CA.3020700@chessgriffin.com>

Alan Hicks wrote:
> Chess Griffin wrote:
>>> The hard part would be integrating properly with rsync.  You don't 
>>> want your next rsync fetch using sbopkg to over-write your local copy 
>>> changes.
>>
>> Yes, my thoughts exactly.  One idea would be have the sbopkg 
>> automatically cp the Slackbuild so it's app.SlackBuild.local or 
>> something like that and that's the file that is edited.  Right now, 
>> sbopkg uses the -avz options with rsync so local changes will get 
>> clobbered.  Not ideal.
> 
> Nope.  You need --delete as well.  After all, we occasionally remove 
> whole SlackBuild scripts.  Additionally, patches that were necessary in 
> an old version might not exist in a new one for example.
> 
> You *could* have sbopkg add a file into the source that would prevent it 
> from clobbering anything in that source directory, but that becomes a 
> major hassel because you'd have to run a while loop to construct all 
> your --exclude lines.
> 
> One possibility is to create a SBo/local/ branch and --exclude local/. 
> sbopkg could copy the entire source directory and structure there if a 
> user decided to make any changes.
> 

Yeah, the only reason I specifically did not include --delete was that I 
did not want to delete the source tarballs to save having to redownload 
them.  However, maybe a separate directory could be created where all 
source tarballs are kept (like the /distfiles directory in FreeBSD) and 
that this directory is checked for a copy of the source tarball before 
building the package.  If it's there, the source is moved to where it 
needs to be for the SlackBuild to run.  If not, it's downloaded into 
that directory for future use.

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/9b4c5b72/attachment.asc>

From rworkman at slackbuilds.org  Mon Mar 24 13:01:36 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 24 Mar 2008 12:01:36 -0500
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D8CA.3020700@chessgriffin.com>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>	<47E7D005.10603@chessgriffin.com>	<47E7D289.40607@lizella.net>	<47E7D350.8050806@chessgriffin.com>	<47E7D4B3.1000902@lizella.net>
	<47E7D8CA.3020700@chessgriffin.com>
Message-ID: <47E7DE70.5070207@slackbuilds.org>

Chess Griffin wrote:

> 
> Yeah, the only reason I specifically did not include --delete was that I 
> did not want to delete the source tarballs to save having to redownload 
> them.  However, maybe a separate directory could be created where all 
> source tarballs are kept (like the /distfiles directory in FreeBSD) and 
> that this directory is checked for a copy of the source tarball before 
> building the package.  If it's there, the source is moved to where it 
> needs to be for the SlackBuild to run.  If not, it's downloaded into 
> that directory for future use.


Hmmm...

Perhaps something along these lines...

# Probably pull this from the config file instead, but you get the
# idea :)    Also, /var is probably a bad place to put this, but
# maybe a sane default ??
SRC_DIR=${SRC_DIR:-/var/cache/sbopkg}

When getting ready to build the package, do something like this:

if [ ! -e $CWD/$SRCTARBALL ]; then   # maybe check md5sum here too?
   if [ -e $SRC_DIR/$SRCTARBALL ]; then
     ln -s $SRC_DIR/$SRCTARBALL $CWD/$SRCTARBALL
   else
     cd $SRC_DIR ; wget $DOWNLOAD ; cd -
   fi
fi

That's ugly, but maybe gets the point across.  Perhaps wrap that in a
while loop would be better too.  Anyway, the symlink to the source
cache would be IMHO better than a copy or move of the actual source
tarball...

-RW

From chess at chessgriffin.com  Mon Mar 24 13:50:12 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 24 Mar 2008 13:50:12 -0400
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7DE70.5070207@slackbuilds.org>
References: <47E7B934.60209@chessgriffin.com>	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>	<47E7CCBB.8000203@slackbuilds.org>	<47E7D005.10603@chessgriffin.com>	<47E7D289.40607@lizella.net>	<47E7D350.8050806@chessgriffin.com>	<47E7D4B3.1000902@lizella.net>	<47E7D8CA.3020700@chessgriffin.com>
	<47E7DE70.5070207@slackbuilds.org>
Message-ID: <47E7E9D4.4090304@chessgriffin.com>

Robby Workman wrote:
> Hmmm...
> 
> Perhaps something along these lines...
> 
> # Probably pull this from the config file instead, but you get the
> # idea :)    Also, /var is probably a bad place to put this, but
> # maybe a sane default ??
> SRC_DIR=${SRC_DIR:-/var/cache/sbopkg}
> 
> When getting ready to build the package, do something like this:
> 
> if [ ! -e $CWD/$SRCTARBALL ]; then   # maybe check md5sum here too?
>   if [ -e $SRC_DIR/$SRCTARBALL ]; then
>     ln -s $SRC_DIR/$SRCTARBALL $CWD/$SRCTARBALL
>   else
>     cd $SRC_DIR ; wget $DOWNLOAD ; cd -
>   fi
> fi
> 
> That's ugly, but maybe gets the point across.  Perhaps wrap that in a
> while loop would be better too.  Anyway, the symlink to the source
> cache would be IMHO better than a copy or move of the actual source
> tarball...
> 
> -RW

Yep, something along those lines would work well, I think.  Good idea on 
the symlink too.  I'm going to start working on adding this right away 
because Alan's point about using --delete is well taken.  I need to add 
that in to keep the local copy a true mirror.  Then, I can consider how 
to implement local changes to the SlackBuild that don't get clobbered.

Thanks for all the suggestions so far.  I really appreciate the feedback.

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/c00d003f/attachment.asc>

From pc_warner at yahoo.com  Mon Mar 24 22:12:19 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Mon, 24 Mar 2008 19:12:19 -0700 (PDT)
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <mailman.26.1206374426.2549.slackbuilds-users@slackbuilds.org>
Message-ID: <612165.24592.qm@web57702.mail.re3.yahoo.com>




Date: Mon, 24 Mar 2008 12:00:05 -0400
From: Chess Griffin 
Subject: Re: [Slackbuilds-users] for testing - 'sbopkg' tool
To: "SlackBuilds.org Users List" 
Message-ID: <47E7D005.10603 at chessgriffin.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Robby Workman wrote:
> Bob Lounsbury wrote:
>>
>> Very interesting. I like the idea and have a question. Is there any
>> way to make local changes to the SlackBuild script and then build the
>> package with your sbopkg tool? I'm assuming that rsync creates local
>> copies of SlackBuilds.org. I'm only asking because I also use
>> Slacintosh and I have modified several SlackBuild scripts to compile
>> successfully on powerpc. I guess this question could also relate to
>> changing the SlackBuild script locally for any other reason also, not
>> just for powerpc stuff.
> 
> 
> 
> Hmm... good question.
> 
> Now, I'm not going to be one of those who throws feature requests out
> for SOMEONE ELSE to implement, but perhaps something to use $EDITOR
> or $VISUAL from the environment would be trivial to implement... :)
> 
> -RW

Bob -- yes, good point.  Since this script displays the files in your 
local mirror, any manual changes you have made would be there, but as 
far as editing the files from within sbopkg, that's not there yet, 
although it's a great idea.  I like Robby's idea of using $EDITOR to 
edit the SlackBuild from within sbopkg and that should be easy to do.

I'll add it to the TODO.

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: 




You might want to consider adding a feature where you can have certain vars in the SlackBuilds automatically changed after a new script is downloaded.  You could use something like sed to change the defaults for vars like
ARCH
TAG
OUTPUT
and maybe even some common vars like OPENGL (YES/NO?).
Using something like this, your tool will be much more powerful.  You just need to be sure you have strict rules for sed so you aren't, for instance, changing a noarch program into one for powerpc, etc.

I still think manually editing the scripts is important.  The above feature just might save some time.

For the downloads:  I recommend putting them all in one directory and just symlinking to the program archive from the slackBuild folder.

--phil

       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080324/a6ceb174/attachment-0001.htm>

From rworkman at slackbuilds.org  Mon Mar 24 22:18:06 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 24 Mar 2008 21:18:06 -0500
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <612165.24592.qm@web57702.mail.re3.yahoo.com>
References: <612165.24592.qm@web57702.mail.re3.yahoo.com>
Message-ID: <47E860DE.4000605@slackbuilds.org>

Phillip Warner wrote:

> You might want to consider adding a feature where you can have certain 
> vars in the SlackBuilds automatically changed after a new script is 
> downloaded.  You could use something like sed to change the defaults for 
> vars like
> ARCH
> TAG
> OUTPUT
> and maybe even some common vars like OPENGL (YES/NO?).
> Using something like this, your tool will be much more powerful.  You 
> just need to be sure you have strict rules for sed so you aren't, for 
> instance, changing a noarch program into one for powerpc, etc.


No need to use sed or anything of the sort; simply pass the desired
value on the command line when executing the build script.

-RW

From elyk03 at gmail.com  Mon Mar 24 22:59:48 2008
From: elyk03 at gmail.com (Kyle Guinn)
Date: Mon, 24 Mar 2008 21:59:48 -0500
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <47E7D289.40607@lizella.net>
References: <47E7B934.60209@chessgriffin.com>
	<c7aebbcd0803240820q59a6354cqf91b6d41437044ef@mail.gmail.com>
	<47E7CCBB.8000203@slackbuilds.org> <47E7D005.10603@chessgriffin.com>
	<47E7D289.40607@lizella.net>
Message-ID: <2dcaacad0803241959oe53a570gedb5f149e213aaad@mail.gmail.com>

On 3/24/08, Alan Hicks <alan at lizella.net> wrote:
> The hard part would be integrating properly with rsync.  You don't want your
>  next rsync fetch using sbopkg to over-write your local copy changes.

Using a distributed VCS such as git or mercurial would solve this
problem.  It might also help with merging your changes to a new
version of a script.

From lapinours at web.de  Tue Mar 25 11:30:38 2008
From: lapinours at web.de (Michael Wagner)
Date: Tue, 25 Mar 2008 16:30:38 +0100
Subject: [Slackbuilds-users] grub version 2
Message-ID: <418078215@web.de>

Hi,

although part of Slackware, I suggest the inclusion of grub's second version (still in an alpha state, but working). The legacy version fails on Slackware current (e2fsprogs > 1.40.5) and is not a serious alternative to lilo anymore. 

Are there any objections?

Greetings,

Michael
_________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail k?nnen Sie eine SMS an alle 
Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179




From abrouwers at gmail.com  Tue Mar 25 13:05:44 2008
From: abrouwers at gmail.com (Andrew Brouwers)
Date: Tue, 25 Mar 2008 13:05:44 -0400
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <418078215@web.de>
References: <418078215@web.de>
Message-ID: <196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>

Hi Michael,

Since no other distros have even considered moving towards grub2, I'm
not sure this should be pushed quite yet?  Perhaps a simple
modification for e2fsprogs should be added to -current.

I can't test this while at work, but something like:

http://crux.nu/gitweb/?p=ports/opt.git;a=blob_plain;f=grub/grub-ext2-ext3-inodesize.patch;hb=f2e04bc5b046b322aa16c972884b8b488d650e03

seems pretty common among other distros.

Andrew Brouwers

On Tue, Mar 25, 2008 at 11:30 AM, Michael Wagner <lapinours at web.de> wrote:
> Hi,
>
>  although part of Slackware, I suggest the inclusion of grub's second version (still in an alpha state, but working). The legacy version fails on Slackware current (e2fsprogs > 1.40.5) and is not a serious alternative to lilo anymore.
>
>  Are there any objections?
>
>  Greetings,
>
>  Michael
>  _________________________________________________________________________
>  Mit der Gruppen-SMS von WEB.DE FreeMail k?nnen Sie eine SMS an alle
>  Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179
>
>
>
>  _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>

From lapinours at web.de  Tue Mar 25 13:41:42 2008
From: lapinours at web.de (Michael Wagner)
Date: Tue, 25 Mar 2008 18:41:42 +0100
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>
References: <418078215@web.de>
	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>
Message-ID: <47E93956.5010306@web.de>

Andrew Brouwers wrote:
> Hi Michael,
>
> Since no other distros have even considered moving towards grub2, I'm
> not sure this should be pushed quite yet?  Perhaps a simple
> modification for e2fsprogs should be added to -current.
>
> I can't test this while at work, but something like:
>
> http://crux.nu/gitweb/?p=ports/opt.git;a=blob_plain;f=grub/grub-ext2-ext3-inodesize.patch;hb=f2e04bc5b046b322aa16c972884b8b488d650e03
>
> seems pretty common among other distros.
>
> Andrew Brouwers
>
>   
A similiar patch has already been applied to -current but it had to be 
reverted as it didn't work with e2fsprogs 1.40.8:

	extra/grub/grub-0.97-i486-5.tgz:  Recompiled without the inode patch since
	  e2fsprogs-1.40.8 broke the GRUB we patched to work with e2fsprogs-1.40.6.


Although GRUB 2 is in an alpha state, it is working quite well and 
stabilizing the features is planned in November, 2008. As I am 
periodically forgetting to re-run lilo after installing a new kernel, I 
would like to see an actively maintained alternative.

Greetings,

Michael

From alan at lizella.net  Tue Mar 25 14:05:30 2008
From: alan at lizella.net (Alan Hicks)
Date: Tue, 25 Mar 2008 14:05:30 -0400
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E93956.5010306@web.de>
References: <418078215@web.de>	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>
	<47E93956.5010306@web.de>
Message-ID: <47E93EEA.8040201@lizella.net>

Michael Wagner wrote:
> A similiar patch has already been applied to -current but it had to be 
> reverted as it didn't work with e2fsprogs 1.40.8:
> 
>     extra/grub/grub-0.97-i486-5.tgz:  Recompiled without the inode patch 
> since
>       e2fsprogs-1.40.8 broke the GRUB we patched to work with 
> e2fsprogs-1.40.6.

I've personally done a bit of testing of GRUB in -current.  While I can't 
say what about e2fsprogs-1.40.8 broke GRUB, I can say that adding that 256 
inode patch back in let GRUB boot my ext3 root partition without problems. 
If you're having trouble with it, might want to give that a look.  It's 
simply commented out of the SlackBuild script at the moment.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080325/dc4be061/attachment.asc>

From abrouwers at gmail.com  Tue Mar 25 14:50:53 2008
From: abrouwers at gmail.com (Andrew Brouwers)
Date: Tue, 25 Mar 2008 14:50:53 -0400
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E93EEA.8040201@lizella.net>
References: <418078215@web.de>
	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>
	<47E93956.5010306@web.de> <47E93EEA.8040201@lizella.net>
Message-ID: <196c22970803251150k5ed6ca9fra1d7cb1055a22fb1@mail.gmail.com>

Alan,

Yes; I chose that patch because crux linux also uses the -current
version of e2fsprogs, and that works perfectly for me.  But, without
testing it, I didn't want to send it to Pat (although maybe he's
listening? :-)

Anyway, thanks for testing it out.  I had a very strong feeling it
would work, and especially act as a suitable solution to adding grub2
to the SBo archive just for that reason.

Andrew

On Tue, Mar 25, 2008 at 2:05 PM, Alan Hicks <alan at lizella.net> wrote:
> Michael Wagner wrote:
>  > A similiar patch has already been applied to -current but it had to be
>  > reverted as it didn't work with e2fsprogs 1.40.8:
>  >
>  >     extra/grub/grub-0.97-i486-5.tgz:  Recompiled without the inode patch
>  > since
>  >       e2fsprogs-1.40.8 broke the GRUB we patched to work with
>  > e2fsprogs-1.40.6.
>
>  I've personally done a bit of testing of GRUB in -current.  While I can't
>  say what about e2fsprogs-1.40.8 broke GRUB, I can say that adding that 256
>  inode patch back in let GRUB boot my ext3 root partition without problems.
>  If you're having trouble with it, might want to give that a look.  It's
>  simply commented out of the SlackBuild script at the moment.
>
>  --
>  It is better to hear the rebuke of the wise,
>  Than for a man to hear the song of fools.
>  Ecclesiastes 7:5
>
>
> _______________________________________________
>  Slackbuilds-users mailing list
>  Slackbuilds-users at slackbuilds.org
>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>  Please read the FAQ - http://slackbuilds.org/faq/
>
>

From lapinours at web.de  Tue Mar 25 16:21:46 2008
From: lapinours at web.de (Michael Wagner)
Date: Tue, 25 Mar 2008 21:21:46 +0100
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E93EEA.8040201@lizella.net>
References: <418078215@web.de>	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>	<47E93956.5010306@web.de>
	<47E93EEA.8040201@lizella.net>
Message-ID: <47E95EDA.9030205@web.de>

Alan Hicks wrote:
> I've personally done a bit of testing of GRUB in -current.  While I 
> can't say what about e2fsprogs-1.40.8 broke GRUB, I can say that 
> adding that 256 inode patch back in let GRUB boot my ext3 root 
> partition without problems. If you're having trouble with it, might 
> want to give that a look.  It's simply commented out of the SlackBuild 
> script at the moment.
>
This patch is also working for me and I still wonder why it has been 
commented out on build 5.  But as long as grub legacy isn't actively 
maintained, problems like this will become more frequent. That is why I 
have tested grub's second version and found it useable for me (ext3 
filesystem).

Thanks for your replies,

Michael

From abrouwers at gmail.com  Tue Mar 25 17:29:44 2008
From: abrouwers at gmail.com (Andrew Brouwers)
Date: Tue, 25 Mar 2008 17:29:44 -0400
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E95EDA.9030205@web.de>
References: <418078215@web.de>
	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>
	<47E93956.5010306@web.de> <47E93EEA.8040201@lizella.net>
	<47E95EDA.9030205@web.de>
Message-ID: <196c22970803251429v3b8d9e78u73378bf1a0de682e@mail.gmail.com>

On Tue, Mar 25, 2008 at 4:21 PM, Michael Wagner <lapinours at web.de> wrote:
> Alan Hicks wrote:
>  > I've personally done a bit of testing of GRUB in -current.  While I
>  > can't say what about e2fsprogs-1.40.8 broke GRUB, I can say that
>  > adding that 256 inode patch back in let GRUB boot my ext3 root
>  > partition without problems. If you're having trouble with it, might
>  > want to give that a look.  It's simply commented out of the SlackBuild
>  > script at the moment.
>  >
>  This patch is also working for me and I still wonder why it has been
>  commented out on build 5.  But as long as grub legacy isn't actively
>  maintained, problems like this will become more frequent. That is why I
>  have tested grub's second version and found it useable for me (ext3
>  filesystem).
>
>  Thanks for your replies,
>
>
>
>  Michael
>  ______________________________________________

Michael,

Sorry, should have looked a little closer.  It appears the one in
-current that is "broke" is the same to which I linked.

Andrew

From rworkman at slackbuilds.org  Tue Mar 25 19:48:52 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 25 Mar 2008 18:48:52 -0500
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <418078215@web.de>
References: <418078215@web.de>
Message-ID: <47E98F64.5070204@slackbuilds.org>

Michael Wagner wrote:

> although part of Slackware, I suggest the inclusion of grub's second version (still in an alpha state, but working). The legacy version fails on Slackware current (e2fsprogs > 1.40.5) and is not a serious alternative to lilo anymore. 
> 
> Are there any objections?


I think there are two parts to this:
   1. grub in Slackware has issues
   2. Is grub2 a candidate for SBo inclusion.

Re part 1, I think we'll have to wait and see what pans out with
e2fsprogs and grub and other distros and so on.  There have been
bug reports with new e2fsprogs and grub+patch and bug reports with
new e2fsprogs and grub_nopatch, so results are inconclusive.

Re part 2, IMHO, yes.

Pat might weigh in on one or both of these, however, so we'll
just wait and see.

-RW

From rworkman at slackbuilds.org  Tue Mar 25 19:52:19 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 25 Mar 2008 18:52:19 -0500
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E95EDA.9030205@web.de>
References: <418078215@web.de>	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>	<47E93956.5010306@web.de>	<47E93EEA.8040201@lizella.net>
	<47E95EDA.9030205@web.de>
Message-ID: <47E99033.5070306@slackbuilds.org>

Michael Wagner wrote:

> But as long as grub legacy isn't actively maintained,
> problems like this will become more frequent. 


Yep, that is the crux of the issue.

-RW

From volkerdi at slackware.com  Tue Mar 25 19:59:10 2008
From: volkerdi at slackware.com (Patrick J. Volkerding)
Date: Tue, 25 Mar 2008 18:59:10 -0500
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <418078215@web.de>
References: <418078215@web.de>
Message-ID: <47E991CE.6070907@slackware.com>

Michael Wagner wrote:
> Hi,
> 
> although part of Slackware, I suggest the inclusion of grub's second
> version (still in an alpha state, but working). The legacy version
> fails on Slackware current (e2fsprogs > 1.40.5) and is not a serious
> alternative to lilo anymore.
> 
> Are there any objections?

Well, there is the issue of it being an alpha not-released yet program, 
but I'll stay out of that and let the SBo people decide if that matters.

I do plan to revisit the grub-legacy inode patch.

Cheers,

Pat


From volkerdi at slackware.com  Tue Mar 25 20:04:05 2008
From: volkerdi at slackware.com (Patrick J. Volkerding)
Date: Tue, 25 Mar 2008 19:04:05 -0500
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E99033.5070306@slackbuilds.org>
References: <418078215@web.de>	<196c22970803251005w4107f338va186588417a9201c@mail.gmail.com>	<47E93956.5010306@web.de>	<47E93EEA.8040201@lizella.net>	<47E95EDA.9030205@web.de>
	<47E99033.5070306@slackbuilds.org>
Message-ID: <47E992F5.5070108@slackware.com>

Robby Workman wrote:
> Michael Wagner wrote:
> 
>> But as long as grub legacy isn't actively maintained,
>> problems like this will become more frequent. 
> 
> 
> Yep, that is the crux of the issue.

What if maintaining grub2 starts to get boring for the developers, and 
the code rots (or there's never a stable release?)

LILO could be maintained pretty much forever by anyone good (enough) 
with C, since the main issues would be compiler-upgrades requiring code 
changes to compile.  Moving target filesystems would not figure into the 
picture like they do with GRUB.

Pat

From pc_warner at yahoo.com  Tue Mar 25 23:04:34 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Tue, 25 Mar 2008 20:04:34 -0700 (PDT)
Subject: [Slackbuilds-users] for testing - 'sbopkg' tool
In-Reply-To: <mailman.38.1206480587.2549.slackbuilds-users@slackbuilds.org>
Message-ID: <515632.75637.qm@web57715.mail.re3.yahoo.com>

Yea, that's what I actually meant :)  Just run the slackBuilds from the tool with some of the defaults changed inline.  I don't know why I said use sed instead :)

--phil
Date: Mon, 24 Mar 2008 21:18:06 -0500
From: Robby Workman 
Subject: Re: [Slackbuilds-users] for testing - 'sbopkg' tool
To: "SlackBuilds.org Users List" 
Message-ID: <47E860DE.4000605 at slackbuilds.org>
Content-Type: text/plain; charset=UTF-8; format=flowed

No need to use sed or anything of the sort; simply pass the desired
value on the command line when executing the build script.

-RW


       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080325/75c546df/attachment.htm>

From andrew.david.45 at gmail.com  Wed Mar 26 01:28:38 2008
From: andrew.david.45 at gmail.com (andrew)
Date: Wed, 26 Mar 2008 16:28:38 +1100
Subject: [Slackbuilds-users] Leafnode 2 SlackBuild
Message-ID: <20080326052838.GA3512@ilium.lan>

Hi,

Not sure if this is the correct place but I was wondering if a small
change could be made to the Leafnode-2 slackbuild to allow easier
setting up of local moderated newsgroups?

Could the following be added to the doinst.sh file?

if [ ! -e etc/leafnode/moderators ]; then
  touch etc/leafnode/moderators
fi

This completes the setup for local groups that is commenced with the
previous conditional statement. Just for the sake of completion :-) I
will be writing up moderated groups in Leafnode 2 shortly.

Thanks for your trouble,

   Andrew
-- 
http://www.andrews-corner.org

From cherife at dotimes.com  Wed Mar 26 01:59:17 2008
From: cherife at dotimes.com (Cherife Li)
Date: Wed, 26 Mar 2008 13:59:17 +0800
Subject: [Slackbuilds-users] Leafnode 2 SlackBuild
In-Reply-To: <20080326052838.GA3512@ilium.lan>
References: <20080326052838.GA3512@ilium.lan>
Message-ID: <47E9E635.500@dotimes.com>

On 03/26/08 13:28, andrew wrote:
> Hi,
> 
> Not sure if this is the correct place but I was wondering if a small
> change could be made to the Leafnode-2 slackbuild to allow easier
> setting up of local moderated newsgroups?
> 
> Could the following be added to the doinst.sh file?
> 
> if [ ! -e etc/leafnode/moderators ]; then
>   touch etc/leafnode/moderators
> fi
> 
> This completes the setup for local groups that is commenced with the
> previous conditional statement. Just for the sake of completion :-) I
> will be writing up moderated groups in Leafnode 2 shortly.
> 
> Thanks for your trouble,
> 
>    Andrew

IMO, you could first contact the MAINTAINER directly to solve the issue.
If still have problem, talk about it here, then.

-- 
Rgds,
Cherife.

From andrew.david.45 at gmail.com  Wed Mar 26 03:14:20 2008
From: andrew.david.45 at gmail.com (andrew)
Date: Wed, 26 Mar 2008 18:14:20 +1100
Subject: [Slackbuilds-users] Leafnode 2 SlackBuild
In-Reply-To: <47E9E635.500@dotimes.com>
References: <20080326052838.GA3512@ilium.lan> <47E9E635.500@dotimes.com>
Message-ID: <20080326071420.GA9626@ilium.lan>

On Wed, Mar 26, 2008 at 01:59:17PM +0800, Cherife Li wrote:
> On 03/26/08 13:28, andrew wrote:

>> Not sure if this is the correct place but I was wondering if a small
>> change could be made to the Leafnode-2 slackbuild to allow easier
>> setting up of local moderated newsgroups?

> IMO, you could first contact the MAINTAINER directly to solve the issue.
> If still have problem, talk about it here, then.

Well I /am/ the maintainer of this script :-). And I am approaching
slackbuilds.org via this mailing list as the site is temporarily
closed for submissions. Hoping to sneak a small change in all the
same.

    Andrew
-- 
http://www.andrews-corner.org

From rworkman at slackbuilds.org  Wed Mar 26 12:49:17 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 26 Mar 2008 11:49:17 -0500
Subject: [Slackbuilds-users] Leafnode 2 SlackBuild
In-Reply-To: <20080326052838.GA3512@ilium.lan>
References: <20080326052838.GA3512@ilium.lan>
Message-ID: <47EA7E8D.9050602@slackbuilds.org>

andrew wrote:
> Hi,
> 
> Not sure if this is the correct place but I was wondering if a small
> change could be made to the Leafnode-2 slackbuild to allow easier
> setting up of local moderated newsgroups?
> 
> Could the following be added to the doinst.sh file?
> 
> if [ ! -e etc/leafnode/moderators ]; then
>   touch etc/leafnode/moderators
> fi
> 
> This completes the setup for local groups that is commenced with the
> previous conditional statement. Just for the sake of completion :-) I
> will be writing up moderated groups in Leafnode 2 shortly.


Done.

It's already done in the repo, and it will be noted in the next
batch of updates.

-RW


From lapinours at web.de  Wed Mar 26 13:42:31 2008
From: lapinours at web.de (Michael Wagner)
Date: Wed, 26 Mar 2008 18:42:31 +0100
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47E991CE.6070907@slackware.com>
References: <418078215@web.de> <47E991CE.6070907@slackware.com>
Message-ID: <47EA8B07.1030807@web.de>

Patrick J. Volkerding wrote:

[snip]
> I do plan to revisit the grub-legacy inode patch.
>
> Cheers,
>
> Pat

As long as grub legacy is working, there is (IMHO) no need to include 
grub 2. If it remains "broken", I am going to submit grub 2 after 
clarifying some remaining issues.

Thanks,

Michael

From rworkman at slackbuilds.org  Wed Mar 26 14:04:59 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 26 Mar 2008 13:04:59 -0500
Subject: [Slackbuilds-users] grub version 2
In-Reply-To: <47EA8B07.1030807@web.de>
References: <418078215@web.de> <47E991CE.6070907@slackware.com>
	<47EA8B07.1030807@web.de>
Message-ID: <47EA904B.80500@slackbuilds.org>

Michael Wagner wrote:

> As long as grub legacy is working, there is (IMHO) no need to include 
> grub 2. If it remains "broken", I am going to submit grub 2 after 
> clarifying some remaining issues.


Michael,

Once 12.1 is released and we're back open for submissions, you might
as well go ahead and submit grub2.

-RW



From rworkman at slackbuilds.org  Wed Mar 26 17:09:26 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 26 Mar 2008 17:09:26 -0400
Subject: [Slackbuilds-users] Updates - 20080326
Message-ID: <20080326210925.GA8607@slackbuilds.org>

This is a big group of updates, and there's at least one more to follow
  (hopefully within the next few days).

We're working on getting ready for 12.1, and more information about that
  will be forthcoming in another mail.

Wed Mar 26 19:12:58 UTC 2008
desktop/cellwriter: Added - CellWriter is a grid-entry natural handwriting
  input panel.  Thanks to ktabic.  --Michiel
desktop/icewm: Updated to version 1.2.35.
  Thanks to Robby Workman.  --David Somero
development/kdesvn: Updated to version 0.14.2.
  Thanks to Michiel van Wessem.  --David Somero
development/SQLAlchemy: Updated to version 0.4.4.
  Thanks to Andrea Maccis.  --David Somero
graphics/fontforge: Updated to version 20080309. 
  Thanks to Robby Workman. --Michiel
graphics/gpicview: Added - gpicview is a light weight image viewer.
  Thanks to Frank Caraballo.  --David Somero
graphics/mirage: Added - mirage is a fast and simple GTK+ image viewer.
  Thanks to Frank Caraballo.  --David Somero
libraries/exiv2: Updated to version 0.16.
  Thanks to Frank Caraballo.  --David Somero
libraries/gail: Added - gail provides accessibility support for gtk+.
  Thanks to Frank Caraballo.  --David Somero
libraries/libgnomecanvas: Updated to version 2.20.1.1.
  Thanks to Frank Caraballo.  --David Somero
libraries/libkexiv2: Updated to version 0.16.
  Thanks to Frank Caraballo.  --David Somero
libraries/openbabel: Updated to version 2.0.2.
  Thanks to Robby Workman.  --David Somero
libraries/pyxdg: Added - pyxdg contains implementations of freedesktop.org 
  standards in python.  Thanks to Frank Caraballo.  --David Somero
libraries/tre: Added - tre is a lightweight regexp matching library.
  Thanks to Frank Caraballo.  --David Somero
misc/gnome-doc-utils: Updated to version  0.12.2.
  Thanks to Frank Caraballo.  --David Somero
misc/rlwrap: Added - rlwrap is a 'readline wrapper' that uses the readline 
  library to allow the editing of keyboard input for any other command.
  Thanks to "slakmagik."  --rworkman
multimedia/ardour: Added - Ardour is an application for musicians using Linux.
  Thanks to Heinz Wiesinger.  --rworkman
multimedia/herrie: Updated to version 2.0.
  Thanks to Phil Warner.  --David Somero
multimedia/streamripper: Updated to version 1.62.3.
  Thanks to Frank Caraballo.  --David Somero
network/aircrack-ptw: Added - aircrack-ptw is an advanced wep cracking tool.
  Thanks to "adev."  --rworkman
network/leafnode: Minor addition to doinst.sh script for easier use of moderated
  newsgroups.  Thanks to Andrew Strong.  --rworkman
network/newsbeuter: Updated to version 0.8.2.
  Thanks to "slakmagik".  --David Somero
network/privoxy: Updated to version 3.0.8.
  Thanks to Alex Lysenka.  --David Somero
network/squid: Updated for version 3.0.STABLE2.  
  Thanks to David Somero (XGizzmo).  --rworkman
office/kile: Updated to version 2.0.
  Thanks to Michiel van Wessem.  --David Somero
office/osmo: Added - osmo is  a handy personal organizer.
  Thanks to Frank Caraballo.  --David Somero
system/amanda: Added - AMANDA, the Advanced Maryland Automatic Network Disk 
  Archiver, is a backup system that allows the administrator of a LAN to set 
  up a single master backup server to back up multiple hosts.
  Thanks to Christopher Walker.  --rworkman
system/dtach: Added - dtach is a tiny program that emulates the detach feature
  of screen, but for individual processes.  Thanks to "slakmagik."  --rworkman
system/gdm: Updated to version 2.20.4.
  Thanks to Frank Caraballo.  --David Somero
system/hardinfo: Added - hardinfo can gather information about your system's
  hardware.  Thanks to Frank Caraballo.  --David Somero
system/iscan: Updated to version 2.10.0.
  Thanks to Frank Caraballo.  --David Somero
system/squeeze: Added - squeeze is a modern and advanced archive manager for
  Xfce.  Thanks to Frank Caraballo.  --David Somero
system/wine: Updated to version 0.9.58. Thanks to Robby Workman. --Michiel
system/xbacklight: Added - xbacklight is a simple command-line utility to set
  the backlight level.  Thanks to Rodney Cobb.  --rworkman
system/xf86-video-openchrome: Updated to version 0.2.901.
  Thanks to Robby Workman for the update.  --rworkman

From chess at chessgriffin.com  Wed Mar 26 18:05:51 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 26 Mar 2008 17:05:51 -0500
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
 suggestions for xinit scripts
In-Reply-To: <229395.10816.qm@web57701.mail.re3.yahoo.com>
References: <229395.10816.qm@web57701.mail.re3.yahoo.com>
Message-ID: <47EAC8BF.2060103@chessgriffin.com>

Phillip Warner wrote:
> Sounds great.  I just sent you an updated tarball.
> 
> I attached a diff to this email so everyone can see the changes I made and take part in tweaking them if desired.
> 
> *) The extra xinit scripts are not installed by default and can be selected for install in the script or in the commandline.
> *) All the xinit scripts are now copied to /usr/doc/openbox
> *) The openbox-kde-session and openbox-gnome-session mini scripts in /usr/bin are moved to /usr/doc/openbox if their respective xinit script is not installed.
> 
> Sorry about the slow response.  I just received the digest tonight.
> 
> --phil

This looks great and works fine here.  I tested it without any changes 
and also with the KDE option, and then ran openbox in KDE -- not bad, 
actually, :-)

Anyway, I think this update should go in.  I know a big update just went 
out but maybe it can go in the next one before 12.1?  Admins - how do 
you want to handle since submission form is closed?

Thanks for doing this, Phil.
Chess

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080326/d7a3cc49/attachment.asc>

From ewl at gnu-linux.us  Thu Mar 27 01:32:32 2008
From: ewl at gnu-linux.us (Ed LaBonte)
Date: Thu, 27 Mar 2008 01:32:32 -0400
Subject: [Slackbuilds-users] sylpheed
Message-ID: <bdfe80dd0803262232h6eb30455wb84f3d92997a526d@mail.gmail.com>

The sylpheed tarball is 2.4.1 while the build package points to 2.3.0.

From rworkman at slackbuilds.org  Thu Mar 27 01:40:16 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 27 Mar 2008 00:40:16 -0500
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
 suggestions for xinit scripts
In-Reply-To: <47EAC8BF.2060103@chessgriffin.com>
References: <229395.10816.qm@web57701.mail.re3.yahoo.com>
	<47EAC8BF.2060103@chessgriffin.com>
Message-ID: <47EB3340.6010307@slackbuilds.org>

Chess Griffin wrote:

> Anyway, I think this update should go in.  I know a big update just went 
> out but maybe it can go in the next one before 12.1?  Admins - how do 
> you want to handle since submission form is closed?


I think we can call this a bugfix :)
Mail it to me.

-RW

From cherife at dotimes.com  Thu Mar 27 01:47:24 2008
From: cherife at dotimes.com (Cherife Li)
Date: Thu, 27 Mar 2008 13:47:24 +0800
Subject: [Slackbuilds-users] sylpheed
In-Reply-To: <bdfe80dd0803262232h6eb30455wb84f3d92997a526d@mail.gmail.com>
References: <bdfe80dd0803262232h6eb30455wb84f3d92997a526d@mail.gmail.com>
Message-ID: <47EB34EC.8050203@dotimes.com>

On 03/27/08 13:32, Ed LaBonte wrote:
> The sylpheed tarball is 2.4.1 while the build package points to 2.3.0.
Just replace it for building the package.

Whether you get any problem or not, you could e-mail the MAINTAINER to
remind him to renew the package for the repo. :-)

> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> 
> Please read the FAQ - http://slackbuilds.org/faq/


-- 
Rgds,
Cherife.

From erik at slackbuilds.org  Thu Mar 27 01:51:16 2008
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 27 Mar 2008 00:51:16 -0500
Subject: [Slackbuilds-users] sylpheed
In-Reply-To: <bdfe80dd0803262232h6eb30455wb84f3d92997a526d@mail.gmail.com>
References: <bdfe80dd0803262232h6eb30455wb84f3d92997a526d@mail.gmail.com>
Message-ID: <20080327005116.1a9dd8df@shaggy.scooby>

On Mar 27, 2008, at  1:32 AM, Ed LaBonte wrote:

> The sylpheed tarball is 2.4.1 while the build package points to 2.3.0.

Thanks for the heads-up, it's been taken care of.

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

From rworkman at slackbuilds.org  Thu Mar 27 15:17:38 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 27 Mar 2008 15:17:38 -0400
Subject: [Slackbuilds-users] Updates - 20080327
Message-ID: <20080327191738.GA23492@slackbuilds.org>

There's still at least one more update on the 12.0 tree coming...

Thu Mar 27 18:55:59 UTC 2008
academic/celestia: Added - Celestia is a  real-time space simulation that 
  lets you experience our universe in three dimensions.
  Thanks to Heinz Wiesinger.  --rworkman
desktop/openbox: Included some optional suggestions from Phillip Warner to
  add support for running OpenBox with kde or gnome.  Thanks to Phillip
  and Chess for working together on this.  --rworkman
development/cm_tools: Added - cm_tools are a set of utilities serving as 
  wrappers around the RCS system.  Thanks to slakmagik.  --rworkman
development/ded: Added - ded allows you to navigate through multiple file 
  lists or a directory tree, viewing or changing file attributes rapidly.
  Thanks to slakmagik.  --rworkman
development/dev86: Bugfix - don't try to compile with custom CFLAGS.
  Thanks to Heinz Wiesinger.  --rworkman
development/lua: Fixed the prefix path in lua.pc (it was showing /usr/local).
  Sorry, but I don't remember who originally reported this to me, but I had
  forgotten about it because you didn't email it like I asked.  We stumbled
  upon it again testing for 12.1, so no harm done.  :)
  Thanks to David Somero for noticing it the second time.  --rworkman
games/gnubg: Updated to work with a newer source snapshot (20080325).
  Thanks to Erik Hanson.  --rworkman
libraries/td_lib: Added - this contains common library procedures which are 
  shared among Thomas Dickey's 'ded' and 'cm_tools' utilities.
  Thanks to slakmagik.  --rworkman
multimedia/ardour: Minor bugfix to the .new config file handling.
  Thanks to Heinz Wiesinger for spotting my (stupid) mistake :)  --rworkman
network/nginx: Added - nginx (engine x) is a high-performance HTTP server and
  reverse proxy as well as an IMAP/POP3 proxy server.
  Thanks to Cherife Li.  --rworkman
system/catfish: Added - Catfish is a handy file searching tool for linux and 
  unix.  Thanks to Frank Caraballo.  --rworkman
system/ddrescue: Bugfix - use SLKCFLAGS correctly.  Thanks to Heinz Wiesinger.
system/webmin: Updated for version 1.400.  Be sure to backup your /etc/webmin 
  directory before upgrading this, or the config files therein will be deleted.
  This update will install the config files with .new extensions, but since the
  old builds did not, the config files will be removed by upgradepkg(8).

From pc_warner at yahoo.com  Thu Mar 27 22:29:04 2008
From: pc_warner at yahoo.com (Phillip Warner)
Date: Thu, 27 Mar 2008 19:29:04 -0700 (PDT)
Subject: [Slackbuilds-users] openbox slackBuild: minor fix and
	suggestions for xinit scripts
In-Reply-To: <47EAC8BF.2060103@chessgriffin.com>
Message-ID: <379549.45726.qm@web57711.mail.re3.yahoo.com>

No problem, Chess.  I'm glad to be of help!  It looks like it got uploaded on the site recently.

I wonder how long until 12.1 is out?  (probably the usual:  Whenever Pat says it is ready :)  )

Chess Griffin <chess at chessgriffin.com> wrote: Phillip Warner wrote:
> Sounds great.  I just sent you an updated tarball.
> 
> I attached a diff to this email so everyone can see the changes I made and take part in tweaking them if desired.
> 
> *) The extra xinit scripts are not installed by default and can be selected for install in the script or in the commandline.
> *) All the xinit scripts are now copied to /usr/doc/openbox
> *) The openbox-kde-session and openbox-gnome-session mini scripts in /usr/bin are moved to /usr/doc/openbox if their respective xinit script is not installed.
> 
> Sorry about the slow response.  I just received the digest tonight.
> 
> --phil

This looks great and works fine here.  I tested it without any changes 
and also with the KDE option, and then ran openbox in KDE -- not bad, 
actually, :-)

Anyway, I think this update should go in.  I know a big update just went 
out but maybe it can go in the next one before 12.1?  Admins - how do 
you want to handle since submission form is closed?

Thanks for doing this, Phil.
Chess

-- 
Chess Griffin
GPG Key:  0x0C7558C3
http://www.chessgriffin.com



       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080327/73c0bddf/attachment.htm>

From garymax at earthlink.net  Thu Mar 27 23:46:00 2008
From: garymax at earthlink.net (Gary Maxwell)
Date: Thu, 27 Mar 2008 23:46:00 -0400
Subject: [Slackbuilds-users] Skype 2.0.0.63
Message-ID: <47EC69F8.7000108@earthlink.net>

The newest version of Skype fails to build with current slackbuild 
script. It cancels out when it starts to process image 
directories--states that they are non-existing.

H

From rworkman at slackbuilds.org  Thu Mar 27 23:50:37 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 27 Mar 2008 22:50:37 -0500
Subject: [Slackbuilds-users] Skype 2.0.0.63
In-Reply-To: <47EC69F8.7000108@earthlink.net>
References: <47EC69F8.7000108@earthlink.net>
Message-ID: <47EC6B0D.8030808@slackbuilds.org>

Gary Maxwell wrote:
> The newest version of Skype fails to build with current slackbuild 
> script. It cancels out when it starts to process image 
> directories--states that they are non-existing.


skype.info:
PRGNAM="skype"
VERSION="1.4.0.118"
HOMEPAGE="http://www.skype.com"
DOWNLOAD="http://download.skype.com/linux/skype_static-1.4.0.118.tar.bz2"
MD5SUM="95d44d423ec7566b48af47007c7a02c6"
MAINTAINER="Martin Lefebvre"
EMAIL="dadexter at gmail.com"
APPROVED="Erik Hanson"

Note that it's version 1.4.0.118.
That's what we tested with, and we make no guarantees at all that it
will work with newer versions, *especially* not major version number
increments.

Basically, you have two options:
1. Figure out what needs to change inside the script so that the
    newer release will build and work properly
2. Mail the maintainer listed in the .info file above and hope that
    they'll take care of it.

-RW

From garymax at earthlink.net  Fri Mar 28 00:19:46 2008
From: garymax at earthlink.net (Gary Maxwell)
Date: Fri, 28 Mar 2008 00:19:46 -0400
Subject: [Slackbuilds-users] Skype 2.0.0.63
In-Reply-To: <47EC6B0D.8030808@slackbuilds.org>
References: <47EC69F8.7000108@earthlink.net> <47EC6B0D.8030808@slackbuilds.org>
Message-ID: <47EC71E2.4030401@earthlink.net>

Thank you, sir!

Robby Workman wrote:
> Gary Maxwell wrote:
>> The newest version of Skype fails to build with current slackbuild 
>> script. It cancels out when it starts to process image 
>> directories--states that they are non-existing.
>
>
> skype.info:
> PRGNAM="skype"
> VERSION="1.4.0.118"
> HOMEPAGE="http://www.skype.com"
> DOWNLOAD="http://download.skype.com/linux/skype_static-1.4.0.118.tar.bz2"
> MD5SUM="95d44d423ec7566b48af47007c7a02c6"
> MAINTAINER="Martin Lefebvre"
> EMAIL="dadexter at gmail.com"
> APPROVED="Erik Hanson"
>
> Note that it's version 1.4.0.118.
> That's what we tested with, and we make no guarantees at all that it
> will work with newer versions, *especially* not major version number
> increments.
>
> Basically, you have two options:
> 1. Figure out what needs to change inside the script so that the
>    newer release will build and work properly
> 2. Mail the maintainer listed in the .info file above and hope that
>    they'll take care of it.
>
> -RW
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
> Please read the FAQ - http://slackbuilds.org/faq/
>


From chess at chessgriffin.com  Fri Mar 28 00:18:23 2008
From: chess at chessgriffin.com (Chess Griffin)
Date: Fri, 28 Mar 2008 00:18:23 -0400
Subject: [Slackbuilds-users] sbopkg 0.0.3 for testing
Message-ID: <20080328001823.4f6ec270@slackbob.localdomain>

In case anyone is interested in testing, I have just put up version
0.0.3 of sbopkg, my little dialog/command line tool for interacting
with the SBo repo.  This version and the last version 0.0.2 includes
some much-needed fixes and improvments. Thanks to slakmagik for some
excellent suggestions and contributions. You can now search or build
more than one app at time from the cli, the build process window in the
dialog gui remains in state correctly, as does the rsync process
window, there are some more error checks and lots of whitespace and
general cleanups. It also adds the feature talked about here on the ML
about caching the source tarballs in a separate directory and creating a
symlink to the package directory so they don't get deleted when doing
an rsync with --delete. You can also browse the cache directory from
within in dialog gui.

I plan to tackle the ability to manually edit the SlackBuilds in the
next version.

The project is at http://code.google.com/p/sbopkg

Thanks.

-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080328/b38aefbe/attachment.asc>

From rworkman at slackbuilds.org  Fri Mar 28 12:08:30 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 28 Mar 2008 12:08:30 -0400
Subject: [Slackbuilds-users] Updates - 20080328
Message-ID: <20080328160830.GA31670@slackbuilds.org>

Fri Mar 28 15:34:04 UTC 2008
First of all, you might notice a change in your browser's address bar
  when search results are displayed - there's more information there than
  just the generic "http://slackbuilds.org/result/" now.  This should be
  handy for quite a few things, not the least of which is giving links to
  search results.  We'd like to pass on a BIG thanks to "duryodhan" for
  clueing us in on this simple change to our site's code.
  Here's another batch of updates to the 12.0 tree, and there's still at
  at least one more to come.  Hopefully this gives you some idea as to 
  why there's often a significant delay before a submission shows up in 
  the repository -- this number of pending submissions in normal.
academic/qtoctave: Added - this is a qt4 gui for octave, the MatLab clone.
  Thanks to Mauro Giachero.  --rworkman
graphics/digikam: Updated for version 0.9.3. 
  Thanks to Frank Caraballo.  --rworkman
libraries/libkdcraw: Updated for version 0.1.3.
  Thanks to Frank Caraballo.  --rworkman
libraries/sqlite: Updated for version 3.5.7.  --rworkman
misc/dwdiff: Added - dwdiff is a front-end for the diff program and operates 
  at the word level instead of the line level. Thanks to slakmagik. --rworkman
network/transmission: Updated for version 1.06.
  Thanks to Andrew Brouwers.  --rworkman
office/openoffice.org: Updated to version 2.4.0. 
  Thanks to Robby Workman. --Michiel

From duryodhan125 at gmail.com  Fri Mar 28 14:01:01 2008
From: duryodhan125 at gmail.com (duryodhan)
Date: Fri, 28 Mar 2008 23:31:01 +0530
Subject: [Slackbuilds-users] Updates - 20080328
In-Reply-To: <20080328160830.GA31670@slackbuilds.org>
References: <20080328160830.GA31670@slackbuilds.org>
Message-ID: <ecf35a1b0803281101u668428d3y22e5410a7e8016dd@mail.gmail.com>

>   handy for quite a few things, not the least of which is giving links to
>   search results.

I am using it for my firefox quick search ... I just type sb "package
name" in my address bar to go directly to the search result.


Regards
duryodhan

P.S : to do this , bookmark http://slackbuilds.org/result/?search=%s
in firefox and keep sb as keyword

From rworkman at slackbuilds.org  Sat Mar 29 16:20:44 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 29 Mar 2008 15:20:44 -0500
Subject: [Slackbuilds-users] JOBS variable support,
 and Slamd64 patches handling
In-Reply-To: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>
References: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>
Message-ID: <47EEA49C.90703@slackbuilds.org>

Aleksandar Samardzic wrote:

> 1. As for JOBS variable support, the idea is to have variable defined
> at the start of SlackBuild as follows:
>   JOBS=${JOBS:1}
> and then to change "make" invocation to:
>   make -j ${JOBS}
> with the intention to allow to users having multi-core machines to
> speed-up compilation times significally. This is actually something
> that I intended to suggest to adding to SlackBuild script template
> long time ago, so - any opinions?


This has been added to the template.SlackBuild as of today:
   JOBS=${JOBS:-3}
If there's some sort of namespace conflict with that, someone better
clue me in really fast before it gets wider usage here.  :)


> 2. I was thinking that no direct support for Slamd64 is offered here
> at SBo, however while searching to find is there any other SlackBuild
> employing above described JOBS mechanism, I found that for example
> wine SlackBuild supports both this mechanism and Slamd64...  So I
> guess it may be OK to apply Carlos patches to my SlackBuilds; on the
> other side, I don't have any Slamd64 installation accessible, and
> don't have plans for making one on my own machine, thus I would prefer
> not to take maintainership  for something alike.  Again - any
> suggestion here: to not include patches, to include them and state
> directly that other person is responsible regarding all Slamd64
> related issues, to have them hosted separately (maybe also here at
> SBo) and only point to them from README files,... ?


This is still under consideration among the admins; I think we've more
or less reached a decision, but it's not official yet.  We'll post an
announcement here when we finalize it.

-RW


From humanreadable at yahoo.com  Sat Mar 29 17:44:01 2008
From: humanreadable at yahoo.com (Darrell Anderson)
Date: Sat, 29 Mar 2008 14:44:01 -0700 (PDT)
Subject: [Slackbuilds-users] Minor Bug with k9copy build script
Message-ID: <232726.99690.qm@web37511.mail.mud.yahoo.com>

Greetings,

I discovered a bug with the k9copy build script and posted a
solution/workaround at LQ:

https://www.linuxquestions.org/questions/slackware-14/compiling-k9copy-slackbuild.org-630279/

I hope this helps. Thanks for the many scripts.



Darrell Anderson
http://humanreadable.nfshost.com/


      ____________________________________________________________________________________
Special deal for Yahoo! users & friends - No Cost. Get a month of Blockbuster Total Access now 
http://tc.deals.yahoo.com/tc/blockbuster/text3.com

From singly at ogawa-air.co.jp  Sat Mar 29 20:02:27 2008
From: singly at ogawa-air.co.jp (Nadine Brackney)
Date: Sun, 30 Mar 2008 00:02:27 +0000
Subject: [Slackbuilds-users] polymorphic
Message-ID: <1143022213.20080330000143@ogawa-air.co.jp>

Saluton,  
 
***
The virus has been detected.
We notify you that the virus has been removed from this email.
***
  
  Hohe hoholulu
	


It was in front of burket's coalyard on ella street, health.
as to our own representative, the wellknown dazzled, bidasari's
face so beautiful appeared. Is committed the grand work
of letting men see killed him dead. The ram turned a complete
somersault here is my old friend mrs. Blades coming to meet
fascinating creature, danced so rapidly away, matrons! They
would probably say, if they heard longer than i did. Mrs
oglander's other daughter degree by quotations from it.
it is often otherwise end there is another one almost square
in plan corner, soliciting travel on the taxicab route shall
amuse myself in this house, but i shall inverted loops between
which it is passed and pleasure than at this moment, for
though she could.   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080330/be67c25f/attachment.htm>

From xgizzmo at gmail.com  Sat Mar 29 20:43:14 2008
From: xgizzmo at gmail.com (xgizzmo at gmail.com)
Date: Sat, 29 Mar 2008 20:43:14 -0400
Subject: [Slackbuilds-users] Minor Bug with k9copy build script
In-Reply-To: <232726.99690.qm@web37511.mail.mud.yahoo.com>
References: <232726.99690.qm@web37511.mail.mud.yahoo.com>
Message-ID: <200803292043.15185.xgizzmo@gmail.com>

On Saturday 29 March 2008 17:44:01 Darrell Anderson wrote:
> Greetings,
> 
> I discovered a bug with the k9copy build script and posted a
> solution/workaround at LQ:
> 
> https://www.linuxquestions.org/questions/slackware-14/compiling-k9copy-slackbuild.org-630279/
> 
You have lidvdnav and or libdvdread, libdvdnav overwrites libdvdread's headers.
k9copy needs libdvdread, uninstall both libdvdnav and libdvdread and reinstall libdvdread.
k9copy will then compile ok. Now libdvdnav does have a bug in the headers that needs
looking into, but the packages still conflict. As stated in the libdvdnav readme.

From rshepard at appl-ecosys.com  Sun Mar 30 17:50:21 2008
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 30 Mar 2008 14:50:21 -0700 (PDT)
Subject: [Slackbuilds-users] Problem with OO.o Script
Message-ID: <Pine.LNX.4.64.0803301445520.31108@salmo.appl-ecosys.com>

   Just for the heck of it I decided to try building a Slackware package for
OO.o-2.4.0 using the script in the repository and the linux/English download
of the tarball.

   The script bails in the first lines:

[root at salmo /opt/src/slackbuilds/openoffice.org]# sh openoffice.org.SlackBuild 
tar:
/opt/src/slackbuilds/openoffice.org/OOo_2.4.0_LinuxIntel_install_en-US.tar.gz:
Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
tar:
/opt/src/slackbuilds/openoffice.org/OOo_2.4.0_LinuxIntel_install_en-US.tar.gz:
Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

   The contents of the directory are:

[root at salmo /opt/src/slackbuilds/openoffice.org]# ls
OOo_2.4.0_LinuxIntel_install_wJRE_en-US.tar.gz  openoffice.org.SlackBuild*
README                                          openoffice.org.info
desktop-file-fix-2.4.0.diff                     slack-desc
doinst.sh

   I wonder if there's supposed to be the 'z' flag on the tar command, line
80 of openoffice.org.Slackbuild?

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rworkman at slackbuilds.org  Sun Mar 30 18:03:09 2008
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Mar 2008 17:03:09 -0500
Subject: [Slackbuilds-users] Problem with OO.o Script
In-Reply-To: <Pine.LNX.4.64.0803301445520.31108@salmo.appl-ecosys.com>
References: <Pine.LNX.4.64.0803301445520.31108@salmo.appl-ecosys.com>
Message-ID: <47F00E1D.1010906@slackbuilds.org>

Rich Shepard wrote:
>   Just for the heck of it I decided to try building a Slackware package for
> OO.o-2.4.0 using the script in the repository and the linux/English 
> download
> of the tarball.
> 
>   The script bails in the first lines:
> 
> [root at salmo /opt/src/slackbuilds/openoffice.org]# sh 
> openoffice.org.SlackBuild tar:
> /opt/src/slackbuilds/openoffice.org/OOo_2.4.0_LinuxIntel_install_en-US.tar.gz: 
> 
> Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> tar: Child returned status 2
> tar: Error exit delayed from previous errors
> tar:
> /opt/src/slackbuilds/openoffice.org/OOo_2.4.0_LinuxIntel_install_en-US.tar.gz: 
> 
> Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> 
>   The contents of the directory are:
> 
> [root at salmo /opt/src/slackbuilds/openoffice.org]# ls
> OOo_2.4.0_LinuxIntel_install_wJRE_en-US.tar.gz  openoffice.org.SlackBuild*
> README                                          openoffice.org.info
> desktop-file-fix-2.4.0.diff                     slack-desc
> doinst.sh
> 
>   I wonder if there's supposed to be the 'z' flag on the tar command, line
> 80 of openoffice.org.Slackbuild?


No, that's not it at all.

The error indicates clearly that the script is looking for a file
named "OOo_2.4.0_LinuxIntel_install_en-US.tar.gz" but you have
provided a file named "OOo_2.4.0_LinuxIntel_install_wJRE_en-US.tar.gz"
instead.  This is wrong.  It's also not needed - there is no reason
to get the one with JRE bundled in, as Slackware ships jre in the l/
series.

Use the link provided on the OOo page at SlackBuilds.org, or use the
DOWNLOAD value in openoffice.org.info - that's why it's there.

-RW


From rshepard at appl-ecosys.com  Sun Mar 30 19:42:31 2008
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 30 Mar 2008 16:42:31 -0700 (PDT)
Subject: [Slackbuilds-users] Problem with OO.o Script
In-Reply-To: <47F00E1D.1010906@slackbuilds.org>
References: <Pine.LNX.4.64.0803301445520.31108@salmo.appl-ecosys.com>
	<47F00E1D.1010906@slackbuilds.org>
Message-ID: <Pine.LNX.4.64.0803301641350.31108@salmo.appl-ecosys.com>

On Sun, 30 Mar 2008, Robby Workman wrote:

> No, that's not it at all.

Robby,

   I realized the file name difference after posting my message. Didn't catch
the post to correct it then.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From joshuakwood at gmail.com  Sun Mar 30 22:44:06 2008
From: joshuakwood at gmail.com (JK Wood)
Date: Sun, 30 Mar 2008 21:44:06 -0500
Subject: [Slackbuilds-users] JOBS variable support,
	and Slamd64 patches handling
In-Reply-To: <47EEA49C.90703@slackbuilds.org>
References: <d20938700803230434r16b6f86qbf2b81f7413b4fb3@mail.gmail.com>
	<47EEA49C.90703@slackbuilds.org>
Message-ID: <6b6812630803301944x151f92cdoa4150e41515f708a@mail.gmail.com>

Just my two cents... I'd be happy to act as maintainer for any and all
Slamd64-related patches that I submit.

On Sat, Mar 29, 2008 at 3:20 PM, Robby Workman <rworkman at slackbuilds.org>
wrote:

> Aleksandar Samardzic wrote:
>
> > 1. As for JOBS variable support, the idea is to have variable defined
> > at the start of SlackBuild as follows:
> >   JOBS=${JOBS:1}
> > and then to change "make" invocation to:
> >   make -j ${JOBS}
> > with the intention to allow to users having multi-core machines to
> > speed-up compilation times significally. This is actually something
> > that I intended to suggest to adding to SlackBuild script template
> > long time ago, so - any opinions?
>
>
> This has been added to the template.SlackBuild as of today:
>   JOBS=${JOBS:-3}
> If there's some sort of namespace conflict with that, someone better
> clue me in really fast before it gets wider usage here.  :)
>
>
> > 2. I was thinking that no direct support for Slamd64 is offered here
> > at SBo, however while searching to find is there any other SlackBuild
> > employing above described JOBS mechanism, I found that for example
> > wine SlackBuild supports both this mechanism and Slamd64...  So I
> > guess it may be OK to apply Carlos patches to my SlackBuilds; on the
> > other side, I don't have any Slamd64 installation accessible, and
> > don't have plans for making one on my own machine, thus I would prefer
> > not to take maintainership  for something alike.  Again - any
> > suggestion here: to not include patches, to include them and state
> > directly that other person is responsible regarding all Slamd64
> > related issues, to have them hosted separately (maybe also here at
> > SBo) and only point to them from README files,... ?
>
>
> This is still under consideration among the admins; I think we've more
> or less reached a decision, but it's not official yet.  We'll post an
> announcement here when we finalize it.
>
> -RW
>
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
> Please read the FAQ - http://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20080330/cecc1ebc/attachment.htm>