Date: Mon, 19 Mar 2018 09:47:04 -0700 From: John Baldwin <jhb@freebsd.org> To: Mark Johnston <markj@freebsd.org> Cc: Mariusz Zaborski <oshogbo@freebsd.org>, Mark Linimon <linimon@lonesome.com>, 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 Message-ID: <5637307.jbg60LYNR5@ralph.baldwin.cx> In-Reply-To: <20180318170738.GB35894@raichu> References: <201711120834.vAC8YQUq006611@repo.freebsd.org> <20180318142039.GA81224@x-wing> <20180318170738.GB35894@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <N-1> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5637307.jbg60LYNR5>