From owner-freebsd-current@FreeBSD.ORG  Fri May 30 08:40:21 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 784A19C7;
 Fri, 30 May 2014 08:40:21 +0000 (UTC)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "cloud.theravensnest.org",
 Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4171D2E21;
 Fri, 30 May 2014 08:40:20 +0000 (UTC)
Received: from [192.168.0.96] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net
 [82.26.1.52]) (authenticated bits=0)
 by theravensnest.org (8.14.7/8.14.7) with ESMTP id s4U8eA5P030239
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Fri, 30 May 2014 08:40:12 GMT (envelope-from theraven@FreeBSD.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: official pkg repo with WITHOUT_X11=true
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <CAPS9+Sv+eSQU==8BYubQ=W2_k13EnS=Zkps96vB7kd+QteRCBg@mail.gmail.com>
Date: Fri, 30 May 2014 09:40:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <35F82676-BED6-4A12-8CC1-3D6C3E8C3281@FreeBSD.org>
References: <alpine.BSF.2.00.1405281803440.43518@erdgeist.org>
 <20F90EAB-ADC5-468C-9AFD-73F93794C4B2@FreeBSD.org>
 <800bc8e04e4cfed10632cca993cce8fa@shatow.net>
 <43B971CB-4810-458D-BC5D-3DC2DC764E39@FreeBSD.org>
 <E7AB8D4C-24DC-4E7E-A46F-441AE2C84806@FreeBSD.org>
 <53874244.5060609@freebsd.org>
 <CAPS9+Sv+eSQU==8BYubQ=W2_k13EnS=Zkps96vB7kd+QteRCBg@mail.gmail.com>
To: Andreas Nilsson <andrnils@gmail.com>
X-Mailer: Apple Mail (2.1874)
Cc: Current FreeBSD <freebsd-current@freebsd.org>,
 Allan Jude <allanjude@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 08:40:21 -0000

On 29 May 2014, at 23:06, Andreas Nilsson <andrnils@gmail.com> wrote:

> Having a "parent" set would be nice, yes. I maintain two repos for =
several
> FreeBSD-versions. Being able to pull some of the deps from packages =
instead
> of blindingly building would be nice.

Yes, for a lot of cases you only want to build a small handful of =
packages with different options, so it would be nice if you could find =
out exactly what the options were for the upstream build and only build =
the packages yourself if you've specified different options or depend on =
a package with different options.

The problem is the notion of dependency here.  In some cases, linking =
against a shared library built with different options won't change your =
program's code, it will just make more things work.  In other cases, =
you'll have different things exposed in headers and even build-only =
dependencies will impact the output. =20

David