From owner-freebsd-arch@FreeBSD.ORG Fri May 16 21:31:06 2014 Return-Path: Delivered-To: freebsd-arch@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 8BD4B790 for ; Fri, 16 May 2014 21:31:06 +0000 (UTC) Received: from mail-qg0-f46.google.com (mail-qg0-f46.google.com [209.85.192.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9972B12 for ; Fri, 16 May 2014 21:31:06 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id q108so5043868qgd.5 for ; Fri, 16 May 2014 14:30:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=xzBKRxk0LsUYE1Rbf4eZNGrV8r0ZbPbMjD7+nu34roE=; b=Gddokdy9AKCFthlzX4Pg7lgKyjgoHzIROb6LtYhk4bEPzHUnVzkvr+7DXx160ZVx8D vMicRPxwlXPaar85UTgj5Bhf1qIN7OXVejn2xJbMb7Uv3VuT8Rl4pxqoBVUf198SF9uo HDecfvNKEUt3JOt4sFjkDXjD/nm7ej1sUR223YS8j59/9q54xF6P4RsDpQD8ezsTNlvi iJDMfzJLtu4o9fUF7/0ZI8fw2LIxdjnVxEZsSFLaMx7tj4G0jwC2ZyWOHw0kTNhKNV/5 +ucWkzLFhcWud7jpvEX+HvpcsPZAaaQ+w5SBdDhgT4Mil8FMnq4DCR8yKDXkY8Wr/ifV aSxg== X-Gm-Message-State: ALoCoQlkUyU07KnRQAH0QCizkpLuEjchg7xNgRHIUzkozkj9b3vKAUoz/DhZZcMIgaZULYXzNxkM X-Received: by 10.224.80.195 with SMTP id u3mr27302709qak.37.1400275859698; Fri, 16 May 2014 14:30:59 -0700 (PDT) MIME-Version: 1.0 Sender: jmmv@meroh.net Received: by 10.96.83.99 with HTTP; Fri, 16 May 2014 14:30:38 -0700 (PDT) X-Originating-IP: [137.122.64.53] In-Reply-To: <20140516041003.E4469580A1@chaos.jnpr.net> References: <20140516041003.E4469580A1@chaos.jnpr.net> From: Julio Merino Date: Fri, 16 May 2014 17:30:38 -0400 X-Google-Sender-Auth: ODXH0onMe_DDHni8qH1ALyLTUsM Message-ID: Subject: Re: Make atf libraries private To: "Simon J. Gerraty" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 21:31:06 -0000 On Fri, May 16, 2014 at 12:10 AM, Simon J. Gerraty wrote: >>I'd like to make the libatf-c and libatf-c++ private, both in CURRENT _and_ in >> stable/10. > > Can you briefly explain why Oh sure. Basically because I do not want the potentially-ancient ATF libraries in base to leak to external components, and because I do not want to have to worry about maintaining compatibility with these ancient versions when the time comes. (This will start happening as soon as FreeBSD 10 ages, for example.) At some point, ports that install tests (lutok, kyua, shtk, ...) *will* require a newer version of atf. Being able to just update devel/atf within ports and get the newer versions of the other ports working is trivial. Having to coordinate the ports updates with newer FreeBSD releases just so that those ports can be updated will be a nightmare. It seems nicer to me to restrict the ATF libraries in base to what FreeBSD needs them for: i.e. the ATF-based test programs inside the tree. Anything else can just install the external package from ports OR it can explicitly link against the private library -- clearly knowing what the compatibility-related consequences of doing so are. (As an aside, it seems that FreeBSD, as a project, wants to move as many libraries into private as possible partly for the reasons mentioned above. This came up during the devsummit. I'm wondering if this was documented anywhere...)