Date: Mon, 29 Apr 2019 12:52:40 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: Lars Engels <lars.engels@0x20.net> Cc: Charles Sprickman <spork@bway.net>, kris@ixsystems.com, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: CFT: FreeBSD Package Base Message-ID: <20190429105240.GB2396@elch.exwg.net> In-Reply-To: <20190429100104.GX62338@e.0x20.net> References: <002901d4fdfb$e52eb890$af8c29b0$@ixsystems.com> <15583041-1D56-44BE-8E88-ECC11C935A09@gromit.dlib.vt.edu> <34C3A77A-7B18-487E-9BC4-5B1087FEEBEA@bway.net> <20190429100104.GX62338@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
## Lars Engels (lars.engels@0x20.net): > > What are the plans to get rid of the hellscape known as “mergemaster”? > > Is there anything exciting and new there either in base or any of the > > ixSystems projects? > > There's /usr/sbin/etcupdate in base. Unfortunately, the official documentation on upgrades does not mention etcupdate at all. The release notes point to freebsd-update for binary upgrades, and to /usr/src/UPDATING for source-based upgrades. UPDATING only documents the mergemaster procedure; etcupdate is only mentioned in a few entries without any detail. The Handbook (chapter 25.3) only documents mergemaster. Even after speed-reading etcupdate(8) I'm not sure how the two-step invocation of mergemaster has to be mapped to etcupdate - I feel I'd be inventing my own procedure here (and, of course, if it breaks I get to keep all the pieces). This situation should be improved. Given that etcupdate is in all supported releases, we can even update UPDATING and the Handbook. So, does anyone have a pointer to the official procedure? Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190429105240.GB2396>