<br><br><div class="gmail_quote">On Fri, Dec 12, 2008 at 5:04 PM, Rich Shepard <span dir="ltr"><<a href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, 12 Dec 2008, Chess Griffin wrote:<br>
<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ah, yes, I see. I think those are just personal preferences for package<br>
development that are not really necessary for using the scripts at SBo.<br>
</blockquote>
<br></div>
Chess,<br>
<br>
While the introduction to that page states these are personal approaches,<br>
the consistency of installing full distribution source implies that's not<br>
optional. A clarifying sentence would greatly assist newcomes such as me.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sounds like you are good to go. :-)<br>
</blockquote>
<br></div>
Thank you.<br>
<br>
However, it turns out that the application I want to use, OpenProject, is<br>
written in java and provided as a .jar file. Unfortunate, IMNSHO. My<br>
experiences are that java apps are only slightly above perl apps in clarity<br>
and maintainability. I prefer C and python; my software engineer partner<br>
(much more experienced than am I) prefers C and ruby while holding the same<br>
opinons of perl and java. But, that's for another discussion over a couple<br>
of pints of handcrafted stout, porter, or ale.<br>
<br>
Carpe weekend,<div><div></div><div class="Wj3C7c"><br>
<br>
Rich<br>
<br>
-- <br>
Richard B. Shepard, Ph.D. | Integrity Credibility<br>
Applied Ecosystem Services, Inc. | Innovation<br>
<<a href="http://www.appl-ecosys.com" target="_blank">http://www.appl-ecosys.com</a>> Voice: 503-667-4517 Fax: 503-667-8863<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
</div></div></blockquote></div>Clarification: All documentation needed for the creation of SlackBuilds for <a href="http://slackbuilds.org">slackbuilds.org</a> can be found at <a href="http://slackbuilds.org">slackbuilds.org</a>.<br>
<br>Does that help?<br>-JK<br>