<br><blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><pc_warner@yahoo.com><http: lists.slackbuilds.org="" pipermail="" slackbuilds-users="" attachments="" 20080312="" a3665b7d="" attachment-0001.html=""><joshuakwood@gmail.com><slackbuilds-users@slackbuilds.org><http: lists.slackbuilds.org="" pipermail="" slackbuilds-users="" attachments="" 20080312="" cd851801="" attachment-0001.html=""><rworkman@slackbuilds.org><slackbuilds-users@slackbuilds.org>Date: Wed, 12 Mar 2008 23:54:03 -0500<br>From: Robby Workman <rworkman@slackbuilds.org><br>Subject: Re: [Slackbuilds-users] wifi-radar.conf need better perms<br>To: "SlackBuilds.org Users List" <slackbuilds-users@slackbuilds.org><br>Message-ID: &lt;47D8B36B.2080602@slackbuilds.org&gt;<br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Phillip Warner wrote:<br>&gt; <br>&gt; When it is updated could you also add keywords so that someone searching <br>&gt;
 for "wifi radar" could find it easily.  I imagine some people would not <br>&gt; realize slackBuilds.org has it if they forget the hyphen in the name or <br>&gt; chose not to search for simply "wifi".<br><br><br>I will - good idea.  Double check it after the update goes public just<br>to make sure I didn't forget.<br><br><br>&gt; Perhaps, as a compromise, the solution for this slackBuild would be to <br>&gt; add an option that would allow the perms to be left alone (say <br>&gt; NOFIXPERMS=true ./wifi-radar.SlackBuild).  If the option was not <br>&gt; specified or not set to true then the slackBuild would cat the <br>&gt; appropriate line into the doinst.sh in order to fix the perms.  Some <br>&gt; note about this should be added to the README.<br><br><br>After some thought, I decided to fix it in the script, put a note in<br>the README, and leave it at that.  For most people using this, they're<br>on a single-user box where it's not an issue anyway, and for
 those<br>people managing multi-user boxes (laptops - are there such creatures?)<br>:) well, they should be checking that sort of thing anyway.<br><br>-RW<br><br></slackbuilds-users@slackbuilds.org></rworkman@slackbuilds.org></slackbuilds-users@slackbuilds.org></rworkman@slackbuilds.org></http:></slackbuilds-users@slackbuilds.org></joshuakwood@gmail.com></http:></pc_warner@yahoo.com></blockquote>The search tags and the slackBuild look much better.&nbsp; Thank you.<br><br>--phil<pc_warner@yahoo.com><http: lists.slackbuilds.org="" pipermail="" slackbuilds-users="" attachments="" 20080312="" a3665b7d="" attachment-0001.html=""><joshuakwood@gmail.com><slackbuilds-users@slackbuilds.org><http: lists.slackbuilds.org="" pipermail="" slackbuilds-users="" attachments="" 20080312="" cd851801=""
 attachment-0001.html=""><rworkman@slackbuilds.org><slackbuilds-users@slackbuilds.org><rworkman@slackbuilds.org><slackbuilds-users@slackbuilds.org></slackbuilds-users@slackbuilds.org></rworkman@slackbuilds.org></slackbuilds-users@slackbuilds.org></rworkman@slackbuilds.org></http:></slackbuilds-users@slackbuilds.org></joshuakwood@gmail.com></http:></pc_warner@yahoo.com><br><pc_warner@yahoo.com><http: lists.slackbuilds.org="" pipermail="" slackbuilds-users="" attachments="" 20080312="" a3665b7d="" attachment-0001.html=""><joshuakwood@gmail.com><slackbuilds-users@slackbuilds.org><http: lists.slackbuilds.org="" pipermail="" slackbuilds-users="" attachments="" 20080312="" cd851801=""
 attachment-0001.html=""><rworkman@slackbuilds.org><slackbuilds-users@slackbuilds.org><rworkman@slackbuilds.org><slackbuilds-users@slackbuilds.org></slackbuilds-users@slackbuilds.org></rworkman@slackbuilds.org></slackbuilds-users@slackbuilds.org></rworkman@slackbuilds.org></http:></slackbuilds-users@slackbuilds.org></joshuakwood@gmail.com></http:></pc_warner@yahoo.com><p>&#32;



      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>