<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/31/2012 19:29, <a class="moz-txt-link-abbreviated" href="mailto:unix_lists@f-m.fm">unix_lists@f-m.fm</a>
wrote:<br>
</div>
<blockquote
cite="mid:1351726150.20140.140661147969745.208121E6@webmail.messagingengine.com"
type="cite">
<pre wrap="">This updates audacity to 2.0.2
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Pbi-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pbi-dev@lists.pcbsd.org">Pbi-dev@lists.pcbsd.org</a>
<a class="moz-txt-link-freetext" href="http://lists.pcbsd.org/mailman/listinfo/pbi-dev">http://lists.pcbsd.org/mailman/listinfo/pbi-dev</a>
</pre>
</blockquote>
<br>
Sorry about the wait! This message got lost in my inbox....<br>
<br>
It looks like there are no discernible changes in the module you
send in compared to out current module for audio/audacity except
that you don't have the extra installation scripts (which I am
cleaning up at the moment).<br>
<br>
In general, a PBI module should be valid for all versions of the
designated program without any modifications. The only time a module
does need to be "updated" to build the newest version is generally
when the FreeBSD port actually changed to a different name, or there
is something in the module that specifically defines or relies on a
particular program version (through installation scripts and such).<br>
<br>
You can look through our current modules at
<a class="moz-txt-link-freetext" href="http://trac.pcbsd.org/browser/pbi/modules">http://trac.pcbsd.org/browser/pbi/modules</a> if you want to check for
program version limitations.<br>
<br>
Thanks anyway!<br>
<br>
<pre class="moz-signature" cols="72">--
~~ Ken Moore ~~
PC-BSD/iXsystems</pre>
</body>
</html>