Date: Sun, 18 Mar 2018 13:07:38 -0400 From: Mark Johnston <markj@FreeBSD.org> To: Mariusz Zaborski <oshogbo@FreeBSD.org> Cc: 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: <20180318170738.GB35894@raichu> In-Reply-To: <20180318142039.GA81224@x-wing> References: <201711120834.vAC8YQUq006611@repo.freebsd.org> <20180305161358.GA704@raichu> <20180305171916.GA2359@lonesome.com> <20180318142039.GA81224@x-wing>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180318170738.GB35894>