From owner-freebsd-pkgbase@freebsd.org Mon May 30 06:34:22 2016 Return-Path: Delivered-To: freebsd-pkgbase@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5C3AB54E04 for ; Mon, 30 May 2016 06:34:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7538516D4; Mon, 30 May 2016 06:34:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1b7GmI-0001zs-Vi; Mon, 30 May 2016 09:34:18 +0300 Date: Mon, 30 May 2016 09:34:18 +0300 From: Slawa Olhovchenkov To: Glen Barber Cc: Ben Woods , "freebsd-pkgbase@freebsd.org" Subject: Re: /etc/rc.d/zfs and /etc/rc.d/zvol no longer in FreeBSD-runtime package? Message-ID: <20160530063418.GB34407@zxy.spb.ru> References: <20160527210001.GI4025@FreeBSD.org> <20160529175701.GA80759@FreeBSD.org> <20160529221945.GE80759@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160529221945.GE80759@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 06:34:22 -0000 On Sun, May 29, 2016 at 10:19:45PM +0000, Glen Barber wrote: > On Mon, May 30, 2016 at 12:13:58AM +0200, Ben Woods wrote: > > Actually, this was a different issue, but I have worked out the problem. It > > relates to r299840. > > https://svnweb.freebsd.org/base?view=revision&revision=299840 > > > > I didn't notice this change, thank you for tracking it down. > > > Basically, r299840 introduced a new FreeBSD-zfs package, which I did not > > have installed. So when I did a pkg upgrade, it upgraded FreeBSD-runtime > > and removed this files which were now split off into the new FreeBSD-zfs > > package. Obviously, since I did not have the new FreeBSD-zfs package > > previously installed, the files were not installed under this new package. > > > > The fix is simple: pkg install FreeBSD-zfs > > > > Yeah, but until you realize what new package is needed, it is a bit > non-intuitive. (This is one of the main reasons we're considering > packaged base "beta" for 11.0-RELEASE.) > > > However, it does raise the point that whenever a new base pkg is created, > > how should users be informed? Should pkg provide a warning that some files > > have been moved to a newer package that isnt being installed, or should it > > be a note in UPDATING? > > > > This is a good question. > > I'm not sure what the answer here is, to be honest. But you raise > a very good, and very serious concern. > > What I think we should do is something along the lines of the MOVED file > in the ports tree. But doing this on a per-file level does not quite > scale very well. My fear here is ending up with something that > resembles OptionalObsoleteFiles.inc. May be adding new feature to pkg? spliting and mergering packages and track history of this in repo base? > In the meantime, would you mind adding this particular issue (not the > FreeBSD-zfs package, but the underlying problem) to the PkgBase wiki > page? > > Glen >