Yeah I had occasion to use that build-pear-package.xml the other day, and I.. uh.. liked it ;) I'll have to look at the channel piece of the new PEAR stuff too. I had set up some of the beta stuff at one point, but I'm sure it'll need tweaking to work properly. I'll see about getting to that :)
Thanks, --Bob On 9/20/05, David Zülke <[EMAIL PROTECTED]> wrote: > Heh I recently rolled the 1.1.1 release of Propel which was my first attempt > at building a PEAR package and... uhm... well, there's a > build-pear-package.xml in generator/pear/ which does the job :) You might > want to have a look at it to see how it works. Or rather... yeah. As soon as > we're ready for 0.10, I'll build that package. *speaks up* > > - David > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Bob Zoller > > Sent: Wednesday, September 21, 2005 12:40 AM > > To: Agavi Development > > Subject: Re: [agavi-dev] Merging Globalization Branch (NOTE NOTE NOTE) > > > > I meant to post something to the list about the mailman hiccup this > > morning, but I got sidetracked. I'm not sure why it died, but it's > > back now, and I don't think anything was lost, only delayed. > > > > Mike I'm all for merging your branch. I browsed your code this > > morning and I'm excited to get it merged. Let me know what changes > > you need made to agavi.org and I'll get them handled. > > > > Also, along the lines of rolling a release: did anyone get a chance > > to look at the way Propel and Creole make their PEAR packages? (cough, > > David ;) ) I guess with the recent release of PEAR 1.4 we can > > actually provide a channel too. I don't have a ton of free time at > > the moment, so if anyone has the desire to help out with any of that, > > speak up! :) > > > > Thanks, > > --Bob > > > > > > On 9/20/05, Mike Vincent <[EMAIL PROTECTED]> wrote: > > > (Resending this, David said he never saw it come through, so here it is! > > ) > > > > > > I believe the globalization branch is ripe for a merge. > > > > > > The bulk of this change is that rather than configure controllers via > > > factories.ini, you will now configure Contexts via contexts.ini. So, > > > factories.ini is no longer needed but I suggest you copy the sample > > > contexts.ini into place and study the differences in your old > > > factories.ini and the new contexts.ini to ensure you have the proper > > > implementations configured for your project. You will also want to > > > alter your index.php according to the one found in the samples > > > directory as you no longer load the controller directly and dispatch > > > it. > > > > > > Other notable changes: > > > Controller is a true abstract factory instead of a broken singleton > > > Controller::getInstance is deprecated, use Controller::newInstance() > > > Controller::initialize is now public > > > Fixed bug in Storage which prevented auto_start from being turned off > > > Daniel Swarbrick's PDO driver contribution > > > ReturnArrayConfigHandler got an option to parse values into booleans > > > (real_booleans) > > > SmartyView uses the SMARTY_CACHE_DIR setting, else uses AG_CACHE_DIR > > > for cache dir. > > > Lots of refactored and a handful of new tests! :) > > > > > > If nobody hollers, I think I'll be merging it in tomorrow evening, > > > provided I can coordinate the necessary changes to agavi.org with Bob. > > > > > > -Mike > > > _______________________________________________ > > > agavi-dev mailing list > > > [email protected] > > > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > > > > > _______________________________________________ > > agavi-dev mailing list > > [email protected] > > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > > > > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
