Date: Wed, 4 Feb 2009 09:48:36 +0000 From: Florent Thoumie <flz@xbsd.org> To: Paul Schmehl <pauls@utdallas.edu> Cc: freebsd-ports@freebsd.org Subject: Re: Question about WRKSRC Message-ID: <a01628140902040148w3ca9b47fk212bca69065d69bb@mail.gmail.com> In-Reply-To: <81F17B20B78F9C5531571788@10.40.128.112> References: <81F17B20B78F9C5531571788@10.40.128.112>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 4, 2009 at 4:42 AM, Paul Schmehl <pauls@utdallas.edu> wrote:
> I maintain the sguil ports; security/sguil-server, security/sguil-sensor and
> security/sguil-agent. It came to my attention today that the pkg-install
> script that I've written for the security/sguil-server port fails during
> package building. (The script works fine when compiling from source.)
>
> The problem appears to be related to the location of WRCSRC, which appears
> to be different than it is when building from source. Am I correct about
> that? Is WRCSRC different when building packages? If so, is there a way to
> differentiate programmatically between a port being built from source and
> one being built from a package?
There's no WRKSRC directory when a package is installed.
I've had a look at sguil-server and you have two options. The first
one is to install your sql script somewhere under ${DATADIR} then read
it from there in your pkg-install script. The second, better in my
opinion, is to move most of your POST-INSTALL target into a shell
script of its own that you'll install in ${DATADIR} (note that it
still requires to install that sql file as well). Quick look shows
that your port is interactive, and not marked as such in Makefile. If
you choose to go with solution #1, then you'll have to set
IS_INTERACTIVE=yes (unless I'm wrong of course).
--
Florent Thoumie
flz@FreeBSD.org
FreeBSD Committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a01628140902040148w3ca9b47fk212bca69065d69bb>