Date: Tue, 6 Sep 2016 16:46:47 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: CeDeROM <cederom@tlen.pl> Cc: freebsd-ports@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ports: on the fly pkg-plist creation from git pull Message-ID: <20160906164647.1d9c9af7@kalimero.tijl.coosemans.org> In-Reply-To: <CAFYkXjnPvAX2jkDzxae_pMKq1aKFw5oD=0ayAvYVgOoZhusMGA@mail.gmail.com> References: <CAFYkXjnPvAX2jkDzxae_pMKq1aKFw5oD=0ayAvYVgOoZhusMGA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Sep 2016 15:52:34 +0200 CeDeROM <cederom@tlen.pl> wrote:
> I am creating a port from a GIT repository. I would like to keep the
> GIT file structure to user can update the project with GIT tools. I
> know this is not the best and not even the valid way to update, but in
> this particular case there is no other choice yet.. and the project
> changes really fast so updates from GIT are reasonable and desired.
> Hopefully it will change in a next major release and we can simply
> create a package.
>
> I did the simple automation of project clone, submodiles clone,
> initial configuration, etc, inside port Makefile.
>
> The problem is with the pkg-plist. I can create one with `make plist`
> based on the staged filesystem and it works until update. I would like
> make to create a plist file after fetch and build as a part of
> automation. How can I call `make makeplis` on each build?
pkg-plist is processed before the staging area is created so running
makeplist from post-install or post-stage is too late. You'll have to
do something like this instead:
post-install:
(cd ${STAGEDIR}${PREFIX} && ${FIND} -s * -not -type d >> ${TMPPLIST})
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160906164647.1d9c9af7>