Date: Tue, 18 Jul 2017 08:33:57 +0200 From: "Klaus T. Aehlig" <aehlig@linta.de> To: Yuri <yuri@rawbw.com> Cc: "ports@freebsd.org" <ports@freebsd.org> Subject: Re: Anybody knows how to patch tarballs that bazel extracts? Message-ID: <20170718063357.GA1276@howard.linta.de> In-Reply-To: <20170717073734.GC2012@howard.linta.de> References: <333c214c-4551-8f7d-9de4-ff4dabd33ab3@rawbw.com> <20170717073734.GC2012@howard.linta.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 17, 2017 at 09:37:34AM +0200, Klaus T. Aehlig wrote:
> However, even with that approach, you should be aware that you're
> embedding the relevant dependencies rather than using them from
> ${LOCALBASE}. So, in the long run, it might be desirable to patch the
> relevant targets in the BUILD files using those external resources to
> point to ${LOCALBASE}. Maybe, one could even lobby for a new_local_library
> WORKSPACE rule at bazel-dev@googlegroups.com. But that's all long-term
> perspective...
Actually, it is not that far in the future; in fact, event today, bazel's
cc_library rule accepts an .so in the sources attribute, making a work around
possible (patching WORKSPACE to point to a hand-crafted directory under WRKDIR
as a local_repository, with hand-crafted BUILD-files, essentially taking
things from ${LOCALBASE}).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170718063357.GA1276>