commit new port - transcode

[Chuck Remes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On May 16, 2007, at 8:59 AM, Daniel J. Luke wrote:

> On May 16, 2007, at 7:54 AM, cremes.devlist at mac.com wrote:
>> I submitted a new port recently and was hoping someone could  
>> commit it for me. Here's the ticket information:
>>
>> http://trac.macports.org/projects/macports/ticket/11933
>
> We generally like to avoid cvs checkouts if possible (and when  
> they're necessary, it's generally preferred to use a tag or date  
> instead of HEAD).
>
> Is there a compelling reason to use cvs HEAD for this port?

Yes. The upcoming 1.1.0 release can only be accessed from HEAD. Plus,  
this is the best way to make sure that, as the code reaches release  
status, it doesn't break under OSX. The other maintainer and I are  
keeping a close eye on things to make sure OSX remains a solidly  
supported target platform. As soon as 1.1.0 is officially released,  
we will update the Portfile to grab a tarball.

There is an older release (1.0.3) which could potentially be used,  
but it's a dead-end for support and functionality. All new  
development is focused on the 1.1.x releases.

In the interim, HEAD is safe. The project developers have a policy of  
not breaking the build so we are (somewhat) assured the port will  
function properly for folks. Again, this is temporary.

Is this sufficient?

cr

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFGSxHNtEOEsNMQp04RAtTTAJ0aMN4m/25Al7syziT2CsmvdI+sAACdE0Hw
x2BWuZGlYN4PBmGRE2YBqHc=
=+Veg
-----END PGP SIGNATURE-----