[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Creating InstallableUnits on the fly
- From: Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx>
- Date: Wed, 3 Jul 2013 12:19:35 +0000
- Accept-language: en-CA, en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: AQHOdxTLr176BCiaj0CrzJCKo9pj2ZlRg1YAgAAfMACAAV/iAP//vaKAgABad4D//8ZGsA==
- Thread-topic: [p2-dev] Creating InstallableUnits on the fly
As soon as you add an IU to a repo it is persisted.
Also if you don't change the version the IU that has been persisted stays over the new one since id+version => identity
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Krzysztof Daniel
Sent: July-03-13 7:45 AM
Subject: Re: [p2-dev] Creating InstallableUnits on the fly
On Wed, 2013-07-03 at 10:24 +0000, Pascal Rapicault wrote:
> IUs without artifacts are supported. This is used extensively throughout p2 testing.
> I think the issue you are running into is that each IU must provide a
> capability with its ID and version in the IIU. NAMESPACE_IU_ID If you look at a p2 IU in a repo, you should be able to see that.
I was pretty close. The problem was that droplets repos were writable and I did not know P2 would autosave them each time I modified requirements -> they were completely unusable.
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
p2-dev mailing list