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 do