[Adium-devl] OK, I suggest a new rule

[Peter Hosey]

First, make sure you have no outstanding changes in your branch  
checkout. (svn st)

If you have no outstanding changes, then try a Deployment build.

If it works, woo-hoo! Now you can tag the version.

Then, check out the tag and *build that*.

If the tag doesn't build, you know you screwed up somewhere and one  
or more of these steps needs to be done over.

I say this because…

> xcodebuild \       %~/Projects/@otherpeoplesprojects/adium/tags/ 
> AdiumX_1.0.2(0)
> > -configuration Deployment
>
> ---[Much spew deleted]---
>
> CpResource build/Deployment/Adium.framework/Versions/A/Resources/ 
> en_AU.lproj/EmoticonNames.strings "Frameworks/Adium Framework/ 
> Resources/en_AU.lproj/EmoticonNames.strings"
> ⋮
> pbxcp: EmoticonNames.strings: No such file or directory
>
> CpResource build/Deployment/Adium.framework/Versions/A/Resources/ 
> en_CA.lproj/EmoticonNames.strings "Frameworks/Adium Framework/ 
> Resources/en_CA.lproj/EmoticonNames.strings"
> ⋮
> pbxcp: EmoticonNames.strings: No such file or directory

This is a virgin 1.0.2 checkout. I've done *nothing* to this WC  
except try to build it.

Besides making sure that a tag *always* works, this rule will have  
the side-effect that the version in the About window exactly matches  
the revision of the tag.
________________________________
\ Peter Hosey / prh at boredzo.org
PGP public key ID: C6550423 (since 2007-01-01)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070410/33d0a372/attachment.sig>