From rworkman at slackbuilds.org  Wed Jul  1 04:12:25 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 30 Jun 2009 23:12:25 -0500
Subject: [Slackbuilds-users] Future Build Scripts
In-Reply-To: <138475.91316.qm@web37501.mail.mud.yahoo.com>
References: <138475.91316.qm@web37501.mail.mud.yahoo.com>
Message-ID: <20090630231225.692400d4@liberty.rlwhome.lan>

On Sun, 28 Jun 2009 14:15:53 -0700 (PDT)
Darrell Anderson <humanreadable at yahoo.com> wrote:

> When 13.0 is released, will the slackbuilds.org build scripts
> continue supporting the older tgz format, the newer txz format, or
> the option to use either?


After some discussion, we have decided that we will continue to
use .tgz for all of our scripts, at least for 13.0.  There will not be
a variable to make this configurable.

We might revisit this again for 13.1, depending on how many other
changes we have to make for that release.  The 13.0 release has brought
so many changes to us that we're a bit overwhelmed at the moment, and
the package compression is just *way* down the ladder with respect to
things that are actually important.

As an aside (a related one though), disk space is cheap.  Anyone using
SlackBuilds most likely has plenty of disk space available, so
compression of the packages is not a huge issue anyway.  The added time
required to build a txz package isn't exactly trivial either, but
as with everything else, stuff that's important to one person might
not be to another person.  In any event, if one prefers to make .txz
packages with our scripts, sed will be their friend.

-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/20090630/d21fa586/attachment.asc>

From chaos.proton at gmail.com  Wed Jul  1 07:52:52 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Wed, 1 Jul 2009 15:52:52 +0800
Subject: [Slackbuilds-users] Future Build Scripts
In-Reply-To: <Pine.LNX.4.61.0906291001430.29184@door.barrier.lan>
References: <138475.91316.qm@web37501.mail.mud.yahoo.com>
	<Pine.LNX.4.61.0906291001430.29184@door.barrier.lan>
Message-ID: <a0adeea50907010052jf071a15o9b75d58e2f64230@mail.gmail.com>

On Mon, Jun 29, 2009 at 16:10, Eric Hameleers <eha at alienbase.nl> wrote:

> On Sun, 28 Jun 2009, Darrell Anderson wrote:
>
>  When 13.0 is released, will the slackbuilds.org build scripts continue
>> supporting the older tgz format, the newer txz format, or the option to use
>> either?
>>
>> Thanks.
>>
>> P.S. I'm not a member of the list.
>>
>> Darrell Anderson
>> http://humanreadable.nfshost.com/
>>
>
> It's really quite simple Darrell:
>
> We are a site that hosts SlackBuild scripts, not packages. It is not about
> supporting any particular package format. If you want to use the old .tgz
> packages, then by all means edit the last line of the script and change the
> extension of the package which is going to be created. These scripts are not
> set in concrete.
>
> When we start adding scripts for Slackware 13.0 in our repository, you can
> expect that they will (or should) support *all* of Slackware 13.0's features
> - which includes the new package formats. When we sign off a script after
> our internal QA round we will have tested it on a full install of Slackware.
>
> Regards, Eric
>
>
The problem becomes more clear when we know SBo only host scripts but not
packages and people can edit them when they feel disappointed. My suggestion
is add a FMT variable like this:

FMT=${FMT:-tgz}
...
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$FMT

So users don't need to modify the script to change the compression
algorithm.(As local modifications will lost after every rsync...)

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

From nille.kungen at gmail.com  Wed Jul  1 10:31:22 2009
From: nille.kungen at gmail.com (=?UTF-8?B?TmlrbGFzICdOaWxsZScgw4VrZXJzdHLDtm0=?=)
Date: Wed, 01 Jul 2009 12:31:22 +0200
Subject: [Slackbuilds-users] Future Build Scripts
In-Reply-To: <a0adeea50907010052jf071a15o9b75d58e2f64230@mail.gmail.com>
References: <138475.91316.qm@web37501.mail.mud.yahoo.com>	<Pine.LNX.4.61.0906291001430.29184@door.barrier.lan>
	<a0adeea50907010052jf071a15o9b75d58e2f64230@mail.gmail.com>
Message-ID: <4A4B3AFA.2030506@gmail.com>

Grissiom wrote:
> On Mon, Jun 29, 2009 at 16:10, Eric Hameleers <eha at alienbase.nl 
> <mailto:eha at alienbase.nl>> wrote:
>
>     On Sun, 28 Jun 2009, Darrell Anderson wrote:
>
>         When 13.0 is released, will the slackbuilds.org
>         <http://slackbuilds.org> build scripts continue supporting the
>         older tgz format, the newer txz format, or the option to use
>         either?
>
>         Thanks.
>
>         P.S. I'm not a member of the list.
>
>         Darrell Anderson
>         http://humanreadable.nfshost.com/
>
>
>     It's really quite simple Darrell:
>
>     We are a site that hosts SlackBuild scripts, not packages. It is
>     not about supporting any particular package format. If you want to
>     use the old .tgz packages, then by all means edit the last line of
>     the script and change the extension of the package which is going
>     to be created. These scripts are not set in concrete.
>
>     When we start adding scripts for Slackware 13.0 in our repository,
>     you can expect that they will (or should) support *all* of
>     Slackware 13.0's features - which includes the new package
>     formats. When we sign off a script after our internal QA round we
>     will have tested it on a full install of Slackware.
>
>     Regards, Eric
>
>  
> The problem becomes more clear when we know SBo only host scripts but 
> not packages and people can edit them when they feel disappointed. My 
> suggestion is add a FMT variable like this:
>
> FMT=${FMT:-tgz}
> ...
> /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$FMT
>
> So users don't need to modify the script to change the compression 
> algorithm.(As local modifications will lost after every rsync...)
>
> -- 
> 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/
>
>   
sed -i 's/.tgz/.txz/' foo.SlackBuild && ./foo.SlackBuild
That works for me.
I say stay with .tgz for now.

From chess at chessgriffin.com  Wed Jul  1 15:31:39 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 1 Jul 2009 11:31:39 -0400
Subject: [Slackbuilds-users] Latest aircrack-ng version
In-Reply-To: <b9f0f75c0906272157m64d6def2w16c7a5ab9e5f41b5@mail.gmail.com>
References: <b9f0f75c0906272157m64d6def2w16c7a5ab9e5f41b5@mail.gmail.com>
Message-ID: <20090701153139.GA5642@localhost>

* Grigorios Bouzakis <grbzks at gmail.com> [2009-06-28 07:57:55]:

> The latest version of the aircrack-ng suite [1], 1.0-rc3, includes
> aircrack-ptw [2],
> so if the script is updated, aircrack-ptw should be removed.
> 
> [1]: http://slackbuilds.org/repository/12.2/network/aircrack-ng/
> [2]: http://slackbuilds.org/repository/12.2/network/aircrack-ptw/
> 

I just built latest aircrack-ng 1.0-rc3 and I do not see where it
includes aircrack-ptw and I don't see it mentioned in the 1.0-rc3
ChangeLog [1] (although maybe I'm not looking for the right thing).  It
seems aircrack-ptw installs some different binaries.  Can you provide
some clarification/information about this?

[1] http://www.aircrack-ng.org/doku.php?id=changelog

-- 
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/20090701/6916efed/attachment.sig>

From chess at chessgriffin.com  Wed Jul  1 15:52:02 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Wed, 1 Jul 2009 11:52:02 -0400
Subject: [Slackbuilds-users] Latest aircrack-ng version
In-Reply-To: <20090701153139.GA5642@localhost>
References: <b9f0f75c0906272157m64d6def2w16c7a5ab9e5f41b5@mail.gmail.com>
	<20090701153139.GA5642@localhost>
Message-ID: <20090701155201.GA5649@localhost>

* Chess Griffin <chess at chessgriffin.com> [2009-07-01 11:31:39]:

> I just built latest aircrack-ng 1.0-rc3 and I do not see where it
> includes aircrack-ptw and I don't see it mentioned in the 1.0-rc3
> ChangeLog [1] (although maybe I'm not looking for the right thing).  It
> seems aircrack-ptw installs some different binaries.  Can you provide
> some clarification/information about this?
> 
> [1] http://www.aircrack-ng.org/doku.php?id=changelog
> 

Responding to my own email ... I was informed in IRC that the
functionality of aircrack-ptw was added to aircrack-ng awhile back -- at
aircrack 0.9.  If that's the case, then it seems this issue would have
been present for prior releases of aircrack-ng.  IOW, this is not an
aircrack 1.0-rc3 specific issue and perhaps aircrack-ptw should have
been removed long ago.

Or are you talking about something else entirely? :-)

-- 
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/20090701/fd3d8e9b/attachment.sig>

From grbzks at gmail.com  Wed Jul  1 17:08:07 2009
From: grbzks at gmail.com (Grigorios Bouzakis)
Date: Wed, 1 Jul 2009 20:08:07 +0300
Subject: [Slackbuilds-users] Latest aircrack-ng version
In-Reply-To: <20090701155201.GA5649@localhost>
References: <b9f0f75c0906272157m64d6def2w16c7a5ab9e5f41b5@mail.gmail.com>
	<20090701153139.GA5642@localhost> <20090701155201.GA5649@localhost>
Message-ID: <b9f0f75c0907011008r15887747q6044a29dc55095f1@mail.gmail.com>

On Wed, Jul 1, 2009 at 6:52 PM, Chess Griffin<chess at chessgriffin.com> wrote:
> * Chess Griffin <chess at chessgriffin.com> [2009-07-01 11:31:39]:
>
>> I just built latest aircrack-ng 1.0-rc3 and I do not see where it
>> includes aircrack-ptw and I don't see it mentioned in the 1.0-rc3
>> ChangeLog [1] (although maybe I'm not looking for the right thing). ?It
>> seems aircrack-ptw installs some different binaries. ?Can you provide
>> some clarification/information about this?
>>
>> [1] http://www.aircrack-ng.org/doku.php?id=changelog
>>
>
> Responding to my own email ... I was informed in IRC that the
> functionality of aircrack-ptw was added to aircrack-ng awhile back -- at
> aircrack 0.9. ?If that's the case, then it seems this issue would have
> been present for prior releases of aircrack-ng. ?IOW, this is not an
> aircrack 1.0-rc3 specific issue and perhaps aircrack-ptw should have
> been removed long ago.
>
> Or are you talking about something else entirely? :-)
>
> --
> Chess Griffin

I think i am talking about the same thing.
I only started using aircrack-ng in 1.0rc3 and when i saw the aircrack-ptw page
on SBo, & afterwards examining its code, i noticed that the files were already
part of aircrack-ng. I assumed that they added in the latest release.

-- 
Greg

From rworkman at slackbuilds.org  Thu Jul  2 17:03:55 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 2 Jul 2009 12:03:55 -0500
Subject: [Slackbuilds-users] krb5 slackbuild
In-Reply-To: <20090626165103.GA17865@canich.net>
References: <2733dfe50906021841l1ad97e6leb77919d8d7dda06@mail.gmail.com>
	<20090624171957.4e8ef76f@liberty.rlwhome.lan>
	<20090626165103.GA17865@canich.net>
Message-ID: <20090702120355.42f5aba0@liberty.rlwhome.lan>

On Fri, 26 Jun 2009 12:51:03 -0400
Tom Canich <tcanich at canich.net> wrote:

> On Wed, Jun 24, 2009 at 05:19:57PM -0500, Robby Workman wrote:
> > On Tue, 2 Jun 2009 22:41:44 -0300
> > Oda <edu.oda at gmail.com> wrote:
> > 
> > > I was writing a slackbuild to krb5 when somebody submit one, so I
> > > decided to wait. But this slackbuild is still in the pending list.
> > > 
> > > Is there any problem with it? Maybe I can help.
> > 
> > 
> > Well, the original submission had some conflicts with other
> > Slackware packages, and there are now two proposals to resolve
> > those conflicts. I hammered out one earlier today, and the original
> > submitter (Tom Canich, CC'd on this mail) has another.  I don't
> > know which is better, to be honest- so long as both work, either is
> > fine with me.  The one I hammered out is here:
> >   http://slackbuilds.org/krb5.tar.gz
> > 
> > Please have a look and see what you guys think; feedback is
> > welcome, and I'd like to get this into the repo for 12.2 if at all
> > possible. Tom's waited long enough as is.
> 
> Sorry for the delayed reply.  I have been away from email for a few 
> days.
> 
> Thanks for your work on this, Robby.  I don't mind waiting -- my only 
> concern is producing a quality package! :)
> 
> Am I correct that your solution is to drop the "et" stuff, rename
> rsh, ftp, and telnet to include a .krb5 suffix?  I agree there is
> probably no reason to include the "et" stuff -- I don't think it does
> anything differently from the software already shipping with
> Slackware.
> 
> My only concern with this solution is portability.  Scripts written
> for other platforms should not require significant modification to
> work on Slackware.  Renaming some programs (or all programs) may
> require significant changes.
> 
> The solution I proposed is an alternate prefix, /usr/kerberos.  This
> is the prefix used on RedHat EL systems*.  This way only the PATH
> need be specified for a script to work on any platform.  The program
> names will remain the same.


Okay, I decided to go with your solution, as the approach does make
more sense.  I'm about to push this out along with a few other things
for our 12.2 repo; if it's not exactly right, we'll fix it up.

Ideally, this will be our final push to slackbuilds/12.2/  :-) 

-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/20090702/785c85f0/attachment-0001.asc>

From rworkman at slackbuilds.org  Thu Jul  2 18:02:25 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 2 Jul 2009 18:02:25 +0000
Subject: [Slackbuilds-users] Updates - 20090702
Message-ID: <20090702180225.GA19981@slackbuilds.org>

Thu Jul  2 17:59:03 UTC 2009
Greetings all; are we getting anxious for 13.0 now that RC1 is out? :-)
  We're all hard at work trying to get things in order for 13.0 (and yes,
  it's a LOT of work), so we're hoping this will be the last update to
  our 12.2 repository.  We'll be in touch on the users mailing list about
  13.0 as soon as we have some useful information available.  As always,
  thanks for your support and encouragement along the way.  --rworkman
desktop/awesome: Updated for version 2.3.6.
  Thanks to Chess Griffin.  --rworkman
libraries/exiftool: Fixed up the perl directories to remove some hardcoded
  directory names and architectures :-)  --rworkman
libraries/libevent: Updated for version 1.4.11.
  Thanks to Erik Hanson.  --rworkman
libraries/libkexif: Added - Libkexif is a library for manipulating EXIF
  information embedded in images. Thanks to Robby Workman for the
  script and to Pierre Cazenave for bringing to our attention that
  this is needed by kphotoalbum.  --pprkut
libraries/libsoup: Updated for version 2.26.2.  --rworkman
libraries/webkit: Updated for version r45012.  --rworkman
network/aircrack-ptw: Removed -- this functionality has been added
  to aircrack-ng.  Thanks to Grigorios Bouzakis for bringing
  this to our attention.  --chess
network/krb5: Added - Kerberos is a network authentication protocol.
  Thanks to Tom Kanich.  --rworkman
network/tor: Updated for version 0.2.0.35.
  Thanks to Erik Hanson.  --michiel


From me at alkos333.net  Fri Jul  3 18:23:51 2009
From: me at alkos333.net (alkos333)
Date: Fri, 3 Jul 2009 13:23:51 -0500
Subject: [Slackbuilds-users] Bad Download Link for Esetroot
In-Reply-To: <a6f13f000906280600r2c6e590free0726a89538be24@mail.gmail.com>
References: <a6f13f000906280600r2c6e590free0726a89538be24@mail.gmail.com>
Message-ID: <a6f13f000907031123u6210b10yeade4691d56374c7@mail.gmail.com>

Here's the new, valid link for Esetroot:
http://www.jnrowe.ukfsn.org/_downloads/Esetroot-20030422.tar.bz2

On Sun, Jun 28, 2009 at 8:00 AM, alkos333<me at alkos333.net> wrote:
> The subject pretty much says it all.
>
> --
> Alex Lysenka
> Computer Science Major
> Operations Management & Information Systems Major
> Northern Illinois University
> alysenka at niu.edu
>



-- 
Alex Lysenka
Computer Science Major
Operations Management & Information Systems Major
Northern Illinois University
alysenka at niu.edu

From rworkman at slackbuilds.org  Fri Jul  3 18:39:29 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 3 Jul 2009 13:39:29 -0500
Subject: [Slackbuilds-users] Bad Download Link for Esetroot
In-Reply-To: <a6f13f000907031123u6210b10yeade4691d56374c7@mail.gmail.com>
References: <a6f13f000906280600r2c6e590free0726a89538be24@mail.gmail.com>
	<a6f13f000907031123u6210b10yeade4691d56374c7@mail.gmail.com>
Message-ID: <20090703133929.6f51721b@liberty.rlwhome.lan>

On Fri, 3 Jul 2009 13:23:51 -0500
alkos333 <me at alkos333.net> wrote:

> Here's the new, valid link for Esetroot:
> http://www.jnrowe.ukfsn.org/_downloads/Esetroot-20030422.tar.bz2


Thanks; fixed.

-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/20090703/37428025/attachment.asc>

From tcanich at canich.net  Fri Jul  3 19:10:37 2009
From: tcanich at canich.net (Tom Canich)
Date: Fri, 3 Jul 2009 15:10:37 -0400
Subject: [Slackbuilds-users] krb5 slackbuild
In-Reply-To: <20090702120355.42f5aba0@liberty.rlwhome.lan>
References: <2733dfe50906021841l1ad97e6leb77919d8d7dda06@mail.gmail.com>
	<20090624171957.4e8ef76f@liberty.rlwhome.lan>
	<20090626165103.GA17865@canich.net>
	<20090702120355.42f5aba0@liberty.rlwhome.lan>
Message-ID: <20090703191037.GC17865@canich.net>

> Okay, I decided to go with your solution, as the approach does make
> more sense.  I'm about to push this out along with a few other things
> for our 12.2 repo; if it's not exactly right, we'll fix it up.

Thanks for your help, Robby.  If there are any outstanding issues 
please let me know, I'm happy to look into them.

> Ideally, this will be our final push to slackbuilds/12.2/  :-) 

That's very exciting :)


From slackware.wagnerm at arcor.de  Mon Jul  6 21:31:00 2009
From: slackware.wagnerm at arcor.de (slackware.wagnerm at arcor.de)
Date: Mon, 6 Jul 2009 23:31:00 +0200 (CEST)
Subject: [Slackbuilds-users] libopensync-plugin-syncml/libsoup
Message-ID: <18576628.1246915860115.JavaMail.ngmail@webmail08.arcor-online.net>

Dear list, 

the recent libsoup update breaks libopensync-plugin-sycml. As long as opensync.org releases version 0.40, libopensync-plugin-syncml has to be configured with '--disable-http'. 

Greetings,

Michael

Jetzt neu: Arcor- Online Butler 5.0 als kostenfreier Download!
Der Arcor-Online Butler loggt Sie automatisch in unsere Online-Dienste ein und Sie kommen mit einem Klick zu Ihren E-Mails, zum Chat und vielem mehr.
www.arcor.de/rd/butler

From pc_warner at yahoo.com  Sat Jul 11 21:58:06 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Sat, 11 Jul 2009 14:58:06 -0700 (PDT)
Subject: [Slackbuilds-users] CurseTheWeather URL fix needed
Message-ID: <759034.17815.qm@web57707.mail.re3.yahoo.com>


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.

--Phillip


      

From chess at chessgriffin.com  Tue Jul 14 22:21:07 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 14 Jul 2009 18:21:07 -0400
Subject: [Slackbuilds-users] Sbopkg 0.30.0beta released for testing
Message-ID: <20090714222105.GA15705@localhost>

Thanks to everyone that has tested sbopkg0.30.0alpha1!  Based on that
feedback, and some further testing of our own, we are now releasing a
beta of 0.30.0.  In addition to various bug fixes, here are some of
enhancements and improvements since the alpha release:

  * Add option to retry a failed build. Thanks to Zordrak for suggesting this
    feature.
  * 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. Thanks to Marco Bonetti and
    Gregory Tourte for the suggestion and the nice discussion.
  * Add a function to delete obsolete (not installed) packages from $OUTPUT.
    Thanks to alkos333 for the idea.
  * Reorganize the queue editing functions a bit for a better user interface;
    'view queue' now only shows the queue; new 'sort' and 'remove' queue menu
    items now handle the editing functions; thanks to Pierre Cazenave for the
    suggestion.

Please note that we've set Slackware 13.0 as the 'default' Slackware
version even though obviously 13.0 has not been released yet.  Just
change the setting in sbopkg.conf back to 12.2 and you should be good to
do.  We're just gettin' prepared.  :-)  Speaking of sbopkg.conf, there
is now one new variable 'CLEANUP' so you may want to check
sbopkg.conf.new and migrate the change over to your own config file.

As always, please feel free to post feedback on the sbopkg mailing list
or in #sbopkg on irc.freenode.net.

Here are direct links to a package and source tarball of
sbopkg-0.30.0beta:

Package:
http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta-noarch-1_cng.tgz

Source:
http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta.tar.gz

Thanks for testing!

-- 
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/20090714/e79aba6a/attachment.sig>

From monkey at sandpframing.com  Tue Jul 14 20:04:51 2009
From: monkey at sandpframing.com (MON KEY)
Date: Tue, 14 Jul 2009 16:04:51 -0400
Subject: [Slackbuilds-users] slack 12.2 swig 1.3.38 link busted
Message-ID: <87iqhvvxng.fsf@sandpframing.com>

The swig source download here:
http://slackbuilds.org/repository/12.2/development/swig/
Pointing here:
http://downloads.sourceforge.net/swig/swig-1.3.38.tar.gz

is dead/non-functional

sourceforge...


From michiel at slackbuilds.org  Wed Jul 15 03:18:04 2009
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Wed, 15 Jul 2009 04:18:04 +0100
Subject: [Slackbuilds-users] slack 12.2 swig 1.3.38 link busted
In-Reply-To: <87iqhvvxng.fsf@sandpframing.com>
References: <87iqhvvxng.fsf@sandpframing.com>
Message-ID: <20090715041804.66163e63@hades.esn.local>

On Tue, 14 Jul 2009 16:04:51 -0400
MON KEY <monkey at sandpframing.com> wrote:

> The swig source download here:
> http://slackbuilds.org/repository/12.2/development/swig/
> Pointing here:
> http://downloads.sourceforge.net/swig/swig-1.3.38.tar.gz
> 
> is dead/non-functional
> 
> sourceforge...

Yep: WFM. See also http://slackbuilds.org/faq/#badlink

Personally I always edit my /etc/fstab with something like the
following line [1]:
212.219.56.167  kent.dl.sourceforge.net      dl.sourceforge.net
downloads.sourceforge.net

-M.


[1] - Adjust as see fit.

> 
> _______________________________________________
> 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/
> 



-- 
-- 
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/20090715/ca9e7ffb/attachment.asc>

From rworkman at slackbuilds.org  Wed Jul 15 04:13:16 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 14 Jul 2009 23:13:16 -0500
Subject: [Slackbuilds-users] slack 12.2 swig 1.3.38 link busted
In-Reply-To: <20090715041804.66163e63@hades.esn.local>
References: <87iqhvvxng.fsf@sandpframing.com>
	<20090715041804.66163e63@hades.esn.local>
Message-ID: <20090714231316.3bb022f2@liberty.rlwhome.lan>

On Wed, 15 Jul 2009 04:18:04 +0100
Michiel van Wessem <michiel at slackbuilds.org> wrote:

> On Tue, 14 Jul 2009 16:04:51 -0400
> MON KEY <monkey at sandpframing.com> wrote:
> 
> > The swig source download here:
> > http://slackbuilds.org/repository/12.2/development/swig/
> > Pointing here:
> > http://downloads.sourceforge.net/swig/swig-1.3.38.tar.gz
> > 
> > is dead/non-functional
> > 
> > sourceforge...
> 
> Yep: WFM. See also http://slackbuilds.org/faq/#badlink
> 
> Personally I always edit my /etc/fstab with something like the
> following line [1]:
> 212.219.56.167  kent.dl.sourceforge.net      dl.sourceforge.net
> downloads.sourceforge.net


s/fstab/hosts/   ;-)

-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/20090714/1693b294/attachment-0001.asc>

From ilgar_eroglu at yahoo.com  Fri Jul 17 05:46:57 2009
From: ilgar_eroglu at yahoo.com (Kemal Ilgar Eroglu)
Date: Thu, 16 Jul 2009 22:46:57 -0700 (PDT)
Subject: [Slackbuilds-users] Typo in sshfs-fuse Slackbuild
Message-ID: <830202.55749.qm@web58208.mail.re3.yahoo.com>


Hi,

In the (Slack 12.2) .Slacbuild of sshfs-fuse, the "$ARCH" = "i686" check is made twice, but the second one was obviously intended for the case x86_64. Could someone please fix it? Thanks,

Ilgar



      

From rworkman at slackbuilds.org  Fri Jul 17 06:00:10 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 17 Jul 2009 01:00:10 -0500
Subject: [Slackbuilds-users] Typo in sshfs-fuse Slackbuild
In-Reply-To: <830202.55749.qm@web58208.mail.re3.yahoo.com>
References: <830202.55749.qm@web58208.mail.re3.yahoo.com>
Message-ID: <20090717010010.3f9f5053@liberty.rlwhome.lan>

On Thu, 16 Jul 2009 22:46:57 -0700 (PDT)
Kemal Ilgar Eroglu <ilgar_eroglu at yahoo.com> wrote:

> In the (Slack 12.2) .Slacbuild of sshfs-fuse, the "$ARCH" = "i686"
> check is made twice, but the second one was obviously intended for
> the case x86_64.


Indeed it was, and it's fixed now.  Thanks!

-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/20090717/579c2a77/attachment.asc>

From vbatts at hashbangbash.com  Mon Jul 20 23:29:19 2009
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Mon, 20 Jul 2009 18:29:19 -0500
Subject: [Slackbuilds-users] x11-ssh-askpass source
Message-ID: <2015330f0907201629g5f86402fif67857377bb9518@mail.gmail.com>

does anyone have this x11-ssh-askpass-1.2.4.1.tar.gz bundle? it
doesn't seem to be accessible on their website again.


vb
205.352.4112
http://hashbangbash.com/

From rworkman at slackbuilds.org  Mon Jul 20 23:45:43 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 20 Jul 2009 18:45:43 -0500
Subject: [Slackbuilds-users] x11-ssh-askpass source
In-Reply-To: <2015330f0907201629g5f86402fif67857377bb9518@mail.gmail.com>
References: <2015330f0907201629g5f86402fif67857377bb9518@mail.gmail.com>
Message-ID: <20090720184543.389c5e10@liberty.rlwhome.lan>

On Mon, 20 Jul 2009 18:29:19 -0500
Vincent Batts <vbatts at hashbangbash.com> wrote:

> does anyone have this x11-ssh-askpass-1.2.4.1.tar.gz bundle? it
> doesn't seem to be accessible on their website again.


http://slackbuilds.org/sources/13.0/x11-ssh-askpass-1.2.4.1.tar.gz

-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/20090720/ee689323/attachment.asc>

From vbatts at hashbangbash.com  Tue Jul 21 03:53:02 2009
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Mon, 20 Jul 2009 22:53:02 -0500
Subject: [Slackbuilds-users] x11-ssh-askpass source
In-Reply-To: <20090720184543.389c5e10@liberty.rlwhome.lan>
References: <2015330f0907201629g5f86402fif67857377bb9518@mail.gmail.com>
	<20090720184543.389c5e10@liberty.rlwhome.lan>
Message-ID: <2015330f0907202053s3c0ba665n662ed2c94d58c235@mail.gmail.com>

donkey chain (danke schoen ;)


vb
205.352.4112
http://hashbangbash.com/



On Mon, Jul 20, 2009 at 6:45 PM, Robby Workman<rworkman at slackbuilds.org> wrote:
> On Mon, 20 Jul 2009 18:29:19 -0500
> Vincent Batts <vbatts at hashbangbash.com> wrote:
>
>> does anyone have this x11-ssh-askpass-1.2.4.1.tar.gz bundle? it
>> doesn't seem to be accessible on their website again.
>
>
> http://slackbuilds.org/sources/13.0/x11-ssh-askpass-1.2.4.1.tar.gz
>
> -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 vlad.dinulescu at avira.com  Thu Jul 23 08:59:25 2009
From: vlad.dinulescu at avira.com (Vlad Dinulescu)
Date: Thu, 23 Jul 2009 11:59:25 +0300
Subject: [Slackbuilds-users] Patch for postgresql 8.4.0
Message-ID: <4A68266D.8070605@avira.com>

Hello,

The slackbuild script for postgresql 8.3.7 does not work for postgresql
8.4.0. Apparently they moved the doc directory from /usr/doc to
/usr/share/doc.

Here's a patch.

-- 
Best regards,
Vlad Dinulescu
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: postgres-8.4.0.patch
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090723/38ef6de1/attachment.pl>

From 7252d9 at gmail.com  Thu Jul 23 10:18:15 2009
From: 7252d9 at gmail.com (dae3)
Date: Thu, 23 Jul 2009 12:18:15 +0200
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
Message-ID: <20090723101815.GE2016@acerrimo>

Running '/etc/rc.d/rc.vboxdrv setup', one is supposed to be able to
build and install the 'vboxdrv' kernel module on the fly.

The script however looks for sources in
'/usr/lib/virtualbox/src/vboxdrv/' while the SlackBuild seems to
install them into '/usr/src/virtualbox-kernel-2.1.4/vboxdrv'.

Did you change the sources' install location without modifying all
references to it?


-- 
~> cat /etc/*-{version,release}|head -n1 && uname -moprs|fold -sw72
Slackware 12.2.0
Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 
GNU/Linux

From adis at linux.org.ba  Thu Jul 23 10:36:39 2009
From: adis at linux.org.ba (Adis Nezirovic)
Date: Thu, 23 Jul 2009 12:36:39 +0200
Subject: [Slackbuilds-users] Patch for postgresql 8.4.0
In-Reply-To: <4A68266D.8070605@avira.com>
References: <4A68266D.8070605@avira.com>
Message-ID: <20090723103639.GH18876@pleo.team.ba>

On Thu, Jul 23, 2009 at 11:59:25AM +0300, Vlad Dinulescu wrote:
> Hello,
> 
> The slackbuild script for postgresql 8.3.7 does not work for postgresql
> 8.4.0. Apparently they moved the doc directory from /usr/doc to
> /usr/share/doc.

Thanks for the patch, I'll submit new slackbuild as soon as the
submission form opens. (After 13.0 is out I guess).

There will be aditional options for PostgreSQL rc script
  /etc/rc.d/rc.postgres {restart|force-restart|unclean-restart}
  /etc/rc.d/rc.postgres {stop|force-stop|unclean-stop}
which will cover all start/stop options for pg_ctl (smart, fast,
immediate)
  http://www.postgresql.org/docs/8.4/interactive/app-pg-ctl.html

Best regards,
Adis
-------------- 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/20090723/6b325aec/attachment.sig>

From pprkut at liwjatan.at  Fri Jul 24 10:30:17 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Fri, 24 Jul 2009 12:30:17 +0200
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
In-Reply-To: <20090723101815.GE2016@acerrimo>
References: <20090723101815.GE2016@acerrimo>
Message-ID: <200907241230.17915.pprkut@liwjatan.at>

On Thursday 23 July 2009 12:18:15 dae3 wrote:
> Running '/etc/rc.d/rc.vboxdrv setup', one is supposed to be able to
> build and install the 'vboxdrv' kernel module on the fly.
>
> The script however looks for sources in
> '/usr/lib/virtualbox/src/vboxdrv/' while the SlackBuild seems to
> install them into '/usr/src/virtualbox-kernel-2.1.4/vboxdrv'.

I know about this already. Comment further down :)

> Did you change the sources' install location without modifying all
> references to it?

Mmm, sort of.
I still think /usr/src is the most appropriate location for kernel module 
sources, that's why I placed them there initially. The vbox-devs implemented
rc.vboxdrv setup way later and went unnoticed until recently.

My position on this is that I'm not going to fix it for 12.2, as it's a non-
issue from my perspective. I see no valid reason an init-script should compile 
kernel-modules. Everyone who needs to recompile the kernel module for a newer 
kernel can either use the virtualbox-kernel.SlackBuild or go to /usr/src and 
build it by hand.

I have it already "fixed" for 13.0 in the form of removing "setup" completely.

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/20090724/1288ab91/attachment.sig>

From 7252d9 at gmail.com  Fri Jul 24 11:15:44 2009
From: 7252d9 at gmail.com (dae3)
Date: Fri, 24 Jul 2009 13:15:44 +0200
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
In-Reply-To: <200907241230.17915.pprkut@liwjatan.at>
References: <20090723101815.GE2016@acerrimo>
	<200907241230.17915.pprkut@liwjatan.at>
Message-ID: <20090724111544.GF2016@acerrimo>

Il 24/07/2009 alle 12:30, Heinz Wiesinger ha scritto:

> On Thursday 23 July 2009 12:18:15 dae3 wrote:
[...]
> > Did you change the sources' install location without modifying all
> > references to it?
> 
> Mmm, sort of.
> I still think /usr/src is the most appropriate location for kernel module 
> sources, that's why I placed them there initially. The vbox-devs implemented
> rc.vboxdrv setup way later and went unnoticed until recently.
> 
> My position on this is that I'm not going to fix it for 12.2, as it's a non-
> issue from my perspective. I see no valid reason an init-script should compile 
> kernel-modules. Everyone who needs to recompile the kernel module for a newer 
> kernel can either use the virtualbox-kernel.SlackBuild or go to /usr/src and 
> build it by hand.
> 
> I have it already "fixed" for 13.0 in the form of removing "setup" completely.


I don't think that's a good idea. Why don't you simply point the script
to the new location?

The VirtualBox GUI is supposed to be able to call the script, so if it
can't find the kernel module, it can make a new one on the spot.  This
turns out to be very convenient every time the user updates or
recompiles the kernel.

By removing the setup option, you are actually removing useful
functionality from the VirtualBox program.


-- 
~> cat /etc/*-{version,release}|head -n1 && uname -moprs|fold -sw72
Slackware 12.2.0
Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 
GNU/Linux


From xgizzmo at gmail.com  Fri Jul 24 11:35:55 2009
From: xgizzmo at gmail.com (xgizzmo at gmail.com)
Date: Fri, 24 Jul 2009 07:35:55 -0400
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
In-Reply-To: <20090724111544.GF2016@acerrimo>
References: <20090723101815.GE2016@acerrimo>
	<200907241230.17915.pprkut@liwjatan.at>
	<20090724111544.GF2016@acerrimo>
Message-ID: <200907240735.55867.xgizzmo@slackbuilds.org>

> The VirtualBox GUI is supposed to be able to call the script, so if it
> can't find the kernel module, it can make a new one on the spot.  This
> turns out to be very convenient every time the user updates or
> recompiles the kernel.
> 
> By removing the setup option, you are actually removing useful
> functionality from the VirtualBox program.
> 
> 


The point of using a SlackBuild is to create a package, by recompiling the 
kernel module you are corrupting the package and the new module can not be 
removed when you uninstall the package. Just my 2 cents.

--dsomero
 

From 7252d9 at gmail.com  Fri Jul 24 11:46:17 2009
From: 7252d9 at gmail.com (dae3)
Date: Fri, 24 Jul 2009 13:46:17 +0200
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
In-Reply-To: <20090724111544.GF2016@acerrimo>
References: <20090723101815.GE2016@acerrimo>
	<200907241230.17915.pprkut@liwjatan.at>
	<20090724111544.GF2016@acerrimo>
Message-ID: <20090724114617.GG2016@acerrimo>

I wrote:

> I don't think that's a good idea. Why don't you simply point the script
> to the new location?
> 
> The VirtualBox GUI is supposed to be able to call the script, so if it
> can't find the kernel module, it can make a new one on the spot.  This
> turns out to be very convenient every time the user updates or
> recompiles the kernel.
> 
> By removing the setup option, you are actually removing useful
> functionality from the VirtualBox program.


Actually, scratch the second paragraph, since module recompilation
happens via the DKMS mechanism.

Lacking DKMS, however, the user *is* told to run 'vboxdrv setup' by the
program, so that functionality should still be provided for.


-- 
~> cat /etc/*-{version,release}|head -n1 && uname -moprs|fold -sw72
Slackware 12.2.0
Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 
GNU/Linux

From 7252d9 at gmail.com  Fri Jul 24 12:03:53 2009
From: 7252d9 at gmail.com (dae3)
Date: Fri, 24 Jul 2009 14:03:53 +0200
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
In-Reply-To: <200907240735.55867.xgizzmo@slackbuilds.org>
References: <20090723101815.GE2016@acerrimo>
	<200907241230.17915.pprkut@liwjatan.at>
	<20090724111544.GF2016@acerrimo>
	<200907240735.55867.xgizzmo@slackbuilds.org>
Message-ID: <20090724120353.GH2016@acerrimo>

Il 24/07/2009 alle 13:35, xgizzmo at gmail.com ha scritto:

> The point of using a SlackBuild is to create a package, by recompiling the 
> kernel module you are corrupting the package and the new module can not be 
> removed when you uninstall the package. Just my 2 cents.


You're not corrupting the package: the old module installed by the
package is still in the old kernel's module directory.

It's true that the new module can't be automatically removed when you
uninstall, but the new module wasn't installed by the package either.


-- 
~> cat /etc/*-{version,release}|head -n1 && uname -moprs|fold -sw72
Slackware 12.2.0
Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36
GNU/Linux

From ben.mendis at gmail.com  Fri Jul 24 12:07:35 2009
From: ben.mendis at gmail.com (Ben A. Mendis)
Date: Fri, 24 Jul 2009 08:07:35 -0400
Subject: [Slackbuilds-users] virtualbox-ose-2.1.4 rc script fails
In-Reply-To: <20090724120353.GH2016@acerrimo>
References: <20090723101815.GE2016@acerrimo>	<200907241230.17915.pprkut@liwjatan.at>	<20090724111544.GF2016@acerrimo>	<200907240735.55867.xgizzmo@slackbuilds.org>
	<20090724120353.GH2016@acerrimo>
Message-ID: <4A69A407.4020306@gmail.com>

I believe what he is saying is that you should build a new package so
that the old module is removed and the new module is being tracked by
the package manager.

dae3 wrote:
> Il 24/07/2009 alle 13:35, xgizzmo at gmail.com ha scritto:
>
>   
>> The point of using a SlackBuild is to create a package, by recompiling the 
>> kernel module you are corrupting the package and the new module can not be 
>> removed when you uninstall the package. Just my 2 cents.
>>     
>
>
> You're not corrupting the package: the old module installed by the
> package is still in the old kernel's module directory.
>
> It's true that the new module can't be automatically removed when you
> uninstall, but the new module wasn't installed by the package either.
>
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090724/57d63adf/attachment.htm>

From mjjzf at syntaktisk.dk  Sat Jul 25 08:37:14 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Sat, 25 Jul 2009 10:37:14 +0200
Subject: [Slackbuilds-users] Abiword dependency
Message-ID: <20090725103714.4dbdddd4@darkstar.example.net>

Dear all,
I have been working with Slackbuilds for the upcoming release, and I
ran into a question; it seems that Abiword requires libgsf built with
libgsf-gio; and Pat's version is built --without-gio.
So in order to build Abiword, it is necessary to rebuild a base
package. How is the Slackbuilds policy on submitting a Slackbuild to
replace a package in the standard distribution?

Yours,
Morten

From grbzks at gmail.com  Sat Jul 25 09:52:34 2009
From: grbzks at gmail.com (Grigorios Bouzakis)
Date: Sat, 25 Jul 2009 12:52:34 +0300
Subject: [Slackbuilds-users] Abiword dependency
In-Reply-To: <20090725103714.4dbdddd4@darkstar.example.net>
References: <20090725103714.4dbdddd4@darkstar.example.net>
Message-ID: <b9f0f75c0907250252y642b84cy994919db8cdc8126@mail.gmail.com>

On Sat, Jul 25, 2009 at 11:37 AM, Morten Juhl-Johansen
Z?lde-Fej?r<mjjzf at syntaktisk.dk> wrote:
> Dear all,
> I have been working with Slackbuilds for the upcoming release, and I
> ran into a question; it seems that Abiword requires libgsf built with
> libgsf-gio; and Pat's version is built --without-gio.
> So in order to build Abiword, it is necessary to rebuild a base
> package. How is the Slackbuilds policy on submitting a Slackbuild to
> replace a package in the standard distribution?

You can't submit a script like that on SBo.
Why doesnt Abiword need libgsf with gio? I build & use abiword here without
problems here. Also abiword finds and links again libgsf:
ldd /usr/bin/abiword |grep sf
libgsf-1.so.114 => /usr/lib64/libgsf-1.so.114 (0x00007f1dd18bd000)


-- 
Greg

From grbzks at gmail.com  Sat Jul 25 09:53:27 2009
From: grbzks at gmail.com (Grigorios Bouzakis)
Date: Sat, 25 Jul 2009 12:53:27 +0300
Subject: [Slackbuilds-users] Abiword dependency
In-Reply-To: <b9f0f75c0907250252y642b84cy994919db8cdc8126@mail.gmail.com>
References: <20090725103714.4dbdddd4@darkstar.example.net>
	<b9f0f75c0907250252y642b84cy994919db8cdc8126@mail.gmail.com>
Message-ID: <b9f0f75c0907250253y3c5bee47ie191b3e65186ef91@mail.gmail.com>

On Sat, Jul 25, 2009 at 12:52 PM, Grigorios Bouzakis<grbzks at gmail.com> wrote:
> On Sat, Jul 25, 2009 at 11:37 AM, Morten Juhl-Johansen
> Z?lde-Fej?r<mjjzf at syntaktisk.dk> wrote:
>> Dear all,
>> I have been working with Slackbuilds for the upcoming release, and I
>> ran into a question; it seems that Abiword requires libgsf built with
>> libgsf-gio; and Pat's version is built --without-gio.
>> So in order to build Abiword, it is necessary to rebuild a base
>> package. How is the Slackbuilds policy on submitting a Slackbuild to
>> replace a package in the standard distribution?
>
> You can't submit a script like that on SBo.
> Why doesnt Abiword need libgsf with gio? I build & use abiword here without
> problems here. Also abiword finds and links again libgsf:
> ldd /usr/bin/abiword |grep sf
> libgsf-1.so.114 => /usr/lib64/libgsf-1.so.114 (0x00007f1dd18bd000)

s/doesnt/does


-- 
Greg

From grbzks at gmail.com  Sat Jul 25 09:55:00 2009
From: grbzks at gmail.com (Grigorios Bouzakis)
Date: Sat, 25 Jul 2009 12:55:00 +0300
Subject: [Slackbuilds-users] Abiword dependency
In-Reply-To: <b9f0f75c0907250253y3c5bee47ie191b3e65186ef91@mail.gmail.com>
References: <20090725103714.4dbdddd4@darkstar.example.net>
	<b9f0f75c0907250252y642b84cy994919db8cdc8126@mail.gmail.com>
	<b9f0f75c0907250253y3c5bee47ie191b3e65186ef91@mail.gmail.com>
Message-ID: <b9f0f75c0907250255t46b8b6a4q6e5eeb5933ca0c50@mail.gmail.com>

On Sat, Jul 25, 2009 at 12:53 PM, Grigorios Bouzakis<grbzks at gmail.com> wrote:
> On Sat, Jul 25, 2009 at 12:52 PM, Grigorios Bouzakis<grbzks at gmail.com> wrote:
>> On Sat, Jul 25, 2009 at 11:37 AM, Morten Juhl-Johansen
>> Z?lde-Fej?r<mjjzf at syntaktisk.dk> wrote:
>>> Dear all,
>>> I have been working with Slackbuilds for the upcoming release, and I
>>> ran into a question; it seems that Abiword requires libgsf built with
>>> libgsf-gio; and Pat's version is built --without-gio.
>>> So in order to build Abiword, it is necessary to rebuild a base
>>> package. How is the Slackbuilds policy on submitting a Slackbuild to
>>> replace a package in the standard distribution?
>>
>> You can't submit a script like that on SBo.
>> Why doesnt Abiword need libgsf with gio? I build & use abiword here without
>> problems here. Also abiword finds and links again libgsf:
>> ldd /usr/bin/abiword |grep sf
>> libgsf-1.so.114 => /usr/lib64/libgsf-1.so.114 (0x00007f1dd18bd000)
>
> s/doesnt/does
>

My original post is full of typos, but i think it makes sense :)

-- 
Greg

From stormtracknole at gmail.com  Wed Jul 29 00:57:34 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Tue, 28 Jul 2009 19:57:34 -0500
Subject: [Slackbuilds-users] sbopkg alpha and slackware current
Message-ID: <a653e2ed0907281757o2be61b46vf198bed6db26c78d@mail.gmail.com>

List,

After many years, I finally made the switch to Slackware Current.  I enjoy
the stability of Slackware itself, but I do enjoy tweaking stuff.  So, of to
Current I go.  So, my question now is, is there a way to test the latest
sbopkg (alpha) with Slackware current?  Or can I build slackbuild packages
with version 12.2?  Not sure if I asked this in the correct list.  Not sure
if this will fall under slackbuilds development or sbopkg.  Thanks ahead of
time!

-stn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090728/fc1aafcb/attachment-0001.htm>

From mauro.giachero at gmail.com  Wed Jul 29 08:59:25 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 29 Jul 2009 10:59:25 +0200
Subject: [Slackbuilds-users] sbopkg alpha and slackware current
In-Reply-To: <a653e2ed0907281757o2be61b46vf198bed6db26c78d@mail.gmail.com>
References: <a653e2ed0907281757o2be61b46vf198bed6db26c78d@mail.gmail.com>
Message-ID: <da3e877f0907290159l2276afa7t6f903d258f8c5d66@mail.gmail.com>

On Wed, Jul 29, 2009 at 2:57 AM, stormtracknole <stormtracknole at gmail.com>wrote:

> List,
>
> After many years, I finally made the switch to Slackware Current.  I enjoy
> the stability of Slackware itself, but I do enjoy tweaking stuff.  So, of to
> Current I go.  So, my question now is, is there a way to test the latest
> sbopkg (alpha) with Slackware current?


Sbopkg itself works just fine in -current. However I must point out that the
latest sbopkg release is the beta:

Package:
http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta-noarch-1_cng.tgz
Source:
http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta.tar.gz

Since that release there has been a bugfix (see r685) + some minor
improvements, so you may want to use the latest SVN version instead.

Or can I build slackbuild packages with version 12.2?


I assume you're on 32 bit.
Most (but not all) SBo scripts work just fine on -current, so you can use
the 12.2 repository. Watch out for SBo packages that made their way to
-current, though (qt4, swig and subversion-bindings come to my mind, but
there are many others).


> Not sure if I asked this in the correct list.  Not sure if this will fall
> under slackbuilds development or sbopkg.  Thanks ahead of time!


You're welcome!


> -stn


-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090729/f9e3eea6/attachment.htm>

From stormtracknole at gmail.com  Wed Jul 29 21:22:02 2009
From: stormtracknole at gmail.com (stormtracknole)
Date: Wed, 29 Jul 2009 16:22:02 -0500
Subject: [Slackbuilds-users] sbopkg alpha and slackware current
In-Reply-To: <da3e877f0907290159l2276afa7t6f903d258f8c5d66@mail.gmail.com>
References: <a653e2ed0907281757o2be61b46vf198bed6db26c78d@mail.gmail.com>
	<da3e877f0907290159l2276afa7t6f903d258f8c5d66@mail.gmail.com>
Message-ID: <a653e2ed0907291422j340393beoa01e4fd9b48b099c@mail.gmail.com>

Thanks for the reply Mauro!  I did not realize that there was a beta package
available.  I just signed up on the sbopkg mail list, so I'm slowly catching
up with that.  I had noticed a possible bug on the alpha version, but I'll
wait and see if it's been taken care of on this latest version.  Thanks
again everyone involved with slackbuilds and sbopkg.  Great, great stuff!!
:^)

-stn

On Wed, Jul 29, 2009 at 3:59 AM, Mauro Giachero <mauro.giachero at gmail.com>wrote:

> On Wed, Jul 29, 2009 at 2:57 AM, stormtracknole <stormtracknole at gmail.com>wrote:
>
>> List,
>>
>> After many years, I finally made the switch to Slackware Current.  I enjoy
>> the stability of Slackware itself, but I do enjoy tweaking stuff.  So, of to
>> Current I go.  So, my question now is, is there a way to test the latest
>> sbopkg (alpha) with Slackware current?
>
>
> Sbopkg itself works just fine in -current. However I must point out that
> the latest sbopkg release is the beta:
>
> Package:
> http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta-noarch-1_cng.tgz
> Source:
> http://sbopkg.googlecode.com/files/sbopkg-0.30.0beta.tar.gz
>
> Since that release there has been a bugfix (see r685) + some minor
> improvements, so you may want to use the latest SVN version instead.
>
> Or can I build slackbuild packages with version 12.2?
>
>
> I assume you're on 32 bit.
> Most (but not all) SBo scripts work just fine on -current, so you can use
> the 12.2 repository. Watch out for SBo packages that made their way to
> -current, though (qt4, swig and subversion-bindings come to my mind, but
> there are many others).
>
>
>> Not sure if I asked this in the correct list.  Not sure if this will fall
>> under slackbuilds development or sbopkg.  Thanks ahead of time!
>
>
> You're welcome!
>
>
>> -stn
>
>
> --
> Mauro Giachero
>
> _______________________________________________
> 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/20090729/df951ce6/attachment.htm>

From chess.griffin at gmail.com  Wed Jul 29 23:03:44 2009
From: chess.griffin at gmail.com (Chess Griffin)
Date: Wed, 29 Jul 2009 19:03:44 -0400
Subject: [Slackbuilds-users] sbopkg alpha and slackware current
In-Reply-To: <a653e2ed0907291422j340393beoa01e4fd9b48b099c@mail.gmail.com>
References: <a653e2ed0907281757o2be61b46vf198bed6db26c78d@mail.gmail.com>
	<da3e877f0907290159l2276afa7t6f903d258f8c5d66@mail.gmail.com>
	<a653e2ed0907291422j340393beoa01e4fd9b48b099c@mail.gmail.com>
Message-ID: <b785ba860907291603y1cccd30r71379b29129ded1@mail.gmail.com>

On Wed, Jul 29, 2009 at 5:22 PM, stormtracknole<stormtracknole at gmail.com> wrote:
> Thanks for the reply Mauro!? I did not realize that there was a beta package
> available.? I just signed up on the sbopkg mail list, so I'm slowly catching
> up with that.? I had noticed a possible bug on the alpha version, but I'll
> wait and see if it's been taken care of on this latest version.? Thanks
> again everyone involved with slackbuilds and sbopkg.? Great, great stuff!!
> :^)
>

Sorry for the delay in responding.  Work is keeping me /extremely/
busy these days with very little free time.  :(  Anyway, Mauro already
pointed out the beta to you and answered your questions, and you said
you joined the sbopkg list, which is great.  If you have any other
questions, bug reports etc. regarding sbopkg, the sbopkg ML is the
place to post 'em.

Thanks for testing out sbopkg -- we definitely appreciate feedback,
bug reports etc.

Thanks!

-- 
Chess Griffin