From elyb at ioplasm.net  Sat Aug  1 05:02:23 2009
From: elyb at ioplasm.net (Brad Ely)
Date: Sat, 1 Aug 2009 01:02:23 -0400
Subject: [Slackbuilds-users] Flash Player 10.0.32.18 update
Message-ID: <20090801010223.2e979c1f.elyb@ioplasm.net>

Here is an update to flash-player-plugin to 10.0.32.18 which "works
for me" on -current (13.0) so someone should verify this works on 12.2.
Adobe's new tar file has the same name but comes with the shared object
file only, and *no* subdirectory.

--- flash-player-plugin.SlackBuild.orig	2009-02-26 23:58:09.000000000 -0500
+++ flash-player-plugin.SlackBuild	2009-08-01 00:16:49.000000000 -0400
@@ -5,7 +5,7 @@
 # Script maintained by Robby Workman <rworkman at slackbuilds.org>
 
 PRGNAM=flash-player-plugin
-VERSION=10.0_r22
+VERSION=10.0_r32
 ARCH=i386
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
@@ -26,10 +26,9 @@
 set -e
 
 rm -rf $PKG
-mkdir -p $TMP $PKG $OUTPUT
-cd $TMP
+mkdir -p $TMP/install_flash_player_10_linux $PKG $OUTPUT
+cd $TMP/install_flash_player_10_linux
 tar xvf $CWD/install_flash_player_10_linux.tar.gz
-cd install_flash_player_10_linux
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .
 
--- flash-player-plugin.info.orig	2009-03-03 14:46:02.000000000 -0500
+++ flash-player-plugin.info	2009-08-01 00:23:42.000000000 -0400
@@ -2,7 +2,7 @@
 VERSION="10.0_r22"
 HOMEPAGE="http://www.adobe.com/products/flashplayer"
 DOWNLOAD="http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_10_linux.tar.gz"
-MD5SUM="23e4c2b844db0f87ff62084178aa2b1f"
+MD5SUM="6306980e40a3266b4b6c173bfcfdc946"
 MAINTAINER="Robby Workman"
 EMAIL="rw at rlworkman.net"
 APPROVED="Erik Hanson"

-- 
Brad Ely

From rworkman at slackbuilds.org  Sat Aug  1 05:11:51 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 1 Aug 2009 00:11:51 -0500
Subject: [Slackbuilds-users] Flash Player 10.0.32.18 update
In-Reply-To: <20090801010223.2e979c1f.elyb@ioplasm.net>
References: <20090801010223.2e979c1f.elyb@ioplasm.net>
Message-ID: <20090801001151.7c46f4aa@liberty.rlwhome.lan>

On Sat, 1 Aug 2009 01:02:23 -0400
Brad Ely <elyb at ioplasm.net> wrote:

> Here is an update to flash-player-plugin to 10.0.32.18 which "works
> for me" on -current (13.0) so someone should verify this works on
> 12.2. Adobe's new tar file has the same name but comes with the
> shared object file only, and *no* subdirectory.


Have a look at this:

http://slackbuilds.org/flash-player-plugin/

That's updated for both 32 and 64 (and for anyone paying attention,
there's a teaser...)  ;-)

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

From vbatts at hashbangbash.com  Sat Aug  1 05:19:27 2009
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Sat, 1 Aug 2009 00:19:27 -0500
Subject: [Slackbuilds-users] Flash Player 10.0.32.18 update
In-Reply-To: <20090801001151.7c46f4aa@liberty.rlwhome.lan>
References: <20090801010223.2e979c1f.elyb@ioplasm.net>
	<20090801001151.7c46f4aa@liberty.rlwhome.lan>
Message-ID: <2015330f0907312219g329699ecpa2e6378827fcf0e7@mail.gmail.com>

DOWNLOAD_x86_64=
nicely nicely


vb
205.352.4112
http://hashbangbash.com/



On Sat, Aug 1, 2009 at 12:11 AM, Robby Workman<rworkman at slackbuilds.org> wrote:
> On Sat, 1 Aug 2009 01:02:23 -0400
> Brad Ely <elyb at ioplasm.net> wrote:
>
>> Here is an update to flash-player-plugin to 10.0.32.18 which "works
>> for me" on -current (13.0) so someone should verify this works on
>> 12.2. Adobe's new tar file has the same name but comes with the
>> shared object file only, and *no* subdirectory.
>
>
> Have a look at this:
>
> http://slackbuilds.org/flash-player-plugin/
>
> That's updated for both 32 and 64 (and for anyone paying attention,
> there's a teaser...) ?;-)
>
> -RW
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>

From druiloor at zonnet.nl  Mon Aug  3 19:53:04 2009
From: druiloor at zonnet.nl (Menno Duursma)
Date: Mon, 3 Aug 2009 21:53:04 +0200 (CEST)
Subject: [Slackbuilds-users] cfengine download location
Message-ID: <alpine.LNX.2.00.0908032130340.2843@pc.desktop>


Hi,

It got to my attention that the download location of cfengine is changed.
A patch against the 12.2 ~.info file:

4c4
< DOWNLOAD="http://www.cfengine.org/downloads/cfengine-2.2.9.tar.gz"
---
> DOWNLOAD="http://www.cfengine.org/tarballs/cfengine-2.2.9.tar.gz"

Also i noticed an update available, of which the changelog reads:
"Protocol fix, potential integer error in server decoding."

Which looks to me as though it might be worth upgrading to...
A (triflingly) tested patch:

diff -ur ./cfengine/cfengine.SlackBuild /home/sbo/12.2/system/cfengine/cfengine.SlackBuild
--- ./cfengine/cfengine.SlackBuild	2009-08-03 21:36:13.000000000 +0200
+++ /home/sbo/12.2/system/cfengine/cfengine.SlackBuild	2009-04-17 05:51:14.000000000 +0200
@@ -8,7 +8,7 @@
  # http://sam.zoy.org/wtfpl/COPYING for more details.

  PRGNAM=cfengine
-VERSION=2.2.10
+VERSION=2.2.9
  ARCH=${ARCH:-i486}
  BUILD=${BUILD:-1}
  TAG=${TAG:-_SBo}
diff -ur ./cfengine/cfengine.info /home/sbo/12.2/system/cfengine/cfengine.info
--- ./cfengine/cfengine.info	2009-08-03 21:35:59.000000000 +0200
+++ /home/sbo/12.2/system/cfengine/cfengine.info	2009-04-17 06:53:20.000000000 +0200
@@ -1,8 +1,8 @@
  PRGNAM="cfengine"
-VERSION="2.2.10"
+VERSION="2.2.9"
  HOMEPAGE="http://www.cfengine.org/"
-DOWNLOAD="http://www.cfengine.org/tarballs/cfengine-2.2.10.tar.gz"
-MD5SUM="3b90ff8bf2ec941cd33cfb65f5012f16"
+DOWNLOAD="http://www.cfengine.org/downloads/cfengine-2.2.9.tar.gz"
+MD5SUM="ce115587078a7a8345dca52891f95513"
  MAINTAINER="Menno Duursma"
  EMAIL="druiloor at zonnet.nl"
  APPROVED="dsomero"



Cheers,
-Menno.

From onan003 at gmail.com  Mon Aug  3 21:30:22 2009
From: onan003 at gmail.com (John Kipp)
Date: Mon, 03 Aug 2009 14:30:22 -0700
Subject: [Slackbuilds-users] Bug with Slack.Build Script 12.2 > Multimedia >
 flash-player-plugin (10.0_r22)
Message-ID: <4A7756EE.7000207@gmail.com>

Dear SlackBuilds:
I tried using the SlackBuilds script shown above with Slackware 12.2. It 
would not compile.
Line 32 of the SlackBuild stops the build. I believe it is because when 
the untarring occurs, you only have the  libflashplayer.so file by 
itself. It is not in a directory install_flash_player_10_linux. So the 
script changes permissions on the $CWD instead of the library. The 
version of the Flash Player Plugin is 10.0 r32.
Thanks a lot for the great SBo. I use them all the time.
John


From rworkman at slackbuilds.org  Mon Aug  3 22:30:43 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 3 Aug 2009 17:30:43 -0500
Subject: [Slackbuilds-users] Bug with Slack.Build Script 12.2 >
 Multimedia > flash-player-plugin (10.0_r22)
In-Reply-To: <4A7756EE.7000207@gmail.com>
References: <4A7756EE.7000207@gmail.com>
Message-ID: <20090803173043.1a626003@liberty.rlwhome.lan>

On Mon, 03 Aug 2009 14:30:22 -0700
John Kipp <onan003 at gmail.com> wrote:

> Dear SlackBuilds:
> I tried using the SlackBuilds script shown above with Slackware 12.2.
> It would not compile.
> Line 32 of the SlackBuild stops the build. I believe it is because
> when the untarring occurs, you only have the  libflashplayer.so file
> by itself. It is not in a directory install_flash_player_10_linux. So
> the script changes permissions on the $CWD instead of the library.
> The version of the Flash Player Plugin is 10.0 r32.


The archive structure did indeed change in r32.

http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-August/004321.html

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

From nille.kungen at gmail.com  Tue Aug  4 05:55:33 2009
From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_=27Nille=27_=C5kerstr=F6m?=)
Date: Tue, 04 Aug 2009 07:55:33 +0200
Subject: [Slackbuilds-users] cfengine download location
In-Reply-To: <alpine.LNX.2.00.0908032130340.2843@pc.desktop>
References: <alpine.LNX.2.00.0908032130340.2843@pc.desktop>
Message-ID: <4A77CD55.5030902@gmail.com>

Menno Duursma skrev:
>
> Hi,
>
> It got to my attention that the download location of cfengine is changed.
> A patch against the 12.2 ~.info file:
>
> 4c4
> < DOWNLOAD="http://www.cfengine.org/downloads/cfengine-2.2.9.tar.gz"
> ---
>> DOWNLOAD="http://www.cfengine.org/tarballs/cfengine-2.2.9.tar.gz"
>
> Also i noticed an update available, of which the changelog reads:
> "Protocol fix, potential integer error in server decoding."
>
> Which looks to me as though it might be worth upgrading to...
> A (triflingly) tested patch:
>
> diff -ur ./cfengine/cfengine.SlackBuild 
> /home/sbo/12.2/system/cfengine/cfengine.SlackBuild
> --- ./cfengine/cfengine.SlackBuild    2009-08-03 21:36:13.000000000 +0200
> +++ /home/sbo/12.2/system/cfengine/cfengine.SlackBuild    2009-04-17 
> 05:51:14.000000000 +0200
> @@ -8,7 +8,7 @@
>  # http://sam.zoy.org/wtfpl/COPYING for more details.
>
>  PRGNAM=cfengine
> -VERSION=2.2.10
> +VERSION=2.2.9
>  ARCH=${ARCH:-i486}
>  BUILD=${BUILD:-1}
>  TAG=${TAG:-_SBo}
> diff -ur ./cfengine/cfengine.info 
> /home/sbo/12.2/system/cfengine/cfengine.info
> --- ./cfengine/cfengine.info    2009-08-03 21:35:59.000000000 +0200
> +++ /home/sbo/12.2/system/cfengine/cfengine.info    2009-04-17 
> 06:53:20.000000000 +0200
> @@ -1,8 +1,8 @@
>  PRGNAM="cfengine"
> -VERSION="2.2.10"
> +VERSION="2.2.9"
>  HOMEPAGE="http://www.cfengine.org/"
> -DOWNLOAD="http://www.cfengine.org/tarballs/cfengine-2.2.10.tar.gz"
> -MD5SUM="3b90ff8bf2ec941cd33cfb65f5012f16"
> +DOWNLOAD="http://www.cfengine.org/downloads/cfengine-2.2.9.tar.gz"
> +MD5SUM="ce115587078a7a8345dca52891f95513"
>  MAINTAINER="Menno Duursma"
>  EMAIL="druiloor at zonnet.nl"
>  APPROVED="dsomero"
>
>
>
> Cheers,
> -Menno.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
Isn't that patch reversed?
/Nille

From druiloor at zonnet.nl  Tue Aug  4 11:20:34 2009
From: druiloor at zonnet.nl (Menno Duursma)
Date: Tue, 4 Aug 2009 13:20:34 +0200 (CEST)
Subject: [Slackbuilds-users] cfengine download location
In-Reply-To: <4A77CD55.5030902@gmail.com>
References: <alpine.LNX.2.00.0908032130340.2843@pc.desktop>
	<4A77CD55.5030902@gmail.com>
Message-ID: <alpine.LNX.2.00.0908041317020.1804@pc.desktop>



On Tue, 4 Aug 2009, Niklas 'Nille' ?kerstr?m wrote:

> Menno Duursma skrev:

> Isn't that patch reversed?

Indeed it is. Flipped however it's untested ...
(In case the build doesn't work after appying: wasn't me done did it. :))

Cheers,
-Menno.

From stormtracknole at gmail.com  Wed Aug  5 16:39:54 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Wed, 5 Aug 2009 11:39:54 -0500
Subject: [Slackbuilds-users] kdenlive Slackbuild
Message-ID: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>

List,

I modified slacky it kdenlive Slackbuild to follow more closely the
requirements for Slackbuilds.org.  So, before I submit my SlackBuild, is
there anyone else planning on adding kdenlive once Slackware 13 comes out?
Just wanted to make sure before I submit it.  Also, can someone take a look
at what I have come up with so far and give me some pointers?  The script
will build kdenlive from svn instead of the standard package.  I also have a
slackbuild for mlt which is a big requirement.  Thanks ahead of time! :^)

-stn

Here's the kdenlive.Slackbuild:

#!/bin/sh

# Slackware build script for <appname>

# Written by (your name) (your contact information)

# (add license information here if you desire; otherwise,
# all submissions are considered to be in the public domain)
# Some licenses may incorporate the "Written by" information
# above, and if so, that line can be omitted
# We strongly suggest *not* using GPL for scripts, as it requires
# a copy of the GPL to be distributed with it.  Since the GPL
# itself is longer than any build script will be, this just doesn't
# make good sense...

# |-----------------------------------------------------------------| #
# REMOVE THIS ENTIRE BLOCK OF TEXT #
#
# $Id: template.SlackBuild,v 1.8 2009/05/27 01:34:37 slackbuilds Exp
slackbuilds $
#
# This template is not meant to be a 'cut and paste' script to
# enable any random user to make a working package.  While
# we're certainly not discouraging use of this template, if
# you haven't manually gone through each step of the process
# without the build script (typically as a normal user, as this
# will reveal problems that you won't see as root), then there's
# a good chance that something important is missing from your
# submission.

# When using this template script, please remove as many of
# these unnecessary comments as possible.  Commented code is
# a good thing, but if it's obvious, there's no need to comment it.
#
# AGAIN, REMOVE THE COMMENTS IF THEY ARE NOT NEEDED - DON'T JUST
# DELETE THIS BLOCK OF TEXT WITHOUT BOTHERING TO READ WHAT'S IN IT.
#
# |-----------------------------------------------------------------| #

PRGNAM=kdenlive			# replace with name of program
VERSION=${VERSION:-`date +%Y%m%d`}		# replace with version of program
ARCH=${ARCH:-i686}		# this should not change
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}		# the "_SBo" is required

CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}	# For consistency's sake, use this
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}	# Drop the package in /tmp

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
fi

if [ ! -d $TMP ]; then
	 mkdir -p $TMP
fi

if [ ! -d $PKG ]; then
	  mkdir -p $PKG
fi

cd $TMP
svn co https://kdenlive.svn.sourceforge.net/svnroot/kdenlive/trunk/kdenlive

echo -e "\E[0;32m+------------------------------------+\E[0;0m"
echo -e "\E[0;32m| Start SlackBuild $NAME-$VERSION |\E[0;0m"
echo -e "\E[0;32m+------------------------------------+\E[0;0m"

cd $PRGNAM

find . -perm 777 -exec chmod 755 {} \;
find . -perm 775 -exec chmod 755 {} \;
find . -perm 555 -exec chmod 755 {} \;
find . -perm 666 -exec chmod 644 {} \;
find . -perm 664 -exec chmod 644 {} \;
find . -perm 444 -exec chmod 644 {} \;

chown -R root:root .

cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_C_FLAGS= \
-DCMAKE_CXX_FLAGS= \
. || exit 1

# cmake doesn't seem able to take CFLAGS and CXXFLAGS 'regoulary'
sed -i  s/"CMAKE_C_FLAGS:STRING="/"CMAKE_C_FLAGS:STRING=\'-O2
-march=i686 -mtune=i686\'"/ CMakeCache.txt
sed -i  s/"CMAKE_CXX_FLAGS:STRING="/"CMAKE_CXX_FLAGS:STRING=\'-O2
-march=i686 -mtune=i686\'"/ CMakeCache.txt

make || exit 1

make install DESTDIR=$PKG || exit 1

mkdir -p $PKG/usr/doc/$NAME-$VERSION
cp -a AUTHORS COPYING ChangeLog INSTALL NEWS README TODO
$PKG/usr/doc/$NAME-$VERSION

( cd $PKG
  find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : |
xargs strip --strip-unneeded 2> /dev/null
  find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d
: | xargs strip --strip-unneeded 2> /dev/null
  find . | xargs file | grep "current ar archive" | cut -f 1 -d : |
xargs strip -g 2> /dev/null
      )

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/slack-desc > $PKG/usr/doc/$NAME-$VERSION/slack-desc
cat $CWD/$NAME.SlackBuild > $PKG/usr/doc/$NAME-$VERSION/$NAME.SlackBuild

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.txz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090805/6ae7ee25/attachment.htm>

From alien at slackbuilds.org  Wed Aug  5 17:37:38 2009
From: alien at slackbuilds.org (Eric Hameleers (SBo))
Date: Wed, 05 Aug 2009 19:37:38 +0200
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
Message-ID: <4A79C362.7080008@slackbuilds.org>

stormtracknole schreef:
> List,
> 
> I modified slacky it kdenlive Slackbuild to follow more closely the
> requirements for Slackbuilds.org.  So, before I submit my SlackBuild, is
> there anyone else planning on adding kdenlive once Slackware 13 comes
> out?  Just wanted to make sure before I submit it.  Also, can someone
> take a look at what I have come up with so far and give me some
> pointers?  The script will build kdenlive from svn instead of the
> standard package.  I also have a slackbuild for mlt which is a big
> requirement.  Thanks ahead of time! :^)
> 
> -stn
> 
> Here's the kdenlive.Slackbuild:
> 
> #!/bin/sh
> 
> # Slackware build script for <appname>
> 
> # Written by (your name) (your contact information)
> 
> # (add license information here if you desire; otherwise,
> 
> # all submissions are considered to be in the public domain)
> # Some licenses may incorporate the "Written by" information
> # above, and if so, that line can be omitted
> # We strongly suggest *not* using GPL for scripts, as it requires
> 
> # a copy of the GPL to be distributed with it.  Since the GPL
> # itself is longer than any build script will be, this just doesn't
> # make good sense...
> 
> # |-----------------------------------------------------------------| #
> 
> # REMOVE THIS ENTIRE BLOCK OF TEXT #
> #
> # $Id: template.SlackBuild,v 1.8 2009/05/27 01:34:37 slackbuilds Exp slackbuilds $
> #
> # This template is not meant to be a 'cut and paste' script to
> # enable any random user to make a working package.  While
> 
> # we're certainly not discouraging use of this template, if
> # you haven't manually gone through each step of the process
> # without the build script (typically as a normal user, as this
> # will reveal problems that you won't see as root), then there's
> 
> # a good chance that something important is missing from your
> # submission.
> 
> # When using this template script, please remove as many of
> # these unnecessary comments as possible.  Commented code is
> # a good thing, but if it's obvious, there's no need to comment it.
> 
> #
> # AGAIN, REMOVE THE COMMENTS IF THEY ARE NOT NEEDED - DON'T JUST
> # DELETE THIS BLOCK OF TEXT WITHOUT BOTHERING TO READ WHAT'S IN IT.
> #
> # |-----------------------------------------------------------------| #

... etc ...

When I look at this SlackBuild header, it tells me that you really
have not paid attention to what it is trying to tell you.
Perhaps you should read it and follow up on it.

Also, since you have copied the slacky.eu script almost verbatim (see
http://repository.slacky.eu/slackware-12.1/multimedia/kdenlive/20080610/src/kdenlive.SlackBuild)
it would be prudent to credit the original author in your version,
although though this is not required here (the original script does
not have a copyright header).

> ARCH=${ARCH:-i686}		# this should not change

Hmm. Out template (like all the rest of Slackware packages) has this line:

ARCH=${ARCH:-i486}		# this should not change

It would be good if you stuck to the template.

I'll be looking for your next post with the updated script.

Finally two more points:

(1) we do not approve scripts that check out SVN sources. You will
have to think of something here (look at other contributions on our
site that use SVN snapshots to get an idea).
(2) This software has a ton of dependencies. You will have to write a
README that lists what other scripts are required from SlackBuilds.org
 - any missing dependencies need to be submitted as scripts by
yourself as well.

Cheers, Eric

From stormtracknole at gmail.com  Wed Aug  5 18:08:12 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Wed, 5 Aug 2009 13:08:12 -0500
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <4A79C362.7080008@slackbuilds.org>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<4A79C362.7080008@slackbuilds.org>
Message-ID: <a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>

Thanks for looking at it Eric!

Yes, I did not hide the fact that the script was taken from slacky.  Sorry
about not changing i686 back to i486.  I had done that change when I
compiled it.  I know the slackbuild is very sloppy and that I have to work
on it some more.  However, before I do, I wanted to make sure that noone
else is working on a script since all the work I would make would be a moot
point.

Originally, I was going to use the stable release, but I changed it to svn
just to run the latest and greatest.  I will change it back to use the
stable release.

As far the as the requirements go, I was able to get all the dependencies
from slackbuilds.org.  The only thing missing is mlt.  I have a slackbuild
for that also.

Sorry for the sloppy work!  I was more concerned with the meat of the script
that I overlooked the commented area.  This is what I get for trying to do
this stuff late at night! :^/

-stn

On Wed, Aug 5, 2009 at 12:37 PM, Eric Hameleers (SBo) <alien at slackbuilds.org
> wrote:

> stormtracknole schreef:
> > List,
> >
> > I modified slacky it kdenlive Slackbuild to follow more closely the
> > requirements for Slackbuilds.org.  So, before I submit my SlackBuild, is
> > there anyone else planning on adding kdenlive once Slackware 13 comes
> > out?  Just wanted to make sure before I submit it.  Also, can someone
> > take a look at what I have come up with so far and give me some
> > pointers?  The script will build kdenlive from svn instead of the
> > standard package.  I also have a slackbuild for mlt which is a big
> > requirement.  Thanks ahead of time! :^)
> >
> > -stn
> >
> > Here's the kdenlive.Slackbuild:
> >
> > #!/bin/sh
> >
> > # Slackware build script for <appname>
> >
> > # Written by (your name) (your contact information)
> >
> > # (add license information here if you desire; otherwise,
> >
> > # all submissions are considered to be in the public domain)
> > # Some licenses may incorporate the "Written by" information
> > # above, and if so, that line can be omitted
> > # We strongly suggest *not* using GPL for scripts, as it requires
> >
> > # a copy of the GPL to be distributed with it.  Since the GPL
> > # itself is longer than any build script will be, this just doesn't
> > # make good sense...
> >
> > # |-----------------------------------------------------------------| #
> >
> > # REMOVE THIS ENTIRE BLOCK OF TEXT #
> > #
> > # $Id: template.SlackBuild,v 1.8 2009/05/27 01:34:37 slackbuilds Exp
> slackbuilds $
> > #
> > # This template is not meant to be a 'cut and paste' script to
> > # enable any random user to make a working package.  While
> >
> > # we're certainly not discouraging use of this template, if
> > # you haven't manually gone through each step of the process
> > # without the build script (typically as a normal user, as this
> > # will reveal problems that you won't see as root), then there's
> >
> > # a good chance that something important is missing from your
> > # submission.
> >
> > # When using this template script, please remove as many of
> > # these unnecessary comments as possible.  Commented code is
> > # a good thing, but if it's obvious, there's no need to comment it.
> >
> > #
> > # AGAIN, REMOVE THE COMMENTS IF THEY ARE NOT NEEDED - DON'T JUST
> > # DELETE THIS BLOCK OF TEXT WITHOUT BOTHERING TO READ WHAT'S IN IT.
> > #
> > # |-----------------------------------------------------------------| #
>
> ... etc ...
>
> When I look at this SlackBuild header, it tells me that you really
> have not paid attention to what it is trying to tell you.
> Perhaps you should read it and follow up on it.
>
> Also, since you have copied the slacky.eu script almost verbatim (see
>
> http://repository.slacky.eu/slackware-12.1/multimedia/kdenlive/20080610/src/kdenlive.SlackBuild
> )
> it would be prudent to credit the original author in your version,
> although though this is not required here (the original script does
> not have a copyright header).
>
> > ARCH=${ARCH:-i686}            # this should not change
>
> Hmm. Out template (like all the rest of Slackware packages) has this line:
>
> ARCH=${ARCH:-i486}              # this should not change
>
> It would be good if you stuck to the template.
>
> I'll be looking for your next post with the updated script.
>
> Finally two more points:
>
> (1) we do not approve scripts that check out SVN sources. You will
> have to think of something here (look at other contributions on our
> site that use SVN snapshots to get an idea).
> (2) This software has a ton of dependencies. You will have to write a
> README that lists what other scripts are required from SlackBuilds.org
>  - any missing dependencies need to be submitted as scripts by
> yourself as well.
>
> Cheers, Eric
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090805/421c7c28/attachment.htm>

From pprkut at liwjatan.at  Wed Aug  5 19:48:33 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Wed, 5 Aug 2009 21:48:33 +0200
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<4A79C362.7080008@slackbuilds.org>
	<a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>
Message-ID: <200908052148.37515.pprkut@liwjatan.at>

On Wednesday 05 August 2009 20:08:12 stormtracknole wrote:
> Thanks for looking at it Eric!
>
> Yes, I did not hide the fact that the script was taken from slacky.  Sorry
> about not changing i686 back to i486.  I had done that change when I
> compiled it.  I know the slackbuild is very sloppy and that I have to work
> on it some more.  However, before I do, I wanted to make sure that noone
> else is working on a script since all the work I would make would be a moot
> point.

I have a SlackBuild for kdenlive's kde3 version. I thought about updating it 
when 13.0 is out, but if you want it, you can have it too :)
It's already following SBo's standards, so if you want to base yours off of it, 
or take it as reference, feel free to do so. It's available at 
http://www.liwjatan.at/files/slackware/slackbuilds/kdenlive/kdenlive.tar.gz

> Originally, I was going to use the stable release, but I changed it to svn
> just to run the latest and greatest.  I will change it back to use the
> stable release.

If you look at SBo and Slackware, you'll see that "lastest and greatest" is 
not exactly our philosophy ;)
All scripts on SBo, that use a svn-version do so for a good and valid reason. 
Kdenlive has regular stable releases. Using a svn-snapshot for it is kind of 
pointless.

Note, my script indeed uses a svn-snapshot. The reason for it though is, that 
I was unable to build the latest release for kde3 against newer ffmpeg 
versions.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090805/b6ea7335/attachment.sig>

From stormtracknole at gmail.com  Wed Aug  5 20:03:51 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Wed, 5 Aug 2009 15:03:51 -0500
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <200908052148.37515.pprkut@liwjatan.at>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<4A79C362.7080008@slackbuilds.org>
	<a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>
	<200908052148.37515.pprkut@liwjatan.at>
Message-ID: <a653e2ed0908051303k5e796429u9bf06748fc92c5f8@mail.gmail.com>

Thanks Heinz for providing your Slackbuild!  Sorry, I'm still stuck on my
Feodra days of "latest and greatest"! lol

The latest version of kdenlive can only be build for kde4.  I'm not exactly
sure when that switched occurred.  Also, it uses cmake instead of the
standard ./configure to build the package.  I'll have to dig around my notes
to make sure I post all the dependecies (which are quite a bit), but they
are all founded on slackbuilds.

I'll make a mental note to not ever include svn as a source for a package!
;^)

-stn

On Wed, Aug 5, 2009 at 2:48 PM, Heinz Wiesinger <pprkut at liwjatan.at> wrote:

> On Wednesday 05 August 2009 20:08:12 stormtracknole wrote:
> > Thanks for looking at it Eric!
> >
> > Yes, I did not hide the fact that the script was taken from slacky.
>  Sorry
> > about not changing i686 back to i486.  I had done that change when I
> > compiled it.  I know the slackbuild is very sloppy and that I have to
> work
> > on it some more.  However, before I do, I wanted to make sure that noone
> > else is working on a script since all the work I would make would be a
> moot
> > point.
>
> I have a SlackBuild for kdenlive's kde3 version. I thought about updating
> it
> when 13.0 is out, but if you want it, you can have it too :)
> It's already following SBo's standards, so if you want to base yours off of
> it,
> or take it as reference, feel free to do so. It's available at
> http://www.liwjatan.at/files/slackware/slackbuilds/kdenlive/kdenlive.tar.gz
>
> > Originally, I was going to use the stable release, but I changed it to
> svn
> > just to run the latest and greatest.  I will change it back to use the
> > stable release.
>
> If you look at SBo and Slackware, you'll see that "lastest and greatest" is
> not exactly our philosophy ;)
> All scripts on SBo, that use a svn-version do so for a good and valid
> reason.
> Kdenlive has regular stable releases. Using a svn-snapshot for it is kind
> of
> pointless.
>
> Note, my script indeed uses a svn-snapshot. The reason for it though is,
> that
> I was unable to build the latest release for kde3 against newer ffmpeg
> versions.
>
> Grs,
> Heinz
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090805/e803f345/attachment.htm>

From mjjzf at syntaktisk.dk  Thu Aug  6 08:46:43 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Thu, 6 Aug 2009 10:46:43 +0200 (CEST)
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <a653e2ed0908051303k5e796429u9bf06748fc92c5f8@mail.gmail.com>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<4A79C362.7080008@slackbuilds.org>
	<a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>
	<200908052148.37515.pprkut@liwjatan.at>
	<a653e2ed0908051303k5e796429u9bf06748fc92c5f8@mail.gmail.com>
Message-ID: <cedd83ef81c8f9b0b7aa5d25afd9243d.squirrel@squirrelmail.gigahost.dk>

Would it be okay if one submitted a build with stable versions - as could
be accepted at Slackbuilds.org - but in the notes also noted that the
author also does a bleeding edge version, which is available on his own
site, but which is not signed by SBo?
That seems like a useful compromise to me.

Yours,
Morten
__
http://www.syntaktisk.dk

From hba.nihilismus at gmail.com  Thu Aug  6 10:36:20 2009
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Thu, 6 Aug 2009 05:36:20 -0500
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <cedd83ef81c8f9b0b7aa5d25afd9243d.squirrel@squirrelmail.gigahost.dk>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<4A79C362.7080008@slackbuilds.org>
	<a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>
	<200908052148.37515.pprkut@liwjatan.at>
	<a653e2ed0908051303k5e796429u9bf06748fc92c5f8@mail.gmail.com>
	<cedd83ef81c8f9b0b7aa5d25afd9243d.squirrel@squirrelmail.gigahost.dk>
Message-ID: <39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>

> Would it be okay if one submitted a build with stable versions - as could
> be accepted at Slackbuilds.org - but in the notes also noted that the
> author also does a bleeding edge version, which is available on his own
> site, but which is not signed by SBo?

Sorry, but as normal user, would you really trust in some "untested"
shell script without the check by any SBo admin for malicious
activity?. I have some slackbuilds at my homepage, but since any SBo
admin haven?t tested them i dont think it would be good to add this
information cause it can be misinterpreted and seen as if SBo?s admins
are agree with them. Thats why i have this message in my homepage:
http://hba.ath.cx/projects/slackbuilds/testing/README.WARNING

My suggestion, just drop an email to MAINTAINER to see if theres an
SlackBuild for the latest and greatest version from svn/hg/git. In
this way you are the one accepting to be in its own from the first
place ;-)

- hba

From mjjzf at syntaktisk.dk  Thu Aug  6 12:40:25 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Thu, 6 Aug 2009 14:40:25 +0200 (CEST)
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<4A79C362.7080008@slackbuilds.org>
	<a653e2ed0908051108g397ed4a0q611865083356903b@mail.gmail.com>
	<200908052148.37515.pprkut@liwjatan.at>
	<a653e2ed0908051303k5e796429u9bf06748fc92c5f8@mail.gmail.com>
	<cedd83ef81c8f9b0b7aa5d25afd9243d.squirrel@squirrelmail.gigahost.dk>
	<39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>
Message-ID: <ec4d12c920ec1145834d535d37799b62.squirrel@squirrelmail.gigahost.dk>


---- 8< ---- Antonio Hern??ndez Blas ---- 8< ----
>> Would it be okay if one submitted a build with stable versions - as
>> could
>> be accepted at Slackbuilds.org - but in the notes also noted that the
>> author also does a bleeding edge version, which is available on his own
>> site, but which is not signed by SBo?
>
> Sorry, but as normal user, would you really trust in some "untested"
> shell script without the check by any SBo admin for malicious
> activity?. I have some slackbuilds at my homepage, but since any SBo
> admin haven??t tested them i dont think it would be good to add this
> information cause it can be misinterpreted and seen as if SBo??s admins
> are agree with them. Thats why i have this message in my homepage:
> http://hba.ath.cx/projects/slackbuilds/testing/README.WARNING
>
> My suggestion, just drop an email to MAINTAINER to see if theres an
> SlackBuild for the latest and greatest version from svn/hg/git. In
> this way you are the one accepting to be in its own from the first
> place ;-)
>
> - hba

I see your point, but my idea was for someone who is a maintainer already
and has submitted an approved stable package. This means that users of the
site knows that he knows how to build a build, even if the unstable build
is not approved for the site - since it has another agenda.

Yours,
M
__
http://www.syntaktisk.dk

From pprkut at liwjatan.at  Thu Aug  6 15:45:57 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Thu, 6 Aug 2009 17:45:57 +0200
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <ec4d12c920ec1145834d535d37799b62.squirrel@squirrelmail.gigahost.dk>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>
	<ec4d12c920ec1145834d535d37799b62.squirrel@squirrelmail.gigahost.dk>
Message-ID: <200908061746.00259.pprkut@liwjatan.at>

On Thursday 06 August 2009 14:40:25 Morten Juhl-Johansen Z?lde-Fej?r wrote:
> ---- 8< ---- Antonio Hern??ndez Blas ---- 8< ----
>
> >> Would it be okay if one submitted a build with stable versions - as
> >> could
> >> be accepted at Slackbuilds.org - but in the notes also noted that the
> >> author also does a bleeding edge version, which is available on his own
> >> site, but which is not signed by SBo?
> >
> > Sorry, but as normal user, would you really trust in some "untested"
> > shell script without the check by any SBo admin for malicious
> > activity?. I have some slackbuilds at my homepage, but since any SBo
> > admin haven??t tested them i dont think it would be good to add this
> > information cause it can be misinterpreted and seen as if SBo??s admins
> > are agree with them. Thats why i have this message in my homepage:
> > http://hba.ath.cx/projects/slackbuilds/testing/README.WARNING
> >
> > My suggestion, just drop an email to MAINTAINER to see if theres an
> > SlackBuild for the latest and greatest version from svn/hg/git. In
> > this way you are the one accepting to be in its own from the first
> > place ;-)
> >
> > - hba
>
> I see your point, but my idea was for someone who is a maintainer already
> and has submitted an approved stable package. This means that users of the
> site knows that he knows how to build a build, even if the unstable build
> is not approved for the site - since it has another agenda.

You jump to conclusions. Having a script approved once does not mean every 
follow up script is perfectly fine. Things can change, in the tarball, the way 
it builds, etc. Although most updates are indeed only simple version bumps, 
also those simple changes can be tricky at times.
Also, even the best maintainer is not perfect and can make mistakes. That's 
why there's the "multiple eyes" approach on SBo.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/a3925464/attachment.sig>

From stormtracknole at gmail.com  Thu Aug  6 22:10:14 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Thu, 6 Aug 2009 17:10:14 -0500
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <200908061746.00259.pprkut@liwjatan.at>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>
	<ec4d12c920ec1145834d535d37799b62.squirrel@squirrelmail.gigahost.dk>
	<200908061746.00259.pprkut@liwjatan.at>
Message-ID: <a653e2ed0908061510m548475bcs33cb62805de27afb@mail.gmail.com>

Thanks everyone for all the responses!  My thinking about using svn for
kdenlive is that this project is rapidly changing!  I compiled the latest
svn and took it for a spin and I'm VERY impressed!  Far more powerful than
kino (in my opinion of course).  Anyway, I have so free time last night and
went back and wrote a compliant SlackBuild straight from the
template.SlackBuild provided in SlackBuilds.org.
I also created a README, slack-desc and kdenlive.info.

I do have one question though, in the kdenlive.info file, there is a section
for MD5SUM.  What exactly is it that I'm signing?  Is is the SlackBuild file
itselft?  I left it blank for the moment.

Ok, I'm posting my SlackBuild here for another check along with the other
required files.  If you guys don't mind to take a look at it.  If all is
good, then I'll gzip it and submit it.  But, before I do that, I need to
work on the MLT SlackBuild as this is one of the main requirements.

Thanks again everyone for all the suggestions!

-stn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/c6c74d15/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdenlive.SlackBuild
Type: application/octet-stream
Size: 1834 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/c6c74d15/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: doinst.sh
Type: application/x-sh
Size: 241 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/c6c74d15/attachment.sh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdenlive.info
Type: application/octet-stream
Size: 236 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/c6c74d15/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slack-desc
Type: application/octet-stream
Size: 883 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/c6c74d15/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: README
Type: application/octet-stream
Size: 755 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/c6c74d15/attachment-0003.obj>

From nille.kungen at gmail.com  Fri Aug  7 00:31:49 2009
From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_=27Nille=27_=C5kerstr=F6m?=)
Date: Fri, 07 Aug 2009 02:31:49 +0200
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <a653e2ed0908061510m548475bcs33cb62805de27afb@mail.gmail.com>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>	<39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>	<ec4d12c920ec1145834d535d37799b62.squirrel@squirrelmail.gigahost.dk>	<200908061746.00259.pprkut@liwjatan.at>
	<a653e2ed0908061510m548475bcs33cb62805de27afb@mail.gmail.com>
Message-ID: <4A7B75F5.4000108@gmail.com>

stormtracknole skrev:
> I do have one question though, in the kdenlive.info 
> <http://kdenlive.info> file, there is a section for MD5SUM.  What 
> exactly is it that I'm signing?  Is is the SlackBuild file itselft?  I 
> left it blank for the moment.
It's the md5sum of the source tarball of kdenlive.
So we all know that when we download the sources everything is as it should.

From stormtracknole at gmail.com  Fri Aug  7 01:07:33 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Thu, 6 Aug 2009 20:07:33 -0500
Subject: [Slackbuilds-users] kdenlive Slackbuild
In-Reply-To: <4A7B75F5.4000108@gmail.com>
References: <a653e2ed0908050939h31652b7asf14aaa135c494732@mail.gmail.com>
	<39be090908060336s7b6bca81u54dd8c73c731113f@mail.gmail.com>
	<ec4d12c920ec1145834d535d37799b62.squirrel@squirrelmail.gigahost.dk>
	<200908061746.00259.pprkut@liwjatan.at>
	<a653e2ed0908061510m548475bcs33cb62805de27afb@mail.gmail.com>
	<4A7B75F5.4000108@gmail.com>
Message-ID: <a653e2ed0908061807n333dd5d2l502d9acde5471de0@mail.gmail.com>

Thanks!  Just wanted to be certain.

2009/8/6 Niklas 'Nille' ?kerstr?m <nille.kungen at gmail.com>

> stormtracknole skrev:
>
>> I do have one question though, in the kdenlive.info <http://kdenlive.info>
>> file, there is a section for MD5SUM.  What exactly is it that I'm signing?
>>  Is is the SlackBuild file itselft?  I left it blank for the moment.
>>
> It's the md5sum of the source tarball of kdenlive.
> So we all know that when we download the sources everything is as it
> should.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090806/dd3b1583/attachment.htm>

From rworkman at slackbuilds.org  Mon Aug 10 04:44:51 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 9 Aug 2009 23:44:51 -0500
Subject: [Slackbuilds-users] cfengine download location
In-Reply-To: <alpine.LNX.2.00.0908032130340.2843@pc.desktop>
References: <alpine.LNX.2.00.0908032130340.2843@pc.desktop>
Message-ID: <20090809234451.1b66a63b@liberty.rlwhome.lan>

On Mon, 3 Aug 2009 21:53:04 +0200 (CEST)
Menno Duursma <druiloor at zonnet.nl> wrote:

> 
> Hi,
> 
> It got to my attention that the download location of cfengine is
> changed. A patch against the 12.2 ~.info file:
> 
> 4c4
> < DOWNLOAD="http://www.cfengine.org/downloads/cfengine-2.2.9.tar.gz"
> ---
> > DOWNLOAD="http://www.cfengine.org/tarballs/cfengine-2.2.9.tar.gz"
> 
> Also i noticed an update available, of which the changelog reads:
> "Protocol fix, potential integer error in server decoding."
> 
> Which looks to me as though it might be worth upgrading to...
> A (triflingly) tested patch:
> 
> diff
> -ur ./cfengine/cfengine.SlackBuild /home/sbo/12.2/system/cfengine/cfengine.SlackBuild
> --- ./cfengine/cfengine.SlackBuild	2009-08-03
> 21:36:13.000000000 +0200
> +++ /home/sbo/12.2/system/cfengine/cfengine.SlackBuild
> 2009-04-17 05:51:14.000000000 +0200 @@ -8,7 +8,7 @@ #
> http://sam.zoy.org/wtfpl/COPYING for more details.
> 
>   PRGNAM=cfengine
> -VERSION=2.2.10
> +VERSION=2.2.9
>   ARCH=${ARCH:-i486}
>   BUILD=${BUILD:-1}
>   TAG=${TAG:-_SBo}
> diff
> -ur ./cfengine/cfengine.info /home/sbo/12.2/system/cfengine/cfengine.info
> --- ./cfengine/cfengine.info	2009-08-03 21:35:59.000000000
> +0200 +++ /home/sbo/12.2/system/cfengine/cfengine.info
> 2009-04-17 06:53:20.000000000 +0200 @@ -1,8 +1,8 @@ PRGNAM="cfengine"
> -VERSION="2.2.10"
> +VERSION="2.2.9"
>   HOMEPAGE="http://www.cfengine.org/"
> -DOWNLOAD="http://www.cfengine.org/tarballs/cfengine-2.2.10.tar.gz"
> -MD5SUM="3b90ff8bf2ec941cd33cfb65f5012f16"
> +DOWNLOAD="http://www.cfengine.org/downloads/cfengine-2.2.9.tar.gz"
> +MD5SUM="ce115587078a7a8345dca52891f95513"
>   MAINTAINER="Menno Duursma"
>   EMAIL="druiloor at zonnet.nl"
>   APPROVED="dsomero"


Nice reversed patch.  :-)

FWIW, I think they put in a redirect for the old link too, because
it still works.  Anyway, I've got the queued for the (still private)
13.0 repo, but it probably won't make it for 12.2 -- we're just a 
bit too swamped with 13.0 stuff at the moment.

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

From erik at slackbuilds.org  Mon Aug 10 05:57:04 2009
From: erik at slackbuilds.org (Erik Hanson)
Date: Mon, 10 Aug 2009 00:57:04 -0500
Subject: [Slackbuilds-users] Flash Player 10.0.32.18 update
In-Reply-To: <20090801010223.2e979c1f.elyb@ioplasm.net>
References: <20090801010223.2e979c1f.elyb@ioplasm.net>
Message-ID: <20090810005704.098778d6@shaggy.scooby>

On Aug 01, 2009, at  1:02 AM, Brad Ely wrote:

> Here is an update to flash-player-plugin to 10.0.32.18 which "works
> for me" on -current (13.0) so someone should verify this works on 12.2.
> Adobe's new tar file has the same name but comes with the shared object
> file only, and *no* subdirectory.

A bit late but I updated the 12.2 repo for r32.

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

From rworkman at slackbuilds.org  Mon Aug 10 19:38:13 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 10 Aug 2009 14:38:13 -0500
Subject: [Slackbuilds-users] Flash Player 10.0.32.18 update
In-Reply-To: <20090810005704.098778d6@shaggy.scooby>
References: <20090801010223.2e979c1f.elyb@ioplasm.net>
	<20090810005704.098778d6@shaggy.scooby>
Message-ID: <20090810143813.49ce8c18@liberty.rlwhome.lan>

On Mon, 10 Aug 2009 00:57:04 -0500
Erik Hanson <erik at slackbuilds.org> wrote:

> On Aug 01, 2009, at  1:02 AM, Brad Ely wrote:
> 
> > Here is an update to flash-player-plugin to 10.0.32.18 which "works
> > for me" on -current (13.0) so someone should verify this works on
> > 12.2. Adobe's new tar file has the same name but comes with the
> > shared object file only, and *no* subdirectory.
> 
> A bit late but I updated the 12.2 repo for r32.


Thanks, Erik!

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

From rworkman at slackbuilds.org  Mon Aug 10 19:55:39 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 10 Aug 2009 14:55:39 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
Message-ID: <20090810145539.0d92fe91@liberty.rlwhome.lan>

As I promised several people privately, here's a list of things that we
have not had time to check/update for 13.0 yet:
  http://slackbuilds.org/NOT_CHECKED

If you maintain one of these and would like to see it in the initial
repo for 13.0, or if you use one of them and would like to "step up"
and handle any needed changes, now is your chance.  I can't promise
that we'll be able to merge in all of the changes we get, even if
they are fixed, but we'll do our best.  

As things are merged into the 13.0 repo (which is still private,
and will be until 13.0 is released), we'll update the listing above,
so be sure to refresh that before replying.

Fixes should come in as replies to this mail, with a complete tarball
attached (just as if you were submitting it on the website - no source
code of the app should be included).

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

From pwcazenave at gmail.com  Mon Aug 10 21:07:36 2009
From: pwcazenave at gmail.com (Pierre Cazenave)
Date: Mon, 10 Aug 2009 22:07:36 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4A808C18.3040000@gmail.com>

Hi Robby,

I've checked all my builds and attached the updates still on the list as 
requested.

development/CImg/
multimedia/wxcam/
system/fdupes/
system/fish/

There's also a few from that list that I've written new scripts for, so 
I'll check to make sure they're suitable for submission.

Pierre

Robby Workman wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
> 
> -RW
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CImg.tar.bz2
Type: application/octet-stream
Size: 2133 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090810/b182e872/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fdupes.tar.bz2
Type: application/octet-stream
Size: 2164 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090810/b182e872/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fish.tar.bz2
Type: application/octet-stream
Size: 2840 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090810/b182e872/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wxcam.tar.bz2
Type: application/octet-stream
Size: 2556 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090810/b182e872/attachment-0003.obj>

From grbzks at xsmail.com  Mon Aug 10 23:28:07 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Tue, 11 Aug 2009 02:28:07 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <1249946887.375.1329222559@webmail.messagingengine.com>



On Mon, 10 Aug 2009 14:55 -0500, "Robby Workman"
<rworkman at slackbuilds.org> wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
> 
> -RW

Is there a new template that automatically handles all possible
architectures, or are users
expected to edit the ARCH variable prior to building the package like
before?
(Only difference is now there is another official architecture).

-- 
 Greg

From michiel at slackbuilds.org  Tue Aug 11 00:31:20 2009
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Tue, 11 Aug 2009 01:31:20 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1249946887.375.1329222559@webmail.messagingengine.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<1249946887.375.1329222559@webmail.messagingengine.com>
Message-ID: <20090811013120.77660e12@hades.esn.local>

On Tue, 11 Aug 2009 02:28:07 +0300
"Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> Is there a new template that automatically handles all possible
> architectures, or are users expected to edit the ARCH variable 
> prior to building the package like
> before?

The official template is up to date as what you need to have in your
slackbuild script as for the different architectures: 

http://slackbuilds.org/template.SlackBuild

as for setting the ARCH; the easiest way of doing this is just setting
the ARCH variable in your shell start-up files. For example, my bashrc,
contains the following line:

export ARCH="x86_64"

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

From grbzks at xsmail.com  Mon Aug 10 23:22:52 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Tue, 11 Aug 2009 02:22:52 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <1249946572.32261.1329221511@webmail.messagingengine.com>



On Mon, 10 Aug 2009 14:55 -0500, "Robby Workman"
<rworkman at slackbuilds.org> wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
> 
> -RW

Is there a new template that automatically handles all possible
architectures, or are users
expected to edit the ARCH variable prior to building the package like
before?
(Only difference is now there is another official architecture).

-- 
 Greg

From nishant at mnspace.net  Tue Aug 11 03:48:40 2009
From: nishant at mnspace.net (Nishant Limbachia)
Date: Mon, 10 Aug 2009 22:48:40 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4A80EA18.1050808@mnspace.net>

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

Robby Workman wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
> 
> -RW

Here's the tarball for dovecot-cmusieve (known as dovecot-sieve in the
12.2 repo).  The name change is warranted because this sieve plugin is
originally based on cmusieve plugin for cyrus IMAP server and called
dovecot-cmusieve on dovecot website.  However, the foremost reason for
name change is that there's a new implementation of sieve plugin for
dovecot and is called dovecot-sieve.  I've tested the build on -current
and haven't seen any problems yet.

Thanks,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqA6hgACgkQeG5dog/51tXMtACdGuaolnSiVfGSrF9mU9FdHPU5
KXUAnROj5sQocpSdEJ1IfzKFC2YKDVVg
=orSi
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dovecot-cmusieve.tar.gz
Type: application/x-gzip
Size: 2874 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090810/0ac85f86/attachment.bin>

From grbzks at xsmail.com  Tue Aug 11 11:20:29 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Tue, 11 Aug 2009 14:20:29 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090811013120.77660e12@hades.esn.local>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan><1249946887.375.1329222559@webmail.messagingengine.com>
	<20090811013120.77660e12@hades.esn.local>
Message-ID: <1249989629.417.1329295469@webmail.messagingengine.com>



On Tue, 11 Aug 2009 01:31 +0100, "Michiel van Wessem"
<michiel at slackbuilds.org> wrote:
> On Tue, 11 Aug 2009 02:28:07 +0300
> "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> > Is there a new template that automatically handles all possible
> > architectures, or are users expected to edit the ARCH variable 
> > prior to building the package like
> > before?
> 
> The official template is up to date as what you need to have in your
> slackbuild script as for the different architectures: 
> 
> http://slackbuilds.org/template.SlackBuild
> 
> as for setting the ARCH; the easiest way of doing this is just setting
> the ARCH variable in your shell start-up files. For example, my bashrc,
> contains the following line:
> 
> export ARCH="x86_64"

Maybe it would be better then to change the comment on this line
ARCH=${ARCH:-i486}              # this should not change
to something more descriptive?

-- 
 Greg

From slackware.wagnerm at arcor.de  Tue Aug 11 12:10:04 2009
From: slackware.wagnerm at arcor.de (Michael Wagner)
Date: Tue, 11 Aug 2009 14:10:04 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A808C18.3040000@gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4A808C18.3040000@gmail.com>
Message-ID: <1249992604.4203.3.camel@laptop>

>From http://slackbuilds.org/NOT_CHECKED:

libopensync-plugin-syncml
gtkam

liopensync-plugin-kdepim should be removed as it doesn't work with
akonadi.

Greetings,

Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gtkam.tar.gz
Type: application/x-compressed-tar
Size: 2365 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090811/eba9157b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libopensync-plugin-syncml.tar.gz
Type: application/x-compressed-tar
Size: 2106 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090811/eba9157b/attachment-0001.bin>

From cnguyenminhtan at free.fr  Tue Aug 11 14:26:31 2009
From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr)
Date: Tue, 11 Aug 2009 16:26:31 +0200 (CEST)
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <1073907678.4943951250000791394.JavaMail.root@zimbra10-e2.priv.proxad.net>

Hello Robby,

Here are feedbacks for the SlackBuilds that I maintain:


desktop/un-fonts-core, it's a fonts package so it should be OK. I will install it on my -current machine and let you know.

network/kftpgrabber: To be removed. No new version since april 2007. So I doubt it will compile on KDE4 (I haven't even tried).

system/skim: To be removed. No new version since a long time ago.

Regards,

Christophe

----- Mail Original -----
De: "Robby Workman" <rworkman at slackbuilds.org>
?: slackbuilds-users at slackbuilds.org
Envoy?: Lundi 10 Ao?t 2009 21h55:39 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: [Slackbuilds-users] Unchecked entries for 13.0

As I promised several people privately, here's a list of things that we
have not had time to check/update for 13.0 yet:
  http://slackbuilds.org/NOT_CHECKED

If you maintain one of these and would like to see it in the initial
repo for 13.0, or if you use one of them and would like to "step up"
and handle any needed changes, now is your chance.  I can't promise
that we'll be able to merge in all of the changes we get, even if
they are fixed, but we'll do our best.  

As things are merged into the 13.0 repo (which is still private,
and will be until 13.0 is released), we'll update the listing above,
so be sure to refresh that before replying.

Fixes should come in as replies to this mail, with a complete tarball
attached (just as if you were submitting it on the website - no source
code of the app should be included).

-RW

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/


From mickeytintincolle at yahoo.fr  Tue Aug 11 16:12:25 2009
From: mickeytintincolle at yahoo.fr (Antoine NONYME)
Date: Tue, 11 Aug 2009 18:12:25 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0 (for me :
 Xfmedia)
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090811181225.6b538d55@zenwalk.hyperion.net>

Le Mon, 10 Aug 2009 14:55:39 -0500,
Robby Workman <rworkman at slackbuilds.org> a ?crit :

> As I promised several people privately, here's a list of things that
> we have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
> 
> -RW

Hello Robby,
I don't have my Slackware 12.2 updated to current, but the SlackBuild
compiles well in my up-to-date Zenwalk . There don't seem to be any
update in Xfmedia according to the official website .

-Antoine

From nille.kungen at gmail.com  Tue Aug 11 16:48:01 2009
From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_=27Nille=27_=C5kerstr=F6m?=)
Date: Tue, 11 Aug 2009 18:48:01 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4A81A0C1.70005@gmail.com>

Robby Workman skrev:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
>
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
Now i wonder about the new arch testing.
I don't have anything but an i486 box to test my builds on.
I can add the other arch to my builds but i can't test it.
So should i add tested arch to my reply with my results?
/Nille

From techjunkus at yahoo.com  Tue Aug 11 17:47:01 2009
From: techjunkus at yahoo.com (Dave)
Date: Tue, 11 Aug 2009 10:47:01 -0700 (PDT)
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <137810.29741.qm@web51106.mail.re2.yahoo.com>

games/zsnes

ZSNES won't build with the newer version of gcc in Slackware 13.0.
However, there's a source archive available that's patched for gcc 4.3.

url:
http://zsnes.sf.net/zsnes151bsrc.tar.bz2

md5sum:
904ee432f378609176ed30c01cf6ea28  zsnes151bsrc.tar.bz2

(that's just the md5sum I see after downloading and double-checking)
I've cc'd the maintainer, and hope to see zsnes included for Slackware 13.0.

Only the version numbers need changing in the SlackBuild:

--- a/zsnes/zsnes.SlackBuild 2009-02-05 13:03:10.000000000 -0500
+++ b/zsnes/zsnes.SlackBuild   2009-08-11 12:54:06.000000000 -0400
@@ -22,9 +22,9 @@
 # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 PRGNAM=zsnes
-VERSION=1.51
-ZSNESSRC=151src
-ZSNESDIR=_1_51
+VERSION=1.51b
+ZSNESSRC=151bsrc
+ZSNESDIR=_1_51b
 ARCH=${ARCH:-i486}
 BUILD=${BUILD:-4}
 TAG=${TAG:-_SBo}


--- On Mon, 8/10/09, Robby Workman <rworkman at slackbuilds.org> wrote:

> From: Robby Workman <rworkman at slackbuilds.org>
> Subject: [Slackbuilds-users] Unchecked entries for 13.0
> To: slackbuilds-users at slackbuilds.org
> Date: Monday, August 10, 2009, 3:55 PM
> As I promised several people
> privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
> ? http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in
> the initial
> repo for 13.0, or if you use one of them and would like to
> "step up"
> and handle any needed changes, now is your chance.? I
> can't promise
> that we'll be able to merge in all of the changes we get,
> even if
> they are fixed, but we'll do our best.? 
> 
> As things are merged into the 13.0 repo (which is still
> private,
> and will be until 13.0 is released), we'll update the
> listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a
> complete tarball
> attached (just as if you were submitting it on the website
> - no source
> code of the app should be included).
> 
> -RW
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 
> 


      

From adamsonj at email.unc.edu  Tue Aug 11 17:58:46 2009
From: adamsonj at email.unc.edu (Joel J. Adamson)
Date: Tue, 11 Aug 2009 13:58:46 -0400
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <6652.1250013526@chondestes.bio.unc.edu>

> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best. =20
Robby,

Should I update my build of bbdb?  It does not depend on any core system
components, and works with the official Slackware Emacs.  What's the
policy on a package like this?

I suppose I need to update to handle the new package format, but I do
not have a -current machine to use (though I could install at home if
this is my duty as a maintainer).

Thanks,
Joel
-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280

From mrc.ildp at gmail.com  Tue Aug 11 20:00:33 2009
From: mrc.ildp at gmail.com (Marco Cecchetti)
Date: Tue, 11 Aug 2009 22:00:33 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>

2009/8/10 Robby Workman <rworkman at slackbuilds.org>

> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>  http://slackbuilds.org/NOT_CHECKED


Hi Robby,
these are my not checked:
*
games/Chatbot-Eliza*/
it does not need any change
I'm going to maintain it, waiting for CADIE... ;-)

*audio/exaile/*
It depends on some gnome packages
so I'm going to take care of it later.

*libraries/gdal/
libraries/libgeotiff/
*I don't use these 2 any more. I'm going to leave the maintenance

*system/mlterm/*
I submit here the changes

Ciao, thanks
-- 
Marco Cecchetti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090811/02e04933/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mlterm.tar.gz
Type: application/x-gzip
Size: 2163 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090811/02e04933/attachment.bin>

From slacker at slaphappygeeks.com  Tue Aug 11 20:13:05 2009
From: slacker at slaphappygeeks.com (Slacker build user)
Date: Tue, 11 Aug 2009 14:13:05 -0600
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4A81D0D1.3070302@slaphappygeeks.com>

Hi Robby,

I do not have a -current box right now but will within about a week.

I will then check argouml, jpicedt, saxon-b and xalan-j

In the mean time, if anyone wants to bring them up to 13.0 feel free, but I am 
still happy to keep them otherwise.

Thanks,

Robert

From mjjzf at syntaktisk.dk  Tue Aug 11 20:27:38 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Tue, 11 Aug 2009 22:27:38 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090811222738.2be182b1@darkstar.example.net>

On Mon, 10 Aug 2009 14:55:39 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> As I promised several people privately, here's a list of things that
> we have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> -RW

My build of Gajim still works.
I am, however, going to submit an updated build and package an extra
optional dependency for it as well.
Yours,
Morten

From rworkman at slackbuilds.org  Tue Aug 11 20:40:11 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 11 Aug 2009 15:40:11 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090811154011.2c559eaa@liberty.rlwhome.lan>

On Mon, 10 Aug 2009 14:55:39 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> As I promised several people privately, here's a list of things that
> we have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).


I don't think I was clear about at least two points:

1. We don't much care for version bumps at this point *unless*
   it's necessary to build on -current.  

2. If you can't test it on both 32bit and 64bit -current,
   don't bother replying for now.  Later on (after the submit
   form is open again), it won't be as big of a problem, but
   for now, it is.

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

From pwcazenave at gmail.com  Tue Aug 11 21:35:00 2009
From: pwcazenave at gmail.com (Pierre Cazenave)
Date: Tue, 11 Aug 2009 22:35:00 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090811154011.2c559eaa@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
Message-ID: <4A81E404.6040707@gmail.com>



Robby Workman wrote:
> On Mon, 10 Aug 2009 14:55:39 -0500
> Robby Workman <rworkman at slackbuilds.org> wrote:
> 
>> As I promised several people privately, here's a list of things that
>> we have not had time to check/update for 13.0 yet:
>>   http://slackbuilds.org/NOT_CHECKED
>>
>> If you maintain one of these and would like to see it in the initial
>> repo for 13.0, or if you use one of them and would like to "step up"
>> and handle any needed changes, now is your chance.  I can't promise
>> that we'll be able to merge in all of the changes we get, even if
>> they are fixed, but we'll do our best.  
>>
>> As things are merged into the 13.0 repo (which is still private,
>> and will be until 13.0 is released), we'll update the listing above,
>> so be sure to refresh that before replying.
>>
>> Fixes should come in as replies to this mail, with a complete tarball
>> attached (just as if you were submitting it on the website - no source
>> code of the app should be included).
> 
> 
> I don't think I was clear about at least two points:
> 
> 1. We don't much care for version bumps at this point *unless*
>    it's necessary to build on -current.  
> 
> 2. If you can't test it on both 32bit and 64bit -current,
>    don't bother replying for now.  Later on (after the submit
>    form is open again), it won't be as big of a problem, but
>    for now, it is.
> 
> -RW
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 

In which case, scratch mine. 64-bit is on my todo list.

From adamsonj at email.unc.edu  Wed Aug 12 01:05:04 2009
From: adamsonj at email.unc.edu (Joel J. Adamson)
Date: Tue, 11 Aug 2009 21:05:04 -0400
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090811154011.2c559eaa@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
Message-ID: <11525.1250039104@chondestes.bio.unc.edu>

> 2. If you can't test it on both 32bit and 64bit -current,
>    don't bother replying for now.  Later on (after the submit
>    form is open again), it won't be as big of a problem, but
>    for now, it is.

Thanks --- that clears it right up for me!

Joel

-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280

From mjjzf at syntaktisk.dk  Wed Aug 12 06:08:11 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Wed, 12 Aug 2009 08:08:11 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A81E404.6040707@gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
	<4A81E404.6040707@gmail.com>
Message-ID: <043baaa05425bfd756ef0165c9ee7e67.squirrel@squirrelmail.gigahost.dk>


---- 8< ---- Pierre Cazenave ---- 8< ----
> In which case, scratch mine. 64-bit is on my todo list.
---- 8< ---- Pierre Cazenave ---- 8< ----

I echo that. 64-bit os on my would-like-to-do-but-can't list.

-Morten
__
http://www.syntaktisk.dk

From chaos.proton at gmail.com  Wed Aug 12 14:37:17 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Wed, 12 Aug 2009 22:37:17 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <043baaa05425bfd756ef0165c9ee7e67.squirrel@squirrelmail.gigahost.dk>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
	<4A81E404.6040707@gmail.com>
	<043baaa05425bfd756ef0165c9ee7e67.squirrel@squirrelmail.gigahost.dk>
Message-ID: <a0adeea50908120737v5863525akecb4a27328199e6e@mail.gmail.com>

For development/pylint/, it's a pure python program which is compatible with
python2.6. So it will be ok to push it to the 13.0 repo after switch the
default ARCH tag to i486 or whatever not "noarch" since it use /usr/lib or
/usr/lib64 depend on the system building it.

For system/qstardict/, it's compatible with 32bit current but I failed to
get qmake to install lib files into /usr/lib64, i.e., it will install
something into /usr/lib even in 64bit system... If you think that's not a
problem, you can push it into 13.0 repo.

-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090812/b001bdd8/attachment.htm>

From disturbed1976 at gmail.com  Wed Aug 12 19:55:40 2009
From: disturbed1976 at gmail.com (Keith Richie)
Date: Wed, 12 Aug 2009 15:55:40 -0400
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908120737v5863525akecb4a27328199e6e@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
	<4A81E404.6040707@gmail.com>
	<043baaa05425bfd756ef0165c9ee7e67.squirrel@squirrelmail.gigahost.dk>
	<a0adeea50908120737v5863525akecb4a27328199e6e@mail.gmail.com>
Message-ID: <66a22e960908121255s27a91671k7f2c0cbc628234a6@mail.gmail.com>

On Wed, Aug 12, 2009 at 10:37 AM, Grissiom<chaos.proton at gmail.com> wrote:
> For development/pylint/, it's a pure python program which is compatible with
> python2.6. So it will be ok to push it to the 13.0 repo after switch the
> default ARCH tag to i486 or whatever not "noarch" since it use /usr/lib or
> /usr/lib64 depend on the system building it.
>
> For system/qstardict/, it's compatible with 32bit current but I failed to
> get qmake to install lib files into /usr/lib64, i.e., it will install
> something into /usr/lib even in 64bit system... If you think that's not a
> problem, you can push it into 13.0 repo.
>
> --
> Cheers,
> Grissiom
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>


for qstardict try this

qmake PLUGINS_DIR=/usr/lib${LIBDIRSUFFIX} QMAKE_CXXFLAGS="$SLKCFLAGS"

From chaos.proton at gmail.com  Thu Aug 13 06:02:41 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Thu, 13 Aug 2009 14:02:41 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <66a22e960908121255s27a91671k7f2c0cbc628234a6@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
	<4A81E404.6040707@gmail.com>
	<043baaa05425bfd756ef0165c9ee7e67.squirrel@squirrelmail.gigahost.dk>
	<a0adeea50908120737v5863525akecb4a27328199e6e@mail.gmail.com>
	<66a22e960908121255s27a91671k7f2c0cbc628234a6@mail.gmail.com>
Message-ID: <a0adeea50908122302m38418beapac58fa5151f5e6f@mail.gmail.com>

On Thu, Aug 13, 2009 at 03:55, Keith Richie <disturbed1976 at gmail.com> wrote:

>
> for qstardict try this
>
> qmake PLUGINS_DIR=/usr/lib${LIBDIRSUFFIX} QMAKE_CXXFLAGS="$SLKCFLAGS"
>

It works ;D

So here is the update.

Thanks a lot ;)

-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/8b4e4b71/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qstardict.tar
Type: application/x-tar
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/8b4e4b71/attachment-0001.tar>

From nobbutl at yahoo.co.uk  Thu Aug 13 11:19:49 2009
From: nobbutl at yahoo.co.uk (David Spencer)
Date: Thu, 13 Aug 2009 12:19:49 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
Message-ID: <4A83F6D5.6090101@yahoo.co.uk>

Marco Cecchetti wrote:
> *libraries/gdal/
> libraries/libgeotiff/
> *I don't use these 2 any more. I'm going to leave the maintenance

I can take those on if everyone agrees. They both need LIBDIRSUFFIX for
x86_64 support, tarballs attached.

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

Some other packages I don't maintain.  Thanks to the maintainers, hope
I've saved you some work :-)

libraries/geos needs to be upversioned to work round a problem with the
new GCC in Slack 13.  It also needs LIBDIRSUFFIX for x86_64.  Tarball
attached.

system/proj needs LIBDIRSUFFIX for x86_64.  Tarball attached.

system/squeeze needs LIBDIRSUFFIX for x86_64.  Tarball attached.

graphics/ufraw tested OK without changes on both i486 and x86_64.

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

Finally a package I do maintain:

graphics/xtrkcad needs to be upversioned to avoid polluting /usr/lib
with noarch stuff on x86_64 (they moved it to /usr/share). Tarball
attached.  The new version uses cmake, so the SlackBuild has significant
changes.

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

Hope all this is clear, thanks to everyone for such great work.
-Dave Spencer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdal.tar.gz
Type: application/gzip
Size: 2119 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/527ad39a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libgeotiff.tar.gz
Type: application/gzip
Size: 1611 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/527ad39a/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: geos.tar.gz
Type: application/gzip
Size: 1705 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/527ad39a/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: proj.tar.gz
Type: application/gzip
Size: 1638 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/527ad39a/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: squeeze.tar.gz
Type: application/gzip
Size: 2251 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/527ad39a/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xtrkcad.tar.gz
Type: application/gzip
Size: 1640 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/527ad39a/attachment-0005.bin>

From mrc.ildp at gmail.com  Thu Aug 13 14:24:48 2009
From: mrc.ildp at gmail.com (Marco Cecchetti)
Date: Thu, 13 Aug 2009 16:24:48 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A83F6D5.6090101@yahoo.co.uk>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
Message-ID: <207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>

2009/8/13 David Spencer <nobbutl at yahoo.co.uk>

> Marco Cecchetti wrote:
> > *libraries/gdal/
> > libraries/libgeotiff/
> > *I don't use these 2 any more. I'm going to leave the maintenance
>
> I can take those on if everyone agrees. They both need LIBDIRSUFFIX for
> x86_64 support, tarballs attached.


Good, thanks for taking care of them.

Just a thing, I added libz path option but probably it is not needed
and now it is not correct for x86_64 arch.

Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/6b271eb0/attachment.htm>

From nobbutl at yahoo.co.uk  Thu Aug 13 21:02:20 2009
From: nobbutl at yahoo.co.uk (David Spencer)
Date: Thu, 13 Aug 2009 22:02:20 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
Message-ID: <4A847F5C.4080508@yahoo.co.uk>

> Just a thing, I added libz path option but probably it is not needed
> and now it is not correct for x86_64 arch.

So, I've been maintainer for about nine hours now, and I've just made my
first embarassing mistake.  Impressive :-)

Apparently, when configure sees "--with-libz=/usr/lib", it just thinks
"external libz, not internal libz", and ignores the supplied path, and
successfully finds the external libz "wherever", and then lies about
where it found it.

checking for deflateInit_ in -lz... yes
checking for inflateCopy in -lz... yes
using libz library from /usr/lib

But... even though configure is ignoring the wrong path and successfully
finding the library, we really *should* give it the correct path.

Revised tarball attached.  I also updated the README, since swig will be
included in Slack 13.  Sorry everyone, and thanks Marco for the
correction.  I hope this has kept the list entertained!

-Dave S.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdal.tar.gz
Type: application/gzip
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090813/28f46a49/attachment-0001.bin>

From chaos.proton at gmail.com  Fri Aug 14 14:16:04 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Fri, 14 Aug 2009 22:16:04 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
Message-ID: <a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>

multimedia/cuetools is ok on both 64bit and 32bit current.

-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/d226e02a/attachment.htm>

From chaos.proton at gmail.com  Fri Aug 14 15:05:46 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Fri, 14 Aug 2009 23:05:46 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
	<a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
Message-ID: <a0adeea50908140805g3d4650d2i4bc08c3b88bd1fb@mail.gmail.com>

For package I don't maintain:

development/nose/, switch default ARCH from noarch to i486.
misc/pinfo, add x86_64 SLKCFLAGS.

I see development/pylint/ is still on the list so I made the tarball as
well.

-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/6ffaa4b2/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pylint.tar
Type: application/x-tar
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/6ffaa4b2/attachment-0003.tar>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nose.tar
Type: application/x-tar
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/6ffaa4b2/attachment-0004.tar>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pinfo.tar
Type: application/x-tar
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/6ffaa4b2/attachment-0005.tar>

From chaos.proton at gmail.com  Fri Aug 14 15:26:39 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Fri, 14 Aug 2009 23:26:39 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908140805g3d4650d2i4bc08c3b88bd1fb@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
	<a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
	<a0adeea50908140805g3d4650d2i4bc08c3b88bd1fb@mail.gmail.com>
Message-ID: <a0adeea50908140826w2f09e8c5u898abc951c9533c4@mail.gmail.com>

Hmm, how could a system without rar support be useful? ;)

Also fix a bug in {C,CXX}FLAGS usage.

-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/35ead700/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: unrar.tar
Type: application/x-tar
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/35ead700/attachment.tar>

From vbatts at hashbangbash.com  Fri Aug 14 21:11:05 2009
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Fri, 14 Aug 2009 16:11:05 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <2015330f0908141411o22013e14h3302b0e09a2a7636@mail.gmail.com>

of mine, xmlstarlet is the only i would see fit to be there immediately.

tested on 32 and 64 bit.

vb
205.352.4112
http://hashbangbash.com/



On Mon, Aug 10, 2009 at 2:55 PM, Robby Workman<rworkman at slackbuilds.org> wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
> ?http://slackbuilds.org/NOT_CHECKED
>
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance. ?I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.
>
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
>
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
>
> -RW
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xmlstarlet.tar.gz
Type: application/x-gzip
Size: 2416 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090814/44c85966/attachment.bin>

From rworkman at slackbuilds.org  Sat Aug 15 05:43:36 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 00:43:36 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A808C18.3040000@gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4A808C18.3040000@gmail.com>
Message-ID: <20090815004336.6b574ec2@liberty.rlwhome.lan>

On Mon, 10 Aug 2009 22:07:36 +0100
Pierre Cazenave <pwcazenave at gmail.com> wrote:

> development/CImg/
> multimedia/wxcam/
> system/fdupes/
> system/fish/


All done; thanks!

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

From rworkman at slackbuilds.org  Sat Aug 15 05:52:55 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 00:52:55 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A80EA18.1050808@mnspace.net>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4A80EA18.1050808@mnspace.net>
Message-ID: <20090815005255.695b9dd6@liberty.rlwhome.lan>

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

On Mon, 10 Aug 2009 22:48:40 -0500
Nishant Limbachia <nishant at mnspace.net> wrote:

> Here's the tarball for dovecot-cmusieve (known as dovecot-sieve in the
> 12.2 repo).  The name change is warranted because this sieve plugin is
> originally based on cmusieve plugin for cyrus IMAP server and called
> dovecot-cmusieve on dovecot website.  However, the foremost reason for
> name change is that there's a new implementation of sieve plugin for
> dovecot and is called dovecot-sieve.  I've tested the build on
> -current and haven't seen any problems yet.


Added (with a note about the replacement); thanks!

- -RW

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEARECAAYFAkqGTTcACgkQvGy9tf6lsvu/WwCghxhLXWk7ofSGFCHr3ScNZ5/5
dtcAn1VIArxHZud6tpjcj5v7lun95BVD
=cnxJ
-----END PGP SIGNATURE-----

From rworkman at slackbuilds.org  Sat Aug 15 05:53:27 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 00:53:27 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1249989629.417.1329295469@webmail.messagingengine.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<1249946887.375.1329222559@webmail.messagingengine.com>
	<20090811013120.77660e12@hades.esn.local>
	<1249989629.417.1329295469@webmail.messagingengine.com>
Message-ID: <20090815005327.34025ea8@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 14:20:29 +0300
"Grigorios Bouzakis" <grbzks at xsmail.com> wrote:

> On Tue, 11 Aug 2009 01:31 +0100, "Michiel van Wessem"
> <michiel at slackbuilds.org> wrote:
> > On Tue, 11 Aug 2009 02:28:07 +0300
> > "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> > > Is there a new template that automatically handles all possible
> > > architectures, or are users expected to edit the ARCH variable 
> > > prior to building the package like
> > > before?
> > 
> > The official template is up to date as what you need to have in your
> > slackbuild script as for the different architectures: 
> > 
> > http://slackbuilds.org/template.SlackBuild
> > 
> > as for setting the ARCH; the easiest way of doing this is just
> > setting the ARCH variable in your shell start-up files. For
> > example, my bashrc, contains the following line:
> > 
> > export ARCH="x86_64"
> 
> Maybe it would be better then to change the comment on this line
> ARCH=${ARCH:-i486}              # this should not change
> to something more descriptive?


I just completely deleted it.  

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

From rworkman at slackbuilds.org  Sat Aug 15 06:26:02 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 01:26:02 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1249992604.4203.3.camel@laptop>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4A808C18.3040000@gmail.com> <1249992604.4203.3.camel@laptop>
Message-ID: <20090815012602.5cd62202@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 14:10:04 +0200
Michael Wagner <slackware.wagnerm at arcor.de> wrote:

> >From http://slackbuilds.org/NOT_CHECKED:
> 
> libopensync-plugin-syncml
> gtkam
> 
> liopensync-plugin-kdepim should be removed as it doesn't work with
> akonadi.


Done @all.

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

From rworkman at slackbuilds.org  Sat Aug 15 16:07:38 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 11:07:38 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1073907678.4943951250000791394.JavaMail.root@zimbra10-e2.priv.proxad.net>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<1073907678.4943951250000791394.JavaMail.root@zimbra10-e2.priv.proxad.net>
Message-ID: <20090815110738.2834570f@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 16:26:31 +0200 (CEST)
cnguyenminhtan at free.fr wrote:

> desktop/un-fonts-core, it's a fonts package so it should be OK. I
> will install it on my -current machine and let you know.


Tested here and it looks fine; added.


> network/kftpgrabber: To be removed. No new version since april 2007.
> So I doubt it will compile on KDE4 (I haven't even tried).
> 
> system/skim: To be removed. No new version since a long time ago.


Both removed.

Thanks!

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

From rworkman at slackbuilds.org  Sat Aug 15 16:10:05 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 11:10:05 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A81A0C1.70005@gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4A81A0C1.70005@gmail.com>
Message-ID: <20090815111005.3da35827@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 18:48:01 +0200
Niklas 'Nille' ?kerstr?m <nille.kungen at gmail.com> wrote:

> Now i wonder about the new arch testing.
> I don't have anything but an i486 box to test my builds on.
> I can add the other arch to my builds but i can't test it.
> So should i add tested arch to my reply with my results?


There's really no good way to handle this, at least for now.
While we'd prefer not to exclude maintainers that only have
one arch or another, the fact remains that there's a lot of
risk in allowing submissions that aren't tested on both.

For the time being, it's probably best to hold off on anything
if you can't test on both arches.  Once the 13.0 repo is made
public, I would expect that you'll be able to look at some of
the existing scripts to see what's likely to need done, and 
probably that will cover the most common cases.  For the ones
that it doesn't, well, that's why we're testing them :-)

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

From rworkman at slackbuilds.org  Sat Aug 15 16:21:23 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 11:21:23 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
Message-ID: <20090815112123.2d4917d2@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 22:00:33 +0200
Marco Cecchetti <mrc.ildp at gmail.com> wrote:

> these are my not checked:
> *
> games/Chatbot-Eliza*/
> it does not need any change
> I'm going to maintain it, waiting for CADIE... ;-)


It's not clear what you mean here - do you want me to remove 
it for now in anticipation of a new submission, or is it fine
to go into the 13.0 tree (mostly) as is?

 
> *audio/exaile/*
> It depends on some gnome packages
> so I'm going to take care of it later.


So this one should be removed for now?


> *libraries/gdal/
> libraries/libgeotiff/
> *I don't use these 2 any more. I'm going to leave the maintenance


Removed.


> *system/mlterm/*
> I submit here the changes


Added.

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

From rworkman at slackbuilds.org  Sat Aug 15 16:29:00 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 11:29:00 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908120737v5863525akecb4a27328199e6e@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811154011.2c559eaa@liberty.rlwhome.lan>
	<4A81E404.6040707@gmail.com>
	<043baaa05425bfd756ef0165c9ee7e67.squirrel@squirrelmail.gigahost.dk>
	<a0adeea50908120737v5863525akecb4a27328199e6e@mail.gmail.com>
Message-ID: <20090815112900.43079cd2@liberty.rlwhome.lan>

On Wed, 12 Aug 2009 22:37:17 +0800
Grissiom <chaos.proton at gmail.com> wrote:

> For development/pylint/, it's a pure python program which is
> compatible with python2.6. So it will be ok to push it to the 13.0
> repo after switch the default ARCH tag to i486 or whatever not
> "noarch" since it use /usr/lib or /usr/lib64 depend on the system
> building it.
> 
> For system/qstardict/, it's compatible with 32bit current but I
> failed to get qmake to install lib files into /usr/lib64, i.e., it
> will install something into /usr/lib even in 64bit system... If you
> think that's not a problem, you can push it into 13.0 repo.


Added both (after catching the later mails about qstardict).

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

From rworkman at slackbuilds.org  Sat Aug 15 16:44:05 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 11:44:05 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <2015330f0908141411o22013e14h3302b0e09a2a7636@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<2015330f0908141411o22013e14h3302b0e09a2a7636@mail.gmail.com>
Message-ID: <20090815114405.05c3c572@liberty.rlwhome.lan>

On Fri, 14 Aug 2009 16:11:05 -0500
Vincent Batts <vbatts at hashbangbash.com> wrote:

> of mine, xmlstarlet is the only i would see fit to be there
> immediately.
> 
> tested on 32 and 64 bit.


See attached tarball for a required patch to find static
libraries in /usr/lib64.  Otherwise, all is good and it's
added now.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xmlstarlet.tar.gz
Type: application/x-gzip
Size: 2374 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/f0bd1a49/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/f0bd1a49/attachment.asc>

From rworkman at slackbuilds.org  Sat Aug 15 16:47:50 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 11:47:50 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090811222738.2be182b1@darkstar.example.net>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811222738.2be182b1@darkstar.example.net>
Message-ID: <20090815114750.711b1434@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 22:27:38 +0200
Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:

> My build of Gajim still works.
> I am, however, going to submit an updated build and package an extra
> optional dependency for it as well.


Added as is with a few minor tweaks for 64bit.
Be sure to sync the changes to your local copy before
submitting the update (after our submit form is open
again). 

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

From rworkman at slackbuilds.org  Sat Aug 15 17:51:01 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 12:51:01 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A83F6D5.6090101@yahoo.co.uk>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
Message-ID: <20090815125101.5a76b20b@liberty.rlwhome.lan>

On Thu, 13 Aug 2009 12:19:49 +0100
David Spencer <nobbutl at yahoo.co.uk> wrote:

> Marco Cecchetti wrote:
> > *libraries/gdal/
> > libraries/libgeotiff/
> > *I don't use these 2 any more. I'm going to leave the maintenance
> 
> I can take those on if everyone agrees. They both need LIBDIRSUFFIX
> for x86_64 support, tarballs attached.


Both added, after checking in the changes from the later mail
(re libz stuff).  We all make mistakes  :-)


> libraries/geos needs to be upversioned to work round a problem with
> the new GCC in Slack 13.  It also needs LIBDIRSUFFIX for x86_64.
> Tarball attached.


Added.

 
> system/proj needs LIBDIRSUFFIX for x86_64.  Tarball attached.


Added.

 
> system/squeeze needs LIBDIRSUFFIX for x86_64.  Tarball attached.


Added.

 
> graphics/ufraw tested OK without changes on both i486 and x86_64.


Added with minor tweaks; also caught a bug in the dcraw script
while looking into this, so that's good :-)


> graphics/xtrkcad needs to be upversioned to avoid polluting /usr/lib
> with noarch stuff on x86_64 (they moved it to /usr/share). Tarball
> attached.  The new version uses cmake, so the SlackBuild has
> significant changes.


Added.

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

From grbzks at xsmail.com  Sat Aug 15 18:24:39 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sat, 15 Aug 2009 21:24:39 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <1250360679.29213.1330007659@webmail.messagingengine.com>



On Mon, 10 Aug 2009 14:55 -0500, "Robby Workman"
<rworkman at slackbuilds.org> wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
> 
> -RW

Here are some of mine.
All that were in the list besides dzen2 which needs custom LDFLAGS
I also left out the neutral cursor theme as it doesn't require any
changes.

colordiff wasn't on the list but changed ARCH to noarch since its just
sh & perl scripts
gtk-engines version bump and x86_64 compliance
leafpad x86_64 compliance
mktorrent changed homepage
tig x86_64 compliance

All have been tested only on x86_64 but should be fine on i486 as well.

-- 
 Greg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: colordiff.tar.gz
Type: application/gzip
Size: 1779 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/baedbf8a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gtk-engines.tar.gz
Type: application/gzip
Size: 1664 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/baedbf8a/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: leafpad.tar.gz
Type: application/gzip
Size: 1937 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/baedbf8a/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mktorrent.tar.gz
Type: application/gzip
Size: 1468 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/baedbf8a/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tig.tar.gz
Type: application/gzip
Size: 2041 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/baedbf8a/attachment-0004.bin>

From mrc.ildp at gmail.com  Sat Aug 15 19:55:45 2009
From: mrc.ildp at gmail.com (Marco Cecchetti)
Date: Sat, 15 Aug 2009 21:55:45 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090815112123.2d4917d2@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<20090815112123.2d4917d2@liberty.rlwhome.lan>
Message-ID: <207ff4b00908151255q3a8beb86ye3a10e2877e7ba13@mail.gmail.com>

2009/8/15 Robby Workman <rworkman at slackbuilds.org>

> On Tue, 11 Aug 2009 22:00:33 +0200
> Marco Cecchetti <mrc.ildp at gmail.com> wrote:
>
> > these are my not checked:
> > *
> > games/Chatbot-Eliza*/
> > it does not need any change
> > I'm going to maintain it, waiting for CADIE... ;-)
>
>
> It's not clear what you mean here - do you want me to remove
> it for now in anticipation of a new submission, or is it fine
> to go into the 13.0 tree (mostly) as is?
>

Yes, it was a joke about Google CADIE :-P Actually I was not clear.
However I think it is ok to go into 13.0 as is.


>
>
> > *audio/exaile/*
> > It depends on some gnome packages
> > so I'm going to take care of it later.
>
>
> So this one should be removed for now?
>
> This should be removed for now. I will submit a new one
after 13.0 is released.

Thanks,
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090815/a3017064/attachment.htm>

From rworkman at slackbuilds.org  Sat Aug 15 22:17:25 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 17:17:25 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <207ff4b00908151255q3a8beb86ye3a10e2877e7ba13@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<20090815112123.2d4917d2@liberty.rlwhome.lan>
	<207ff4b00908151255q3a8beb86ye3a10e2877e7ba13@mail.gmail.com>
Message-ID: <20090815171725.464fe543@liberty.rlwhome.lan>

On Sat, 15 Aug 2009 21:55:45 +0200
Marco Cecchetti <mrc.ildp at gmail.com> wrote:

> 2009/8/15 Robby Workman <rworkman at slackbuilds.org>
> 
> > On Tue, 11 Aug 2009 22:00:33 +0200
> > Marco Cecchetti <mrc.ildp at gmail.com> wrote:
> >
> > > these are my not checked:
> > > *
> > > games/Chatbot-Eliza*/
> > > it does not need any change
> > > I'm going to maintain it, waiting for CADIE... ;-)
> >
> >
> > It's not clear what you mean here - do you want me to remove
> > it for now in anticipation of a new submission, or is it fine
> > to go into the 13.0 tree (mostly) as is?
> >
> 
> Yes, it was a joke about Google CADIE :-P Actually I was not clear.
> However I think it is ok to go into 13.0 as is.


Ah, okay, I'm a bit slow today :-)
Only change was to default i486 instead of noarch, since the
perldir and such will change on x86_64, so the package won't
truly be a noarch pack.


> > > *audio/exaile/*
> > > It depends on some gnome packages
> > > so I'm going to take care of it later.
> >
> >
> > So this one should be removed for now?
> >
> This should be removed for now. I will submit a new one
> after 13.0 is released.


Okay, removed.  Thanks!

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

From rworkman at slackbuilds.org  Sat Aug 15 22:49:28 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 15 Aug 2009 17:49:28 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0 (for me :
 Xfmedia)
In-Reply-To: <20090811181225.6b538d55@zenwalk.hyperion.net>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090811181225.6b538d55@zenwalk.hyperion.net>
Message-ID: <20090815174928.0bfeb71e@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 18:12:25 +0200
Antoine NONYME <mickeytintincolle at yahoo.fr> wrote:

> I don't have my Slackware 12.2 updated to current, but the SlackBuild
> compiles well in my up-to-date Zenwalk . There don't seem to be any
> update in Xfmedia according to the official website .


I patched a the build system to put the html docs in the
correct place (in such a way that an integrated help
function should be able to find them) and added all of 
the other docs to the package; it's in the 13.0 repo now.

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

From rworkman at slackbuilds.org  Sun Aug 16 05:32:17 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 00:32:17 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
	<a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
Message-ID: <20090816003217.0a6f4d76@liberty.rlwhome.lan>

On Fri, 14 Aug 2009 22:16:04 +0800
Grissiom <chaos.proton at gmail.com> wrote:

> multimedia/cuetools is ok on both 64bit and 32bit current.


Added.

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

From rworkman at slackbuilds.org  Sun Aug 16 05:57:45 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 00:57:45 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1250360679.29213.1330007659@webmail.messagingengine.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<1250360679.29213.1330007659@webmail.messagingengine.com>
Message-ID: <20090816005745.2fbfc455@liberty.rlwhome.lan>

On Sat, 15 Aug 2009 21:24:39 +0300
"Grigorios Bouzakis" <grbzks at xsmail.com> wrote:

> All that were in the list besides dzen2 which needs custom LDFLAGS
> I also left out the neutral cursor theme as it doesn't require any
> changes.


So what should I do with those?


> colordiff wasn't on the list but changed ARCH to noarch since its just
> sh & perl scripts


Fixed; thanks.


> gtk-engines version bump and x86_64 compliance


Added.


> leafpad x86_64 compliance


Added.


> mktorrent changed homepage


Fixed, along with some build fixes to add our SLKCFLAGS.


> tig x86_64 compliance


Added.

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

From rworkman at slackbuilds.org  Sun Aug 16 06:06:05 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 01:06:05 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908140826w2f09e8c5u898abc951c9533c4@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
	<a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
	<a0adeea50908140805g3d4650d2i4bc08c3b88bd1fb@mail.gmail.com>
	<a0adeea50908140826w2f09e8c5u898abc951c9533c4@mail.gmail.com>
Message-ID: <20090816010605.5d08dc28@liberty.rlwhome.lan>

On Fri, 14 Aug 2009 23:26:39 +0800
Grissiom <chaos.proton at gmail.com> wrote:

> Hmm, how could a system without rar support be useful? ;)
> 
> Also fix a bug in {C,CXX}FLAGS usage.


In makefile.unix, CXXFLAGS is left undefined for linux builds,
so simply doing this will suffice:
  make CXXFLAGS="$SLKCFLAGS" -f makefile.unix

I handled it here and added unrar to the 13.0 repo.

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

From rworkman at slackbuilds.org  Sun Aug 16 06:12:39 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 01:12:39 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <a0adeea50908140805g3d4650d2i4bc08c3b88bd1fb@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<207ff4b00908111300j64cb905bk7a994df0bdd1449a@mail.gmail.com>
	<4A83F6D5.6090101@yahoo.co.uk>
	<207ff4b00908130724t558ddfeai7823e034dc672483@mail.gmail.com>
	<a0adeea50908140716k50046201n24be54d983a9f66@mail.gmail.com>
	<a0adeea50908140805g3d4650d2i4bc08c3b88bd1fb@mail.gmail.com>
Message-ID: <20090816011239.201078fa@liberty.rlwhome.lan>

On Fri, 14 Aug 2009 23:05:46 +0800
Grissiom <chaos.proton at gmail.com> wrote:

> development/nose/, switch default ARCH from noarch to i486.
> misc/pinfo, add x86_64 SLKCFLAGS.


Both added.


> I see development/pylint/ is still on the list so I made the tarball
> as well.


It was gone by the time I saw this mail, so...  :-)

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

From rworkman at slackbuilds.org  Sun Aug 16 06:49:29 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 01:49:29 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <137810.29741.qm@web51106.mail.re2.yahoo.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<137810.29741.qm@web51106.mail.re2.yahoo.com>
Message-ID: <20090816014929.59861743@liberty.rlwhome.lan>

On Tue, 11 Aug 2009 10:47:01 -0700 (PDT)
Dave <techjunkus at yahoo.com> wrote:

> games/zsnes
> 
> ZSNES won't build with the newer version of gcc in Slackware 13.0.
> However, there's a source archive available that's patched for gcc
> 4.3.
> 
> url:
> http://zsnes.sf.net/zsnes151bsrc.tar.bz2
> 
> md5sum:
> 904ee432f378609176ed30c01cf6ea28  zsnes151bsrc.tar.bz2
> 
> (that's just the md5sum I see after downloading and double-checking)
> I've cc'd the maintainer, and hope to see zsnes included for
> Slackware 13.0.


Done and added to our 13.0 repo; thanks!

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

From grbzks at xsmail.com  Sun Aug 16 06:49:43 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sun, 16 Aug 2009 09:49:43 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090816005745.2fbfc455@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan><1250360679.29213.1330007659@webmail.messagingengine.com>
	<20090816005745.2fbfc455@liberty.rlwhome.lan>
Message-ID: <1250405383.27050.1330054329@webmail.messagingengine.com>



On Sun, 16 Aug 2009 00:57 -0500, "Robby Workman"
<rworkman at slackbuilds.org> wrote:
> On Sat, 15 Aug 2009 21:24:39 +0300
> "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> 
> > All that were in the list besides dzen2 which needs custom LDFLAGS
> > I also left out the neutral cursor theme as it doesn't require any
> > changes.
> 
> 
> So what should I do with those?
> 
> -RW

I don't intend to submit scripts for dzen2 ATM.
In fact i don't use it so if anyone does and wants to maintain it, be my
guest.
If not i will submit a script for it at some later time.
You can leave it out for now.

Regarding neutral, its just a cursor theme, so the script should work
just fine.
You can just use the one for 12.2 or get the attached files.
I rewrote all scripts that were on the list again, after consulting the
originals
as they are very simple.
The attached ones should be identical to the 12.2 files.

-- 
 Greg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: neutral.tar.gz
Type: application/gzip
Size: 1402 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090816/75664726/attachment.bin>

From rworkman at slackbuilds.org  Sun Aug 16 06:57:59 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 01:57:59 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1250405383.27050.1330054329@webmail.messagingengine.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<1250360679.29213.1330007659@webmail.messagingengine.com>
	<20090816005745.2fbfc455@liberty.rlwhome.lan>
	<1250405383.27050.1330054329@webmail.messagingengine.com>
Message-ID: <20090816015759.33fcc94e@liberty.rlwhome.lan>

On Sun, 16 Aug 2009 09:49:43 +0300
"Grigorios Bouzakis" <grbzks at xsmail.com> wrote:

> On Sun, 16 Aug 2009 00:57 -0500, "Robby Workman"
> <rworkman at slackbuilds.org> wrote:
> > On Sat, 15 Aug 2009 21:24:39 +0300
> > "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> > 
> > > All that were in the list besides dzen2 which needs custom LDFLAGS
> > > I also left out the neutral cursor theme as it doesn't require any
> > > changes.
> > 
> > 
> > So what should I do with those?
> > 
> 
> I don't intend to submit scripts for dzen2 ATM.
> In fact i don't use it so if anyone does and wants to maintain it, be
> my guest.
> If not i will submit a script for it at some later time.
> You can leave it out for now.


Okay, it's now listed as removed.  If you don't use it any more,
then I'd suggest just leaving it out for good.  If someone else
wants it, then they can pull it from the 12.2 repo and maintain
it if they care enough.


> Regarding neutral, its just a cursor theme, so the script should work
> just fine.


I hardcoded the "noarch" so that it's not overridden by an ARCH 
value in the environment and put this one in the 13.0 repo.

Thanks!

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

From rworkman at slackbuilds.org  Sun Aug 16 06:58:49 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 01:58:49 -0500
Subject: [Slackbuilds-users] CurseTheWeather URL fix needed
In-Reply-To: <759034.17815.qm@web57707.mail.re3.yahoo.com>
References: <759034.17815.qm@web57707.mail.re3.yahoo.com>
Message-ID: <20090816015849.734c27c1@liberty.rlwhome.lan>

On Sat, 11 Jul 2009 14:58:06 -0700 (PDT)
Phillip Warner <pc_warner at yahoo.com> wrote:

> CurseTheWeather does not work for now.
> 
> Recently weather.com started requiring a different URL format for
> their XML feeds.  They now require prod, link, par, and key values.
> The par (partner) and key values I believe are supposed to be
> obtained by requesting them from weather.com.  I emailed the
> CurseTheWeather maintainer (Dan) about obtaining these values from
> weather.com.
> 
> I made a temporary patch that will allow ctw to work.  The par and
> key values are from the liquid weather project.  This works, but this
> probably violates some weather.com policy.  In addition, these values
> apparently do not let you view a full 10 day forecast.  Instead it is
> limited to five days.  As such, I'd prefer not to release this patch
> on the list, and would rather see if Dan can get the needed codes
> soon.  I just wanted all the CurseTheWeather SBo users on this list
> to know of the problem.


I'm just curious - any news on this?

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

From grbzks at xsmail.com  Sun Aug 16 07:44:47 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sun, 16 Aug 2009 10:44:47 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090816015759.33fcc94e@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan><1250360679.29213.1330007659@webmail.messagingengine.com><20090816005745.2fbfc455@liberty.rlwhome.lan><1250405383.27050.1330054329@webmail.messagingengine.com>
	<20090816015759.33fcc94e@liberty.rlwhome.lan>
Message-ID: <1250408687.556.1330057451@webmail.messagingengine.com>



On Sun, 16 Aug 2009 01:57 -0500, "Robby Workman"
<rworkman at slackbuilds.org> wrote:
> On Sun, 16 Aug 2009 09:49:43 +0300
> "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> 
> > On Sun, 16 Aug 2009 00:57 -0500, "Robby Workman"
> > <rworkman at slackbuilds.org> wrote:
> > > On Sat, 15 Aug 2009 21:24:39 +0300
> > > "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> > > 
> > > > All that were in the list besides dzen2 which needs custom LDFLAGS
> > > > I also left out the neutral cursor theme as it doesn't require any
> > > > changes.
> > > 
> > > 
> > > So what should I do with those?
> > > 
> > 
> > I don't intend to submit scripts for dzen2 ATM.
> > In fact i don't use it so if anyone does and wants to maintain it, be
> > my guest.
> > If not i will submit a script for it at some later time.
> > You can leave it out for now.
> 
> 
> Okay, it's now listed as removed.  If you don't use it any more,
> then I'd suggest just leaving it out for good.  If someone else
> wants it, then they can pull it from the 12.2 repo and maintain
> it if they care enough.
> 
> 
> -RW

Here's also scripts for msmtp which is one of dadexter's former
packages.
It wasn't on the list but i can maintain it if noone else will.

-- 
 Greg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: msmtp.tar.gz
Type: application/gzip
Size: 1840 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090816/3118f599/attachment-0001.bin>

From rworkman at slackbuilds.org  Sun Aug 16 19:32:28 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 16 Aug 2009 14:32:28 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <1250408687.556.1330057451@webmail.messagingengine.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<1250360679.29213.1330007659@webmail.messagingengine.com>
	<20090816005745.2fbfc455@liberty.rlwhome.lan>
	<1250405383.27050.1330054329@webmail.messagingengine.com>
	<20090816015759.33fcc94e@liberty.rlwhome.lan>
	<1250408687.556.1330057451@webmail.messagingengine.com>
Message-ID: <20090816143228.5159ee90@liberty.rlwhome.lan>

On Sun, 16 Aug 2009 10:44:47 +0300
"Grigorios Bouzakis" <grbzks at xsmail.com> wrote:

> Here's also scripts for msmtp which is one of dadexter's former
> packages.
> It wasn't on the list but i can maintain it if noone else will.


This one had already been bumped, but I changed the maintainer
info to yours.

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

From pc_warner at yahoo.com  Mon Aug 17 00:47:07 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Sun, 16 Aug 2009 17:47:07 -0700 (PDT)
Subject: [Slackbuilds-users] CurseTheWeather URL fix needed
In-Reply-To: <20090816015849.734c27c1@liberty.rlwhome.lan>
Message-ID: <415611.53882.qm@web57702.mail.re3.yahoo.com>

Dan went ahead and just used my patch as is and released a new version of ctw.  I emailed him back asking him to look into obtaining the weather.com values properly, but I think he has other priorities right now.  I did not post back on this list because I was hoping he would get back to me.

As mentioned previously, ctw now only shows the forecast for 5 days instead of 10.  When I made the patch I did not bother changing the UI, since the patch was intended to be temporary until Dan could get the full weather.com support back.  As a result, half of the UI is empty (the missing 5 days) instead of just spreading it out.  This doesn't bother me, and I don't intend on fixing it unless there's a lot of people this does bother.

My patch also added support for transparency, so that is included in the new version.

A version bump should be all the SlackBuild needs.  The link for the new version is http://opensource.hld.ca/trac.cgi/browser/trunk/ctw/dist/CurseTheWeather-0.5.tar.gz

--phillip

--- On Sat, 8/15/09, Robby Workman <rworkman at slackbuilds.org> wrote:

> From: Robby Workman <rworkman at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] CurseTheWeather URL fix needed
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Cc: pc_warner at yahoo.com
> Date: Saturday, August 15, 2009, 11:58 PM
> On Sat, 11 Jul 2009 14:58:06 -0700
> (PDT)
> Phillip Warner <pc_warner at yahoo.com>
> wrote:
> 
> > CurseTheWeather does not work for now.
> > 
> > Recently weather.com started requiring a different URL
> format for
> > their XML feeds.? They now require prod, link,
> par, and key values.
> > The par (partner) and key values I believe are
> supposed to be
> > obtained by requesting them from weather.com.? I
> emailed the
> > CurseTheWeather maintainer (Dan) about obtaining these
> values from
> > weather.com.
> > 
> > I made a temporary patch that will allow ctw to
> work.? The par and
> > key values are from the liquid weather project.?
> This works, but this
> > probably violates some weather.com policy.? In
> addition, these values
> > apparently do not let you view a full 10 day
> forecast.? Instead it is
> > limited to five days.? As such, I'd prefer not to
> release this patch
> > on the list, and would rather see if Dan can get the
> needed codes
> > soon.? I just wanted all the CurseTheWeather SBo
> users on this list
> > to know of the problem.
> 
> 
> I'm just curious - any news on this?
> 
> -RW
> 


      

From druiloor at zonnet.nl  Mon Aug 17 06:51:37 2009
From: druiloor at zonnet.nl (Menno Duursma)
Date: Mon, 17 Aug 2009 08:51:37 +0200 (CEST)
Subject: [Slackbuilds-users] SlackBuilds, Package:Lua (fwd)
Message-ID: <alpine.LNX.2.00.0908170851330.1884@pc.desktop>



---------- Forwarded message ----------
Date: Sun, 16 Aug 2009 16:18:22 +0200 (CEST)
From: Menno Duursma <druiloor at zonnet.nl>
To: sylkat <kryzoxy at gmail.com>
Subject: Re: SlackBuilds, Package:Lua



On Sun, 16 Aug 2009, sylkat wrote:

> Hi,
> 
> Im a new spanish slack user, i get your slackbuild "lua", install and i see
> that the post installation script is not correct.
> 
> It create a soft link liblua.so pointing to liblua.so.5.1.4:
> 
> liblua.so -> liblua.so.5.1.4
> 
> And the library installed is liblua-5.1.so then is a invalid link and not
> work in compilation but configure script not detect invalid link!
> 
> I don't know how to report this bug so i email you.
> 
> Regards,

Thanks!

This is fine (although i'd rather someone else would take over maintainership 
of this...) You could sent it to the slackbuild-users at slackbuilds.org list 
too/alwell.

I don't know if anything uses those links, but anyways, a quick patch:
This came about with the 64bit suport i guess, i could submit this but it
may brake 64 (however unlikely) probably a good idee to forward this mail.

Cheers,
-Menno.

--- ../lua.old/lua.SlackBuild   2009-06-18 17:22:08.000000000 +0200
+++ ./lua.SlackBuild    2009-08-16 15:57:52.000000000 +0200
@@ -54,13 +54,14 @@
  sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool

  make
-make install DESTDIR=/$PKG
+make install DESTDIR=$PKG

  # Let's make sure all of the library symlinks correctly exist
  ( cd $PKG/usr/lib$LIBDIRSUFFIX
-  ln -sf liblua.so.${VERSION} liblua.so.5
-  ln -sf liblua.so.${VERSION} liblua.so
-  chmod 0755 liblua.so.${VERSION}
+  # Fix for autotools version
+  ln -sf liblua-5.1.so liblua.so.$VERSION
+  ln -sf liblua-5.1.so liblua.so.5.1
+  ln -sf liblua-5.1.so liblua.so.5
  )

  ( cd $PKG


From rworkman at slackbuilds.org  Mon Aug 17 13:15:51 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 17 Aug 2009 08:15:51 -0500
Subject: [Slackbuilds-users] SlackBuilds, Package:Lua (fwd)
In-Reply-To: <alpine.LNX.2.00.0908170851330.1884@pc.desktop>
References: <alpine.LNX.2.00.0908170851330.1884@pc.desktop>
Message-ID: <20090817081551.0506e121@liberty.rlwhome.lan>

On Mon, 17 Aug 2009 08:51:37 +0200 (CEST)
Menno Duursma <druiloor at zonnet.nl> wrote:

> On Sun, 16 Aug 2009, sylkat wrote:
> 
> > Im a new spanish slack user, i get your slackbuild "lua", install
> > and i see that the post installation script is not correct.
> > 
> > It create a soft link liblua.so pointing to liblua.so.5.1.4:
> > 
> > liblua.so -> liblua.so.5.1.4
> > 
> > And the library installed is liblua-5.1.so then is a invalid link
> > and not work in compilation but configure script not detect invalid
> > link!
>
> 
> This is fine (although i'd rather someone else would take over
> maintainership of this...) You could sent it to the
> slackbuild-users at slackbuilds.org list too/alwell.
> 
> I don't know if anything uses those links, but anyways, a quick patch:
> This came about with the 64bit suport i guess, i could submit this
> but it may brake 64 (however unlikely) probably a good idee to
> forward this mail.
> 
> Cheers,
> -Menno.
> 
> --- ../lua.old/lua.SlackBuild   2009-06-18 17:22:08.000000000 +0200
> +++ ./lua.SlackBuild    2009-08-16 15:57:52.000000000 +0200
> @@ -54,13 +54,14 @@
>   sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g'
> libtool
> 
>   make
> -make install DESTDIR=/$PKG
> +make install DESTDIR=$PKG
> 
>   # Let's make sure all of the library symlinks correctly exist
>   ( cd $PKG/usr/lib$LIBDIRSUFFIX
> -  ln -sf liblua.so.${VERSION} liblua.so.5
> -  ln -sf liblua.so.${VERSION} liblua.so
> -  chmod 0755 liblua.so.${VERSION}
> +  # Fix for autotools version
> +  ln -sf liblua-5.1.so liblua.so.$VERSION
> +  ln -sf liblua-5.1.so liblua.so.5.1
> +  ln -sf liblua-5.1.so liblua.so.5
>   )
> 
>   ( cd $PKG


Hi Menno,

We tweaked the script a bit to make everything build on x86_64
(much thanks to Aaron Hsu for some help with it), and the result
is attached - how's that look?

-RW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lua.tar.gz
Type: application/x-gzip
Size: 2106 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/52f6551e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/52f6551e/attachment.asc>

From druiloor at zonnet.nl  Mon Aug 17 14:14:41 2009
From: druiloor at zonnet.nl (Menno Duursma)
Date: Mon, 17 Aug 2009 16:14:41 +0200 (CEST)
Subject: [Slackbuilds-users] SlackBuilds, Package:Lua (fwd)
In-Reply-To: <20090817081551.0506e121@liberty.rlwhome.lan>
References: <alpine.LNX.2.00.0908170851330.1884@pc.desktop>
	<20090817081551.0506e121@liberty.rlwhome.lan>
Message-ID: <alpine.LNX.2.00.0908171604590.3531@pc.desktop>



On Mon, 17 Aug 2009, Robby Workman wrote:

> We tweaked the script a bit to make everything build on x86_64
> (much thanks to Aaron Hsu for some help with it), and the result
> is attached - how's that look?

Nice one! Tests good. One thing though, in case someone has compiled some
app against the former version, they'll have to create a compatibility
link unless this patch (and unlikely the .so.5.1 will _ever_ be used):

--- lua.tmp/lua.SlackBuild      2009-08-10 01:32:27.000000000 +0200
+++ lua/lua.SlackBuild  2009-08-17 16:02:05.000000000 +0200
@@ -8,7 +8,7 @@

  PRGNAM=lua
  VERSION=5.1.4
-ARCH=${ARCH:-x86_64}
+ARCH=${ARCH:-i486}
  BUILD=${BUILD:-2}
  TAG=${TAG:-_SBo}

@@ -68,7 +68,7 @@
    gcc -shared *.o -o liblua.so.5.1.4
    cp -a liblua.so.5.1.4 $PKG/usr/lib${LIBDIRSUFFIX}
    ( cd $PKG/usr/lib${LIBDIRSUFFIX}
-    ln -s liblua.so.5.1.4 liblua.so.5.1
+    ln -s liblua.so.5.1.4 liblua-5.1.so
      ln -s liblua.so.5.1.4 liblua.so.5
      ln -s liblua.so.5.1.4 liblua.so
    )


From rworkman at slackbuilds.org  Mon Aug 17 14:25:20 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 17 Aug 2009 09:25:20 -0500
Subject: [Slackbuilds-users] SlackBuilds, Package:Lua (fwd)
In-Reply-To: <alpine.LNX.2.00.0908171604590.3531@pc.desktop>
References: <alpine.LNX.2.00.0908170851330.1884@pc.desktop>
	<20090817081551.0506e121@liberty.rlwhome.lan>
	<alpine.LNX.2.00.0908171604590.3531@pc.desktop>
Message-ID: <20090817092520.1e02feeb@liberty.rlwhome.lan>

On Mon, 17 Aug 2009 16:14:41 +0200 (CEST)
Menno Duursma <druiloor at zonnet.nl> wrote:

> On Mon, 17 Aug 2009, Robby Workman wrote:
> 
> > We tweaked the script a bit to make everything build on x86_64
> > (much thanks to Aaron Hsu for some help with it), and the result
> > is attached - how's that look?
> 
> Nice one! Tests good. One thing though, in case someone has compiled
> some app against the former version, they'll have to create a
> compatibility link unless this patch (and unlikely the .so.5.1 will
> _ever_ be used):
> 
> --- lua.tmp/lua.SlackBuild      2009-08-10 01:32:27.000000000 +0200
> +++ lua/lua.SlackBuild  2009-08-17 16:02:05.000000000 +0200
> @@ -8,7 +8,7 @@
> 
>   PRGNAM=lua
>   VERSION=5.1.4
> -ARCH=${ARCH:-x86_64}
> +ARCH=${ARCH:-i486}
>   BUILD=${BUILD:-2}
>   TAG=${TAG:-_SBo}
> 
> @@ -68,7 +68,7 @@
>     gcc -shared *.o -o liblua.so.5.1.4
>     cp -a liblua.so.5.1.4 $PKG/usr/lib${LIBDIRSUFFIX}
>     ( cd $PKG/usr/lib${LIBDIRSUFFIX}
> -    ln -s liblua.so.5.1.4 liblua.so.5.1
> +    ln -s liblua.so.5.1.4 liblua-5.1.so
>       ln -s liblua.so.5.1.4 liblua.so.5
>       ln -s liblua.so.5.1.4 liblua.so
>     )
> 


I'll keep this handy just in case, but I think the easiest
solution is to just rebuild whatever needed that so that it
won't need that link :-)   

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

From spook123 at gmail.com  Wed Aug 19 03:29:55 2009
From: spook123 at gmail.com (Ash)
Date: Wed, 19 Aug 2009 11:29:55 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4e7c15550908182029j770d3575o9ba7b4e7f287fcba@mail.gmail.com>

I've checked dia for both 32 and 64, works fine, but I had to fix the script
for 64.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/d2f2465b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dia.tar.gz
Type: application/x-gzip
Size: 1951 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/d2f2465b/attachment-0001.bin>

From spook123 at gmail.com  Wed Aug 19 04:01:10 2009
From: spook123 at gmail.com (Ash)
Date: Wed, 19 Aug 2009 12:01:10 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4e7c15550908182101l65fa92ccpd9db07ca920aff3c@mail.gmail.com>

system/usbmon is fine without change.
system/usbview is attached, needed the x86_64 ARCH added.

Ash


2009/8/11 Robby Workman <rworkman at slackbuilds.org>

> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>  http://slackbuilds.org/NOT_CHECKED
>
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.
>
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
>
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
>
> -RW
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/d867f1e2/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usbview.tar.gz
Type: application/x-gzip
Size: 1483 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/d867f1e2/attachment.bin>

From vmj at linuxbox.fi  Sun Aug 16 22:13:52 2009
From: vmj at linuxbox.fi (Mikko Varri)
Date: Mon, 17 Aug 2009 01:13:52 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090816221352.GA19810@linuxbox.fi>



> 
> development/zope.testing/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

> 
> development/zope.interface/
> 

Works as is; attachment fixes the slack-desc and removes unused
variables.  Feel free to ignore this attachment and move over the
version that you already have in the repository.

> 
> development/kiwi/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

Attachment also cleans up the README.

> 
> development/gazpacho/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

Changed build number back to 1.

Added a patch that removes unneeded manipulation of PYTHONPATH (which
breaks the package on slackware64).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: zope.testing.tar.gz
Type: application/octet-stream
Size: 1373 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/25285bf0/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zope.interface.tar.gz
Type: application/octet-stream
Size: 1479 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/25285bf0/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kiwi.tar.gz
Type: application/octet-stream
Size: 1634 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/25285bf0/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gazpacho.tar.gz
Type: application/octet-stream
Size: 2196 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/25285bf0/attachment-0007.obj>

From vmj at linuxbox.fi  Mon Aug 17 20:31:25 2009
From: vmj at linuxbox.fi (Mikko Varri)
Date: Mon, 17 Aug 2009 23:31:25 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090817203125.GC19810@linuxbox.fi>



> 
> development/zope.testing/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

> 
> development/zope.interface/
> 

Works as is; attachment fixes the slack-desc and removes unused
variables.  Feel free to ignore this attachment and move over the
version that you already have in the repository.

> 
> development/kiwi/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

Attachment also cleans up the README.

> 
> development/gazpacho/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

Changed build number back to 1.

Added a patch that removes unneeded manipulation of PYTHONPATH (which
breaks the package on slackware64).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: zope.testing.tar.gz
Type: application/octet-stream
Size: 1373 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/e2ddaacb/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zope.interface.tar.gz
Type: application/octet-stream
Size: 1479 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/e2ddaacb/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kiwi.tar.gz
Type: application/octet-stream
Size: 1634 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/e2ddaacb/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gazpacho.tar.gz
Type: application/octet-stream
Size: 2196 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090817/e2ddaacb/attachment-0007.obj>

From vmj at linuxbox.fi  Tue Aug 18 19:24:15 2009
From: vmj at linuxbox.fi (Mikko Varri)
Date: Tue, 18 Aug 2009 22:24:15 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090818192415.GE19810@linuxbox.fi>


Hi,


Here's most of my NOT_CHECKED packages.

> 
> development/zope.testing/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

> 
> development/zope.interface/
> 

Works as is; attachment fixes the slack-desc and removes unused
variables.  Feel free to ignore this attachment and move over the
version that you already have in the repository.

> 
> development/kiwi/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

Attachment also cleans up the README.

> 
> development/gazpacho/
> 

Changed hardcoded "noarch" to ${ARCH:-i486}.

Changed build number back to 1.

Added a patch that removes unneeded manipulation of PYTHONPATH (which
breaks the package on slackware64).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: zope.testing.tar.gz
Type: application/octet-stream
Size: 1373 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090818/679e289b/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zope.interface.tar.gz
Type: application/octet-stream
Size: 1479 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090818/679e289b/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kiwi.tar.gz
Type: application/octet-stream
Size: 1634 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090818/679e289b/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gazpacho.tar.gz
Type: application/octet-stream
Size: 2196 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090818/679e289b/attachment-0003.obj>

From vmj at linuxbox.fi  Wed Aug 19 08:52:11 2009
From: vmj at linuxbox.fi (Mikko Varri)
Date: Wed, 19 Aug 2009 11:52:11 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090816221352.GA19810@linuxbox.fi>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090816221352.GA19810@linuxbox.fi>
Message-ID: <20090819085211.GA29906@linuxbox.fi>

Sorry everyone for the duplicates of the below message.  IP-address
changes at my end didn't go smoothly.  Completely my fault. :)

-vmj



On Mon, Aug 17, 2009 at 01:13:52AM +0300, Mikko Varri wrote:
> 
> 
> > 
> > development/zope.testing/
> > 
> 
> Changed hardcoded "noarch" to ${ARCH:-i486}.
> 
> > 
> > development/zope.interface/
> > 
> 
> Works as is; attachment fixes the slack-desc and removes unused
> variables.  Feel free to ignore this attachment and move over the
> version that you already have in the repository.
> 
> > 
> > development/kiwi/
> > 
> 
> Changed hardcoded "noarch" to ${ARCH:-i486}.
> 
> Attachment also cleans up the README.
> 
> > 
> > development/gazpacho/
> > 
> 
> Changed hardcoded "noarch" to ${ARCH:-i486}.
> 
> Changed build number back to 1.
> 
> Added a patch that removes unneeded manipulation of PYTHONPATH (which
> breaks the package on slackware64).
> 





> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 


From spook123 at gmail.com  Wed Aug 19 11:20:48 2009
From: spook123 at gmail.com (Ash)
Date: Wed, 19 Aug 2009 19:20:48 +0800
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <4e7c15550908190420j114eb55au1bd8fe91c76dc4ee@mail.gmail.com>

system/xosd is attached, tested both 32 and 64.
system/worker works fine without any changes. tested both arch.

Ash


2009/8/11 Robby Workman <rworkman at slackbuilds.org>

> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>  http://slackbuilds.org/NOT_CHECKED
>
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.
>
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
>
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).
>
> -RW
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/6af4e173/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xosd.tar.gz
Type: application/x-gzip
Size: 1665 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/6af4e173/attachment.bin>

From rworkman at slackbuilds.org  Wed Aug 19 13:28:05 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 19 Aug 2009 08:28:05 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090818192415.GE19810@linuxbox.fi>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090818192415.GE19810@linuxbox.fi>
Message-ID: <20090819082805.0eb8a330@liberty.rlwhome.lan>

On Tue, 18 Aug 2009 22:24:15 +0300
Mikko Varri <vmj at linuxbox.fi> wrote:

> > development/zope.testing/
> Changed hardcoded "noarch" to ${ARCH:-i486}.
> 
> > development/zope.interface/
> Works as is; attachment fixes the slack-desc and removes unused
> variables.  Feel free to ignore this attachment and move over the
> version that you already have in the repository.
> 
> > development/kiwi/
> Changed hardcoded "noarch" to ${ARCH:-i486}.
> Attachment also cleans up the README.
> 
> > development/gazpacho/
> Changed hardcoded "noarch" to ${ARCH:-i486}.
> Changed build number back to 1.
> Added a patch that removes unneeded manipulation of PYTHONPATH (which
> breaks the package on slackware64).


All added; thanks!

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

From rworkman at slackbuilds.org  Wed Aug 19 13:49:01 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 19 Aug 2009 08:49:01 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4e7c15550908182029j770d3575o9ba7b4e7f287fcba@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4e7c15550908182029j770d3575o9ba7b4e7f287fcba@mail.gmail.com>
Message-ID: <20090819084901.5d73f157@liberty.rlwhome.lan>

On Wed, 19 Aug 2009 11:29:55 +0800
Ash <spook123 at gmail.com> wrote:

> I've checked dia for both 32 and 64, works fine, but I had to fix the
> script for 64.


Added ; thanks!

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

From rworkman at slackbuilds.org  Wed Aug 19 13:54:35 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 19 Aug 2009 08:54:35 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4e7c15550908182101l65fa92ccpd9db07ca920aff3c@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4e7c15550908182101l65fa92ccpd9db07ca920aff3c@mail.gmail.com>
Message-ID: <20090819085435.4711a850@liberty.rlwhome.lan>

On Wed, 19 Aug 2009 12:01:10 +0800
Ash <spook123 at gmail.com> wrote:

> system/usbmon is fine without change.
> system/usbview is attached, needed the x86_64 ARCH added.


Both added; thanks!

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

From rworkman at slackbuilds.org  Wed Aug 19 14:05:55 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 19 Aug 2009 09:05:55 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4e7c15550908190420j114eb55au1bd8fe91c76dc4ee@mail.gmail.com>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<4e7c15550908190420j114eb55au1bd8fe91c76dc4ee@mail.gmail.com>
Message-ID: <20090819090555.47fff968@liberty.rlwhome.lan>

On Wed, 19 Aug 2009 19:20:48 +0800
Ash <spook123 at gmail.com> wrote:

> system/xosd is attached, tested both 32 and 64.
> system/worker works fine without any changes. tested both arch.


Added with some minor cleanups; thanks!

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

From audrius at neutrino.lt  Wed Aug 19 17:27:37 2009
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Wed, 19 Aug 2009 20:27:37 +0300
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <20090819172737.GA15398@kiras.skynet.lt>

On Mon, 2009-08-10 at 14:55:39 -0500, Robby Workman wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED
> 
> If you maintain one of these and would like to see it in the initial
> repo for 13.0, or if you use one of them and would like to "step up"
> and handle any needed changes, now is your chance.  I can't promise
> that we'll be able to merge in all of the changes we get, even if
> they are fixed, but we'll do our best.  
> 
> As things are merged into the 13.0 repo (which is still private,
> and will be until 13.0 is released), we'll update the listing above,
> so be sure to refresh that before replying.
> 
> Fixes should come in as replies to this mail, with a complete tarball
> attached (just as if you were submitting it on the website - no source
> code of the app should be included).

development/python3:
  I'm going to update this for freshly released version 3.1.1 and solve
  some issues (like /usr/bin/2to3 overwriting the one from Python
  2.6.2), so it should be removed for now.
office/fbreader:
  I can't test this on x86_64, but it seems to work fine on i486, the
  only change needed is to set UI to qt4 in the SlackBuild.  I'm also
  abandoning this with libraries/liblinebreak, if anybody's interested,
  feel free to take them over.
system/spambayes:
  Changed ARCH from noarch to ${ARCH:-i486}, otherwise works fine as is
  on -current.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spambayes.tar.gz
Type: application/x-tar-gz
Size: 1532 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/6eecebf5/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090819/6eecebf5/attachment.sig>

From druiloor at zonnet.nl  Wed Aug 19 22:55:34 2009
From: druiloor at zonnet.nl (Menno Duursma)
Date: Thu, 20 Aug 2009 00:55:34 +0200 (CEST)
Subject: [Slackbuilds-users] HAR and ntpd, named and libcap-ng
Message-ID: <alpine.LNX.2.00.0908200020010.20251@pc.desktop>


Hello list readers,

About a talk at HAR2009, of which the outline can be found here:
http://druiloor.punt.nl/?id=469116

(Sunny wether: didn't go to well, shit happens, yada yada yada).

Anyways besides my own stuff i used ntpd and named as examples. Of which
the first can be linked against libcap, as described by slackamp here:
http://www.linuxquestions.org/questions/slackware-14/run-ntpd-as-non-root-617019/

(Or last i tried, at least).

BIND named can be started with '-u <user>' as described in its rc file.
One thing not to overlook might be group access to /etc/rndc.key there.

Otherwise chroot them . Or maybe wrap 'm. PAM and redesign roots access
rights, whatever. Unless u trust those daemons to never have a 0-day.

One thing libcap-ng can be used for is to easily check for cap-bits set
on running processes (a build-script for that package is attached).

Looking up the filesystem bits maybe a bit harder, cfengine/puppet/etc
should be able to support it (probably with external scripts currently).

Besides libcap-ng, some interesting stuff is available here:
http://www.friedhoff.org/downloads.html

(Note capable_probe.tar.bz2 needs kernel probes enabled).

Hope this helps, take care,
-Menno.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libcap-ng.tar.gz
Type: application/octet-stream
Size: 1842 bytes
Desc: 
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090820/546783d2/attachment.obj>

From rworkman at slackbuilds.org  Thu Aug 20 03:40:56 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 19 Aug 2009 22:40:56 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090819172737.GA15398@kiras.skynet.lt>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<20090819172737.GA15398@kiras.skynet.lt>
Message-ID: <20090819224056.28834bf5@liberty.rlwhome.lan>

On Wed, 19 Aug 2009 20:27:37 +0300
Audrius Ka?ukauskas <audrius at neutrino.lt> wrote:

> development/python3:
>   I'm going to update this for freshly released version 3.1.1 and
> solve some issues (like /usr/bin/2to3 overwriting the one from Python
>   2.6.2), so it should be removed for now.
> office/fbreader:
>   I can't test this on x86_64, but it seems to work fine on i486, the
>   only change needed is to set UI to qt4 in the SlackBuild.  I'm also
>   abandoning this with libraries/liblinebreak, if anybody's
> interested, feel free to take them over.
> system/spambayes:
>   Changed ARCH from noarch to ${ARCH:-i486}, otherwise works fine as
> is on -current.


Noted and added/removed as appropriate; thanks!

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

From chris.abela at maltats.com  Thu Aug 20 10:28:16 2009
From: chris.abela at maltats.com (Chris Abela)
Date: Thu, 20 Aug 2009 12:28:16 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0 dump.SlackBuild
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <E1Me4sY-0007EY-45@fender51.maltanet.net>

Hi,

A dump.SlackBuild user has notified me about an insidious bug in the script.
Moreover I noted that a new dump version was released and the old link for
the source code was moved.

The attached SlackBuild is attached for your consideration. I tested this
application as much as I could and it looks fine here.

Chris Abela

-----Original Message-----
From: slackbuilds-users-bounces at slackbuilds.org
[mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Robby
Workman
Sent: 10 August 2009 21:56
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] Unchecked entries for 13.0

As I promised several people privately, here's a list of things that we
have not had time to check/update for 13.0 yet:
  http://slackbuilds.org/NOT_CHECKED

If you maintain one of these and would like to see it in the initial
repo for 13.0, or if you use one of them and would like to "step up"
and handle any needed changes, now is your chance.  I can't promise
that we'll be able to merge in all of the changes we get, even if
they are fixed, but we'll do our best.  

As things are merged into the 13.0 repo (which is still private,
and will be until 13.0 is released), we'll update the listing above,
so be sure to refresh that before replying.

Fixes should come in as replies to this mail, with a complete tarball
attached (just as if you were submitting it on the website - no source
code of the app should be included).

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump.tar.gz
Type: application/x-gzip
Size: 2341 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090820/586b4321/attachment.bin>

From chris.abela at maltats.com  Thu Aug 20 14:21:13 2009
From: chris.abela at maltats.com (Chris Abela)
Date: Thu, 20 Aug 2009 16:21:13 +0200
Subject: [Slackbuilds-users] Unchecked entries for 13.0 dump.SlackBuild
Message-ID: <E1Me8Vy-0008Ef-Hi@fender51.maltanet.net>

Hi,

Please note that this SlackBuild was meant only for Slackware 12.2

I still need to test it on Slackware 13 as I do have a current install.
Moreover it is failing on kongoni64 Live CD.

Chris

-----Original Message-----
From: Chris Abela [mailto:chris.abela at maltats.com] 
Sent: 20 August 2009 12:28
To: 'SlackBuilds.org Users List'
Subject: RE: [Slackbuilds-users] Unchecked entries for 13.0 dump.SlackBuild

Hi,

A dump.SlackBuild user has notified me about an insidious bug in the script.
Moreover I noted that a new dump version was released and the old link for
the source code was moved.

The attached SlackBuild is attached for your consideration. I tested this
application as much as I could and it looks fine here.

Chris Abela

-----Original Message-----
From: slackbuilds-users-bounces at slackbuilds.org
[mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Robby
Workman
Sent: 10 August 2009 21:56
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] Unchecked entries for 13.0

As I promised several people privately, here's a list of things that we
have not had time to check/update for 13.0 yet:
  http://slackbuilds.org/NOT_CHECKED

If you maintain one of these and would like to see it in the initial
repo for 13.0, or if you use one of them and would like to "step up"
and handle any needed changes, now is your chance.  I can't promise
that we'll be able to merge in all of the changes we get, even if
they are fixed, but we'll do our best.  

As things are merged into the 13.0 repo (which is still private,
and will be until 13.0 is released), we'll update the listing above,
so be sure to refresh that before replying.

Fixes should come in as replies to this mail, with a complete tarball
attached (just as if you were submitting it on the website - no source
code of the app should be included).

-RW


From mfilpot at gmail.com  Thu Aug 20 18:01:39 2009
From: mfilpot at gmail.com (Matthew Fillpot)
Date: Thu, 20 Aug 2009 14:01:39 -0400
Subject: [Slackbuilds-users] Unchecked entries for 13.0
Message-ID: <3d32cb0a0908201101p5fc5a5bgc680d8883fb924db@mail.gmail.com>

I do not see yakuake or Urban Terror on the Unchecked Entries list.

Do we have a new build of yakuake that works on KDE4 and QT4, or is this an
orphaned package looking for a new maintainer? I have a well tested script
to build yakuake with kmake and the modified dependencies that is ready for
submission if necessary.

The UrbanTerror build script needs modified to reference the updated libcurl
libraries, without the update the users are unable to download maps from
game servers. I will be submitting the updated archive later today.

-- 
Thank You,
Matthew Fillpot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090820/8185e424/attachment.htm>

From carlos at strangeworlds.co.uk  Sun Aug 23 10:20:47 2009
From: carlos at strangeworlds.co.uk (Carlos Corbacho)
Date: Sun, 23 Aug 2009 11:20:47 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <200908231120.47528.carlos@strangeworlds.co.uk>

On Monday 10 August 2009 20:55:39 Robby Workman wrote:
> As I promised several people privately, here's a list of things that we
> have not had time to check/update for 13.0 yet:
>   http://slackbuilds.org/NOT_CHECKED

development/django/
development/stgit/

Work fine here on Slackware64. (Given they're both pure Python packages, I'd 
be surprised if they doesn't work on i486, but I can't test that).

Also, there was some discussion recently about the architecture that should be 
set for Python packages - was an official decision reached? I couldn't find 
anything on the SBo site.

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

From carlos at strangeworlds.co.uk  Sun Aug 23 21:11:28 2009
From: carlos at strangeworlds.co.uk (Carlos Corbacho)
Date: Sun, 23 Aug 2009 22:11:28 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <200908231120.47528.carlos@strangeworlds.co.uk>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<200908231120.47528.carlos@strangeworlds.co.uk>
Message-ID: <200908232211.28608.carlos@strangeworlds.co.uk>

On Sunday 23 August 2009 11:20:47 Carlos Corbacho wrote:
> On Monday 10 August 2009 20:55:39 Robby Workman wrote:
> > As I promised several people privately, here's a list of things that we
> > have not had time to check/update for 13.0 yet:
> >   http://slackbuilds.org/NOT_CHECKED
>
> development/django/
> development/stgit/
>
> Work fine here on Slackware64. (Given they're both pure Python packages,
> I'd be surprised if they doesn't work on i486, but I can't test that).
>
> Also, there was some discussion recently about the architecture that should
> be set for Python packages - was an official decision reached? I couldn't
> find anything on the SBo site.

I've just e-mailed Daniel de Kok about taking over maintainership of the 
Django package, and he's agreed, so can you update the maintainer details for 
it as well?

However, he's now no longer using Slackware these days, so the rest of his 
packages are up for grabs. The remainer are (from grepping 12.2 for his e-mail 
address):

./desktop/matchbox-desktop/
./desktop/matchbox-panel/
./desktop/matchbox-window-manager/
./development/flup/
./development/pil/
./development/psycopg2/
./games/defcon/
./graphics/grap/
./libraries/libmatchbox/
./misc/matchbox-common/

(I'm happy to take over psycopg2 if no-one else is interested, but I don't 
have any interest in Matchbox or the other bits on that list).

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

From seanm at seanm.ca  Sun Aug 23 22:16:46 2009
From: seanm at seanm.ca (Sean MacLennan)
Date: Sun, 23 Aug 2009 18:16:46 -0400
Subject: [Slackbuilds-users] XEmacs SlackBuild
Message-ID: <20090823181646.38cd10a0@lappy.seanm.ca>

I have an XEmacs Slackbuild file I have started modifying to more
closely fit the slackbuilds format. I hope it is ok to ask questions
here about the SlackBuild file. If not, ignore this email ;)

The file is at the bottom of the email. Please be kind, this files is
many years old and predates the SlackBuild file when the files where
all called make-slack.

1) First off, there are three patches. One of the patches just gets
shifted function keys working. This patch could very easily be mapped
out for the slackbuilds case, but I have used this patch for years with
no problems.

The other two patches allow you to build an XEmacs package while XEmacs
is installed. I could leave out the two patches, but you would have to
uninstall XEmacs to build a new XEmacs package.

2) A second problem is that I require two XEmacs packages to build the
Slackware package. These packages are required to use the XEmacs
package system. Yes, you need some packages to get the package system
going to download packages :( Adding them to the Slackware package made
sense for personal use and for Linuxpackages. I am not sure it is a
good idea to require them for the slackbuilds case since the versions
are hardcoded.

3) The website made it clear you have to set the SLKCFLAGS. I really
think this is a bad idea for XEmacs. I have a comment in the SlackBuild
file about this. How hard a requirement is this?

Cheers,
   Sean

#!/bin/sh
# Slackware build script for XEmacs
# Created by Sean MacLennan <xemacs at seanm.ca>

CWD=`pwd`

DO_UNTAR=1
DO_BUILD=1
DO_SLACKBUILDS=1

VERSION=21.4.22
BASE_VERSION=2.19
EFS_VERSION=1.34
ARCH=${ARCH:-i486}
BUILD=${BUILD:-2}

if [ $DO_SLACKBUILDS -eq 1 ] ; then
TMP=${TMP:-/tmp/SBo}
TAG=${TAG:-_SBo}
OUTPUT=${OUTPUT:-/tmp}

# This is required for slackbuilds. I recommend turning this off since
# XEmacs quite often needs to be built at specific optimization
# levels. You are much better off trusting the XEmacs Makefile ;)
#
# That said, with Slackware 12.2 a quick sanity check of the xemacs
# with the i486 options worked.
#
# To turn it off, change the true below to false
if true; then
if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
   SLKCFLAGS="-O2 -march=i686 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
fi
fi

else
TMP=${TMP:-/tmp}
TAG=${TAG:-sam}
OUTPUT=$TMP
fi

#DATADIR=usr/share
DATADIR=usr/lib

# Let's be nice and warn upfront if things are missing
ok=1
for f in xemacs-$VERSION.tar.bz2 \
	xemacs-base-$BASE_VERSION-pkg.tar.gz \
	efs-$EFS_VERSION-pkg.tar.gz \
	check-features.patch \
	dump-paths.patch \
	mod-shift.patch ; do
    [ -f ./$f ] || { echo "$f missing"; ok=0; }
done
[ $ok = 1 ] || exit 2

PKG=$TMP/package-xemacs
rm -rf $PKG
mkdir -p $TMP $OUPUT $PKG || exit 1

cd $TMP
if [ $DO_UNTAR -eq 1 ] ; then
    rm -rf xemacs-$VERSION
    tar xjf $CWD/xemacs-$VERSION.tar.bz2 || exit 1

    cd xemacs-$VERSION

    # These patches allow building xemacs with xemacs installed
    # dump-paths patch from Enrico Scholz
    patch -p1 < $CWD/dump-paths.patch || exit 1
    patch -p1 < $CWD/check-features.patch || exit 1

    # Obsolete in Xorg 6.9.0
    patch -p1 < $CWD/mod-shift.patch || exit 1
else
    cd xemacs-$VERSION || exit 1
    echo "Skipping untar...."
fi

if [ $DO_BUILD -eq 1 ] ; then
    if [ -n "$SLKCFLAGS" ] ; then
    CFLAGS="$SLKCFLAGS" ./configure \
		--prefix=/usr \
		--datadir=/$DATADIR \
		--with-sound=none \
		--with-file-coding \
		$ARCH-slackware-linux || exit 1
    else
    ./configure \
		--prefix=/usr \
		--datadir=/$DATADIR \
		--with-sound=none \
		--with-file-coding \
		$ARCH-slackware-linux || exit 1
    fi

    make || exit 1
else
    echo "Skipping build...."
fi


make prefix=$PKG/usr datadir=$PKG/$DATADIR install || exit 1
#make prefix=$PKG/usr datadir=$PKG/$DATADIR gzip-el

(   # Add minimal packages to allow package tools to work
    mkdir -p $PKG/$DATADIR/xemacs/xemacs-packages
    cd $PKG/$DATADIR/xemacs/xemacs-packages
    tar zxf $CWD/xemacs-base-$BASE_VERSION-pkg.tar.gz || exit 1
    tar zxf $CWD/efs-$EFS_VERSION-pkg.tar.gz || exit 1
    # Make sure the .elc files are newer
    find . -name \*.elc -exec touch {} \;
)

# What is this 2.3M for?????
rm -rf $PKG/usr/lib/xemacs-$VERSION/$ARCH-slackware-linux/include

strip_bins () {
    for f in $1/*; do
        if file $f | fgrep -q "not stripped" ; then
	    strip $f
        fi
    done
}

strip_bins $PKG/usr/bin
strip_bins $PKG/usr/lib/xemacs-$VERSION/$ARCH-slackware-linux

gzip $PKG/usr/man/*/*

# Some documentation
mkdir -p $PKG/usr/doc/xemacs-$VERSION
cp BUGS CHANGES-release COPYING ChangeLog \
    Installation PROBLEMS README README.packages \
    $PKG/usr/doc/xemacs-$VERSION

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

# For lp.n
chown -R root.root $PKG
#chown -R root.bin $PKG/usr/bin

cat <<EOF >$PKG/install/doinst.sh
#!/bin/sh

# Make sure the elc files are newer than the el files
touch $DATADIR/xemacs-$VERSION/lisp/*.elc
touch $DATADIR/xemacs-$VERSION/lisp/*/*.elc
touch $DATADIR/xemacs/xemacs-packages/lisp/xemacs-base/*.elc
touch $DATADIR/xemacs/xemacs-packages/lisp/efs/*.elc

EOF

# And add the slackbuild
install -D -m664 $CWD/xemacs.SlackBuild
$PKG/usr/src/slackbuilds/xemacs.SlackBuild

########################################################################

cd $PKG

if [ $DATADIR = "usr/share" ] ; then
  ( cd usr/bin
    XBIN=../share/xemacs-$VERSION/bin
    mkdir -p $XBIN || exit 1
    mv xemacs-$VERSION xemacs*.dmp $XBIN || exit 1
    rm xemacs
    ln -s $XBIN/xemacs-$VERSION xemacs
  ) || exit 3
fi

########################################################################
# Split out info package
rm -rf $PKG-info
INFODIR=$DATADIR/xemacs-$VERSION/info
mkdir -p $PKG-info/$INFODIR
mkdir -p $PKG-info/install
cat $CWD/slack-desc-info > $PKG-info/install/slack-desc

mv $INFODIR/* $PKG-info/$INFODIR
gzip $PKG-info/$INFODIR/*

# DO NOT gzip the dir file - it screws up XEmacs
gunzip $PKG-info/$INFODIR/dir.gz

########################################################################
# Split out lisp package
rm -rf $PKG-lisp
LISPDIR=$DATADIR/xemacs-$VERSION/lisp
mkdir -p $PKG-lisp/$LISPDIR
mkdir -p $PKG-lisp/install
cat $CWD/slack-desc-lisp > $PKG-lisp/install/slack-desc

# Taken from gzip-el.sh in lib-src dir
find "$LISPDIR" -type f -name "*.el" -print |
    while read file; do
	if [ -s "${file}c" ] ; then
	    install -D -m 644 "$file" "$PKG-lisp/$file"
	    rm "$file"
	fi
    done

cat <<EOF >$PKG-lisp/install/doinst.sh
#!/bin/sh

# Make sure the .elc files are newer
find $LISPDIR -name \*.elc -exec touch {} \;
EOF

########################################################################
# Split out misc package
rm -rf $PKG-misc
ETCDIR=$DATADIR/xemacs-$VERSION/etc
mkdir -p $PKG-misc/$ETCDIR
mkdir -p $PKG-misc/install
cat $CWD/slack-desc-misc > $PKG-misc/install/slack-desc

cp -a $ETCDIR/photos $PKG-misc/$ETCDIR
rm -rf $ETCDIR/photos

cp -a $ETCDIR/sparcworks $PKG-misc/$ETCDIR
rm -rf $ETCDIR/sparcworks

cp -a $ETCDIR/tests $PKG-misc/$ETCDIR
rm -rf $ETCDIR/tests

for f in $ETCDIR/* ; do
    [ -f $f ] && mv $f $PKG-misc/$ETCDIR
done

# This is required - put it back
mv $PKG-misc/$ETCDIR/package-index.LATEST.gpg $PKG/$ETCDIR

########################################################################
# Build the packages

cd $PKG
makepkg -l y -c n $OUTPUT/xemacs-$VERSION-$ARCH-$BUILD$TAG.tgz
cd $PKG-info
makepkg -l n -c n $OUTPUT/xemacs-info-$VERSION-noarch-$BUILD$TAG.tgz
cd $PKG-lisp
makepkg -l n -c n $OUTPUT/xemacs-lisp-$VERSION-noarch-$BUILD$TAG.tgz
cd $PKG-misc
makepkg -l n -c n $OUTPUT/xemacs-misc-$VERSION-noarch-$BUILD$TAG.tgz

# Clean up the extra stuff:
if [ "$1" = "--cleanup" ]; then
  rm -rf $TMP/xemacs-${VERSION}
  rm -rf $PKG $PKG-info $PKG-lisp $PKG-misc
fi

From chess at chessgriffin.com  Mon Aug 24 20:12:00 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 24 Aug 2009 16:12:00 -0400
Subject: [Slackbuilds-users] Sbopkg 0.30.0 Released
Message-ID: <20090824201200.GB14924@localhost>

Howdy folks!

Based on the Slackware-current ChangeLog, it seems that a release of
Slackware 13.0 is very near.  To celebrate this event, and to let folks
get their proverbial ducks in a row when it comes to upgrading or
installing, we would like to announce the final release of sbopkg
version 0.30.0!  This update has been many months in the making, and
contains many new features, enhancements, and bug-fixes.  Please note
that this is a *major* upgrade, and will probably require most folks to
substantially modify their existing sbopkg.conf (or, more likely, use
the sbopkg.conf.new) as well as potentially move or modify their local
rsync'd SlackBuilds.org repository.  Furthermore, sbopkg 0.27.4 and
prior installed to /usr/bin and the new sbopkg 0.30.0 installs to
/usr/sbin.  As a result, we strongly recommend removing any prior
versions of sbopkg before doing a fresh install of version 0.30.0.  Also
note that with this release, the sbopkg 0.27.x branch will no longer be
maintained.

This new version of sbopkg has lots of great cleanups, security
improvements, and new features.  Here is a short, edited list of just
some of the items in the ChangeLog:

* Move sbopkg to /usr/sbin; remove code related to user-mode support;
  sbopkg must now be run as root in all cases.
* Apply a major code cleanup that touches just about every part of
  sbopkg.
* Implement configurable repository support by introducing a new
  /etc/sbopkg/repos.d directory where separate repositories files can
  be maintained and also by adding support for git-based repositories.
  The Slamd64Builds repository is now listed, to the joy of all the
  Slamd64 users out there.
* Add support for new *.txz, *.tlz, and *.tbz Slackware package
  extensions.
* Require build queuefiles have a '.sqf' file extension and change
  queuefile format.  No longer will the queuefile format be 'APP VERSION
  ON/OFF' but instead will simply be one 'APP' per line.  If a user
  wants an APP to be deselected in the dialog menus, simply put a '-' in
  front of it, e.g. '-APP'.  This should make creating, using, and
  sharing queuefiles much easier and more intuitive.  Add ability to
  have recursive queuefiles, so one queuefile named "foo.sqf" may have
  an entry "@bar" in which case as the foo.sqf queuefile is parsed, it
  will recursively go down into the 'bar.sqf' queuefile as well.  The
  '@' symbol is used in front of an entry in a queuefile to denote
  another queuefile.
* Add ability to load more than one queuefile at a time when building
  from command line interface.
* Add several new functions related to checking GPG-signed tarballs,
  such as those that SlackBuilds.org provides.
* Add ability to dump all installed packages into a build queue.
* Add ability to pass build options in a queuefile when separated by
  a pipe character, i.e. app | FOO=yes BAR=no
* Add support for Slackware 64 by a 'uname -m' test for x86_64 and
  if true, set ARCH to x86_64.
* Add option to retry a failed build.
* Add CLEANUP configuration variable, which when set to YES tells
  sbopkg to delete the extracted sources, and all the associated
  "residuals" of the build, as soon as the build is finished.
* Add a function to delete obsolete (not installed) packages from
  $OUTPUT.
* Add dialog notification of whether a queued package is installed.
* Add a dialog option to automatically uncheck installed packages
  from the active queue, together with a command line option -k that
  automatically skips such packages when building with -b or -i.
* Add ability to 'invert' all selected/deselected in the clear cache
  and obsolete sources and packages dialogs.
* Numerous other user interface improvements.

The full ChangeLog.txt can be viewed here:

http://www.sbopkg.org/docs/ChangeLog.txt

The result of this work is that both the sbopkg.conf and the directory
layout for the local rsync copy of the SBo tree has changed fairly
significantly.  It might be possible to copy your current SBo tree from
the old default of /home/sbo/12.2 (for example) to the new default of
/var/lib/sbopkg/SBo/12.2 but it might just be easier to let sbopkg make
the new directories and perform a fresh rsync.  Please make a backup of
your local rsync copy and sbopkg.conf if you have made any changes to
them.

We highly recommend that everyone read the new sbopkg.conf file and the
corresponding man page sbopkg.conf(5) -- as well as the main sbopkg(8)
man page -- to understand the changes.  Also, please be sure to look at
the documentation in the doc/ directory.  There are documents in there
that explain how the queuefiles work and how the new
/etc/sbopkg/renames.d and /etc/sbopkg/repos.d directories function.
There are many significant changes as compared to sbopkg 0.27.x.
Additionally, while sbopkg 0.30.0 may work fine on Slackware 12.2 and
below, it is primarily intended to be used on Slackware 13.0.  In fact,
Slackware 13.0 is now set as the default Slackware version in
anticipation of the new release.  You can change it back to 12.2 if you
wish in the sbopkg.conf file.

As you can probably tell, the new queuefile structure underwent a major
overhaul, that we think makes the queuefiles much more convenient to
use.  Several sample queuefiles are provided in the doc/ directory, and
others (including user-submitted queuefiles) can be found at the
sbopkg.org website:  http://www.sbopkg.org/queues/13.0 -- please feel
free to contribute more.

A package and source tarball for sbopkg 0.30.0 can be found at the
sbopkg project website:

http://www.sbopkg.org

Finally, I would like to thank my two co-developers, Mauro Giachero and
slakmagik.  Their assistance, advice, and code contributions have been
invaluable.  I would also like to thank the many users who tested,
provided feedback, posted bug reports, or requested enchancements.  We
tried to keep track of everyone and provide proper credit in the
ChangeLog.txt.  If we failed to mention someone, please let us know and
we will correct the omission.  Everyone's contributions have been
extremely helpful and we have greatly appreciated the feedback.

Thanks and enjoy!

-- 
Chess Griffin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090824/b91ca94b/attachment.sig>

From grbzks at xsmail.com  Tue Aug 25 06:23:44 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Tue, 25 Aug 2009 09:23:44 +0300
Subject: [Slackbuilds-users] info files on submitted packages
Message-ID: <1251181424.18017.1331471259@webmail.messagingengine.com>

It has come to my attention that the sumbitted scripts for packages that
install
info files in /usr/info, common mostly in GNU tools, but not limited to
those
don't add entries to the /usr/info/dir file which makes autocompletion
fail.

AFAIK Pat ships a custom dir file making sure that the entries there
reflect the
packages part of Slackware. But if you install others the dir file isn't
updated,
at least not for the ones i've checked available on SBo.
I don't know what other implications this has, since i don't use the
info files much.
But i have 3 packages installing one, msmtp, gtypist & ratpoison, &
autocompletion
fails for them all.

To deal with this there could be something like the following in
doinst.sh:

install-info /usr/info/$package.info $/usr/info/dir 2> /dev/null

that adds the entry to the dir file. Most tools in SBo don't have
multiple info files
like it happens for example with a2ps in Slackware.

Of course that entry will stay there even if the custom installed
package is
unistalled. It would need something like
install-info --delete /usr/info/$package.info $/usr/info/dir 2>
/dev/null
but Slackware doesnt have a way to do that automatically upon package
removal.

Maybe it would be worth adding an entry to the doinst.sh in the
template.SlackBuild?
Thoughts?

Greg

From marco.bonetti at slackware.it  Tue Aug 25 15:42:12 2009
From: marco.bonetti at slackware.it (Marco Bonetti)
Date: Tue, 25 Aug 2009 17:42:12 +0200 (CEST)
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090810145539.0d92fe91@liberty.rlwhome.lan>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
Message-ID: <45193.88.149.157.90.1251214932.squirrel@webmail.slackware.it>

Hello all,
sorry for the delay but you hit me while on vacation ;-)
here's an initial list of stuff, more packages to follow as I fix/upgrade
them, I don't have a 13.0 yet nor a 64bit system. I'll try to be on one of
them as soon as possible, though.

+ SocksiPy: it uses the python packages building system, I just add a
setup.py as it lacks one so it should be ok
+ hping3: looks ok to me
+ mozilla-prism: this is 32bit only binary repackage. I could try with a
source build but this option has very low priority right now ;-)
+ w3af: noarch package installed into /opt, it's ok.

ciao!

-- 
Marco Bonetti
BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/

My GnuPG key id: 0x86A91047


From adamsonj at email.unc.edu  Tue Aug 25 17:42:47 2009
From: adamsonj at email.unc.edu (Joel J. Adamson)
Date: Tue, 25 Aug 2009 13:42:47 -0400
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <1251181424.18017.1331471259@webmail.messagingengine.com>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
Message-ID: <27806.1251222167@chondestes.bio.unc.edu>

> To deal with this there could be something like the following in
> doinst.sh:
> 
> install-info /usr/info/$package.info $/usr/info/dir 2> /dev/null
> 
> that adds the entry to the dir file. Most tools in SBo don't have
> multiple info files
> like it happens for example with a2ps in Slackware.

I have thought we should have this for a long time, and I include one in
the doinst.sh for my Emacs-CVS SlackBuild, but I've never had problems
with including new info files from SlackBuilds.  I have no explanation
for how the new entries get there, however ;)

Joel

-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090825/72eced38/attachment.sig>

From adamsonj at email.unc.edu  Tue Aug 25 17:47:40 2009
From: adamsonj at email.unc.edu (Joel J. Adamson)
Date: Tue, 25 Aug 2009 13:47:40 -0400
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <27806.1251222167@chondestes.bio.unc.edu>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
	<27806.1251222167@chondestes.bio.unc.edu>
Message-ID: <28164.1251222460@chondestes.bio.unc.edu>

> I have thought we should have this for a long time, and I include one in
> the doinst.sh for my Emacs-CVS SlackBuild, but I've never had problems
> with including new info files from SlackBuilds.  I have no explanation
> for how the new entries get there, however ;)

Whoops, I have my explanation: I do this with each install:

,----
| cd /usr/share/info
| for file in *
| do
|     install-info $file dir
| done
`----

I should do something more package-specific.

Joel
-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090825/e7ad273f/attachment.sig>

From vhann3000 at gmail.com  Wed Aug 26 15:47:22 2009
From: vhann3000 at gmail.com (Oli D)
Date: Wed, 26 Aug 2009 11:47:22 -0400
Subject: [Slackbuilds-users] [Slackware 12.1] Audacity Slackbuild page -
	unlisted dependencies
Message-ID: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>

Hi,

I just built and installed audacity from SlackBuilds:
http://slackbuilds.org/repository/12.1/audio/audacity/

The problem here is the SlackBuilds page only list "wxPython or wxGTK
and libsoundfile" as dependencies
for the audacity SlackBuilds.

I installed a fair amount of packages before this SlackBuild would
actually compile and I don't remember each
of them, but I do know for sure that the following is needed:
raptor: http://slackbuilds.org/repository/12.1/libraries/raptor/

Maybe this will be useful to someone.

Regards,
Olivier Diotte

From chess at chessgriffin.com  Wed Aug 26 15:52:13 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 26 Aug 2009 11:52:13 -0400
Subject: [Slackbuilds-users] [Slackware 12.1] Audacity Slackbuild page -
	unlisted dependencies
In-Reply-To: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>
References: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>
Message-ID: <8682df160908260852w64caf032p4f8f92486492861d@mail.gmail.com>

On Wed, Aug 26, 2009 at 11:47 AM, Oli D<vhann3000 at gmail.com> wrote:
> Hi,
>
> I just built and installed audacity from SlackBuilds:
> http://slackbuilds.org/repository/12.1/audio/audacity/
>
> The problem here is the SlackBuilds page only list "wxPython or wxGTK
> and libsoundfile" as dependencies
> for the audacity SlackBuilds.
>
> I installed a fair amount of packages before this SlackBuild would
> actually compile and I don't remember each
> of them, but I do know for sure that the following is needed:
> raptor: http://slackbuilds.org/repository/12.1/libraries/raptor/
>
> Maybe this will be useful to someone.
>

No, sorry.

I have been the maintainer of the Audacity SlackBuild at
SlackBuilds.org since its inception at Slackware 11.0 and have built
Audacity countless times over the years.  The only dependencies it
needs are the ones listed.  It sure as heck never needed raptor.
Something is wrong on your system.

Are you doing your building on a clean, full install of Slackware 12.1?

-- 
Chess Griffin

From listreader at lupulin.net  Wed Aug 26 18:24:11 2009
From: listreader at lupulin.net (paul wisehart)
Date: Wed, 26 Aug 2009 14:24:11 -0400
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <200908232211.28608.carlos@strangeworlds.co.uk>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>	<200908231120.47528.carlos@strangeworlds.co.uk>
	<200908232211.28608.carlos@strangeworlds.co.uk>
Message-ID: <4A957DCB.5010102@lupulin.net>

Carlos Corbacho wrote:
> On Sunday 23 August 2009 11:20:47 Carlos Corbacho wrote:
>> On Monday 10 August 2009 20:55:39 Robby Workman wrote:
>>> As I promised several people privately, here's a list of things that we
>>> have not had time to check/update for 13.0 yet:
>>>   http://slackbuilds.org/NOT_CHECKED
>> development/django/
>> development/stgit/
>>
>> Work fine here on Slackware64. (Given they're both pure Python packages,
>> I'd be surprised if they doesn't work on i486, but I can't test that).
>>
>> Also, there was some discussion recently about the architecture that should
>> be set for Python packages - was an official decision reached? I couldn't
>> find anything on the SBo site.
> 
> I've just e-mailed Daniel de Kok about taking over maintainership of the 
> Django package, and he's agreed, so can you update the maintainer details for 
> it as well?

Lemme know if you need any help with django or python related stuff.
I've been using my own django slackbuild since django 1.o was released.
(I currently have one for 1.1 that works with 64bit slackware)

I also have a bunch of python related slackbuilds that can be used with 
django.

(I name all my python slackbuilds py-<package-name> ex. py-django)

--
paul


From carlos at strangeworlds.co.uk  Wed Aug 26 21:34:06 2009
From: carlos at strangeworlds.co.uk (Carlos Corbacho)
Date: Wed, 26 Aug 2009 22:34:06 +0100
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <4A957DCB.5010102@lupulin.net>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<200908232211.28608.carlos@strangeworlds.co.uk>
	<4A957DCB.5010102@lupulin.net>
Message-ID: <200908262234.07197.carlos@strangeworlds.co.uk>

On Wednesday 26 August 2009 19:24:11 paul wisehart wrote:
> Lemme know if you need any help with django or python related stuff.
> I've been using my own django slackbuild since django 1.o was released.
> (I currently have one for 1.1 that works with 64bit slackware)

I already have a local SlackBuild for 1.0 (which should be trivial to update 
for 1.1), but thanks anyway.

(And if I can't package Python stuff, then I should probably quit my day job 
:)

> I also have a bunch of python related slackbuilds that can be used with
> django.

Anything of particular interest?

> (I name all my python slackbuilds py-<package-name> ex. py-django)

(Yuck... Reminds me far too much of the Debian style of python-<package name> 
(where package name may or may not be the name of the upstream package...))

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

From vhann3000 at gmail.com  Thu Aug 27 00:41:34 2009
From: vhann3000 at gmail.com (Oli D)
Date: Wed, 26 Aug 2009 20:41:34 -0400
Subject: [Slackbuilds-users] [Slackware 12.1] Audacity Slackbuild page -
	unlisted dependencies
In-Reply-To: <8682df160908260852w64caf032p4f8f92486492861d@mail.gmail.com>
References: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>
	<8682df160908260852w64caf032p4f8f92486492861d@mail.gmail.com>
Message-ID: <8e469e7d0908261741r1b855458h41d54e098eb85c33@mail.gmail.com>

On Wed, Aug 26, 2009 at 11:52 AM, Chess Griffin<chess at chessgriffin.com> wrote:
> No, sorry.
>
> I have been the maintainer of the Audacity SlackBuild at
> SlackBuilds.org since its inception at Slackware 11.0 and have built
> Audacity countless times over the years. ?The only dependencies it
> needs are the ones listed. ?It sure as heck never needed raptor.
> Something is wrong on your system.
>
> Are you doing your building on a clean, full install of Slackware 12.1?
>
> --
> Chess Griffin

Sorry for the way I sounded, I knew the problem had a high probability
of being on my side (now I'm 99% sure it is ^^ ).

Still, it's weird that the compile didn't work without raptor and did
once I installed it.
As for whether or not my system is a clean full Slackware 12.1.0, I don't know.
I believe it's full though it's certainly not freshly installed.

Also, I installed quite a bunch of packages (I think those were Slacky
packages as I
initially thought those were Slackware packages (they were Slackbuilds too)).

But then, I just deinstalled the raptor SlackBuild package and here's
the 10 last lines or so
of audacity SlackBuild's:

g++ -c -I../lib-src/portmixer/include
-I../lib-src/portaudio-v19/include -O2 -march=i486 -mtune=i686  -Wall
-I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread
-I../lib-src/FileDialog -O2 -march=i486 -mtune=i686 -Wall
-I/tmp/SBo/audacity-src-1.3.6/lib-src/lib-widget-extra
-I../lib-src/libresample/include -I../lib-src/libnyquist/nyx
-I../lib-src/libvamp        -O2 -march=i486 -mtune=i686 -Wall
-I/tmp/SBo/audacity-src-1.3.6/lib-src/portsmf   -fno-strict-aliasing
-I./include -I. -DLIBDIR=\"/usr/lib\"   -Wall
effects/ladspa/LoadLadspa.cpp -o effects/ladspa/LoadLadspa.o
In file included from effects/ladspa/LoadLadspa.cpp:42:
/usr/include/lrdf.h:8:20: error: raptor.h: No such file or directory
make[1]: *** [effects/ladspa/LoadLadspa.o] Error 1
make[1]: Leaving directory `/tmp/SBo/audacity-src-1.3.6/src'
make: *** [audacity] Error 2

You are probably right in saying there's something wrong with my
system but I still can't
install Audacity if I don't install raptor. Maybe there is a bug
somewhere, maybe my system
is wrong, I don't know, but the problem is there.

Regards,
Olivier Diotte

From rworkman at slackbuilds.org  Thu Aug 27 00:59:52 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 26 Aug 2009 19:59:52 -0500
Subject: [Slackbuilds-users] [Slackware 12.1] Audacity Slackbuild page -
 unlisted dependencies
In-Reply-To: <8e469e7d0908261741r1b855458h41d54e098eb85c33@mail.gmail.com>
References: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>
	<8682df160908260852w64caf032p4f8f92486492861d@mail.gmail.com>
	<8e469e7d0908261741r1b855458h41d54e098eb85c33@mail.gmail.com>
Message-ID: <20090826195952.77fd5e3f@liberty.rlwhome.lan>

On Wed, 26 Aug 2009 20:41:34 -0400
Oli D <vhann3000 at gmail.com> wrote:

> Sorry for the way I sounded, I knew the problem had a high probability
> of being on my side (now I'm 99% sure it is ^^ ).


You're still short 1%  :-)


> Also, I installed quite a bunch of packages (I think those were Slacky
> packages as I > initially thought those were Slackware packages
> 
> But then, I just deinstalled the raptor SlackBuild package and here's
> the 10 last lines or so
> of audacity SlackBuild's:
> 
> g++ -c -I../lib-src/portmixer/include
> -I../lib-src/portaudio-v19/include -O2 -march=i486 -mtune=i686  -Wall
> -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8
> -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread
> -I../lib-src/FileDialog -O2 -march=i486 -mtune=i686 -Wall
> -I/tmp/SBo/audacity-src-1.3.6/lib-src/lib-widget-extra
> -I../lib-src/libresample/include -I../lib-src/libnyquist/nyx
> -I../lib-src/libvamp        -O2 -march=i486 -mtune=i686 -Wall
> -I/tmp/SBo/audacity-src-1.3.6/lib-src/portsmf   -fno-strict-aliasing
> -I./include -I. -DLIBDIR=\"/usr/lib\"   -Wall
> effects/ladspa/LoadLadspa.cpp -o effects/ladspa/LoadLadspa.o
> In file included from effects/ladspa/LoadLadspa.cpp:42:
> /usr/include/lrdf.h:8:20: error: raptor.h: No such file or directory
> make[1]: *** [effects/ladspa/LoadLadspa.o] Error 1
> make[1]: Leaving directory `/tmp/SBo/audacity-src-1.3.6/src'
> make: *** [audacity] Error 2


Whatever installs that lrdf.h header also requires raptor.
Probably one of the the packages from slacky or elsewhere is
linked with raptor.  This is why precompiled packages without
a clear dependency tree are often problematic.

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

From vhann3000 at gmail.com  Thu Aug 27 03:28:34 2009
From: vhann3000 at gmail.com (Oli D)
Date: Wed, 26 Aug 2009 23:28:34 -0400
Subject: [Slackbuilds-users] [Slackware 12.1] Audacity Slackbuild page -
	unlisted dependencies
In-Reply-To: <8e469e7d0908261918w16dbbbdej4dad135e062987d2@mail.gmail.com>
References: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>
	<8682df160908260852w64caf032p4f8f92486492861d@mail.gmail.com>
	<8e469e7d0908261741r1b855458h41d54e098eb85c33@mail.gmail.com>
	<20090826195952.77fd5e3f@liberty.rlwhome.lan>
	<8e469e7d0908261918w16dbbbdej4dad135e062987d2@mail.gmail.com>
Message-ID: <8e469e7d0908262028g20d6a19di99d9ee721c013282@mail.gmail.com>

On Wed, Aug 26, 2009 at 8:59 PM, Robby Workman<rworkman at slackbuilds.org> wrote:
> Whatever installs that lrdf.h header also requires raptor.
> Probably one of the the packages from slacky or elsewhere is
> linked with raptor.  This is why precompiled packages without
> a clear dependency tree are often problematic.
>
> -RW
>

Ok, I investigated the case and found this in
/usr/doc/liblrdf-0.4.0/liblrdf.Slackbuild:
#!/bin/sh
# Heavily based on the Slackware 12.1 SlackBuild
# http://plugin.org.uk/lrdf/
# Requirements: raptor, ladspa
# Packager Vincenzi Loris - slacky at slacky.it

So I guess it DOES is a Slacky package problem.

Thanks for the help and for being so respectful.

P.S.: Sorry for the individual email Robby Workman.

Regards,
Olivier Diotte

From chess at chessgriffin.com  Wed Aug 26 23:48:36 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 26 Aug 2009 19:48:36 -0400
Subject: [Slackbuilds-users] [Slackware 12.1] Audacity Slackbuild page	-
	unlisted dependencies
In-Reply-To: <8e469e7d0908262028g20d6a19di99d9ee721c013282@mail.gmail.com>
References: <8e469e7d0908260847i71412c6ckc15454c82d3a1c0d@mail.gmail.com>
	<8682df160908260852w64caf032p4f8f92486492861d@mail.gmail.com>
	<8e469e7d0908261741r1b855458h41d54e098eb85c33@mail.gmail.com>
	<20090826195952.77fd5e3f@liberty.rlwhome.lan>
	<8e469e7d0908261918w16dbbbdej4dad135e062987d2@mail.gmail.com>
	<8e469e7d0908262028g20d6a19di99d9ee721c013282@mail.gmail.com>
Message-ID: <20090826234836.GA3262@localhost>

* Oli D <vhann3000 at gmail.com> [2009-08-26 23:28:34]:

> Ok, I investigated the case and found this in
> /usr/doc/liblrdf-0.4.0/liblrdf.Slackbuild:
> #!/bin/sh
> # Heavily based on the Slackware 12.1 SlackBuild
> # http://plugin.org.uk/lrdf/
> # Requirements: raptor, ladspa
> # Packager Vincenzi Loris - slacky at slacky.it
> 
> So I guess it DOES is a Slacky package problem.
> 
> Thanks for the help and for being so respectful.
> 
> P.S.: Sorry for the individual email Robby Workman.
> 
> Regards,
> Olivier Diotte
 
Sorry if I was a little gruff in my earlier reply.  I've just had lots
of emails over time from folks insisting that a script was broken when
it was actually a PEBKAC issue that could have been discovered with a
little effort.  Not that you were saying that, but others have and
sometimes my patience level is exhausted.

I think I am getting cranky in my old age.

Scratch "I think" from the previous sentence.  :-)

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090826/f840b396/attachment.sig>

From sbo at tpa.me.uk  Thu Aug 27 13:25:46 2009
From: sbo at tpa.me.uk (Zordrak)
Date: Thu, 27 Aug 2009 14:25:46 +0100
Subject: [Slackbuilds-users] UID/GID 90 (Heartbeat) Conflicts with POP in
	Slack
Message-ID: <4A96895A.9040405@tpa.me.uk>

WRT http://slackbuilds.org/uid_gid.txt

heartbeat
=======
User:    hacluster	UID: 90		GID: 90
Group:   haclient			GID: 90


UID & GID 90 are already assigned to POP in Slackware.

I am personally using 95 instead.. feel free to save me from changing
mine for canonicalisation and use 95 :)

Ta
--
Zordrak
sbo at tpa.me.uk

From erik at slackbuilds.org  Thu Aug 27 13:49:32 2009
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 27 Aug 2009 08:49:32 -0500
Subject: [Slackbuilds-users] UID/GID 90 (Heartbeat) Conflicts with POP
 in Slack
In-Reply-To: <4A96895A.9040405@tpa.me.uk>
References: <4A96895A.9040405@tpa.me.uk>
Message-ID: <20090827084932.0ddf5352@shaggy.doo>

On Aug 27, 2009, at  2:25 PM, Zordrak wrote:

> UID & GID 90 are already assigned to POP in Slackware.

As discussed on IRC, this has be re-assigned to UID/GID 226.

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

From michiel at slackbuilds.org  Fri Aug 28 04:34:54 2009
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Fri, 28 Aug 2009 05:34:54 +0100
Subject: [Slackbuilds-users] Slackware{,
 64}-13.0 Released and Slackbuilds.org 13.0 Repository available.
Message-ID: <20090828053454.51499ca3@hades.esn.local>

Yes it's that time again!

http://slackware.com/announce/13.0.php

There is a new release of Slackware-13.0 and with that the new repo is
also made available at http://slackbuilds.org/repository/13.0/

Please note that that the build scripts are now available for both 32
and 64 bit. This also means there are some changes you need to be
aware of when submitting new or updated builds to us. More details on
that can be found here:  http://slackbuilds.org/guidelines/

To read more on how to use scripts on Slackware64, we have updated our
faq and your answer is: http://slackbuilds.org/faq/#x86_64

Enjoy and have fun..

On behalf of the entire SlackBuilds.org Team.

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

From michiel at slackbuilds.org  Fri Aug 28 05:27:17 2009
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Fri, 28 Aug 2009 06:27:17 +0100
Subject: [Slackbuilds-users] Updates - 20090828
Message-ID: <20090828062717.312f8760@hades.esn.local>

Wed Aug 26 10:00:38 CDT 2009

Well, it's that time again - the newest release of Slackware (13.0) is
now on the mirrors, and since we know everyone is itching for
SlackBuilds.org goodness, we (hopefully) won't disappoint you.  As
usual, the ChangeLog is quite long, and perhaps even longer than usual
this time around.  There are quite a few new additions to the tree,
many old and unmaintained removals, and many updates.  It's entirely
possible (likely even) that we neglected to fix all of the README
files, so if you find any mentions of stuff that that's now part of
Slackware (and thus doesn't need to be noted as a dep), let us know.
Of course, other bug reports are also encouraged, but maybe there won't
be many of those :-) Congratulations to Pat and the Slackware team for
another fine release, and we hope you all enjoy Slackware 13.0 and the
updated SlackBuilds.org stuff. As always, thanks for your support and
encouragement of both the Slackware team and us; happy Slacking!  --
the SlackBuilds.org Admin Team

The following entries are now included in Slackware 13.0, so they are no
  longer in the SlackBuilds.org repository:
  desktop/thunar-volman
  development/boost
  development/cupsddk
  development/gmm
  development/pil
  development/pycups
  development/sip
  development/swig
  development/subversion-bindings (part of the subversion package)
  graphics/djvulibre
  graphics/openexr
  libraries/babl
  libraries/chmlib
  libraries/clucene
  libraries/exiv2
  libraries/gegl
  libraries/glew
  libraries/ilmbase
  libraries/iso-codes
  libraries/jasper
  libraries/libarchive
  libraries/libdvdread
  libraries/libical
  libraries/libiptc (part of iptables now)
  libraries/libmcrypt
  libraries/libnl
  libraries/libvncserver
  libraries/libxklavier
  libraries/libzip
  libraries/pyqt3
  libraries/pyqt4
  libraries/qt4
  libraries/raptor
  libraries/rasqal
  libraries/redland
  libraries/taglib-extras
  libraries/urwid
  multimedia/mplayer
  network/iw
  network/snownews
  network/x11-ssh-askpass
  system/dc3dd
  system/dolphin (part of kde)
  system/lzma (part of xz)
  system/xorg-server-xephyr

The following entries were removed for other reasons:
  academic/bibletime: Removed; this won't compile with kde4. 
  academic/bibletime-i18n: Removed; this won't compile with kde4. 
  academic/qalculate-kde: Removed; this won't compile with kde4. 
  academic/rkward: Removed; this won't compile with kde4. 
  academic/scilab: Removed; this won't build a good package on x86_64.
  academic/xdrawchem: This requires qt3, so it's gone.
  academic/xoscope: Removed; this won't compile.
  audio/exaile: Removed; the maintainer plans to resubmit this after
13.0 is released.  --rworkman
  audio/moodbar: Removed; this won't work with Amarok2.  --pprkut
  audio/orpheus: Removed; this won't build and appears to be abandoned
    upstream.  --rworkman
  business/tinyerp-client: Removed; replaced with openerp-client.
--pprkut business/tinyerp-server: Removed; replaced with
openerp-server.  --pprkut desktop/ccsm: Removed; this is unmaintained.
--dsomero desktop/compiz-bcop: Removed; this is unmaintained.  --dsomero
  desktop/compiz-fusion-plugins-extra: Removed; this is unmaintained.
--dsomero desktop/compiz-fusion-plugins-main: Removed; this is
unmaintained.  --dsomero desktop/compiz-fusion-plugins-unsupported:
Removed; this is unmaintained.  --dsomero
  desktop/compizconfig-backend-gconf: Removed; this is unmaintained.
--dsomero desktop/compizconfig-backend-kconfig: Removed; this is
unmaintained.  --dsomero desktop/compizconfig-python: Removed; this is
unmaintained.  --dsomero desktop/domino: Removed; this requires kde3.
--pprkut desktop/dzen: Removed; this is unmaintained.  --rworkman
  desktop/emerald: Removed; this is unmaintained.  --dsomero
  desktop/emerald-themes: Removed; this is unmaintained.  --dsomero
  desktop/fusion-icon: Removed; this is unmaintained.  --dsomero
  desktop/kbfx: Removed; this requires kde3.  --rworkman
  desktop/kcometen3: Removed; this requires kde3.  --michiel
  desktop/kirocker: Removed; this requires kde3.  --rworkman
  desktop/kkbswitch: Removed; this requires kde3.  --rworkman
  desktop/krypt: Removed; this requires kde3.  --rworkman
  desktop/ksmoothdock: Removed; this requires kde3.  --rworkman
  desktop/pypanel: Removed; won't compile on x86_64 and upstream
    is dead.  --chess
  desktop/QtCurve-KDE3: Removed; replaced with QtCurve-KDE4.  --michiel
  desktop/SystemPreferences: Removed (this depends on the gnustep stuff
    that was removed).  --rworkman
  desktop/simple-ccsm: Removed; this is unmaintained.  --dsomero
  desktop/thunar-shares: Renamed (now called thunar-shares-plugin).
  desktop/wmCalClock: Removed (download link is inaccessible).
--rworkman desktop/wmMoonClock: Removed (download link is
inaccessible).  --rworkman desktop/wmSun: Removed (download link is
inaccessible).  --rworkman desktop/wmnet: Removed (download link is
inaccessible).  --rworkman desktop/wmpower: Removed (download link is
inaccessible).  --rworkman desktop/wmsm.app: Removed (download link is
inaccessible).  --rworkman desktop/xfce4-battery-plugin: Removed; as
far as I'm concerned, this is now obsolete - use xfce4-power-manager
instead.  --rworkman desktop/xfce4-eyes-plugin: Removed; if someone
thinks this is actually worth having, then feel free to resubmit it
(and maintain it).  --rworkman development/Ice: Removed; this is
unmaintained.  --rworkman development/Pivy: Removed; this is
unmaintained.  --rworkman development/ProjectCenter: Removed; this
depends on the gnustep stuff that was also removed.  --rworkman
  development/boost-bindings: Removed; this is unmaintained.  --rworkman
  development/bugle: Removed; this won't build on 13.0, and it was
unmaintained anyway.  --rworkman
  development/gccxml: Removed; this is unmaintained.  --rworkman
  development/gorm: Removed; this depends on the gnustep stuff that was
also removed.  --rworkman
  development/kdbg: Removed; this required kde3.  --michiel
  development/motor: Removed; this won't build on 13.0 and has been 
    unmaintained upstream for a long time.  --michiel
  development/mysqlcc: Removed; this requires qt3.  --pprkut
  development/psycopg: Removed; everything uses psycopg2 by now.
--pprkut development/pygccxml: Removed; this is unmaintained.
--rworkman development/pyplusplus: Removed; this is unmaintained.
--rworkman development/python3: Removed; this will be resubmitted with
some cleanups and a version bump after the 13.0 release.  --rworkman
  development/valgrind: Removed; incompatible with 13.0's glibc.
--pprkut games/defcon: Removed; this is a 32bits binary only.  --michiel
  games/ivan: Removed; this won't compile. 
  games/koules: Removed; this won't compile.
  games/ksudoku: Removed; This is now part of kdegames.  --pprkut
  games/nethack: Removed; this won't compile. 
  games/widelands: Removed; this won't compile.  --pprkut
  games/xgalaga: Removed; this won't compile.
  graphics/enblend-enfuse: Removed; this requires libxmi, which won't
build on 13.0.  --rworkman
  graphics/gwenview: This is now part of kdegraphics.
  graphics/gwenview-i18n: This is now part of kdegraphics.
  graphics/hugin: Removed; this requires enblend-enfuse, which requires
    libxmi, which was removed because it won't build on 13.0.
--rworkman libraries/gail: This is now part of gtk-2.14.x.
  libraries/gnustep-{back,base,gui,make}: Removed.  Best I can tell,
it's not a trivial pursuit to package this stuff correctly on x86_64,
and I have neither the time nor desire to spend any more time on it.
--rworkman libraries/karma-sharp: Removed; this is unmaintained.
--rworkman libraries/libcompizconfig: Removed; this is unmaintained.
--dsomero libraries/libkdcraw: This is now part of kdegraphics.
  libraries/libffi: Removed; conflicts with gcc-java-4.3.3.
  libraries/libghttp: Removed; this won't build on 13.0.  --rworkman
  libraries/libkexiv2: This is now part of kdegraphics.
  libraries/libkipi: This is now part of kdegraphics.
  libraries/libopensync-plugin-kdepim: Removed; this doesn't work with
kde4. libraries/libqalculate: Removed; this won't build on 13.0.
--rworkman libraries/libxmi: Removed; this won't build on 13.0.
--rworkman librarues/lrmi: Removed; Unmaintained upstream.  --pprkut
  libraries/xmltv_prereq: Removed; this is unmaintained.  --dsomero
  misc/recode: Removed; this won't build on 13.0.  --pprkut
  misc/zaptel: This won't build on 2.6.29+ kernels.  --rworkman
  multimedia/mplayer-codecs-all: Removed (renamed to mplayer-codecs).
  multimedia/mythplugins: Removed; this is unmaintained.  --dsomero
  multimedia/myththemes: Removed; this is unmaintained.  --dsomero
  multimedia/mythtv: Removed; this is unmaintained.  --dsomero
  multimedia/xmltv: Removed; this is unmaintained.  --dsomero
  network/arora: Removed until a workaround is found. This will not work
    correctly with Slackware 13's version of Qt.  --dsomero
  network/dillo: Removed; this is unmaintained, and newer versions will
require some more work to build on 13.0.  --rworkman
  network/dovecot-sieve: Removed (renamed to dovecot-cmusieve).
--rworkman network/kftpgrabber: Removed (won't work with kde4).
--rworkman network/kmyfirewall: Removed; this requires kde3.  --rworkman
  network/knetmon: Removed; this requires kde3.  --rworkman
  network/kssh: Removed; this requires kde3.  --rworkman
  network/madwifi-driver: Removed; this won't build on 13.0.  --rworkman
  network/madwifi-tools: Removed; this won't build on 13.0.  --rworkman
  network/miniupnpd: This needs to catch up with the new iptables API.
  network/muttng: Removed; this is unmaintained.  --rworkman
  network/ntop: Removed; the buildscript of ntop wants to do too much
    on it's own that is not scriptable.  --Michiel
  network/tork: Removed; this requires kde3.  --pprkut
  office/basket: Removed; this requires kde3. --michiel
  office/gnumeric: Removed; the 1.8.x "stable" branch requires quite a
few gnome libs, and since we had 1.9.1 already for 12.2, I'd rather not
roll back to 1.8.x.  However, every new release of 1.9.x bumps the
libgsf requirement to whatever is the latest at that particular time,
so no matter what we here, it's highly likely that it will be wrong in
the near future.  Therefore, we'll wait for 13.0 to release and let the 
    gnumeric maintainer find a release of it that matches the libgsf
that's in 13.0.  Sorry for the book.  --rworkman
  office/kmobiletools: kde4 port seems unstable and unmaintained.
--pprkut office/kdissert: Removed; This is no longer maintained
upstream and QT3 only. 
  office/kmymoney2: Removed; this requires kde3.  --michiel
  office/lyx_qt4: Removed; (renamed to lyx).  --michiel
  office/oooqs2: Removed; this has not been updated for newer OOo.
--rworkman office/taskjuggler: Removed; this requires kde3.  --pprkut
  office/tellico: Removed; this requires kde3.  --michiel
  system/915resolution: Removed; this should no longer be needed.
--rworkman system/cdrkit: Removed; this is unmaintained.  --rworkman
  system/filelight: Removed; this requires kde3.  --michiel
  system/komparator: Removed; this is unmaintained.  --dsomero
  system/kshutdown: Removed; this requires kde3.  There is a kde4
version in development, so the maintainer is free to submit an update.
--rworkman system/lapsus: no kde4 port available yet.
  system/mrxvt: Removed; the license for this script is GPL, which
requires it to include a copy of the GPL, which is braindead for a
script that's *many* times smaller than the GPL itself, so mrxvt is
removed until or unless the build script is relicensed.  --rworkman
  system/nvidia-legacy71-driver: incompatible with xorg-server >= 1.5
  system/nvidia-legacy71-kernel: incompatible with xorg-server >= 1.5
  system/skim: Removed (unmaintained).  --rworkman
  system/slackins: This requires qt3, so it's gone.

The following entries were updated for 13.0:
  academic/celestia: Updated for version 1.6.0.  --pprkut
  academic/link-grammar: Updated for version 4.5.8.  --rworkman
  accessibility/linuxwacom: Updated for version 0.8.3_6.  --rworkman
  accessibility/jpilot: Updated for version 1.6.2 and included a patch
to use the expected libdir rather than violating POLA.  --rworkman
  audio/ardour: Updated for version 2.8.1.  --pprkut
  audio/gmpc: Updated for version 0.18.98.  --erik
  audio/gmpc-plugins: Updated for version 0.18.98.  --erik
  audio/gtkpod: Updated for version 0.99.14.  --rworkman
  audio/mp3blaster: Updated for version 3.2.5.  --rworkman
  audio/mpd: Updated for version 0.15.2.  --erik
  audio/ocp: Updated for version 0.1.17.  --erik
  desktop/QtCurve-Gtk2: Updated for version 0.65.3. --michiel
  desktop/crystal: Updated for version 2.0.3.  --michiel
  desktop/enlightenment: Updated for version 0.16.999.062.  --erik
  desktop/google-gadgets-for-linux: Updated for version 0.11.0.
--pprkut desktop/rss-glx: Updated for version 0.9.0.  --erik
  desktop/thunar-shares-plugin: Added (renamed from thunar-shares).
--rworkman desktop/thunar-svn-plugin: Updated for version 003 and added
a patch from Gentoo to build with subversion-1.6.x.  --rworkman
  desktop/thunar-thumbnailers: Updated for version 0.4.1.  --rworkman
  desktop/xfce4-clipman-plugin: Updated for version 1.0.1.  --rworkman
  desktop/xfce4-cpugraph-plugin: Updated for version 0.4.0.  --rworkman
  desktop/xfce4-dict: Updated for version 0.5.3.  --rworkman
  desktop/xfce4-diskperf-plugin: Updated for version 2.2.0.  --rworkman
  desktop/xfce4-genmon-plugin: Updated for version 3.2.  --rworkman
  desktop/xfce4-mpc-plugin: Updated for version 0.3.3.  --rworkman
  desktop/xfce4-notes-plugin: Updated for version 1.7.0.  --rworkman
  desktop/xfce4-places-plugin: Updated for version 1.2.0.  --rworkman
  desktop/xfce4-screenshooter: Updated for version 1.6.0.  --rworkman
  desktop/xfce4-timer-plugin: Updated for version 0.6.1.  --rworkman
  desktop/xfce4-wavelan-plugin: Updated for version 0.5.5.  --rworkman
  desktop/xfce4-weather-plugin: Updated for version 0.7.3.  --rworkman
  desktop/xfce4-xkb-plugin: Updated for version 0.5.3.3.  --rworkman
  desktop/xfce4-xmms-plugin: Updated for version 0.5.2.  --rworkman
  development/MySQL-python: Updated for version 1.2.3c1.  --pprkut
  development/SQLAlchemy: Updated for version 0.5.5.  --pprkut
  development/acpica: Updated for version 20090625. --pprkut
  development/apache-maven: Updated for version 2.2.0.  --pprkut
  development/bashdb: Updated for version 4.0-0.3.  --erik
  development/bzr: Updated for version 1.16.1.  --rworkman
  development/gob2: Updated for version 2.0.16.  --erik
  development/patchutils: Updated for version 0.3.1.  --rworkman
  development/kdesvn: Updated for version 1.3.2.  --michiel
  development/kdiff3: Updated for version 0.9.95.  --michiel
  development/llvm: Updated for version 2.5.  --pprkut
  development/psycopg2: Updated for version 2.0.11.  --pprkut
  games/bzflag: Updated for version 2.0.12.  --chess
  games/desmume: Updated for version 0.9.4.
    Thanks to Larry Hajali.  --pprkut
  games/gnubg: Updated for version 0.90.0_20090817.  --erik
  games/mednafen: Updated for version 0.8.C.  --pprkut
  games/scummvm: Updated for version 0.13.1.  --pprkut
  games/spring: Updated for version 0.79.1.2.  --rworkman
  games/springlobby: Updated for version 0.0.1.10494.  --rworkman
  games/warzone2100: Updated for version 2.2.1.  --dsomero
  games/wesnoth: Updated for version 1.6.4.  --michiel
  games/zsnes: Updated for version 1.51b.
    Thanks to "Dave" on slackbuilds-users.  --rworkman
  graphics/fontforge: Updated for version 20090622.  --rworkman
  graphics/gtkam: Updated for version 0.1.16.1.
    Thanks to Michael Wagner.  --rworkman
  graphics/inkscape: Updated for version 0.47pre0.  --rworkman
  graphics/lilypond: Updated for version 2.12.2.  --pprkut
  graphics/mftrace: Updated for version 1.2.15.  --pprkut
  graphics/opengtl: Updated for version 0.9.9.  --pprkut
  graphics/xtrkcad: Updated for version 4.0.3a.  
    Thanks to David Spencer.  --rworkman
  libraries/PyXML: Included a patch to work with python-2.6.
    Thanks to Vincent Batts for the heads-up on this.  --pprkut
  libraries/cln: Updated for version 1.3.0.  --rworkman
  libraries/e_dbus: Updated for version 0.5.0.062.  --erik
  libraries/ecore: Updated for version 0.9.9.062.  --erik
  libraries/edje: Updated for version 0.9.92.062.  --erik
  libraries/eet: Updated for version 1.2.2.  --erik
  libraries/efreet: Updated for version 0.5.0.062.  --erik
  libraries/eina: Updated for version 0.0.2.062.  --erik
  libraries/embryo: Updated for version 0.9.9.062.  --erik
  libraries/evas: Updated for version 0.9.9.062.  --erik
  libraries/exempi: Updated for version 2.1.1.
  libraries/exo-notify: Updated for version 0.3.101 to match the exo
version in Slackware's xfce package.  --rworkman
  libraries/gdal: Updated for version 1.6.0.
    Thanks to Marco Cecchetti.  --rworkman
  libraries/geos: Updated for version 3.0.4.  
    Thanks to Marco Cecchetti.  --rworkman
  libraries/gst-python: Updated for version 0.10.15.  As of right now,
there is an 0.10.16 release, but it won't build for me.  --rworkman
  libraries/gtk-qt-egine: Updated for version 1.1.  --michiel
  libraries/icu4c: Updated for version 4.2.1.  --pprkut
  libraries/id3lib: Included a patch to build on 13.0.  --rworkman
  libraries/libburn: Updated for version 0.6.8.  --rworkman
  libraries/libetpan: Updated for version 0.58.  --rworkman
  libraries/libglademm: Updated for version 2.6.7.  --pprkut
  libraries/libinklevel: Updated for version 0.8.0.  --rworkman
  libraries/libisoburn: Updated for version 0.3.8.  --rworkman
  libraries/libisofs: Updated for version 0.6.20.  --rworkman
  libraries/libmpd: Updated for version 0.18.98.  --erik
  libraries/libnfnetlink: Updated for version 1.0.0.  --rworkman
  libraries/libopenraw: Updated for version 0.0.8.  --michiel
  libraries/libpri: Updated for version 1.4.10.1.  --rworkman
  libraries/libquicktime: Updated for version 1.1.3.  --pprkut
  libraries/libsmbios: Updated for version 2.2.19.  --rworkman
  libraries/libtorrent: Updated for version 0.12.4.  --rworkman
  libraries/libtorrent-rasterbar: Updated for version 0.14.4.
--rworkman libraries/openbabel: Updated for version 2.2.1.  --rworkman
  libraries/physfs: Updated for version 2.0.0.  --dsomero
  libraries/slv2: Updated for version 0.6.6.  --pprkut
  libraries/swfdec: Updated for version 0.8.4.  --erik
  libraries/wvstream: Updated for version 4.6.  --rworkman
  libraries/xalan-c: Included a patch to compile with gcc-4.3.  --pprkut
  misc/fcitx: Updated for version 3.6.0.   --michiel
  misc/gnome-doc-utils: Updated for version 0.17.2.  --rworkman
  misc/krename: Updated for version 3.9.3  --pprkut
  multimedia/Songbird: Updated for version 1.20.  --michiel
  multimedia/flash-player-plugin: Updated for version 10.0.32.18.
--rworkman multimedia/flash-player-standalone: Updated for version
10.0.32.18.  --pprkut multimedia/gst-gnome-vfs: Updated for version
0.10.23 (to match the version of gst-plugins-base that's in 13.0).
--rworkman multimedia/gst-plugins-bad: Updated for version 0.10.13.
--michiel multimedia/gst-plugins-good: Updated for version 0.10.15.
--michiel multimedia/gst-plugins-ugly: Updated for version 0.10.12.
--michiel multimedia/kaffeine: Updated for version 1.0_pre1.  --michiel
  multimedia/mkvtoolnix: Updated for version 2.9.8.  --erik
  multimedia/transcode: Updated for version 1.1.3.  --pprkut
  multimedia/wxcam: Updated for version 1.0.4.
    Thanks to Pierre Cazenave.  --rworkman
  network/LimeWire: Updated for version 5.1.4.  --rworkman
  network/aircrack-ng: Updated for version 1.0_rc3 since previous
version did not build on Slackware64.  --chess
  network/autossh: Updated for version 1.4b.  --rworkman
  network/b43-fwcutter: Updated for version 012.  --rworkman
  network/claws-mail: Updated for version 3.7.2.  --rworkman
  network/claws-mail-extra-plugins: Updated for version 3.7.2.
--rworkman network/dropbear: Updated for version 0.52.  --rworkman
  network/ipvsadm: Updated for version 1.25.  --pprkut
  network/konversation: Updated for version 1.2_alpha4.  --michiel
  network/lighttpd: Updated for version 1.4.23.  --rworkman
  network/memcached: Updated for version 1.2.8.  --rworkman
  network/msmtp: Updated for version 1.4.17.  --rworkman
  network/ndiswrapper: Updated for version 1.55.  --rworkman
  network/skype: Switched to the shared build to get better
    KDE4 Integration.  --pprkut
  network/tor: Updated for version 0.2.1.19.  --dsomero
  network/wireshark: Updated for version 1.2.1.  --michiel
  network/xtables-addons: Updated for version 1.17.  --rworkman
  office/abiword: Updated for version 2.6.8.  --rworkman
  office/adobe-reader: Updated for version 9.1.2.  --pprkut
  office/apvlv: Updated for version 0.0.6.6.  --rworkman
  office/eqonomize: Updated for version 0.6.  --pprkut
  office/kchmviewer: Updated for version 4.0.  --michiel
  office/lyx: Updated for version 1.6.3.  --michiel
  office/moneydance: Updated for version 2008_b640.  --rworkman
  office/scribus: Updated for version 1.3.5.rc3.  --rworkman
  system/apcupsd: Updated for version 3.14.7.  --rworkman
  system/cdemu-daemon: Patched to compile on 13.0.  --pprkut
  system/cfengine: Updated for version 2.2.10.  
    Thanks to Menno Duursma.  --rworkman
  system/ddrescue: Updated for version 1.11.  --pprkut
  system/dosbox: Updated for version 0.73.  --michiel
  system/fakeroot: Updated for version 1.12.4.  --rworkman
  system/fpm2: Updated for version 0.75.  --erik
  system/gammu: Updated for version 1.25.0.  --pprkut
  system/gdm: Updated for version 2.20.10.  --rworkman
  system/htop: Updated for version 0.8.3. This fixes the segfaulting
problem on htop-0.8.2 when trying to sort.  --michiel
  system/krusader: Updated for version 2.0.0.  --rworkman
  system/lbzip2: Updated for version 0.15.  --erik
  system/nvidia-driver: Updated for version 185.18.31.  --pprkut
  system/nvidia-kernel: Updated for version 185.18.31.  --pprkut
  system/nvidia-legacy173-driver: Updated for version 173.14.20.
--pprkut system/nvidia-legacy173-kernel: Updated for version
173.14.20.  --pprkut system/nvidia-legacy96-driver: Updated for version
96.43.13.  --pprkut system/nvidia-legacy96-kernel: Updated for version
96.43.13.  --pprkut system/pommed: Updated for version 1.26.  --rworkman
  system/powertop: Updated for version 1.11.  --pprkut
  system/qemu: Updated for 0.10.6.  --rworkman
  system/rkhunter: Updated for version 1.3.4.  --rworkman
  system/set_rlimits: Updated for version 1.3.0.  --rworkman
  system/virtualbox-ose: Updated for version 3.0.4.  --pprkut
  system/virtualbox-ose-addons: Updated for version 3.0.4.  --pprkut
  system/virtualbox-kernel: Updated for version 3.0.4.  --pprkut
  system/virtualbox-kernel-addons: Updated for version 3.0.4.  --pprkut
  system/wine: Updated for version 1.1.24.  Note that this won't build
on a stock Slackware 13.0 64bit system - you'll need 32bit
compatibility stuff to do so.  We won't say it doesn't work, but we
don't support it. system/xfburn: Updated for version 0.4.2.  --rworkman
  system/yakuake: Updated for version 2.9.6.  --pprkut
  system/zeroinstall-injector: Updated for version 0.41.1.  --erik

The following were added to the repository for 13.0:
  business/openerp-client: Added (Renamed from tinyerp-client).
--pprkut business/openerp-server: Added (Renamed from openerp-server).
--pprkut desktop/QtCurve-KDE: Added; this replaces QtCurve-KDE3.
--michiel desktop/xfce4-mailwatch-plugin: Added xfce4-mailwatch-plugin
is a plugin for the XFCE4 panel to check mail. --dsomero
  desktop/xfce4-notifyd: Added. xfce4-notifyd is a notification daemon
    for the XFCE desktop. Thanks to Frank Caraballo.  --michiel
  desktop/xfswitch-plugin: Added. Thanks to rworkman.  --michiel
  libraries/pangomm: Added. Pangomm is a C++ API for Pango. --erik
  libraries/pychart: Added. This is needed for openerp-server.  --pprkut
  libraries/pydot: Added. This is needed for openerp-server.  --pprkut
  libraries/pyicu: Added. This is needed for vobject.  --pprkut
  libraries/pytz: Added. This is needed for openerp-server.  --pprkut
  libraries/vobject: Added. This is needed for openerp-server.  --pprkut
  multimedia/mplayer-codecs: Added (renamed from mplayer-codecs-all).
  network/dovecot-cmusieve: Added (renamed from dovecot-sieve).  
    Thanks to Nishant Limbachia.  --rworkman
  office/evince: Added. Evince is a lightweight PDF and document viewer.
    Thanks to Andrew Bouwers for the buildscript.  --michiel

The following entries were not checked at all for 13.0, as we simply ran
  out of time to do them.  We know that some of these were likely
mentioned on the mailing list, but we were too busy trying to get
everything ready for the release of 13.0.  Sorry for the inconvenience,
but maybe we'll be ready for new submissions pretty soon...
  audio/SlimServer: Removed.
  audio/amSynth: Removed.
  audio/quodlibet: Removed.
  audio/scmpc: Removed.
  audio/tuxguitar: Removed.
  audio/xmms2: Removed.
  business/clacct: Removed.
  business/ledger: Removed.
  business/xtuple: Removed.
  desktop/3ddesktop: Removed.
  desktop/Alphacube-GTK: Removed.
  desktop/Blokkal: Removed.
  desktop/CurseTheWeather: Removed.
  desktop/adesklets: Removed.
  desktop/alltray: Removed.
  desktop/alphacube: Removed.
  desktop/bbrun: Removed.
  desktop/blended: Removed.
  desktop/brightside: Removed.
  desktop/candido: Removed.
  desktop/cellwriter: Removed.
  desktop/cylonminimal: Removed.
  desktop/desklaunch: Removed.
  desktop/docker: Removed.
  desktop/dwm: Removed.
  desktop/fbdesk: Removed.
  desktop/ffmpegthumbnailer: Removed.
  desktop/furiusisomount: Removed.
  desktop/gtk-smooth-engine: Removed.
  desktop/industrial-cursor-theme: Removed.
  desktop/ion: Removed.
  desktop/kooldock: Removed.
  desktop/linstasquared: Removed.
  desktop/lipstik: Removed.
  desktop/nitrogen: Removed.
  desktop/oroborus: Removed.
  desktop/parcellite: Removed.
  desktop/pclock: Removed.
  desktop/pekwm: Removed.
  desktop/rezlooks: Removed.
  desktop/root-tail: Removed.
  desktop/stalonetray: Removed.
  desktop/ubuntulooks: Removed.
  desktop/whaw: Removed.
  desktop/xmobar: Removed.
  desktop/xxkb: Removed.
  development/Amaya: Removed.
  development/Coin: Removed.
  development/Genshi: Removed.
  development/Jinja: Removed.
  development/LLgen: Removed.
  development/Quarter: Removed.
  development/SilverCity: Removed.
  development/Werkzeug: Removed.
  development/Xdialog: Removed.
  development/argouml: Removed.
  development/astyle: Removed.
  development/autogen: Removed.
  development/boo: Removed.
  development/bouml: Removed.
  development/bouml_docs: Removed.
  development/bzrtools: Removed.
  development/cc65: Removed.
  development/cgdb: Removed.
  development/check: Removed.
  development/cm_tools: Removed.
  development/codeblocks: Removed.
  development/cvsps: Removed.
  development/ded: Removed.
  development/diakonos: Removed.
  development/django: Removed.
  development/eagle: Removed.
  development/easyedit: Removed.
  development/easygui: Removed.
  development/empty: Removed.
  development/esvn: Removed.
  development/flup: Removed.
  development/glade3: Removed.
  development/gputils: Removed.
  development/gtk-sharp: Removed.
  development/gtkdialog: Removed.
  development/hexedit: Removed.
  development/hgsvn: Removed.
  development/ht: Removed.
  development/hugs98: Removed.
  development/jasspa: Removed.
  development/jbigkit: Removed.
  development/ketchup: Removed.
  development/kompozer: Removed.
  development/kontrollerlab: Removed.
  development/latrace: Removed.
  development/libanculus-sharp: Removed.
  development/loki: Removed.
  development/mcpp: Removed.
  development/mono: Removed.
  development/mono-addins: Removed.
  development/monotone: Removed.
  development/ndesk-dbus: Removed.
  development/ndesk-dbus-glib: Removed.
  development/netbeans: Removed.
  development/openmpi: Removed.
  development/piklab: Removed.
  development/psyco: Removed.
  development/pydblite: Removed.
  development/python-pmw: Removed.
  development/qdevelop: Removed.
  development/qt-creator: Removed.
  development/quilt: Removed.
  development/re2c: Removed.
  development/saxonb: Removed.
  development/scite: Removed.
  development/sdcc: Removed.
  development/shed: Removed.
  development/sloccount: Removed.
  development/smake: Removed.
  development/source-highlight: Removed.
  development/splint: Removed.
  development/stgit: Removed.
  development/swi-prolog-lite: Removed.
  development/tailor: Removed.
  development/tavrasm: Removed.
  development/tkcvs: Removed.
  development/tokyocabinet: Removed.
  development/uisp: Removed.
  development/uncrustify: Removed.
  development/vic: Removed.
  development/xalan-j: Removed.
  development/zile: Removed.
  games/Phalanx: Removed.
  games/armagetronad: Removed.
  games/blobAndConquer: Removed.
  games/brickout: Removed.
  games/bygfoot: Removed.
  games/chromium-bsu: Removed.
  games/circuslinux: Removed.
  games/crack-attack: Removed.
  games/crossfire-client: Removed.
  games/epsxe: Removed.
  games/fortune_firefly: Removed.
  games/freeciv: Removed.
  games/freedroidrpg: Removed.
  games/frotz: Removed.
  games/gemdropx: Removed.
  games/gens: Removed.
  games/gnugo: Removed.
  games/ivan: Removed.
  games/kobodeluxe: Removed.
  games/koules: Removed.
  games/monsterz: Removed.
  games/nethack: Removed.
  games/nevernoid: Removed.
  games/pysolfc: Removed.
  games/pysweeper: Removed.
  games/qgo: Removed.
  games/qmc2: Removed.
  games/sms_sdl: Removed.
  games/transfusion: Removed.
  games/tuxpuck: Removed.
  games/typhoon_2001: Removed.
  games/xaos: Removed.
  games/xgalaga++: Removed.
  games/xscrabble: Removed.
  games/z26: Removed.
  graphics/bashgallery: Removed.
  graphics/comix: Removed.
  graphics/digikam: Removed.
  graphics/djview4: Removed.
  graphics/exif: Removed.
  graphics/exiftags: Removed.
  graphics/fbida: Removed.
  graphics/fly: Removed.
  graphics/gerbv: Removed.
  graphics/gimmage: Removed.
  graphics/gliv: Removed.
  graphics/gpicview: Removed.
  graphics/grap: Removed.
  graphics/jhead: Removed.
  graphics/kipi-plugins: Removed.
  graphics/kphotoalbum: Removed.
  graphics/mirage: Removed.
  graphics/pcb: Removed.
  graphics/photoprint: Removed.
  graphics/plotutils: Removed.
  graphics/qcomicbook: Removed.
  graphics/rawstudio: Removed.
  graphics/svp: Removed.
  graphics/tripod: Removed.
  graphics/unpaper: Removed.
  graphics/yafray: Removed.
  graphics/zgv: Removed.
  libraries/clearsilver: Removed.
  libraries/gst-ffmpeg: Removed.
  libraries/guile-gtk: Removed.
  libraries/libnids: Removed.
  libraries/libstroke: Removed.
  libraries/libzrtpcpp: Removed.
  libraries/nss-mysql: Removed.
  libraries/pcsc-perl: Removed.
  libraries/pcsc-tools: Removed.
  libraries/perl-trayicon: Removed.
  libraries/python-spidermonkey: Removed.
  libraries/stfl: Removed.
  libraries/webkit-sharp: Removed.
  libraries/xmonad-contrib: Removed.
  misc/biosdisk: Removed.
  misc/bsdsfv: Removed.
  misc/cksfv: Removed.
  misc/di: Removed.
  misc/gxmessage: Removed.
  misc/heyu: Removed.
  misc/iscan-firmware: Removed.
  misc/iscan-proprietary-drivers: Removed.
  misc/kover: Removed.
  misc/kvm: Removed.
  misc/misctools: Removed.
  misc/qstat: Removed.
  misc/rlwrap: Removed.
  misc/rng-tools: Removed.
  misc/xclip: Removed.
  misc/xsel: Removed.
  multimedia/Miro: Removed.
  multimedia/devede: Removed.
  multimedia/divx4linux: Removed.
  multimedia/dvdrip: Removed.
  multimedia/ffmpeg2theora: Removed.
  multimedia/flvtool2: Removed.
  multimedia/gcstar: Removed.
  multimedia/gecko-mediaplayer: Removed.
  multimedia/gnome-mplayer: Removed.
  multimedia/gpac: Removed.
  multimedia/grip: Removed.
  multimedia/imagination: Removed.
  multimedia/k9copy: Removed.
  multimedia/kdetv: Removed.
  multimedia/kid3: Removed.
  multimedia/kmplayer: Removed.
  multimedia/mmsclient: Removed.
  multimedia/mppenc: Removed.
  multimedia/quodlibet-plugins: Removed.
  multimedia/remoot: Removed.
  multimedia/subtitleeditor: Removed.
  multimedia/tvtime: Removed.
  multimedia/vcdimager: Removed.
  multimedia/vkeybd: Removed.
  multimedia/vobcopy: Removed.
  multimedia/xine-plugin: Removed.
  network/SocksiPy: Removed.
  network/amap: Removed.
  network/bmon: Removed.
  network/bot-sentry: Removed.
  network/castget: Removed.
  network/ccrtp: Removed.
  network/chrony: Removed.
  network/davfs2: Removed.
  network/deluge: Removed.
  network/dsniff: Removed.
  network/dynamips: Removed.
  network/efax-gtk: Removed.
  network/esmtp: Removed.
  network/exim: Removed.
  network/fcgi: Removed.
  network/flock: Removed.
  network/galaxium: Removed.
  network/ganglia: Removed.
  network/guarddog: Removed.
  network/heimdal: Removed.
  network/hping3: Removed.
  network/htscanner: Removed.
  network/ilbc: Removed.
  network/iscsitarget: Removed.
  network/kadu: Removed.
  network/kazehakase: Removed.
  network/kcheckgmail: Removed.
  network/kdebluetooth: Removed.
  network/kitchensync: Removed.
  network/kmess: Removed.
  network/kmldonkey: Removed.
  network/kuftp: Removed.
  network/linphone: Removed.
  network/linuxdcpp: Removed.
  network/lostirc: Removed.
  network/mozilla-prism: Removed.
  network/mozplugger: Removed.
  network/mrtg: Removed.
  network/msn-pecan: Removed.
  network/mumble: Removed.
  network/museek+: Removed.
  network/naim: Removed.
  network/netkit: Removed.
  network/netkit-filesystem: Removed.
  network/netkit-kernel: Removed.
  network/newsbeuter: Removed.
  network/nginx: Removed.
  network/nicotine-plus: Removed.
  network/nikto: Removed.
  network/noip: Removed.
  network/packit: Removed.
  network/phrel: Removed.
  network/pidgin-hotkeys: Removed.
  network/pidgin-otr: Removed.
  network/polipo: Removed.
  network/qbittorrent: Removed.
  network/radvd: Removed.
  network/retroshare: Removed.
  network/rtorrent: Removed.
  network/scli: Removed.
  network/sim: Removed.
  network/smb4k: Removed.
  network/spamassassin: Removed.
  network/strongswan: Removed.
  network/tcptrack: Removed.
  network/tsocks: Removed.
  network/tucan: Removed.
  network/twinkle: Removed.
  network/twitter-cmdline: Removed.
  network/varnish: Removed.
  network/vde2: Removed.
  network/w3af: Removed.
  network/w3m: Removed.
  network/weechat: Removed.
  network/wifi-radar: Removed.
  network/xrdp: Removed.
  network/znc: Removed.
  office/aiksaurus: Removed.
  office/brlcad: Removed.
  office/ding: Removed.
  office/freemind: Removed.
  office/full-pack: Removed.
  office/gocr: Removed.
  office/kbgoffice: Removed.
  office/kbibtex: Removed.
  office/keepassx: Removed.
  office/kile: Removed.
  office/mairix: Removed.
  office/openrpt: Removed.
  office/osmo: Removed.
  office/pdftk: Removed.
  office/pyroom: Removed.
  office/tdl: Removed.
  office/tth: Removed.
  office/xmblackberry: Removed.
  system/Esetroot: Removed.
  system/adcfw-log: Removed.
  system/artwiz-aleczapka: Removed.
  system/atari++: Removed.
  system/atari800: Removed.
  system/atari800_os++: Removed.
  system/atari800_roms: Removed.
  system/atarisio: Removed.
  system/atol: Removed.
  system/catfish: Removed.
  system/cdcopy: Removed.
  system/chkconfig: Removed.
  system/clex: Removed.
  system/detachtty: Removed.
  system/dosemu: Removed.
  system/dtach: Removed.
  system/dump: Removed.
  system/efont-unicode-bdf: Removed.
  system/fxload: Removed.
  system/gkrellflynn: Removed.
  system/gkrellm-volume: Removed.
  system/gpsman: Removed.
  system/gxemul: Removed.
  system/hardinfo: Removed.
  system/hibernate-script: Removed.
  system/ibam: Removed.
  system/iscan: Removed.
  system/lirc: Removed.
  system/lxtask: Removed.
  system/montecarlo: Removed.
  system/motion: Removed.
  system/moto4lin: Removed.
  system/mybashburn: Removed.
  system/openct: Removed.
  system/opensc: Removed.
  system/par2cmdline: Removed.
  system/pcsc-lite: Removed.
  system/pipemeter: Removed.
  system/pmem: Removed.
  system/postgis: Removed.
  system/powernowd: Removed.
  system/profont: Removed.
  system/pygresql: Removed.
  system/qdu: Removed.
  system/rdiff-backup: Removed.
  system/rox-filer: Removed.
  system/runit: Removed.
  system/sash: Removed.
  system/scim-fcitx: Removed.
  system/splix: Removed.
  system/star: Removed.
  system/stardict: Removed.
  system/stress: Removed.
  system/suspend: Removed.
  system/tarsnap: Removed.
  system/tiger: Removed.
  system/treesize: Removed.
  system/ttf-sil-gentium: Removed.
  system/twin: Removed.
  system/unison: Removed.
  system/vice: Removed.
  system/vncviewer: Removed.
  system/watchdog: Removed.
  system/x2vnc: Removed.
  system/xautolock: Removed.
  system/xtermcontrol: Removed.
  system/yeahconsole: Removed.

-- 
Michiel van Wessem
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090828/5856ca37/attachment-0001.asc>

From mjjzf at syntaktisk.dk  Fri Aug 28 08:35:29 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Fri, 28 Aug 2009 10:35:29 +0200
Subject: [Slackbuilds-users] The plot thickens: A couple of 13.0 questions
Message-ID: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>

So, a new day, a new Slackware version. Have looked at the RCs -
interesting changes. Let's see what we can make out of this one!
Competition is strong - the 12.2 was a very good release, in my opinion.
Done torrenting down, now pushing. I will be preparing some updated
versions of my Slackbuilds for the submission queue - I put off the
version bumps until after the new release. Now, a couple of questions:
After a cleanup of the Gnome dependencies, the development version of
Abiword now builds on Slackware - with one exception: It requires libgsf
to be rebuilt to include gio.
Will such a rebuilding package be acceptable for Slackbuilds? Of course,
it doubles a package which is already in Slackware, and all that is
necessary is a minor revision in the official libgsf Slackbuild.
Second, my Thinkpad doesn't work very well with encrypted networks using
the Ath5k driver, and so I have relied on Madwifi so far. I see from the
previous Slackbuilds-users email that Madwifi won't build on 13.0. Any
thoughts on why this is so? I may have to go the PCMCIA route without
Madwifi (which is, incidently, the only non-free software I need and use).
Again, thank you for the effort put into Slackbuilds - it is an extremely
strong community contribution. Praise Bob, keep slacking!

Yours,
Morten
__
http://www.syntaktisk.dk

From rworkman at slackbuilds.org  Fri Aug 28 13:24:58 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 28 Aug 2009 08:24:58 -0500
Subject: [Slackbuilds-users] The plot thickens: A couple of 13.0
 questions
In-Reply-To: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
References: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
Message-ID: <20090828082458.751cd1f4@liberty.rlwhome.lan>

On Fri, 28 Aug 2009 10:35:29 +0200
Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:

> So, a new day, a new Slackware version. Have looked at the RCs -
> interesting changes. Let's see what we can make out of this one!
> Competition is strong - the 12.2 was a very good release, in my
> opinion. Done torrenting down, now pushing. I will be preparing some
> updated versions of my Slackbuilds for the submission queue - I put
> off the version bumps until after the new release. Now, a couple of
> questions: After a cleanup of the Gnome dependencies, the development
> version of Abiword now builds on Slackware - with one exception: It
> requires libgsf to be rebuilt to include gio.


No, it doesn't: http://rlworkman.net/pkgs/13.0/
Well, I don't know about the development version, but if it requires
something that Slackware doesn't (yet) include, then I guess we'll
just stick to the stable version in our repository here.


> Will such a rebuilding package be acceptable for Slackbuilds? Of
> course, it doubles a package which is already in Slackware, and all
> that is necessary is a minor revision in the official libgsf
> Slackbuild. Second, my Thinkpad doesn't work very well with encrypted
> networks using the Ath5k driver, and so I have relied on Madwifi so
> far. I see from the previous Slackbuilds-users email that Madwifi
> won't build on 13.0. Any thoughts on why this is so? I may have to go
> the PCMCIA route without Madwifi (which is, incidently, the only
> non-free software I need and use). 


The network code has some changes that madwifi doesn't like.
You might get lucky and find patches lying around somewhere, 
but since most people don't need it (and *I* certainly don't),
it wasn't (and won't be) very high on my priority list.


> Again, thank you for the effort
> put into Slackbuilds - it is an extremely strong community
> contribution. Praise Bob, keep slacking!


Thanks, and here's hoping :-)

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

From rworkman at slackbuilds.org  Fri Aug 28 13:29:59 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 28 Aug 2009 08:29:59 -0500
Subject: [Slackbuilds-users] Updates - 20090828
In-Reply-To: <20090828062717.312f8760@hades.esn.local>
References: <20090828062717.312f8760@hades.esn.local>
Message-ID: <20090828082959.06fd5b4e@liberty.rlwhome.lan>

On Fri, 28 Aug 2009 06:27:17 +0100
Michiel van Wessem <michiel at slackbuilds.org> wrote:

> Wed Aug 26 10:00:38 CDT 2009
> 
> Well, it's that time again - the newest release of Slackware (13.0) is
> now on the mirrors, and since we know everyone is itching for
> SlackBuilds.org goodness, we (hopefully) won't disappoint you.  As
> usual, the ChangeLog is quite long, and perhaps even longer than usual
> this time around.  There are quite a few new additions to the tree,
> many old and unmaintained removals, and many updates.  It's entirely
> possible (likely even) that we neglected to fix all of the README
> files, so if you find any mentions of stuff that that's now part of
> Slackware (and thus doesn't need to be noted as a dep), let us know.
> Of course, other bug reports are also encouraged, but maybe there
> won't be many of those :-) Congratulations to Pat and the Slackware
> team for another fine release, and we hope you all enjoy Slackware
> 13.0 and the updated SlackBuilds.org stuff. As always, thanks for
> your support and encouragement of both the Slackware team and us;
> happy Slacking!  -- the SlackBuilds.org Admin Team


As I guess everyone noticed, there were >400 things that didn't even
get checked for 13.0 goodness because we simply didn't have time.
We know that some of those were mentioned on this mailing list, 
and while we would have preferred to get those included, it just
couldn't happen, unfortunately.  Once the submit page opens back up,
please consider submitting those to us (if we haven't already done
them and followed up with you).

On a related note, here's a sincere "thanks" from me personally to
the rest of the SlackBuilds.org team, espcially to Erik Hanson for
handling the server maintenance and to Heinz Wiesinger for taking
care of the website changes required.  I'm proud to be a part of
this talented and wonderful group!

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

From chess at chessgriffin.com  Fri Aug 28 14:22:35 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Fri, 28 Aug 2009 10:22:35 -0400
Subject: [Slackbuilds-users] Sbopkg 0.30.0 Issues
Message-ID: <8682df160908280722m18043f79ob2fecee97a6cb917@mail.gmail.com>

First of all, huge congratulations to Patrick and the entire Slackware
team on the release of Slackware 13.0.  IMHO, this is definitely the
best release yet, and the addition of Slackware 64 is awesome.

Second, big thanks to everyone associated with SlackBuilds.org --
admins, maintainers, and contributors alike.  Getting the repo ready
for a new release is a major job by itself, but adding in the
Slackware 64 support made it even bigger.

Third, unfortunately, there have been a few issues that have cropped
up with sbopkg 0.30.0 that we are working to fix.  The major issue is
that the "Check for Updates" feature seems to be broken when checking
for certain updates.  We're working on a fix and should have that
ready soon.  Building and installing stuff with 0.30.0 is working
fine, however.

Thanks.

-- 
Chess Griffin

From chess at chessgriffin.com  Fri Aug 28 18:23:01 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Fri, 28 Aug 2009 14:23:01 -0400
Subject: [Slackbuilds-users] Sbopkg 0.30.1 Bugfix Release
Message-ID: <20090828182301.GA26149@localhost>

We have released sbopkg version 0.30.1, which is intended to address a
couple of issues that were identified after Slackware 13.0 was released.
We apologize for the inconvenience resulting from these bugs.  If you
find anything else wonky, please, please file a bug report at the
http://code.google.com/p/sbopkg Issue Tracker.

Here is the ChangeLog for this release:

  * Fix the updates code for the 13.0 repo; thanks to everybody who
    contacted us about this issue.
  * Fix the $SBOPKGTMP sanity check. Thanks to Ken Roberts for raising the
    issue.
  * Update the renames file.

A package and tarball can be downloaded from the sbopkg website:

http:/www.sbopkg.org

Thanks!

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090828/882d0f23/attachment.sig>

From alan at lizella.net  Fri Aug 28 19:15:59 2009
From: alan at lizella.net (Alan Hicks)
Date: Fri, 28 Aug 2009 15:15:59 -0400
Subject: [Slackbuilds-users] The plot thickens: A couple of 13.0
 questions
In-Reply-To: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
References: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
Message-ID: <20090828151559.19c7dcf4@raven.lizella.net>

On Fri, 28 Aug 2009 10:35:29 +0200
Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:

> Second, my Thinkpad doesn't work very well with encrypted
> networks using the Ath5k driver, and so I have relied on Madwifi so
> far. I see from the previous Slackbuilds-users email that Madwifi
> won't build on 13.0.

Check the IRC channels for madwifi.  Some people may be able to assist
you there with compiling an SVN version.  I've had to do that in the
past to get my Atheros card working.  Thankfully, ath9k works great for
me so far.

-- 
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: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090828/af234d5d/attachment.asc>

From rob0 at slackbuilds.org  Fri Aug 28 19:23:37 2009
From: rob0 at slackbuilds.org (Rob McGee)
Date: Fri, 28 Aug 2009 14:23:37 -0500
Subject: [Slackbuilds-users] madwifi (was: The plot thickens: ...)
In-Reply-To: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
References: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
Message-ID: <200908281423.42923.rob0@slackbuilds.org>

On Friday 28 August 2009 03:35:29 Morten Juhl-Johansen Z?lde-Fej?r
   wrote:
> Second, my Thinkpad doesn't work very well with encrypted networks
> using the Ath5k driver, and so I have relied on Madwifi so far. I
> see from the previous Slackbuilds-users email that Madwifi won't
> build on 13.0. Any thoughts on why this is so?

Madwifi is a victim of the fact that 2.6.X kernels can and do vary
widely for different values of X. The madwifi 0.9.4 source builds
on/for older kernels, X < 24.

For newer kernels, you might find success with the "trunk" branch,
http://snapshots.madwifi-project.org/madwifi-trunk/ . But for you,
best would probably be to get ath5k working. New functionality is
being added all the time. Try with the kernel in testing/ .

I keep one madwifi machine on hand to act as access point. Last I
heard, master mode functionality still isn't available in mainstream
ath5k. Client functionality *should* be working by now.

From mjjzf at syntaktisk.dk  Fri Aug 28 19:52:11 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Fri, 28 Aug 2009 21:52:11 +0200
Subject: [Slackbuilds-users] madwifi (was: The plot thickens: ...)
In-Reply-To: <200908281423.42923.rob0@slackbuilds.org>
References: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
	<200908281423.42923.rob0@slackbuilds.org>
Message-ID: <1ea0d9a77e73b931122a6c79ecc540cb.squirrel@squirrelmail.gigahost.dk>


---- 8< ---- Rob McGee ---- 8< ----
> I keep one madwifi machine on hand to act as access point. Last I
> heard, master mode functionality still isn't available in mainstream
> ath5k. Client functionality *should* be working by now.
---- 8< ---- Rob McGee ---- 8< ----

Thank you for your thoughts.
Actually, the story is like this:
Ath5k runs very, very well on my Thinkpad. It does, however, have some
difficulties when I hit WPA/WPA2 - it randomly connects and disconnects.
It seems there is a dark, evil corner of Atheros Skunkworks reserved for
the chip they put in this otherwise magnificent piece of hardware - and
pretty much all others work.
There was a note this was being worked on on the Thinkwiki. I remember
seeing a notice from Pat that he was throwing the most recent kernel in
/extra, so perhaps that is the route.
Currently, I am using a PCMCIA card based on RT2500, but the quality is
below what the Atheros card can do when it shows off - so I will keep
looking into this.

Yours,
Morten
__
http://www.syntaktisk.dk

From mjjzf at syntaktisk.dk  Fri Aug 28 19:54:58 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Fri, 28 Aug 2009 21:54:58 +0200
Subject: [Slackbuilds-users] Medit page
Message-ID: <db7cda7351dee4cdab093035224d56a7.squirrel@squirrelmail.gigahost.dk>

Just a small detail:
I was installing the editor Medit -
http://slackbuilds.org/repository/13.0/development/medit/ - and the page
says that PyGTK is available at Slackbuilds.
I believe it is now included in Slackware, isn't that right?

Yours,
Morten
__
http://www.syntaktisk.dk

From mjjzf at syntaktisk.dk  Fri Aug 28 20:23:08 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?iso-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Fri, 28 Aug 2009 22:23:08 +0200
Subject: [Slackbuilds-users] Xfburn source file
Message-ID: <0e47c8110352952b9c461d9a4ba63351.squirrel@squirrelmail.gigahost.dk>

I was looking into Xfburn at
http://slackbuilds.org/repository/13.0/system/xfburn/ - it seems that the
source file linked to at
http://goodies.xfce.org/releases/xfburn/xfburn-0.4.2.tar.bz2 does not
exist in the folder - the newest version available there is 0.4.1.

Yours,
Morten
__
http://www.syntaktisk.dk

From rworkman at slackbuilds.org  Fri Aug 28 20:39:56 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 28 Aug 2009 15:39:56 -0500
Subject: [Slackbuilds-users] Xfburn source file
In-Reply-To: <0e47c8110352952b9c461d9a4ba63351.squirrel@squirrelmail.gigahost.dk>
References: <0e47c8110352952b9c461d9a4ba63351.squirrel@squirrelmail.gigahost.dk>
Message-ID: <20090828153956.022625e9@liberty.rlwhome.lan>

On Fri, 28 Aug 2009 22:23:08 +0200
Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:

> I was looking into Xfburn at
> http://slackbuilds.org/repository/13.0/system/xfburn/ - it seems that
> the source file linked to at
> http://goodies.xfce.org/releases/xfburn/xfburn-0.4.2.tar.bz2 does not
> exist in the folder - the newest version available there is 0.4.1.


Fixed; thanks.  The download links changed on the xfce side of things.
I hope all of my goodies are still correct :/

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

From volkerdi at slackware.com  Fri Aug 28 21:26:19 2009
From: volkerdi at slackware.com (Patrick J. Volkerding)
Date: Fri, 28 Aug 2009 16:26:19 -0500
Subject: [Slackbuilds-users] The plot thickens: A couple of 13.0
	questions
In-Reply-To: <20090828082458.751cd1f4@liberty.rlwhome.lan>
References: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
	<20090828082458.751cd1f4@liberty.rlwhome.lan>
Message-ID: <4A984B7B.7050205@slackware.com>

Robby Workman wrote:
> On Fri, 28 Aug 2009 10:35:29 +0200
> Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:
> 
>> So, a new day, a new Slackware version. Have looked at the RCs -
>> interesting changes. Let's see what we can make out of this one!
>> Competition is strong - the 12.2 was a very good release, in my
>> opinion. Done torrenting down, now pushing. I will be preparing some
>> updated versions of my Slackbuilds for the submission queue - I put
>> off the version bumps until after the new release. Now, a couple of
>> questions: After a cleanup of the Gnome dependencies, the development
>> version of Abiword now builds on Slackware - with one exception: It
>> requires libgsf to be rebuilt to include gio.
> 
> 
> No, it doesn't: http://rlworkman.net/pkgs/13.0/
> Well, I don't know about the development version, but if it requires
> something that Slackware doesn't (yet) include, then I guess we'll
> just stick to the stable version in our repository here.

I heard the same thing about goffice and gnumeric, but wasn't sure of 
the side effects of enabling gio...  like, does it require other parts 
of GNOME to avoid routing data to a black hole?  I know there are gio 
things already included in glib, and had verified that libgsf compiles 
just fine with gio enabled.

Probably it's something to float now in -current, but it seemed a little 
too risky as 13.0 approached.

Pat

From nobbutl at yahoo.co.uk  Fri Aug 28 22:32:42 2009
From: nobbutl at yahoo.co.uk (David Spencer)
Date: Fri, 28 Aug 2009 23:32:42 +0100
Subject: [Slackbuilds-users] libxmi
Message-ID: <4A985B0A.3080706@yahoo.co.uk>

Looks like a number of packages got removed due to libxmi not building.
Sorry about this. For some reason they weren't on the untested list? Or
was there a separate broken list that I missed? Anyway, to help
maintainers of dependent packages with testing prior to reopening the
submissions, attached is a revised SlackBuild that fixes the build problem.

Incidentally, maybe other maintainers are struggling with the same
problem of ancient packages that embed ancient automake scripts that
don't know about x86_64.  The solution came from the SlackBuild for
soundtouch:

am=$(automake --version | grep "1." | cut -d " " -f 4 | cut -d "." -f 2)
for i in config.guess config.sub depcomp install-sh missing; do
  rm -f $i
  ln -s /usr/share/automake-1.$am/$i $i
done

I must add, it's a wonderful and remarkable achievement to release the
new SlackBuilds.org repo simultaneously with Slackware 13.0. Wow! Thanks!

-Dave Spencer
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: libxmi.SlackBuild
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090828/b7286bfb/attachment.pl>

From rworkman at slackbuilds.org  Sat Aug 29 04:28:35 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 28 Aug 2009 23:28:35 -0500
Subject: [Slackbuilds-users] libxmi
In-Reply-To: <4A985B0A.3080706@yahoo.co.uk>
References: <4A985B0A.3080706@yahoo.co.uk>
Message-ID: <20090828232835.6b1f1c67@liberty.rlwhome.lan>

On Fri, 28 Aug 2009 23:32:42 +0100
David Spencer <nobbutl at yahoo.co.uk> wrote:

> Looks like a number of packages got removed due to libxmi not
> building. Sorry about this. For some reason they weren't on the
> untested list? Or was there a separate broken list that I missed?
> Anyway, to help maintainers of dependent packages with testing prior
> to reopening the submissions, attached is a revised SlackBuild that
> fixes the build problem.


Dang.  I searched all over the place for help on fixing up 
libxmi and came up empty, and based on the fact that it hasn't
seen a release in forever plus a few days, I just gave up on it
and removed it (and everything that depended on it).  The reason
it wasn't on the "missing" list is because it had already been
determined to be beyond salvage, but it's obvious that I was
wrong.


> Incidentally, maybe other maintainers are struggling with the same
> problem of ancient packages that embed ancient automake scripts that
> don't know about x86_64.  The solution came from the SlackBuild for
> soundtouch:
> 
> am=$(automake --version | grep "1." | cut -d " " -f 4 | cut -d "." -f
> 2) for i in config.guess config.sub depcomp install-sh missing; do
>   rm -f $i
>   ln -s /usr/share/automake-1.$am/$i $i
> done


Good find on this, both for whoever came up with it originally and
to you for finding it again.  Thanks!!!

Can you make a complete tarball of everything (just like you would
submit to us if the submission form were open) and mail it to me?
I'll get it added in our next update.

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

From rworkman at slackbuilds.org  Sat Aug 29 04:32:53 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 28 Aug 2009 23:32:53 -0500
Subject: [Slackbuilds-users] The plot thickens: A couple of 13.0
 questions
In-Reply-To: <4A984B7B.7050205@slackware.com>
References: <7f9823a6358cd35ccd97b0cb7982eb26.squirrel@squirrelmail.gigahost.dk>
	<20090828082458.751cd1f4@liberty.rlwhome.lan>
	<4A984B7B.7050205@slackware.com>
Message-ID: <20090828233253.3029ea73@liberty.rlwhome.lan>

On Fri, 28 Aug 2009 16:26:19 -0500
"Patrick J. Volkerding" <volkerdi at slackware.com> wrote:

> Robby Workman wrote:
> > On Fri, 28 Aug 2009 10:35:29 +0200
> > Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:
> > 
> >> So, a new day, a new Slackware version. Have looked at the RCs -
> >> interesting changes. Let's see what we can make out of this one!
> >> Competition is strong - the 12.2 was a very good release, in my
> >> opinion. Done torrenting down, now pushing. I will be preparing
> >> some updated versions of my Slackbuilds for the submission queue -
> >> I put off the version bumps until after the new release. Now, a
> >> couple of questions: After a cleanup of the Gnome dependencies,
> >> the development version of Abiword now builds on Slackware - with
> >> one exception: It requires libgsf to be rebuilt to include gio.
> > 
> > 
> > No, it doesn't: http://rlworkman.net/pkgs/13.0/
> > Well, I don't know about the development version, but if it requires
> > something that Slackware doesn't (yet) include, then I guess we'll
> > just stick to the stable version in our repository here.
> 
> I heard the same thing about goffice and gnumeric, but wasn't sure of 
> the side effects of enabling gio...  like, does it require other
> parts of GNOME to avoid routing data to a black hole?  I know there
> are gio things already included in glib, and had verified that libgsf
> compiles just fine with gio enabled.


The "black hole" concern is exactly why I never even suggested it
along the way to 13.0.  I know that the xfce devs have encountered
some issues in that area (stuff hardcoded to look for "gnome-mount"
and "gnome-terminal" and such), and I haven't had time to do any
testing at all with gio-enabled applications, so I simply don't
know how/if they're going to behave. 

 
> Probably it's something to float now in -current, but it seemed a
> little too risky as 13.0 approached.


Yep yep; we'll talk more on that later.  :-)

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

From rworkman at slackbuilds.org  Sat Aug 29 05:36:02 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 29 Aug 2009 00:36:02 -0500
Subject: [Slackbuilds-users] Medit page
In-Reply-To: <db7cda7351dee4cdab093035224d56a7.squirrel@squirrelmail.gigahost.dk>
References: <db7cda7351dee4cdab093035224d56a7.squirrel@squirrelmail.gigahost.dk>
Message-ID: <20090829003602.5d3e5b27@liberty.rlwhome.lan>

On Fri, 28 Aug 2009 21:54:58 +0200
Morten Juhl-Johansen Z?lde-Fej?r <mjjzf at syntaktisk.dk> wrote:

> Just a small detail:
> I was installing the editor Medit -
> http://slackbuilds.org/repository/13.0/development/medit/ - and the
> page says that PyGTK is available at Slackbuilds.
> I believe it is now included in Slackware, isn't that right?


Indeed it is.  Fixed ; thanks.

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

From rworkman at slackbuilds.org  Sat Aug 29 05:42:02 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 29 Aug 2009 00:42:02 -0500
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <1251181424.18017.1331471259@webmail.messagingengine.com>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
Message-ID: <20090829004202.3ce4cb9f@liberty.rlwhome.lan>

On Tue, 25 Aug 2009 09:23:44 +0300
"Grigorios Bouzakis" <grbzks at xsmail.com> wrote:

> It has come to my attention that the sumbitted scripts for packages
> that install info files in /usr/info, common mostly in GNU tools, 
> but not limited to those don't add entries to the /usr/info/dir 
> file which makes autocompletion fail.
> 
> AFAIK Pat ships a custom dir file making sure that the entries there
> reflect the packages part of Slackware. But if you install others 
> the dir file isn't updated, at least not for the ones i've checked 
> available on SBo.  I don't know what other implications this has, 
> since i don't use the info files much.  But i have 3 packages 
> installing one, msmtp, gtypist & ratpoison, & autocompletion fails 
> for them all.
> 
> To deal with this there could be something like the following in
> doinst.sh:
> 
> install-info /usr/info/$package.info $/usr/info/dir 2> /dev/null
> 
> that adds the entry to the dir file. Most tools in SBo don't have
> multiple info files like it happens for example with a2ps in 
> Slackware.
> 
> Of course that entry will stay there even if the custom installed
> package is unistalled. It would need something like
> install-info --delete /usr/info/$package.info $/usr/info/dir 2> /dev/null
> but Slackware doesnt have a way to do that automatically upon package
> removal.
> 
> Maybe it would be worth adding an entry to the doinst.sh in the
> template.SlackBuild?
> Thoughts?


If (and that *is* an *if*) we do this, we would need to do it in a 
way that's alternate-root safe.  Hypothetically speaking, if we do
it, what happens *when* a package is removed and info's dir file 
still has entry in it?  Does it simply enable autocompletion of a
now nonexistent file(name), or does it cause any actual problems?

FWIW, I'm wondering all of this while (again) cursing the idea 
that texinfo is somehow superior to mandoc.  Sheesh.

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

From grbzks at xsmail.com  Sat Aug 29 06:08:44 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sat, 29 Aug 2009 09:08:44 +0300
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <20090829004202.3ce4cb9f@liberty.rlwhome.lan>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
	<20090829004202.3ce4cb9f@liberty.rlwhome.lan>
Message-ID: <20090829060844.GA3565@dark>

On Sat, Aug 29, 2009 at 12:42:02AM -0500, Robby Workman wrote:
> On Tue, 25 Aug 2009 09:23:44 +0300
> "Grigorios Bouzakis" <grbzks at xsmail.com> wrote:
> 
> > It has come to my attention that the sumbitted scripts for packages
> > that install info files in /usr/info, common mostly in GNU tools, 
> > but not limited to those don't add entries to the /usr/info/dir 
> > file which makes autocompletion fail.
> > 
> > AFAIK Pat ships a custom dir file making sure that the entries there
> > reflect the packages part of Slackware. But if you install others 
> > the dir file isn't updated, at least not for the ones i've checked 
> > available on SBo.  I don't know what other implications this has, 
> > since i don't use the info files much.  But i have 3 packages 
> > installing one, msmtp, gtypist & ratpoison, & autocompletion fails 
> > for them all.
> > 
> > To deal with this there could be something like the following in
> > doinst.sh:
> > 
> > install-info /usr/info/$package.info $/usr/info/dir 2> /dev/null
> > 
> > that adds the entry to the dir file. Most tools in SBo don't have
> > multiple info files like it happens for example with a2ps in 
> > Slackware.
> > 
> > Of course that entry will stay there even if the custom installed
> > package is unistalled. It would need something like
> > install-info --delete /usr/info/$package.info $/usr/info/dir 2> /dev/null
> > but Slackware doesnt have a way to do that automatically upon package
> > removal.
> > 
> > Maybe it would be worth adding an entry to the doinst.sh in the
> > template.SlackBuild?
> > Thoughts?
> 
> 
> If (and that *is* an *if*) we do this, we would need to do it in a 
> way that's alternate-root safe.  Hypothetically speaking, if we do
> it, what happens *when* a package is removed and info's dir file 
> still has entry in it?  Does it simply enable autocompletion of a
> now nonexistent file(name), or does it cause any actual problems?
> 
> FWIW, I'm wondering all of this while (again) cursing the idea 
> that texinfo is somehow superior to mandoc.  Sheesh.
> 
> -RW

What happens here for example with 'info xboard' which i don't have
installed, is that instead of opening the info file which is missing, you
are presented with the contents of the dir file, so you can choose
another info file to look at. If you choose xboard it returns 'xboard:
no such file or directory'.
I don't think having entries for not existant info files in dir causes
any trouble, but on the other hand not updating the dir file, which is
how things work now, doesn't either.
You just can't complete them in command line, and invocking texinfo by
executing just info which gives you the contents of the dir file won't
present you with an option to view the info file for the application you
installed outside of Slackware.

BTW the entries above are not completely corrent. They should be:
install-info /usr/info/$PKGNAM.info /usr/info/dir 2> /dev/null
& install-info --delete /usr/info/$PKGNAM.info /usr/info/dir 2>
/dev/null

This could also be added into the info part of the SlackBuild eg.
# Compress info pages and remove the package's dir file
# If no info pages are installed by the software, don't leave this in
# the script
rm -f $PKG/usr/info/dir
gzip -9 $PKG/usr/info/*.info*
install-info /usr/info/$PKGNAM.info /usr/info/dir 2> /dev/null

instead of the doinst.sh script

-- 
Greg

From xgizzmo at slackbuilds.org  Sat Aug 29 09:47:28 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Sat, 29 Aug 2009 05:47:28 -0400
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <20090829060844.GA3565@dark>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
	<20090829004202.3ce4cb9f@liberty.rlwhome.lan>
	<20090829060844.GA3565@dark>
Message-ID: <200908290547.29192.xgizzmo@slackbuilds.org>

On Saturday 29 August 2009 02:08:44 Grigorios Bouzakis wrote:
> This could also be added into the info part of the SlackBuild eg.
> # Compress info pages and remove the package's dir file
> # If no info pages are installed by the software, don't leave this in
> # the script
> rm -f $PKG/usr/info/dir
> gzip -9 $PKG/usr/info/*.info*
> install-info /usr/info/$PKGNAM.info /usr/info/dir 2> /dev/null
> 
> instead of the doinst.sh script
> 

That will put the the information in the build system which may 
or may not be the system you are installing the package on.

--dsomero

From grbzks at xsmail.com  Sat Aug 29 10:07:59 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sat, 29 Aug 2009 13:07:59 +0300
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <200908290547.29192.xgizzmo@slackbuilds.org>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
	<20090829004202.3ce4cb9f@liberty.rlwhome.lan>
	<20090829060844.GA3565@dark>
	<200908290547.29192.xgizzmo@slackbuilds.org>
Message-ID: <20090829100758.GA4676@dark>

On Sat, Aug 29, 2009 at 05:47:28AM -0400, xgizzmo at slackbuilds.org wrote:
> On Saturday 29 August 2009 02:08:44 Grigorios Bouzakis wrote:
> > This could also be added into the info part of the SlackBuild eg.
> > # Compress info pages and remove the package's dir file
> > # If no info pages are installed by the software, don't leave this in
> > # the script
> > rm -f $PKG/usr/info/dir
> > gzip -9 $PKG/usr/info/*.info*
> > install-info /usr/info/$PKGNAM.info /usr/info/dir 2> /dev/null
> > 
> > instead of the doinst.sh script
> > 
> 
> That will put the the information in the build system which may 
> or may not be the system you are installing the package on.
> 
> --dsomero

Oh right. /usr/info/dir can't/shouldn't be altered from the build
script. I guess the only way would be to add
install-info /usr/info/$PRGNAM.info /usr/info/dir 2> /dev/null
to the doinst.sh.
But even then, it can't work automatically. $PRGNAM has to be replaced
with the actual name of the file(s)

-- 
Greg

From grbzks at xsmail.com  Sat Aug 29 11:43:59 2009
From: grbzks at xsmail.com (Grigorios Bouzakis)
Date: Sat, 29 Aug 2009 14:43:59 +0300
Subject: [Slackbuilds-users] info files on submitted packages
In-Reply-To: <20090829100758.GA4676@dark>
References: <1251181424.18017.1331471259@webmail.messagingengine.com>
	<20090829004202.3ce4cb9f@liberty.rlwhome.lan>
	<20090829060844.GA3565@dark>
	<200908290547.29192.xgizzmo@slackbuilds.org>
	<20090829100758.GA4676@dark>
Message-ID: <20090829114359.GA3562@dark>

On Sat, Aug 29, 2009 at 01:07:58PM +0300, Grigorios Bouzakis wrote:
> On Sat, Aug 29, 2009 at 05:47:28AM -0400, xgizzmo at slackbuilds.org wrote:
> > On Saturday 29 August 2009 02:08:44 Grigorios Bouzakis wrote:
> > > This could also be added into the info part of the SlackBuild eg.
> > > # Compress info pages and remove the package's dir file
> > > # If no info pages are installed by the software, don't leave this in
> > > # the script
> > > rm -f $PKG/usr/info/dir
> > > gzip -9 $PKG/usr/info/*.info*
> > > install-info /usr/info/$PKGNAM.info /usr/info/dir 2> /dev/null
> > > 
> > > instead of the doinst.sh script
> > > 
> > 
> > That will put the the information in the build system which may 
> > or may not be the system you are installing the package on.
> > 
> > --dsomero
> 
> Oh right. /usr/info/dir can't/shouldn't be altered from the build
> script. I guess the only way would be to add
> install-info /usr/info/$PRGNAM.info /usr/info/dir 2> /dev/null
> to the doinst.sh.
> But even then, it can't work automatically. $PRGNAM has to be replaced
> with the actual name of the file(s)
> 

And since the info files are normally gzipped in the SlackBuild, it
should be eg. for msmtp:
install-info /usr/info/msmtp.info.gz /usr/info/dir 2> /dev/null

-- 
Greg

From willysr at gmail.com  Sun Aug 30 04:43:57 2009
From: willysr at gmail.com (Willy Sudiarto Raharjo)
Date: Sun, 30 Aug 2009 11:43:57 +0700
Subject: [Slackbuilds-users] Wrong Version Number on NVIdia Legacy 96.43.11
Message-ID: <6db5b9f70908292143h12737e45neb489fbd0f604ab0@mail.gmail.com>

Hello

http://slackbuilds.org/repository/13.0/system/nvidia-legacy96-kernel/
http://slackbuilds.org/repository/13.0/system/nvidia-legacy96-driver/

Both lists 96.43.13 on the version, but in this page
http://slackbuilds.org/result/?search=nvidia&sv=13.0 it showed as
96.43.11


-- 
Willy Sudiarto Raharjo
Registered Linux User : 336579
Web : http://www.informatix.or.id/willy
Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com

From ml at mareichelt.de  Sun Aug 30 13:51:40 2009
From: ml at mareichelt.de (markus reichelt)
Date: Sun, 30 Aug 2009 15:51:40 +0200
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
Message-ID: <20090830135140.GA5563@tatooine.rebelbase.local>

Its buildscript states:

"NOTE: This will not build on a stock x86_64 system."

Kind of a bummer for me, sitting on a fresh install of 13-64...

So, are there any workarounds/plans to get this hummer talking to us
-64 users?

-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090830/72a6fa6b/attachment.sig>

From pprkut at liwjatan.at  Sun Aug 30 14:45:02 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Sun, 30 Aug 2009 16:45:02 +0200
Subject: [Slackbuilds-users] Wrong Version Number on NVIdia Legacy
	96.43.11
In-Reply-To: <6db5b9f70908292143h12737e45neb489fbd0f604ab0@mail.gmail.com>
References: <6db5b9f70908292143h12737e45neb489fbd0f604ab0@mail.gmail.com>
Message-ID: <200908301645.09207.pprkut@liwjatan.at>

On Sunday 30 August 2009 06:43:57 Willy Sudiarto Raharjo wrote:
> Hello
>
> http://slackbuilds.org/repository/13.0/system/nvidia-legacy96-kernel/
> http://slackbuilds.org/repository/13.0/system/nvidia-legacy96-driver/
>
> Both lists 96.43.13 on the version, but in this page
> http://slackbuilds.org/result/?search=nvidia&sv=13.0 it showed as
> 96.43.11

Thanks for the report! Fixed.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090830/bf2973b2/attachment.sig>

From pprkut at liwjatan.at  Sun Aug 30 14:50:17 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Sun, 30 Aug 2009 16:50:17 +0200
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <20090830135140.GA5563@tatooine.rebelbase.local>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
Message-ID: <200908301650.17529.pprkut@liwjatan.at>

On Sunday 30 August 2009 15:51:40 markus reichelt wrote:
> Its buildscript states:
>
> "NOTE: This will not build on a stock x86_64 system."
>
> Kind of a bummer for me, sitting on a fresh install of 13-64...
>
> So, are there any workarounds/plans to get this hummer talking to us
> -64 users?

Unfortunately the only way to get vbox on slack64 is by either running the 
binary build (ie virtualbox puel), or by installing 32bit-compat libs for the 
compilation.

Virtualbox needs the gcc, g++ and glibc 32bit components, but only on build 
time. It runs fine without them, so you can remove those packages again after 
building the package.

I tried to talk to the vbox devs already weeks ago, making them aware of the 
situation that slack64 doesn't have 32bit compat libs included, but no luck.
They don't seem to care enough about such an "exotic" system.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090830/f986884e/attachment.sig>

From ml at mareichelt.de  Sun Aug 30 15:33:49 2009
From: ml at mareichelt.de (markus reichelt)
Date: Sun, 30 Aug 2009 17:33:49 +0200
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <200908301650.17529.pprkut@liwjatan.at>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<200908301650.17529.pprkut@liwjatan.at>
Message-ID: <20090830153349.GB5563@tatooine.rebelbase.local>

* Heinz Wiesinger <pprkut at liwjatan.at> wrote:

> > So, are there any workarounds/plans to get this hummer talking to us
> > -64 users?
> 
> Unfortunately the only way to get vbox on slack64 is by either
> running the binary build (ie virtualbox puel), or by installing
> 32bit-compat libs for the compilation.
> 
> Virtualbox needs the gcc, g++ and glibc 32bit components, but only
> on build time. It runs fine without them, so you can remove those
> packages again after building the package.

Where do I find these?

I just installed slack13-64 on a new machine and this is my first
time fiddling around with a pure 64bit OS. I am compiling some
essential packages for personal use, no probs so far (util-linux-ng
with loop-AES support, aespipe, dietlibc, ...).

But really, VirtualBox is a must for me these days.


> I tried to talk to the vbox devs already weeks ago, making them
> aware of the situation that slack64 doesn't have 32bit compat libs
> included, but no luck. They don't seem to care enough about such an
> "exotic" system.

Doesn't sound too promising... I'll gladly chime in. Who knows, maybe
they just need a little push to come to their senses.

-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090830/4bd3f2ee/attachment.sig>

From banderols at gmail.com  Sun Aug 30 17:03:41 2009
From: banderols at gmail.com (Murat D. Kadirov)
Date: Sun, 30 Aug 2009 23:03:41 +0600
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <20090830153349.GB5563@tatooine.rebelbase.local>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<200908301650.17529.pprkut@liwjatan.at>
	<20090830153349.GB5563@tatooine.rebelbase.local>
Message-ID: <20090830170341.GA5556@appolo>

On Sun, Aug 30, 2009 at 05:33:49PM +0200, markus reichelt wrote:
> * Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> 
> > > So, are there any workarounds/plans to get this hummer talking to us
> > > -64 users?
> > 
> > Unfortunately the only way to get vbox on slack64 is by either
> > running the binary build (ie virtualbox puel), or by installing
> > 32bit-compat libs for the compilation.
> > 
> > Virtualbox needs the gcc, g++ and glibc 32bit components, but only
> > on build time. It runs fine without them, so you can remove those
> > packages again after building the package.
> 
> Where do I find these?

http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib

-- 
Murat D. Kadirov
PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6  76EE 1B97 0A0E CEC0 6AA0

From rworkman at slackbuilds.org  Sun Aug 30 17:07:27 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Aug 2009 12:07:27 -0500
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <20090830153349.GB5563@tatooine.rebelbase.local>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<200908301650.17529.pprkut@liwjatan.at>
	<20090830153349.GB5563@tatooine.rebelbase.local>
Message-ID: <20090830120727.390f29be@liberty.rlwhome.lan>

On Sun, 30 Aug 2009 17:33:49 +0200
markus reichelt <ml at mareichelt.de> wrote:

> * Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> 
> > > So, are there any workarounds/plans to get this hummer talking to
> > > us -64 users?
> > 
> > Unfortunately the only way to get vbox on slack64 is by either
> > running the binary build (ie virtualbox puel), or by installing
> > 32bit-compat libs for the compilation.
> > 
> > Virtualbox needs the gcc, g++ and glibc 32bit components, but only
> > on build time. It runs fine without them, so you can remove those
> > packages again after building the package.
> 
> Where do I find these?
> 
> I just installed slack13-64 on a new machine and this is my first
> time fiddling around with a pure 64bit OS. I am compiling some
> essential packages for personal use, no probs so far (util-linux-ng
> with loop-AES support, aespipe, dietlibc, ...).
> 
> But really, VirtualBox is a must for me these days.


The binary-only is fine - I've been using it on x86_64 since
well before any of you knew we had an x86_64 version :-)


> > I tried to talk to the vbox devs already weeks ago, making them
> > aware of the situation that slack64 doesn't have 32bit compat libs
> > included, but no luck. They don't seem to care enough about such an
> > "exotic" system.
> 
> Doesn't sound too promising... I'll gladly chime in. Who knows, maybe
> they just need a little push to come to their senses.


Well, as with everything else, sometimes the effort/time required
to do something isn't worth the payoff.  I don't *know* that this
is one of those, but it very well could be.

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

From mickeytintincolle at yahoo.fr  Sun Aug 30 17:44:37 2009
From: mickeytintincolle at yahoo.fr (Antoine NONYME)
Date: Sun, 30 Aug 2009 19:44:37 +0200
Subject: [Slackbuilds-users] PokerTH slackbuild
Message-ID: <20090830194437.3dcdf2a1@slack.volderking.com>

The SlackBuild in PokerTH contains the qmake command "qmake-qt4
pokerth.pro" but in my Slack 13.0 system qmake-qt4 doesn't exists and
should be replaced by "qmake pokerth.pro" .

From rworkman at slackbuilds.org  Sun Aug 30 19:07:55 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Aug 2009 14:07:55 -0500
Subject: [Slackbuilds-users] PokerTH slackbuild
In-Reply-To: <20090830194437.3dcdf2a1@slack.volderking.com>
References: <20090830194437.3dcdf2a1@slack.volderking.com>
Message-ID: <20090830140755.5abbbe30@liberty.rlwhome.lan>

On Sun, 30 Aug 2009 19:44:37 +0200
Antoine NONYME <mickeytintincolle at yahoo.fr> wrote:

> The SlackBuild in PokerTH contains the qmake command "qmake-qt4
> pokerth.pro" but in my Slack 13.0 system qmake-qt4 doesn't exists and
> should be replaced by "qmake pokerth.pro" .


Thanks; this will be fixed in the next update.

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

From mickeytintincolle at yahoo.fr  Sun Aug 30 19:26:38 2009
From: mickeytintincolle at yahoo.fr (Antoine NONYME)
Date: Sun, 30 Aug 2009 21:26:38 +0200
Subject: [Slackbuilds-users] Qemu SlackBuild
Message-ID: <20090830212638.3a9c377a@slack.volderking.com>

The compiling of qemu requires the "texi2html" command that I don't
have althrough every package of the "t" series is installed . I
compiled the SlackBuild by creating a blank
executable /usr/bin/texi2html file and commenting "set -e" in the
SlackBuild, but it is obviously a bad solution .

From xgizzmo at slackbuilds.org  Sun Aug 30 19:31:52 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Sun, 30 Aug 2009 15:31:52 -0400
Subject: [Slackbuilds-users] Qemu SlackBuild
In-Reply-To: <20090830212638.3a9c377a@slack.volderking.com>
References: <20090830212638.3a9c377a@slack.volderking.com>
Message-ID: <200908301531.52236.xgizzmo@slackbuilds.org>

On Sunday 30 August 2009 15:26:38 Antoine NONYME wrote:
> The compiling of qemu requires the "texi2html" command that I don't
> have althrough every package of the "t" series is installed . I
> compiled the SlackBuild by creating a blank
> executable /usr/bin/texi2html file and commenting "set -e" in the
> SlackBuild, but it is obviously a bad solution .
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 
> 

You have to be logged in with root's profile.
That means you have to use "su -" not "su" or
you have to log yourself in as root user at 
the login prompt.

--dsomero

From mickeytintincolle at yahoo.fr  Sun Aug 30 19:39:39 2009
From: mickeytintincolle at yahoo.fr (Antoine NONYME)
Date: Sun, 30 Aug 2009 21:39:39 +0200
Subject: [Slackbuilds-users] Qemu SlackBuild
In-Reply-To: <200908301531.52236.xgizzmo@slackbuilds.org>
References: <20090830212638.3a9c377a@slack.volderking.com>
	<200908301531.52236.xgizzmo@slackbuilds.org>
Message-ID: <20090830213939.364ba2f4@slack.volderking.com>

Le Sun, 30 Aug 2009 15:31:52 -0400,
xgizzmo at slackbuilds.org a ?crit :

> On Sunday 30 August 2009 15:26:38 Antoine NONYME wrote:
> > The compiling of qemu requires the "texi2html" command that I don't
> > have althrough every package of the "t" series is installed . I
> > compiled the SlackBuild by creating a blank
> > executable /usr/bin/texi2html file and commenting "set -e" in the
> > SlackBuild, but it is obviously a bad solution .
> 
> You have to be logged in with root's profile.
> That means you have to use "su -" not "su" or
> you have to log yourself in as root user at 
> the login prompt.
> 
> --dsomero

Thanks you . This "issue" should be noted in the README file, because
some people (or software) are stupid :)


From timp at timp.com.au  Sun Aug 30 21:40:40 2009
From: timp at timp.com.au (Timothy Pollard)
Date: Mon, 31 Aug 2009 07:40:40 +1000
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <20090830120727.390f29be@liberty.rlwhome.lan>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<200908301650.17529.pprkut@liwjatan.at>
	<20090830153349.GB5563@tatooine.rebelbase.local>
	<20090830120727.390f29be@liberty.rlwhome.lan>
Message-ID: <20090831074040.2b93b6a3@shammah.timp.com.au>

On Sun, 30 Aug 2009 12:07:27 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:
> On Sun, 30 Aug 2009 17:33:49 +0200
> markus reichelt <ml at mareichelt.de> wrote:
> 
> > * Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> > 
> > > > So, are there any workarounds/plans to get this hummer talking to
> > > > us -64 users?
> > > 
> > > Unfortunately the only way to get vbox on slack64 is by either
> > > running the binary build (ie virtualbox puel), or by installing
> > > 32bit-compat libs for the compilation.
> > > ...
> > 
> > ...
> > But really, VirtualBox is a must for me these days.
> 
> 
> The binary-only is fine - I've been using it on x86_64 since
> well before any of you knew we had an x86_64 version :-)
> ...
> 
> -RW

Do you use a SlackBuild for that or just use the official installer? 

-- 
TimP
[http://blog.timp.com.au]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090831/b0c5ddb4/attachment.asc>

From rworkman at slackbuilds.org  Mon Aug 31 03:24:22 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Aug 2009 22:24:22 -0500
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <20090831074040.2b93b6a3@shammah.timp.com.au>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<200908301650.17529.pprkut@liwjatan.at>
	<20090830153349.GB5563@tatooine.rebelbase.local>
	<20090830120727.390f29be@liberty.rlwhome.lan>
	<20090831074040.2b93b6a3@shammah.timp.com.au>
Message-ID: <20090830222422.26ee103c@liberty.rlwhome.lan>

On Mon, 31 Aug 2009 07:40:40 +1000
Timothy Pollard <timp at timp.com.au> wrote:

> On Sun, 30 Aug 2009 12:07:27 -0500
> Robby Workman <rworkman at slackbuilds.org> wrote:
> > On Sun, 30 Aug 2009 17:33:49 +0200
> > markus reichelt <ml at mareichelt.de> wrote:
> > 
> > > * Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> > > 
> > > > > So, are there any workarounds/plans to get this hummer
> > > > > talking to us -64 users?
> > > > 
> > > > Unfortunately the only way to get vbox on slack64 is by either
> > > > running the binary build (ie virtualbox puel), or by installing
> > > > 32bit-compat libs for the compilation.
> > > > ...
> > > 
> > > ...
> > > But really, VirtualBox is a must for me these days.
> > 
> > 
> > The binary-only is fine - I've been using it on x86_64 since
> > well before any of you knew we had an x86_64 version :-)
> > ...
> > 
> 
> Do you use a SlackBuild for that or just use the official installer? 


I just let the installer do its thing.

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

From rworkman at slackbuilds.org  Mon Aug 31 03:51:38 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Aug 2009 22:51:38 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <3d32cb0a0908201101p5fc5a5bgc680d8883fb924db@mail.gmail.com>
References: <3d32cb0a0908201101p5fc5a5bgc680d8883fb924db@mail.gmail.com>
Message-ID: <20090830225138.0d40eb39@liberty.rlwhome.lan>

On Thu, 20 Aug 2009 14:01:39 -0400
Matthew Fillpot <mfilpot at gmail.com> wrote:

> I do not see yakuake or Urban Terror on the Unchecked Entries list.
> 
> Do we have a new build of yakuake that works on KDE4 and QT4, or is
> this an orphaned package looking for a new maintainer? I have a well
> tested script to build yakuake with kmake and the modified
> dependencies that is ready for submission if necessary.
> 
> The UrbanTerror build script needs modified to reference the updated
> libcurl libraries, without the update the users are unable to
> download maps from game servers. I will be submitting the updated
> archive later today.


I guess you saw that both of those were fixed up by us.
Yakuake should be fine regardless, but if UT still needs work,
let us know.

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

From listreader at lupulin.net  Mon Aug 31 03:55:02 2009
From: listreader at lupulin.net (paul wisehart)
Date: Sun, 30 Aug 2009 23:55:02 -0400
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <20090830225138.0d40eb39@liberty.rlwhome.lan>
References: <3d32cb0a0908201101p5fc5a5bgc680d8883fb924db@mail.gmail.com>
	<20090830225138.0d40eb39@liberty.rlwhome.lan>
Message-ID: <4A9B4996.6060305@lupulin.net>

Robby Workman wrote:
> On Thu, 20 Aug 2009 14:01:39 -0400
> Matthew Fillpot <mfilpot at gmail.com> wrote:
> 
>> I do not see yakuake or Urban Terror on the Unchecked Entries list.
>>
>> Do we have a new build of yakuake that works on KDE4 and QT4, or is
>> this an orphaned package looking for a new maintainer? I have a well
>> tested script to build yakuake with kmake and the modified
>> dependencies that is ready for submission if necessary.
>>
>> The UrbanTerror build script needs modified to reference the updated
>> libcurl libraries, without the update the users are unable to
>> download maps from game servers. I will be submitting the updated
>> archive later today.
> 
> 
> I guess you saw that both of those were fixed up by us.
> Yakuake should be fine regardless, but if UT still needs work,
> let us know.
> 

anybody play the superman map?


From rworkman at slackbuilds.org  Mon Aug 31 04:03:43 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Aug 2009 23:03:43 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <200908231120.47528.carlos@strangeworlds.co.uk>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<200908231120.47528.carlos@strangeworlds.co.uk>
Message-ID: <20090830230343.2df8415b@liberty.rlwhome.lan>

On Sun, 23 Aug 2009 11:20:47 +0100
Carlos Corbacho <carlos at strangeworlds.co.uk> wrote:

> On Monday 10 August 2009 20:55:39 Robby Workman wrote:
> > As I promised several people privately, here's a list of things
> > that we have not had time to check/update for 13.0 yet:
> >   http://slackbuilds.org/NOT_CHECKED
> 
> development/django/
> development/stgit/
> 
> Work fine here on Slackware64. (Given they're both pure Python
> packages, I'd be surprised if they doesn't work on i486, but I can't
> test that).


Both are queued for addition in the next update, and I changed the
maintainer of django to you.


> Also, there was some discussion recently about the architecture that
> should be set for Python packages - was an official decision reached?
> I couldn't find anything on the SBo site.


Yes, python and perl (and anything else that puts things in a *64/ 
directory should be ARCH=${ARCH:-i486}.

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

From rworkman at slackbuilds.org  Mon Aug 31 04:45:06 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 30 Aug 2009 23:45:06 -0500
Subject: [Slackbuilds-users] Unchecked entries for 13.0
In-Reply-To: <45193.88.149.157.90.1251214932.squirrel@webmail.slackware.it>
References: <20090810145539.0d92fe91@liberty.rlwhome.lan>
	<45193.88.149.157.90.1251214932.squirrel@webmail.slackware.it>
Message-ID: <20090830234506.134a837c@liberty.rlwhome.lan>

On Tue, 25 Aug 2009 17:42:12 +0200 (CEST)
"Marco Bonetti" <marco.bonetti at slackware.it> wrote:

> + SocksiPy: it uses the python packages building system, I just add a
> setup.py as it lacks one so it should be ok


This is fine; added in next update.


> + hping3: looks ok to me


This errors out with endian issues on x86_64.  Probably a trivial
fix, but no time to investigate right now.  If someone on a 64bit
system wants to have a go at it, feel free.  While you're at it,
have a look at making it use our SLKCFLAGS too.


> + mozilla-prism: this is 32bit only binary repackage. I could try
> with a source build but this option has very low priority right
> now ;-)


Yep, I'm ignoring this one for now.


> + w3af: noarch package installed into /opt, it's ok.


Added in next update.

Thanks! 

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

From pprkut at liwjatan.at  Sun Aug 30 21:19:03 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Sun, 30 Aug 2009 23:19:03 +0200
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <20090830120727.390f29be@liberty.rlwhome.lan>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<20090830153349.GB5563@tatooine.rebelbase.local>
	<20090830120727.390f29be@liberty.rlwhome.lan>
Message-ID: <200908302319.06295.pprkut@liwjatan.at>

On Sunday 30 August 2009 19:07:27 Robby Workman wrote:
> On Sun, 30 Aug 2009 17:33:49 +0200
>
> markus reichelt <ml at mareichelt.de> wrote:
> > * Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> > > > So, are there any workarounds/plans to get this hummer talking to
> > > > us -64 users?
> > >
> > > Unfortunately the only way to get vbox on slack64 is by either
> > > running the binary build (ie virtualbox puel), or by installing
> > > 32bit-compat libs for the compilation.
> > >
> > > Virtualbox needs the gcc, g++ and glibc 32bit components, but only
> > > on build time. It runs fine without them, so you can remove those
> > > packages again after building the package.
> >
> > Where do I find these?
> >
> > I just installed slack13-64 on a new machine and this is my first
> > time fiddling around with a pure 64bit OS. I am compiling some
> > essential packages for personal use, no probs so far (util-linux-ng
> > with loop-AES support, aespipe, dietlibc, ...).
> >
> > But really, VirtualBox is a must for me these days.
>
> The binary-only is fine - I've been using it on x86_64 since
> well before any of you knew we had an x86_64 version :-)

I agree. For most people the binary installer might be the best idea for now. 
But, just to clarify, the once built slackware package of virtualbox-ose 
hasn't any 32bit deps either.

> > > I tried to talk to the vbox devs already weeks ago, making them
> > > aware of the situation that slack64 doesn't have 32bit compat libs
> > > included, but no luck. They don't seem to care enough about such an
> > > "exotic" system.
> >
> > Doesn't sound too promising... I'll gladly chime in. Who knows, maybe
> > they just need a little push to come to their senses.
>
> Well, as with everything else, sometimes the effort/time required
> to do something isn't worth the payoff.  I don't *know* that this
> is one of those, but it very well could be.

This may very well be the case, which is why I didn't pursue this any further. 
The developers stated their opinion on this matter and it's their software 
after all.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090830/73ed4263/attachment.sig>

From chaos.proton at gmail.com  Mon Aug 31 06:33:10 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Mon, 31 Aug 2009 14:33:10 +0800
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <200908302319.06295.pprkut@liwjatan.at>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<20090830153349.GB5563@tatooine.rebelbase.local>
	<20090830120727.390f29be@liberty.rlwhome.lan>
	<200908302319.06295.pprkut@liwjatan.at>
Message-ID: <a0adeea50908302333v4e018317gb16454d9630a7e70@mail.gmail.com>

On Mon, Aug 31, 2009 at 05:19, Heinz Wiesinger<pprkut at liwjatan.at> wrote:
> On Sunday 30 August 2009 19:07:27 Robby Workman wrote:
>> The binary-only is fine - I've been using it on x86_64 since
>> well before any of you knew we had an x86_64 version :-)
>
> I agree. For most people the binary installer might be the best idea for now.
> But, just to clarify, the once built slackware package of virtualbox-ose
> hasn't any 32bit deps either.
>

Yes. Once you build a package, it hasn't any 32bit deps. But, does SBo
provide any binary packages? NO. What if a user runs Slackware64 but
doesn't have 32bit slackware in hand? I know you can always run the
installer and let it pour files into /opt but we are talking about
SlackBuilds which users can make use of the package system of
Slackware, right?

Is there any way to build package from the VBox installer? If so, it
may become independent from the 32bit build environment.

-- 
Cheers,
Grissiom

From pprkut at liwjatan.at  Mon Aug 31 07:12:07 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Mon, 31 Aug 2009 09:12:07 +0200
Subject: [Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
In-Reply-To: <a0adeea50908302333v4e018317gb16454d9630a7e70@mail.gmail.com>
References: <20090830135140.GA5563@tatooine.rebelbase.local>
	<200908302319.06295.pprkut@liwjatan.at>
	<a0adeea50908302333v4e018317gb16454d9630a7e70@mail.gmail.com>
Message-ID: <200908310912.10426.pprkut@liwjatan.at>

On Monday 31 August 2009 08:33:10 Grissiom wrote:
> On Mon, Aug 31, 2009 at 05:19, Heinz Wiesinger<pprkut at liwjatan.at> wrote:
> > On Sunday 30 August 2009 19:07:27 Robby Workman wrote:
> >> The binary-only is fine - I've been using it on x86_64 since
> >> well before any of you knew we had an x86_64 version :-)
> >
> > I agree. For most people the binary installer might be the best idea for
> > now. But, just to clarify, the once built slackware package of
> > virtualbox-ose hasn't any 32bit deps either.
>
> Yes. Once you build a package, it hasn't any 32bit deps. But, does SBo
> provide any binary packages? NO.

That is why there's the note in the README and why it's marked as UNTESTED on 
x86_64 in the .info file.

> What if a user runs Slackware64 but doesn't have 32bit slackware in hand?

Then he is unable to build virtualbox-ose.

> I know you can always run the installer and let it pour files into /opt but
> we are talking about SlackBuilds which users can make use of the package 
> system of Slackware, right?

Sure, but virtualbox-puel has a lot more constraints to handle then 
virtualbox-ose. In short, you will never get that kind of system integration -
ose has with -puel. So even if there was a SlackBuild for it, it would most 
likely still put everything in /opt.

> Is there any way to build package from the VBox installer? If so, it
> may become independent from the 32bit build environment.

There sure is a way to make a SlackBuild for virtualbox-puel (the -kernel part 
is the same for both I think). That being said, I'm not going to write one, 
but will happily have a look on it when someone submits one.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090831/868d407b/attachment.sig>

From marco.bonetti at slackware.it  Mon Aug 31 08:43:44 2009
From: marco.bonetti at slackware.it (Marco Bonetti)
Date: Mon, 31 Aug 2009 10:43:44 +0200 (CEST)
Subject: [Slackbuilds-users] Unchecked entries for 13.0
Message-ID: <52828.88.149.157.90.1251708224.squirrel@webmail.slackware.it>

On Mon, August 31, 2009 06:45, Robby Workman wrote:
>> + hping3: looks ok to me
>
>
> This errors out with endian issues on x86_64.  Probably a trivial fix,
but no time to investigate right now.  If someone on a 64bit system
wants to have a go at it, feel free.  While you're at it, have a look at
making it use our SLKCFLAGS too.
ok, I'll address it: I've got one machine upgraded to slackware-13.0 and a
slackware64-13.0 in the near future, but not sooner.

> Thanks!
Thanks to you and your team for the work you put into slackbuilds.org!

by the way, after the slackware-13.0 upgrade I tried out some packages I
need on that machine which are not owned by me, here some reports: +
deluge: it spits out a lot of warning but it runs ok, I suppose they are
just due to the python upgrade so I think version upgrading the package
will just ix it
+ tvtime: it works very well.

ciao

-- 
Marco Bonetti
BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/

My GnuPG key id: 0x0B60BC5F



-- 
Marco Bonetti
BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/

My GnuPG key id: 0x0B60BC5F


From chris.abela at maltats.com  Mon Aug 31 14:38:52 2009
From: chris.abela at maltats.com (Chris Abela)
Date: Mon, 31 Aug 2009 16:38:52 +0200
Subject: [Slackbuilds-users] Ponderings on gc.SlackBuild
Message-ID: <E1Mi825-00038C-Lf@fender55.maltanet.net>

Hi All,

1. The gc.SlackBuild puts the man file in /usr/man/man1/

> mkdir -p $PKG/usr/man/man1
> mv $PKG/usr/share/gc/gc.man $PKG/usr/man/man1/gc.1
> gzip -9 $PKG/usr/man/man1/gc.1

While the first line in the man file suggests that this is the correct
place, I suspect that gc is a C library Function, not a User Command and
thus /usr/man/man3 would have been more appropriate:

< mkdir -p $PKG/usr/man/man3
< mv $PKG/usr/share/gc/gc.man $PKG/usr/man/man3/gc.3
< gzip -9 $PKG/usr/man/man3/gc.3

2. The gc homepage recommend Version 6.8.
While the slackbuilds.org links to Version 7.1, the Slackbuild also works
for gc6.8
"Typically several versions will be available. Usually you should first try
to use gc_source/gc.tar.gz". If that fails, then we should try Version 7.1.
gc6.8 builds fine here.
Why was it decided agains the recommendations of the source author?

3. The link from /usr/doc/gc-$VERSION to /usr/share/gc is perhaps
superflous. Slackers know where to find their docs, right :-) ?

Chris



From mjjzf at syntaktisk.dk  Mon Aug 31 15:26:25 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Mon, 31 Aug 2009 17:26:25 +0200
Subject: [Slackbuilds-users] Slim Slackbuild
Message-ID: <20090831172625.5fb1732e@espero.syntaktisk.dk>

I saw that Slim hadn't made it into the 13.0 Slackbuilds repo; but I
checked out the 12.2 build, and it worked as it should on 13.0.

Yours,
Morten

__
Morten Juhl-Johansen Z?lde-Fej?r
mjjzf at syntaktisk.dk * http://syntaktisk.dk