[Adium-devl] SoC Adium w/ libpurple

[Evan Schoenberg]

There's supposedly some way to have a subversion repo mirror a  
monotone one, but I don't think that's necessary.

Here's what I suggest: Use monotone for libpurple work.  Use the  
script which already exists to automatically sync the monotone  
repository on a local checkout to your own Libpurple.framework  
checkout.  For bonus points, that checkout is a subversion branch,  
and after using the script or at milestones commit to the subversion  
branch.

Any monotone checkout allows local commits and branching -- no need  
for anything serverside, though I've pinged the pidgin devel list  
about making that possible, too.

So:
1) Checkout pidgin monotone to ~/pidgin.  Checkout  
Libpurple.framework svn to ~/libpurple. Checkout adium to ~/adium
2) Work on ~/pidgin
3) mtn commit if desired
4) ~/libpurple/pidgin_update
	This will update your local svn checkout from ~/pidgin, apply any  
Adium-specific patches, build Libpurple.framework, copy it into the  
appropriate place in the adium checkout, and delete the built plugin  
so that XCode properly recompiles and rebuilds when Adium builds next.
5) svn commit if desired
6) Build and run Adium

Does that seem reasonable?

-Evan

On Apr 16, 2007, at 12:38 PM, Augie Fackler wrote:

> Hm, I'm having trouble coming up with ideas of good ways to handle
> this. Does anyone know how well monotone and svn can interact with
> each other?
> Augie
>
> On Apr 15, 2007, at 5:52 PM, Andreas Monitzer wrote:
>
>> Hi folks,
>>
>> Thanks for picking my project :) I've started my planning phase, and
>> am thinking about how I should integrate the changes I need into
>> libpurple.
>> For this, I'd need a branch in some way. However, libpurple was moved
>> to the monotone version control system. I'd prefer having a single
>> repository to work on, since my Adium branch and my libpurple branch
>> have to be kept in sync (changes in libpurple will need the
>> corresponding changes in Adium). How should I do this? This might
>> also be an issue for other Adium SoC projects.
>> We also have to coordinate this with the libpurple developers.
>>
>> andy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070416/783bad13/attachment-0001.html>
-------------- 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/20070416/783bad13/attachment.sig>