--
Rick Hurst, Web developer, Bristol, England
http://www.rickhurst.co.uk
Mm - I didn't want to give the impression that using it was a no-no -
only that I didn't use it, since I like to keep the build process as
similar as possible across Mac OS X and Linux to save my sanity
(amongst other reasons).
Cheers,
Dan
--
Dan Fairs <dan....@gmail.com> | http://www.stereoplex.com/
> Mm - I didn't want to give the impression that using it was a no-no -
> only that I didn't use it, since I like to keep the build process as
> similar as possible across Mac OS X and Linux to save my sanity
> (amongst other reasons).
Being lazy/ sysadminphobic i'd rather use the installer - are there
any specific obstacles I am likely to come up against? The main point
of this excercise is to familiarise myself with all the new
eggybuildoutadapter stuff
Duncan Booth encouraged me to look into the egg-tastic Buildout
future, and so far I believe in it: There is currently a transitional
mess of different bits of legacy and new methods, but for maintaining
a system, buildout is the way forward.
Dan's how-to was the key - and having control of your python using
that virtual thingy is rather vital.
F.
--
Fraser Stephens
> Duncan Booth encouraged me to look into the egg-tastic Buildout
> future, and so far I believe in it: There is currently a transitional
> mess of different bits of legacy and new methods, but for maintaining
> a system, buildout is the way forward.
>
> Dan's how-to was the key - and having control of your python using
> that virtual thingy is rather vital.
OK sold. I think python versions (and not knowing which one i'm using)
have caused me grief in the past, so i'd best roll up my sleeves :)
I skipped the "fresh-build and install of Python" steps in Dan's
how-to, and used the one that came in the plone 3 installer. Worked
for me...
Nice thing is that my production instance (on Linux) is identical to
my OSX instance. I've stopped using the Windows server for obvious
reasons.
F.
--
Fraser Stephens