Re: [Gnu-arch-users] copying archive?

[Abraham Egnor]

I apologize for the vagueness in terminology; I'm still fairly new to
arch.  Mirroring, as I understand it, allows a read-only (i.e. no commits
allowed) copy of a repository to be made at a new location, but with the
same name.  What I'd like to do is somewhat different - make a read-write
(i.e. commits can be made) copy of a repository to a new location and with
a new name.

Perhaps more detail about the problem would be helpful.  I'm investigating
arch for use in a small software company of which I am an employee. 
Currently, each developer has their own archive with their own version of
the various projects we've been working on.  However, we'd like to create
a new archive that has a "canonical" version of all of our projects, from
which developers can fork their own versions as needed.  A simple way to
do this would be to just make tags in the canonical archive from whatever
source we decide; however, that has the disadvantage of leaving the
revision history still in some random developer's home directory, where
it's more likely to get accidentally nuked than if it were elsewhere.

Abe

Aaron Bentley <address@hidden> writes:
>On Mon, 2004-02-16 at 16:29, Abraham Egnor wrote:
>> Is it possible to copy or move an archive from one location to another,
>> i.e. from "address@hidden/project--branch--version" to
>> "address@hidden/project--branch--version"?  
>
>Having the same archive available at multiple locations is fine.  But
>let's be clear about location:
>it's the URL, not the name.  address@hidden is the archive name, and is part of
>the package/version/revision name.
>
>For example, my archive is available at
>
>
>Mirroring is supported directly.  To achieve what you want, you could
>mirror the archive, and tag.
>
>Then if anyone wants access to an old version of a disappeared archive,
>you can just make your mirror available, and they can use that.
>
>Aaron
>
>-- 
>Aaron Bentley
>Director of Technology
>PanoMetrics, Inc.
>
>