On Apr 18, 2011, at 8:11 PM, Evan Schoenberg, M.D. wrote: > > > On Mar 29, 2011, at 12:26 PM, Ryan Govostes wrote: > >> Definitely yes. >> >> I am strongly opposed to the original decision to move binaries to trunk. I >> encountered a number of build errors when the switch occurred, and it >> prevents me from tweaking my compiler and SDK settings as I like, without a >> great deal of work. >> >> Let's move back to source for all of the frameworks, using subrepositories. >> If we can do a read-only mirror of the im.adium.adium branch of libpurple to >> our repo that'd be great. > > We should be able to use a subrepo, which will be read-only for anonymous and > read-write if you have appropriate push access, once libpurple makes the > switch to monotone. > > At that time, setting up a subrepo and then using an Xcode build target which > calls out to configure & make seems ideal. It's outside my comfort zone to > do it right, but I'd support someone wanting to take it on. You might look > to perian's build process, for example, which uses an Xcode project and > several targets with automake-based builds, as a useful model.
If someone will ping me when their move to hg finishes, I'll gladly take a run at this. > > -Evan
