discuss-gnustep
[Top][All Lists]
Advanced

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

Re: GNUSTEP_INSTALLATION_DIR and GNUSTEP_INSTALLATION_DOMAIN


From: Yves de Champlain
Subject: Re: GNUSTEP_INSTALLATION_DIR and GNUSTEP_INSTALLATION_DOMAIN
Date: Sun, 27 May 2007 08:37:58 -0400


Le 07-05-27 à 04:40, Sebastian Reitenbach a écrit :

Hi,

I am fiddling around with updating the openbsd gnustep ports. With the new gnustep-make 2.0 it tells me I shall use GNUSTEP_INSTALLATION_DOMAIN in
favour of GNUSTEP_INSTALLATION_DIR.

The package creation process first installs everything in a fake root
directory, then builds a file list for the package and creates the package.

With the 1.X make I defined sth. like this in the Makefile:
GNUSTEP_INSTALLATION_DIR=${WRKINST}/$(GNUSTEP_SYSTEM_ROOT)
WRKINST is the fake root directory mentioned above.
With the new version, I shall use sth. like this:
GNUSTEP_INSALLATION_DOMAIN=LOCAL


Is it possible to add a prefix like WRKINST to the
GNUSTEP_INSTALLATION_DOMAIN to be able to install it in an arbitrary
location? I took a quick look into the common.make file, but I couldn't find any hint. Will the GNUSTEP_INSTALLATION_DIR dissappear in a future version of gnustep-make? If it is not possible, do I can suppress the deprecated
warnings regarding GNUSTEP_INSTALLATION_DIR while running make?

gnustep-make now understand DESTDIR

Also, you don't really need to set GNUSTEP_INSTALLATION_DOMAIN since LOCAL is the default and the few packages that go in SYSTEM are already up to date.

I use this TCL script just in case (reinplace is BSD's sed_inplace, the regex could be smarter but I'm not ;-) :

foreach gmf [glob -nocomplain -directory ${worksrcpath} GNUmakefile*] {
    reinplace \
"s|GNUSTEP_INSTALLATION_DIR = \$\(GNUSTEP_SYSTEM_ROOT\)| GNUSTEP_INSTALLATION_DOMAIN=SYSTEM|g" \
            $gmf
}

yves





reply via email to

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