[Slackbuilds-users] Sonata lyric fetching failed
I just noticed that sonata didn't fetch lyrics anymore. So I looked around and found that it uses lyricwiki.org for the purpose. And since the lyric site has been moved to lyrics.wikia.com, it leads to non-functional lyric module. The file in source that bears lyric funtion is sonata/info.py. So while waiting for the sonata next version, a simple line can be added to sonata.SlackBuild (just before 'python setup.py install ... ') to solve this issue: sed -i s#lyricwiki.org#lyrics.wikia.org#g sonata/info.py Regards, -- Binh Nguyen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
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 different shells. Le 02.11.2010 21:15, Donald Allen a écrit : On Tue, Nov 2, 2010 at 3:30 PM, B Watson yalh...@gmail.com mailto:yalh...@gmail.com wrote: On 11/2/10, Max Miorim miorim...@gmail.com mailto:miorim...@gmail.com wrote: Unless we're talking about using either /bin/bash or /bin/sh, the problem that I see with this is that it would open the precedence to accept submissions of scripts using other shells like csh and zsh, that could be a problem for the people that review the scripts, as they'd have to learn the particularities of other shells - it could slow down the process of review-approval considerably. Yah, I hadn't thought about csh. Definitely agree the rule should be /bin/bash, or /bin/sh for scripts that were tested with ash. the same thing that took 16.702 seconds using bash as /bin/sh took 6.803 with ash and pretty much the same happens to every script that we tested. Interesting. Never even occurred to me to test performance, I expect interpreters to be slow, and at least subconsciously I was aware that bash is bloated... but wouldn't have guessed ash would be *that* much faster. Hm. I just now thought I'd try a couple of things in ash, as an interactive shell, on slack64 13.1, and the damn thing segfaulted halfway through typing the first command. /me runs off to do some more testing... Yes, but it was really fast until it blew up I've had the same experience in search of a less bloated browser than Firefox (really solid, reliable code of significant complexity is not so easy to come by). They all make sense, according to their developers, until you try to use them in real-life situations. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org mailto:SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] gprolog README typo fixes
On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: A few minor typo fixes. Diff attached: --- README.orig 2010-11-04 10:20:04.412448942 -0400 +++ README2010-11-04 10:20:30.663595260 -0400 @@ -1,10 +1,9 @@ -The gprolog configure script appears to ignore the execc-prefix +The gprolog configure script appears to ignore the exec-prefix information handed to it which indicates where compiled binaries should be installed. It insists on installing everything into /usr/gprolog-$VERSION/ and then creating symlinks in /usr/bin. This script will correct this by moving the files in -/usr/gprolog-$VERSION to their propper places in /usr, +/usr/gprolog-$VERSION to their proper places in /usr, ie: binaries are placed in /usr/bin, libraries in /usr/lib or /usr/lib64 and documentation in /usr/doc/gprolog-$VERSION. - Fixed in my branch, thanks! Should be part of the next push of updates. Grs, Heinz signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Task link error
Nice. Thank you On Sat, Nov 6, 2010 at 1:37 PM, Heinz Wiesinger ppr...@slackbuilds.org wrote: On Thursday 04 November 2010 16:26:38 luciano wrote: Task doesn't build. The link seems wrong. It gives 404 message. Thanks for the report! I fixed this in my branch, it should be part of the next push of updates. Grs, Heinz ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] gprolog README typo fixes
On Sat, Nov 6, 2010 at 11:38 AM, Heinz Wiesinger ppr...@slackbuilds.org wrote: On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: A few minor typo fixes. Diff attached: Fixed in my branch, thanks! Should be part of the next push of updates. Grs, Heinz Thanks, Heinz! -- Andrew Antle andrew dot antle at gmail dot com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] gprolog README typo fixes
On Sat, Nov 6, 2010 at 11:38 AM, Heinz Wiesinger ppr...@slackbuilds.org wrote: On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: A few minor typo fixes. Diff attached: Fixed in my branch, thanks! Should be part of the next push of updates. Grs, Heinz Thanks, Heinz! -- Andrew Antle andrew dot antle at gmail dot com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/