[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c
From: |
Robert Collins |
Subject: |
Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c restrictions? |
Date: |
Sat, 29 Jan 2005 10:07:44 +1100 |
On Fri, 2005-01-28 at 14:55 -0600, Matthew Dempsky wrote:
> Rob Browning <address@hidden> writes:
>
> > 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.
I never added 'find the root and build from there' or the 'require a
root' to config-manager, yet it was still very useful ;). In terms of
impact, only scripts that cd somewhere other than the tree root before
running *-config commands will be impacted. It uses -d to determine
where to build the config.
I think that removing the constraints, and the heuristic search path to
the config, and then adding -d would be best from UI point of view.
Rob
signature.asc
Description: This is a digitally signed message part