[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-mirrors] What is the best way to do infrequent internal mirroring?
|
On 10/25/2011 01:51 AM, David Williams wrote:
On 10/24/2011 03:54 PM, Terry Parker wrote:
Yes the b3 aggregator creates a self-consistent repo--I really like
that. The problem we have with the b3 aggregator is that trying to
mirror something as simple as
"http://download.eclipse.org/releases/indigo/" and
"http://download.eclipse.org/webtools/indigo/", the
RepositoryVerifier reports "Cannot complete the install because of a
conflicting dependency" for multiple versions of the same plug-in.
What does the mirrored setup look like after it is mirrored? I'd
assume there is a top-level composite repository that aggregates the
original 3.N.N releases. If that is the case, mirroring the entire
repo, modifying the composite repository to cull out older Eclipse
versions, and then using the b3 aggregator might be the easiest
approach for us.
Yes, they are composites. In some cases the composite points to other
composites. Sometimes the composites URLs "point to" the file system,
sometimes to http URLs. (Yes, we've heard complaints before :) ...
such as bug 350031 [1] ... and its that way for a reason, so unlikely
to change)
If you have the disk space, I think using the rsync script three times
(or more) a year is also a valid solution.
Denis