[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Upgrades through ProfileChangeRequest
- From: Matt Hughes <hughes.matt@xxxxxxxxx>
- Date: Wed, 7 Apr 2010 12:28:16 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OegVoQXIZ+lNiFF5YmPCtiFUN4VzbM3Iz3ABB5vMjAXruCBjkRZzWxrOIbEn4KpFTg IEVpeGgOmiUGHeNH9995OOAB9WW2GKDb3weVUSMqID4s0rRhlglb5D0OByCrFDoIecXX TUfN9Inc631e+bTOws1GPmwte3k9Of492qPts=
I have a pretty simple use case I believe. I want to install an
artifact via a ProfileChangeRequest and if an earlier version of that
artifact already exists, I want to remove the old version and install
the new version.
For some reason, I thought all I had to do was mark the addition to
the PCR, hand it to the IDirector and it would figure out the upgrade
(that is, add a removal action for the old version). I realize that
doesn't work -- at least not as I am doing it now -- but isn't there
some way to tell P2 (via requirements, maybe?) to perform the upgrade?
Unless I'm missing something, it is up to the developer to search
through their repositories and mark the old versions as removals in
the PCR. Seems like this is a pretty basic use case.