<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    I think slackbuilds should read #!/bin/bash (and not sh or ash) for
    maximum safety and compatility.<br>
    It's&nbsp; a 2 minute job for everyone the alter the script to build with
    ash (if it would build with ash or any other)<br>
    but it can't be the job of every maintainer to test building against
    all the&nbsp; different shells.<br>
    <br>
    <br>
    <br>
    Le 02.11.2010 21:15, Donald Allen a &eacute;crit&nbsp;:
    <blockquote
      cite="mid:AANLkTi=iWko3ko+Bh+pAmmUiR8HFGzvwMZEBXCCK-JjS@mail.gmail.com"
      type="cite"><br>
      <br>
      <div class="gmail_quote">On Tue, Nov 2, 2010 at 3:30 PM, B Watson
        <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:yalhcru@gmail.com">yalhcru@gmail.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          On 11/2/10, Max Miorim &lt;<a moz-do-not-send="true"
            href="mailto:miorimmax@gmail.com">miorimmax@gmail.com</a>&gt;
          wrote:<br>
          <br>
          &gt; Unless we're talking about using either /bin/bash or
          /bin/sh, &nbsp;the<br>
          &gt; problem that I see with this is that it would open the
          precedence to<br>
          &gt; accept submissions of scripts using other shells like csh
          and zsh,<br>
          &gt; that could be a problem for the people that review the
          scripts, as<br>
          &gt; they'd have to learn the particularities of other shells
          - it could<br>
          &gt; slow down the process of review-&gt;approval
          considerably.<br>
          <br>
          Yah, I hadn't thought about csh. Definitely agree the rule
          should be<br>
          /bin/bash, or /bin/sh for scripts that were tested with ash.<br>
          <br>
          &gt; the same thing that took 16.702 seconds using bash as
          /bin/sh took<br>
          &gt; 6.803 with ash and pretty much the same happens to every
          script that<br>
          &gt; we tested.<br>
          <br>
          Interesting. Never even occurred to me to test performance, I
          expect<br>
          interpreters to be slow, and at least subconsciously I was
          aware that bash<br>
          is bloated... but wouldn't have guessed ash would be *that*
          much faster.<br>
          <br>
          Hm. I just now thought I'd try a couple of things in ash, as
          an<br>
          interactive shell, on slack64 13.1, and the damn thing
          segfaulted halfway<br>
          through typing the first command. /me runs off to do some more
          testing...<br>
        </blockquote>
        <div><br>
        </div>
        <div>Yes, but it was really fast until it blew up ....</div>
        <div><br>
        </div>
        <div>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.&nbsp;</div>
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          _______________________________________________<br>
          SlackBuilds-users mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
          <a moz-do-not-send="true"
            href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users"
            target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
          Archives - <a moz-do-not-send="true"
            href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/"
            target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
          FAQ - <a moz-do-not-send="true"
            href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
          <br>
        </blockquote>
      </div>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="http://slackbuilds.org/faq/">http://slackbuilds.org/faq/</a>

</pre>
    </blockquote>
    <br>
  </body>
</html>