To: gnu-arch-users@gnu.org
Mail-Followup-To: gnu-arch-users@gnu.org
Subject: Re: [Gnu-arch-users] What's the rationale behind the
	cmd-build-config.c restrictions?
References: <87zmyu50ym.fsf@trouble.defaultvalue.org>
From: Matthew Dempsky <jivera@flame.org>
Date: Fri, 28 Jan 2005 14:55:03 -0600
In-Reply-To: <87zmyu50ym.fsf@trouble.defaultvalue.org> (Rob Browning's
	message of "Thu, 27 Jan 2005 09:46:41 -0600")
Message-ID: <87mzut5l5k.fsf@flame.org>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 981
Lines: 35
Rob Browning <rlb@defaultvalue.org> writes:

> In cmd-build-config.c we have:
>
>     if (!arch_valid_config_name (config))
>       {
>         safe_printfmt (2, "%s: invalid config name (%s)\n",
>                        argv[0], config);
>         exit (2);
>       }
>
>     tree_root = arch_tree_root (0, dir, 0);
>
>     if (!tree_root)
>       {
>         safe_printfmt (2, "%s: not in project tree (%s)\n",
>                        argv[0], dir);
>         exit (1);
>       }
>
> What's the rationale behind these restrictions?

Mostly it's because the config is built relative to the tree root.  I
suppose you could add a -d option (or something) for where the tree
root should be located instead, and then it's no longer necessary to
be in an arch tree.


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/