On January 28, 2016 1:23:22 PM EST, Glen Barber <g...@freebsd.org> wrote: >On Thu, Jan 28, 2016 at 09:12:53PM +0300, Slawa Olhovchenkov wrote: >> I see two hudge problem for support upgrades from older RELEASE >> versions (supported too): key (used for repo signing) change and need >> to access ports packages to install (installed outdated release can't >> find pkg packet for install). >> >> Can you more detailed describe current propolsal of new packaging >> system? pkg is part of base installed packages? Or after installing >> base packages pkg installed from `ports`? For disc1.iso case. >> >> How handled boot/device.hints and var/db/etcupdate? >> >> How handled boot block updates? > >These are all valid questions, but let's take a step back for a bit, >and >not put the carriage in front of the horse. > >The initial email in this thread was intended to provide an update on >the status. Some things, such as file merging, is already in place in >a few of the packages. Not all, yet. > >Unexpected things are going to happen. That is the only thing that is >a guarantee right now. In other words, implementation (from what is >now >in the project branch) may change. And yes, there needs to be a way to >upgrade from older releases. > >But let's not get too far ahead of ourselves. > >Glen
Can we have verbose and/or semi-interactive configuration merge, as offered by etcupdate or mergemaster? - Nikolai Lifanov _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"