[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [p2-dev] Avoiding Director-Added Repository Locations?
- From: "Mark Melvin" <Mark.Melvin@xxxxxxxxxx>
- Date: Wed, 10 Jun 2009 08:05:56 -0700
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acnp1kVJyYcLATkaScyjjea55GdKLQAABmPA
- Thread-topic: [p2-dev] Avoiding Director-Added Repository Locations?
Right, sorry. All I am doing is the
eclipsec.exe -application org.eclipse.equinox.p2.director
-metadataRepository <path_to_repo> -artifactRepository
And I end up with <path_to_repo> in my list of
repositories. I can see when this would be useful, but it would be nice if
it was avoidable, even via a command line flag.
I think you'll need to give more
details about what your installer is doing. Is it based on the p2 installer,
does it use the p2 director application, etc? In general these tools try not
to pollute the profile with extra install-time repositories, by removing any
repositories they added when install completes. There could be a bug with
someone not cleaning up properly, but it's hard to say for sure without
knowing more about what your installer is doing.
Sent by: p2-dev-bounces@xxxxxxxxxxx
06/09/2009 03:37 PM
P2 developer discussions
|"P2 developer discussions"
|[p2-dev] Avoiding Director-Added
I noticed as a side-effect of our installer
installing from a local
filesystem repository (basically on the install
CD), P2 adds a location
into the Available Software Sites that is
Really what I want is our internet-based URL.
That's fine, I can add
this via an addRepository(..) touchpoint
action - but how do I avoid the
filesystem based one from getting in there
(or how can I remove it)?
The problem with simply removing it is...well, I
have no idea what it
could be. Some people may run the installer from
the network, or a CD
drive that could be any drive letter.
I guess I
could just leave it there, but if it is a CD drive, won't this
every time the user checks for