arx-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Arx-users] How to init a new project tree to a non-default archive?


From: Walter Landry
Subject: Re: [Arx-users] How to init a new project tree to a non-default archive?
Date: Mon, 04 Apr 2005 00:40:38 -0400 (EDT)

Kevin Smith <address@hidden> wrote:
> I think I want to have several archives on my machine. Thus, I don't
> want to set a global default archive. But there doesn't seem to be any
> way to specify which archive to use when doing the "arx init" on a tree.
> The error message says "No default archive set and no archive specified"
> but "arx init --help" doesn't say how to specify an archive.

For an archive foo with branch bar, the syntax is foo/bar.  I have
changed the error message (arx.2.2,62) to say

  No default archive set and no archive specified
          arx
  To set a default archive, use "arx param default-archive <archive name>".
  To specify the archive in the name, for an archive "foo" and
  a branch "bar", the syntax is "foo/bar".

and now "arx init --help" has an example (arx.2.2,63)

----------------------------------------------

address@hidden:~$ arx init -H
Initialize the current tree
usage: init [options] branch

 --dir DIR                      cd to DIR first
 --no-add                       Don't add files

Initialize the current directory so that it can be commit'ed
as a completely new line of development.  For example,

  arx init foo/bar

will initialize the current directory as the project "bar" stored
in the archive "foo".  If you have set your default archive to "foo"
(see arx param -H), then it is just

  arx init bar

ArX will automatically (unless given the --no-add option) recursively
add all of the files and directories so that they will be included in
the archive.

----------------------------------------------

> Should I enter this as a bug?

Reading through the manual, I noticed there is no one place that
describes the syntax (foo/bar.baz,14).  There should be.  I have
created a bug entry.

Thanks,
Walter





reply via email to

[Prev in Thread] Current Thread [Next in Thread]