From owner-freebsd-ports@freebsd.org  Tue Jul 18 06:34:15 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CA6EC7DD2D
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue, 18 Jul 2017 06:34:15 +0000 (UTC) (envelope-from aehlig@linta.de)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 789731ED2
 for <freebsd-ports@freebsd.org>; Tue, 18 Jul 2017 06:34:15 +0000 (UTC)
 (envelope-from aehlig@linta.de)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 74465C7DD2C; Tue, 18 Jul 2017 06:34:15 +0000 (UTC)
Delivered-To: ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7213EC7DD2B
 for <ports@mailman.ysv.freebsd.org>; Tue, 18 Jul 2017 06:34:15 +0000 (UTC)
 (envelope-from aehlig@linta.de)
Received: from isilmar-4.linta.de (isilmar-4.linta.de [136.243.71.142])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 332A51ED0
 for <ports@freebsd.org>; Tue, 18 Jul 2017 06:34:14 +0000 (UTC)
 (envelope-from aehlig@linta.de)
Received: by isilmar-4.linta.de (Postfix, from userid 10)
 id C7CEB2008A3; Tue, 18 Jul 2017 06:34:12 +0000 (UTC)
Received: from howard.linta.de by isilmar-4.linta.de with BSMTP;
 18 Jul 2017 06:34:12 -0000
Received: by howard.linta.de (Postfix, from userid 1001)
 id 6907B6E3702; Tue, 18 Jul 2017 08:33:57 +0200 (CEST)
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>
References: <333c214c-4551-8f7d-9de4-ff4dabd33ab3@rawbw.com>
 <20170717073734.GC2012@howard.linta.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170717073734.GC2012@howard.linta.de>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 06:34:15 -0000

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}).