Unfortunately, this happens (even though we try to avoid it), and it's
not always obvious to either the submitter or us when it does. As with
the actual Slackware tree, the best we can hope to happen is to quickly
catch it when it does and push an update. I'll try to look at the new
gwenview as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 10 May 2009 21:05:23 -0500
Nishant Limbachia wrote:
> I uploaded slackbuild for clamav-unofficial-sigs this morning but a
> newer version was released this afternoon :-). Can you please take
> down the script from pending and I'll upload new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I uploaded slackbuild for clamav-unofficial-sigs this morning but a
newer version was released this afternoon :-). Can you please take
down the script from pending and I'll upload newer version later.
Thanks,
- --
Nishant Limbachia
nish...@mnspace.n
Robby Workman skrev:
On Sun, 10 May 2009 01:33:42 -0500
Robby Workman wrote:
On Sat, 09 May 2009 10:30:12 +0200
Niklas 'Nille' Åkerström wrote:
I seen that in slackware the builds often use LIBDIRSUFFIX now.
So i wonder if we should add LIBDIRSUFFIX to template.SlackBuild
since i th
Again, some minor permission problems have sneaked into this update for those
who use rsync to keep up to date:
rsync:
opendir "12.2/audio/mp3gain" (in slackbuilds) failed:
Permission denied (13)
rsync:
send_files failed to open "12.2/games/gnubg/gnubg.info" (in slackbuilds):
Permission d
Sun May 10 22:39:13 UTC 2009
audio/mp3gain: Added - mp3gain is a command-line normalizer.
Thanks to B. Watson. --chess
development/gsoap: Added - gSOAP is a development toolkit that simplifies
the overall use of XML in any type of application.
Thanks to Heinz Wiesinger. --rworkman
developm
On Sun, 10 May 2009 01:33:42 -0500
Robby Workman wrote:
> On Sat, 09 May 2009 10:30:12 +0200
> Niklas 'Nille' Åkerström wrote:
>
> > I seen that in slackware the builds often use LIBDIRSUFFIX now.
> > So i wonder if we should add LIBDIRSUFFIX to template.SlackBuild
> > since i think alot of peo
On Sun, 10 May 2009 19:27:28 +0200
Sebastien BALLET wrote:
> After reading the thread "Slackbuilds in python ?" it seems that the
> submission that I made on 16/4 (i.e kernel-pae) is wrong. Indeed, this
> slackbuild builds multiple package at a time, which is something that
> slackbuilds.org do n
Hi,
After reading the thread "Slackbuilds in python ?" it seems that the
submission that I made on 16/4 (i.e kernel-pae) is wrong. Indeed, this
slackbuild builds multiple package at a time, which is something that
slackbuilds.org do not want. To correct this mistake, I have made two
slackbuilds (k
On Sun, May 10, 2009 at 9:06 AM, Morten Juhl-Johansen Zölde-Fejér
wrote:
> after the next Slackware release next week (no, I have no idea, just
> dreaming).
That just begs the question - when is the next release coming outl?
-- Ah.. that's right, when it's ready. :)
--
Alex Lysenka
Computer Sci
On Thu, 7 May 2009 09:52:43 -0500
Robby Workman wrote:
> Well, if it requires updating packages that are in Slackware, we can
> consider the abiword version we have now to be the last one for 12.2.
>
> -RW
Agreed. No problem in this.
As Alex pointed out, 2.7.0 is where the action is right now..
At Sat, 9 May 2009 17:57:48 -0400,
xgiz...@slackbuilds.org wrote:
> They are removed and added to the doinst.sh script so they can be recreated
> on the target system. In other words the correct way is to make the symlink
> in the slackbuild. It will automaticly be added to the doinst.sh script.
Good catch everybody. I extracted my package and the links are part of the
doinst.sh script file.
Sorry to bother.
Xavier
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-use
13 matches
Mail list logo
