/etc/rc.d/zfs and /etc/rc.d/zvol no longer in FreeBSD-runtime package?

[Slawa Olhovchenkov]

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
>