[44043] trunk/dports/devel

[Ryan Schmidt]

On Dec 20, 2008, at 14:23, William Siegrist wrote:

> On Dec 20, 2008, at 12:50 AM, Ryan Schmidt wrote:
>
>> On Dec 19, 2008, at 15:36, wsiegrist at apple.com wrote:
>>
>>> +fetch.type	svn
>>> +svn.url		http://svn.macosforge.org/repository/darwinbuild/trunk/
>>> +svn.tag		HEAD
>>
>> If there is no tag for the 0.8.0 version, then you should use the  
>> revision number that corresponds to the 0.8.0 version, not HEAD.  
>> Using HEAD means building the port at different times fetches  
>> different files from the darwinbuild repository, which we do not  
>> want to occur; we want every user to get the same build every time.
>>
>> Is 0.8.0 released yet? If not, the port name darwinbuild-devel  
>> might be more appropriate, and let the port darwinbuild be for the  
>> latest released version instead. Unless the latest released  
>> version is so old as to not be useful.
>
> There's no tag or revision for 0.8.0,  thats just the version of  
> trunk (like MP 1.8.0). There's also no stable released version, so  
> I left off the -devel in the name. And yes, I know you get new  
> files every time. I'm the primary developer of darwinbuild these  
> days and recommend people live on trunk. This port is for people  
> already running MP on a machine so they can "port upgrade  
> darwinbuild" instead of doing the "svn up ... ; make ; make  
> install" manually each time.

Still, we want people to get the same software on their machine every  
time they build a given epoch+version+revision+variant combination of  
a given port. So you should pin this port to a specific upstream  
revision in the svn.tag. You can always increment the port's revision  
and svn.tag when you want to release new changes to MacPorts users;  
that way they will be informed via "port outdated" of the  
availability of the new changes.

Otherwise you get the situation that two users install "version  
0.8.0" at different times, and the software works one way for one  
user and another way (or even not at all) for a second user and  
because they have the same version installed they will think they  
have the same software when in fact unbeknownst to them they have  
different upstream revisions.