Recover Make ARG's from a ports Install

[Randy Pratt]

On Mon, 12 Mar 2007 20:15:20 -0400
Parv <parv at pair.com> wrote:

> in message <042d01c76476$b226bc30$16743490$@net>,
> wrote Alexander Schlichting thusly...
> >
> > On a server I have a package installed using ports and now I have
> > to install the package with exactly the same make arguments on
> > another server. I just don't find a way to see what arguments
> > where used to install it the first time. With Linux I would look
> > into config.status is there something similar with FreeBSD?
> 
> There may be config.status present in $WRKSRC directory (in a port
> directory, run "make -V WRKSRC" to find the value) if that port's
> make process generates such a file AND you have not run "make clean"
> yet.  (That also means you have to compile the port yourself.)
> 
> To save make arguments for future use, you could write a wrapper
> which would save the arguments in a file|database before running
> appropriate make target.  Use the same wrapper to retrieve the
> stored arguments.
> 
> Below is my attempt at such a wrapper (feel free to change) ...
> 
>   http://www103.pair.com/parv/comp/src/sh/pmk
> 
> 
> ... to see available commands just run "pmk" without any arguments.
> Provide arguments to a make target as ...
> 
>   pmk <command> [ arg_1 arg_2 arg_3 ... ]

There is already a mechanism in place for this:

	/usr/local/etc/pkgtools.conf

See man 5 pkgtools.conf for a full description.  It has the advantage
that portupgrade will use the contents of that file when updating
to new versions so that your settings are not lost.

Make arguments as well as a variety of other options for installing
and updating ports can reside there.  Typically, I use this if
there are no OPTIONS (ie, "make config") settings available and
I need to use non-default options.

The only difference is that you would use "portupgrade -N ..." or
portinstall to install new ports rather than "make install".  See the
man pages for further information.

HTH,

Randy
--