From owner-svn-src-all@freebsd.org Mon Mar 19 17:25:58 2018 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39C8DF5D8D3; Mon, 19 Mar 2018 17:25:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC4B77AA5C; Mon, 19 Mar 2018 17:25:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 751AF10A87D; Mon, 19 Mar 2018 13:25:57 -0400 (EDT) From: John Baldwin To: Mark Johnston Cc: Mariusz Zaborski , Mark Linimon , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r325739 - in head: lib/libcasper/services lib/libcasper/services/cap_syslog share/mk Date: Mon, 19 Mar 2018 09:47:04 -0700 Message-ID: <5637307.jbg60LYNR5@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180318170738.GB35894@raichu> References: <201711120834.vAC8YQUq006611@repo.freebsd.org> <20180318142039.GA81224@x-wing> <20180318170738.GB35894@raichu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 19 Mar 2018 13:25:57 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 17:25:58 -0000 On Sunday, March 18, 2018 01:07:38 PM Mark Johnston wrote: > On Sun, Mar 18, 2018 at 03:20:39PM +0100, Mariusz Zaborski wrote: > > On Mon, Mar 05, 2018 at 11:19:16AM -0600, Mark Linimon wrote: > > > On Mon, Mar 05, 2018 at 11:13:58AM -0500, Mark Johnston wrote: > > > > The growing divergence with stable/11 makes it rather painful to > > > > maintain a port, depending on libcasper, that aims to work on both 11 > > > > and head. > > > > > > Even an MFC won't help you, in the medium-term. > > > > > > e.g. via https://www.freebsd.org/security/#sup, even if the MFC made it > > > into 11.2, you would still have several months of supporting the old > > > one. (The FreeBSD package builds are based on the oldest supported > > > point release from a branch.) The current estimate for 11.2 is late June. > > > > > > mcl > > > > Hi, > > > > Sorry for delay I just get back. > > > > Yes I can integrate all my changes in libcasper and I guess libcapsicum. > > I'm did do a lot of integrations to stable so I have one question - > > if I understand correctly all changes which change API/ABI but are > > pointed as SHLIB_MAJOR I can safety integrate. > > > > Mark what else can I do? > > Sorry, I don't quite follow. I don't think SHLIB_MAJOR bumps can be > MFCed: what happens if an SA is later released for the library in > question? We have MFC'd them in the past I believe and rolled the shlib into the misc/compatXX package (so that one might need misc/compat11 to run older 11.x binaries even on an 11.x host). We haven't done that nearly as often since adding symbol versioning though. I don't know if we ever had to deal with merging an SA to an old library version though. -- John Baldwin