Re: [cross-project-issues-dev] Coexistence of Update Manager sites and P

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Answers embedded.

David M Williams ---06/22/2008 02:00:58 PM---I hope the list doesn't mind mere "how to use" question to this list ... but, figure it may impact

From:	David M Williams <david_williams@xxxxxxxxxx>
To:	<cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/22/2008 02:00 PM
Subject:	[cross-project-issues-dev] Coexistence of Update Manager sites and P2 repositories.

---

I hope the list doesn't mind mere "how to use" question to this list ... but, figure it may impact several projects, so figured it'd be a good place to discuss. 

And, there's actually several questions. 

With the old update manager technology, when we wanted to test the "get updates for existing features" _before_ the updates were actually at the production site, we could use a site policy file to "trick" update manger into looking elsewhere for the updates to existing features (namely, it'd look on the test site listed in the policy file). 
(See http://wiki.eclipse.org/Using_Policy_Files for how to do this). 

>So, question 1: Does P2 offer this same sort of thing? Does is allow a "policy file" of some sort? (I don't see the User Preference as their used to be, but figure maybe the concept is still there, but implemented differently?. 
	In p2, policy files are no longer necessary because what you install is unaware of where it got installed from. To test this case you simply need to add a repository containing the updates and search for updates.

>Question 2: Any "tips or tricks" on managing a site for both Update Manager and P2 Updates ... in other words, a site that contains upgrades for both Europa and Ganymede?  We in WTP have always strived to have one update site "for everything released". I know technically the same site can act as a UM site, and a P2 repository, I'm just wondering if anyone has tested this yet ... 
	From a runtime perspective, there is no particular tricks required to keep both files in the same location. p2 will first look for content.jar/xml and eventually digest/site.xml if the loading of the content.jar fails. We have been testing this on the eclipse update site since we still have a site.xml and content.jar, and it is also the case for the ganymede update site (http://ganymede-mirror2.eclipse.org/releases/ganymede/site.xml).

>or, if there will be any complications we should plan for? In particular, what we want is that if a user with Europa based product goes there for updates to their existing Europa features, that it will be obvious to them what to get, and they won't be confused and accidentally try to update to the Ganymede version of everything. 
	This is an UM question and this has not changed with p2 since the UM code stayed unchanged.

>Question 3. I guess question 2 begs the additional question ... is it expected, or has anyone tested, having a Europa installation, and then update everything to Ganymede?  This was asked a long time ago .... see bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=223434 ... any volunteers? Or anyone tried it yet? 
	This is not expected to work (and it has never been) and will not work because the resulting system will not be fully functional because of the absence of p2 information.


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev