|Re: [p2-dev] Follow up on shared install issue|
|I also thought that this could fix the issue we encounter for shared install, however I think it will just delay the problem to when the user installs something.|
To be more precise, here is the situation I'm worried about
- When the EPP package is built, the bundles.info will contain the slf4j bundle
- When the user runs the install (and depending the repositories enabled), slf4j may end up being removed (because the code that computes the attachment of the current profile also uses the planner), thus producing a user bundles.info that is not a proper subset of the shared one.
Even if this is not the real case, some users have shown more complex setup (install more, lock read only, etc.) that could end up revealing the issue and making the troubleshooting even more complex.
On 2010-08-21, at 10:51 PM, Ian Bull wrote:
Since the problem happens when we set roaming back to true (because we plan, but the plan isn't stable and thus things get removed), we could also fix it by forcing the roaming property in without computing a plan (just create a custom plan setting roaming back to true). Again, this won't fix the root problem, but it will give the EPP guys a director app that will work.