Hi Tres!
Tres Seaver wrote:
yuppie wrote:
So the use cases for these DeltaProfiles are very limited. Using XSLT
would allow us to unify DeltaProfiles and ExtensionProfiles, providing
an automated way for creating ExtensionProfiles.
The major use case for deltas (no matter whether they do
Regarding CMFQuickInstaller, I wanted to remind the list that CPS has
subclassed portal_setup to add a number of functionalities related to
upgrades (but not really uninstall): cps:upgradeStep.
I also revamped part of the ZMI to provide easier ways to apply one
import step for one profile (in
Hi Tres!
Tres Seaver wrote:
I'll note that my original architecture document[1] contemplated two
kinds of add-on profiles:
- ExtensionProfiles could register *new* kinds of steps, as well as
making non-destructive insertions to the configuration created by a
baseline profile.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Hi Tres!
Tres Seaver wrote:
I'll note that my original architecture document[1] contemplated two
kinds of add-on profiles:
- ExtensionProfiles could register *new* kinds of steps, as well as
making non-destructive
Hi Lennart!
Lennart Regebro wrote:
I don't exactly understand what makes a customization snapshot
different from an extension profile,
You can't understand what is different because there is no difference ;)
except that you note what profile it is diffed from.
Even this small difference
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
I don't exactly understand what makes a customization snapshot
different from an extension profile, except that you note what
profile it is diffed from.
Other than that, I think this proposal sounds good.
I'll note that
yuppie wrote:
Since CMF 1.5.1 CMFSetup/GenericSetup supports extension profiles. They
are quite useful, but their current format has some fundamental issues:
I posted something in a similar vein to this on plone-developers last
night, about using GenericSetup profiles for product
yuppie-2 wrote:
GenericSetup uses a completely different approach than
CMFQuickInstaller. It is focused on states, not on changes.
Indeed. From having used it recently, it just seems to be an easier way of
working, so I'm trying to find out how we can meet the use cases that CMFQI
meets
Hi Martin!
Martin Aspeli wrote:
- The procedure I have in mind depends on the ability to create
customization snapshots. As a first step the setup tool would create
this snapshot. In the next step it would combine all dependencies of
that snapshot minus uninstalled extensions plus new
