Rob,<br><br>I would personally base this decision on the number of inquires you get regarding the plug-ins required by the package. If there is a good number of people, I would consider mentioning it in the README. If not, I would leave it as it is.
<br><br><br>Best Regards,<br>Alex <br><br><div><span class="gmail_quote">On 4/2/07, <b class="gmail_sendername">Robby Workman</b> <<a href="mailto:rworkman@slackbuilds.org">rworkman@slackbuilds.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Daniel de Kok wrote:<br>> On Sun, March 25, 2007 8:41 pm, Robby Workman wrote:<br>>> As solved on the irc channel, the solution is to install the
<br>>> seamonkey package. No development headers are included with<br>>> the stock Firefox package.<br>><br>> Maybe we should add a note to the README file (if it's not already noted<br>> there)?
<br><br><br>I don't know - it's been customary to assume that the user has the<br>full package set from official Slackware, and I personally am very<br>hesitant to open the door to mentioning requirements that are part
<br>of Slackware. What do you guys think - is this one worth an<br>exception?<br><br>RW<br><br>--<br><br><a href="http://slackbuilds.org">http://slackbuilds.org</a><br>_______________________________________________<br>Slackbuilds-users mailing list
<br><a href="mailto:Slackbuilds-users@slackbuilds.org">Slackbuilds-users@slackbuilds.org</a><br><a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
</a><br></blockquote></div><br>