23. apr. 2013 kl. 10:35 skrev Jochen Dekeyser [via Plone]
<[email protected]>:
> Hi,
>
> I want to install an additional profile of another add-on (a dependency like
> in metadata.xml) in an upgrade step. Now, I do this with some custom code.
> Although it works, it looks like overkill... Is there some GenericSetup-stuff
> that can handle this kind of situation (like metadata.xml but for
> upgradesteps)?
If there is a profile for the upgrade step, it could work "the same way" as a
dependency (replace "default" with "upgrade profile" name"
> Jochen
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://plone.293351.n2.nabble.com/Best-practice-to-install-additional-dependency-profile-in-upgradestep-tp7564667.html
> To start a new topic under Product Developers, email
> [email protected]
> To unsubscribe from Plone, click here.
> NAML
--
View this message in context:
http://plone.293351.n2.nabble.com/Best-practice-to-install-additional-dependency-profile-in-upgradestep-tp7564667p7564669.html
Sent from the Product Developers mailing list archive at Nabble.com.
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
