pcp
[Top] [All Lists]

Re: [pcp] RFC: invocation of revised configure/make system

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: [pcp] RFC: invocation of revised configure/make system
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 20 Apr 2012 11:53:57 +1000
Cc: pcp developers <pcp@xxxxxxxxxxx>
In-reply-to: <20120419204235.GA18822@xxxxxxxxxx>
References: <20120419204235.GA18822@xxxxxxxxxx>
On Thu, 2012-04-19 at 16:42 -0400, Frank Ch. Eigler wrote:
> Hi - 
> 
> In relation to http://oss.sgi.com/bugzilla/show_bug.cgi?id=921, and a
> bunch of email that followed, plus a helpful phone conversation, I'd
> like to propose a revision to the configure/build system.
> 
> The current code uses a combination of GNUmakefile, configure.in, and
> Makepkgs to generate builds that are hard-wired to be installed on top
> of system directories such as /etc, /usr, etc.  I would like to
> generalize it to also support installation into private unprivileged
> directories (/home/developer/foo) and non-distro systemwide
> directories (/usr/local).  To do this, I suggest moving toward the
> more typical usage of autoconf.
> 
> The new build workflow would be either:
> 
> (a) for /usr/local or private installs:
>     autoconf  # since generated files are not in git any more
>     ./configure [--prefix=PRIVATE_DIRECTORY]
>     make all install
> 
> (b) for distribution-overlaying installs (/etc, /usr, etc.):
>     ./Makepkgs
> 
> That's it.  The previous
>     make configure_pcp
> target would not be needed and would be dropped.  The perl modules'
> would be treated the same as the C code, in that they would be installed
> in the appropriate PARENT_DIRECTORY or system directory as appropriate.
> 
> If this seems OK so far, I can go on about how this could be done..

No objections from me ... sounds promising, so please drill down on how
this would work.

Cheers, Ken.

<Prev in Thread] Current Thread [Next in Thread>