[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Equivalent of Update Policy for P2

Miles:

> Nick: Is it also worth adding that you also need to control the list of repositories ("Available Software Sites")?

If you feel the wiki needs revision, don't hesitate. It is, by definition, an ever-growing document. Anything unclear or not fully explained welcomes your addition(s). All you need is a Bugzilla ID and you can start contributing. (Perhaps a screenshot of the unchecked repositiories would help?)

--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb

Inactive hide details for "Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>"Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>


          "Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>
          Sent by: p2-dev-bounces@xxxxxxxxxxx

          07/23/08 07:49 AM

          Please respond to
          P2 developer discussions <p2-dev@xxxxxxxxxxx>

To

"P2 developer discussions" <p2-dev@xxxxxxxxxxx>

cc


Subject

RE: [p2-dev] Equivalent of Update Policy for P2

OK. Once I removed references to the external Eclipse and Ganymede sites I stopped seeing attempts to connect to these sites whilst installing IUs from internal Eclipse and Ganymede mirrors. (The mirrors do not have a site.xml.)

Nick: Is it also worth adding that you also need to control the list of repositories ("Available Software Sites")?

Question(s):

1. How would one control the list of repositories when installing Eclipse using the p2 installer or director application?
2. We have an internal mirror containing a mix of 3rd party features sourced from a variety of external update sites. It does not have P2 metadata. When I add this site to my list of "Available Software Sites" every distinct update site mentioned by the features in the mirror gets added to my list as well. These are all external sites. How do I prevent this from happening?

Thanks,

Miles

Miles Daffin
Morgan Stanley | Technology

20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572

Miles.Daffin@xxxxxxxxxxxxxxxxx



From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Nick Boldt
Sent:
22 July 2008 16:23
To:
P2 developer discussions
Subject:
Re: [p2-dev] Equivalent of Update Policy for P2

Thanks for the info. I've updated the wiki:

http://wiki.eclipse.org/Using_Policy_Files

Can you review that and verify what I've written is correct?

Thx,

--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling ::
http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb

Inactive hide details for Pascal Rapicault/Ottawa/IBM@IBMCAPascal Rapicault/Ottawa/IBM@IBMCA

                  Pascal Rapicault/Ottawa/IBM@IBMCA
                  Sent by: p2-dev-bounces@xxxxxxxxxxx

                  07/22/08 09:00 AM

Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>
To

P2 developer discussions <p2-dev@xxxxxxxxxxx>
cc

P2 developer discussions <p2-dev@xxxxxxxxxxx>, p2-dev-bounces@xxxxxxxxxxx
Subject

Re: [p2-dev] Equivalent of Update Policy for P2

Here you are focusing on a particular limitation of the director application whose behavior could be argued to be correct :-) Currently the behavior you get is the same than if you had in the UI "added the repos", and then installed the IU listed on the command line.
As for avoiding reaching mirrors specified for a particular repo, there are two ways. Either you are in control of the repo in which case you don't add to the artifact repo the information on mirrors, or you are not and you can set the VM arg
"eclipse.p2.mirrors" to false. Still if you have multiple artifact repos, they will all be consulted before p2 gives up on dl.


Inactive hide details for Nick Boldt---07/22/2008 08:10:48 AM---Or, to put it another way... how are policy files [1] handled iNick Boldt---07/22/2008 08:10:48 AM---Or, to put it another way... how are policy files [1] handled in p2? How can you force p2 to use onl

From:

Nick Boldt/Toronto/IBM@IBMCA

To:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

07/22/2008 08:10 AM

Subject:

Re: [p2-dev] Equivalent of Update Policy for P2




Or, to put it another way... how are policy files [1] handled in p2? How can you force p2 to use only a specific mirror, rather than all the available mirrors?

[1]
http://wiki.eclipse.org/Using_Policy_Files

See also:


https://bugs.eclipse.org/bugs/show_bug.cgi?id=235491
https://bugs.eclipse.org/bugs/show_bug.cgi?id=236762
http://wiki.eclipse.org/Equinox_p2_director_application

--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling ::
http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb

Inactive hide details for "Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>"Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>
                                                                  "Daffin, Miles \(IT\)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>
                                                                  Sent by: p2-dev-bounces@xxxxxxxxxxx

                                                                  07/22/08 07:26 AM


Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>
To

"P2 developer discussions" <p2-dev@xxxxxxxxxxx>
cc
Subject

[p2-dev] Equivalent of Update Policy for P2

Hi All,

In 3.3 I could ensure that users could only update features from our internal mirror sites. Can anyone explain how I would do this with P2? (This seems like a gaping hole.)

Thanks,

Miles


Miles Daffin

Morgan Stanley | Technology

20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572

Miles.Daffin@xxxxxxxxxxxxxxxxx



NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/p2-dev
[attachment "pic08842.gif" deleted by Pascal Rapicault/Ottawa/IBM]
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/p2-dev

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/p2-dev



NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error._______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

GIF image

GIF image

GIF image

GIF image

GIF image