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): .
I also revamped part of the ZMI to provide easier ways to apply one
import step for one profile (in non-purge mode)
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
-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-
On 7/26/06, yuppie <[EMAIL PROTECTED]> wrote:
Even this small difference doesn't exist. The profile it is diffed from
is just a normal dependency.
OK. I'm trying to come up with errors in this plan, but I fail. The
closest i come is that you will need to have different extension
profiles for di
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
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 not
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 differen
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.
___
Zope-CMF maillist - Zope-CMF@lists.zop
Hi!
Martin Aspeli wrote:
yuppie wrote:
Yes. The ImportContext has only access to the last profile selected.
What still might happen with broken import handlers - especially
importVarious - is that the handlers themselves change settings
independent of any profile files.
Aha. What's the co
yuppie wrote:
Aha - so it seems was confused :) So, to be clear, "run all import steps"
will only apply to the last selected "active" profile, even if that's an
extension-profile?
Yes. The ImportContext has only access to the last profile selected.
What still might happen with broken import h
Hi Martin!
Martin Aspeli wrote:
Aha - so it seems was confused :) So, to be clear, "run all import steps"
will only apply to the last selected "active" profile, even if that's an
extension-profile?
Yes. The ImportContext has only access to the last profile selected.
What still might happen
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 exten
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
mee
Hi Martin!
GenericSetup uses a completely different approach than
CMFQuickInstaller. It is focused on states, not on changes.
The early versions of GenericSetup (FKA CMFSetup) didn't even have
extension profiles and importVarious handlers. I invented those hacks to
give GenericSetup more mo
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 installation
15 matches
Mail list logo
