[Silva-general] Upgrading buildout to different version

[Jonathan Bowlas]

Thanks Kit/Andy for the info, much appreciated - once we move into
production with this I'll move all products to their own parts and
leave the products dir for testing overrides.

J

2010/1/19 Andy Altepeter <aaltepet at bethel.edu>:
> Hi Jon,
>
>> It seems that checkAddedPaths is checking for any products that aren't
>> added via buildout into 'parts' but since I revised our buildout
>> scripts to install everything in 'products' the script raises this
>> exception informing me that these are new paths.
>>
>> To resove this I've commented out the call to checkAddedPaths from
>> Native.py and it works fine. So my question is twofold - is it ok to
>> comment out checkAddedPaths and should I really be installing
>> everything in 'parts'?
>
> Short answer: yes.  You can have a set of "zope products" installed in a part,
> and add automatically add that part as a 'products' directive in your
> instances zope.conf.  That's definitely the way to go.  Note your part
> directory doesn't need to be located in {buildoutroot}/parts.  The
> {buildoutroot}/products directory is a part, but in a different location.
>
> After you run buildout, it stores the state of that buildout in (I think)
> {buildoutroot}.installed.cfg, so it knows if new paths were added to a part
> (i.e. the {buildoutroot}/products directory) after the last time buildout was
> run.  The best bet is to use buildout to install your zope products.
>
> regards,
> Andy
>>
>> Cheers
>>
>> Jon
>>
>> _______________________________________________
>> silva-general mailing list
>> silva-general at lists.infrae.com
>> https://lists.infrae.com/mailman/listinfo/silva-general
>>
>
>