Re: [Slackbuilds-users] A slight 'problem' with the app I'm supposed to maintain...

-Encoding Keep-Alive: timeout=15, max=197 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: text/html -- TuxaneMedia / SARL Burro-net 7 Place du Pont F-66400 Céret T:: +33 4 68 82 73 20 @:: j...@tuxane.com Web:: http://www.burro-net.com PGP:: http://www.tuxane.com/pub/jenspub.asc TVA

[Slackbuilds-users] Two more for 14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everybody, I just tested my SlackBuilds and it seems they will build without changes : system/unetbootin development/scite Jens - -- TuxaneMedia / SARL Burro-net 7 Place du Pont F-66400 Céret T:: +33 4 68 82 73 20 @:: j...@tuxane.com

Re: [Slackbuilds-users] requirements in README files

Am 10.07.2012 06:54, schrieb Chess Griffin: I have no idea if the current SBo admins are considering adding dependency information like the OP suggested. Maybe so, maybe not. And whatever they decide is fine by me. I don't know if I remember it 100% correctly, but I think we had the subject

Re: [Slackbuilds-users] requirements in README files

Am 10.07.2012 06:54, schrieb Chess Griffin: I have no idea if the current SBo admins are considering adding dependency information like the OP suggested. Maybe so, maybe not. And whatever they decide is fine by me. I don't know if I remember it 100% correctly, but I think we had the subject

Re: [Slackbuilds-users] requirements in README files

Am 10.07.2012 06:54, schrieb Chess Griffin: I have no idea if the current SBo admins are considering adding dependency information like the OP suggested. Maybe so, maybe not. And whatever they decide is fine by me. I don't know if I remember it 100% correctly, but I think we had the subject

Re: [Slackbuilds-users] requirements in README files

Am 10.07.2012 18:31, schrieb J: is this absolute fact? can we get some admins to chime in? if this is fact, and all admins are doing it and following the same format, then this means that for 14.0 we'll have consistency, and my work here is done. No, not fact, but experience (just from the

[Slackbuilds-users] cairo-dock and cairo-dock -plugins SlackBuilds

I guess there is a typo in the package . The SlackBuild files are called Slackbuild so it can't build. Try to use 'Edit SlackBuild' in SboPkg and you'll see it's empty ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] google-chrome

Am 25.03.2011 07:29, schrieb Patrick J. Volkerding: but it's almost never a good time for selinux. I agree absolutely, I wouldn't like Selinux to go into Slackware. I can live perfectly without it ___ SlackBuilds-users mailing list

Re: [Slackbuilds-users] Exim Sbo

I forget the rest: the link to the correct version for the sbo would be ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.72.tar.bz2 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] Exim Sbo

Am 17.01.2011 11:48, schrieb Thomas Morper: build and run 4.72 using the download link I finally simply downloaded the 4.72 manually to /var/cache/sbopkg and the restarted the build queue as slackbuilds run fine then even when the DL failed ___

Re: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts

I think slackbuilds should read #!/bin/bash (and not sh or ash) for maximum safety and compatility. It's a 2 minute job for everyone the alter the script to build with ash (if it would build with ash or any other) but it can't be the job of every maintainer to test building against all the