Fri, 3 Mar 2017 09:20:39 +0100 Theo Buehler <[email protected]> > On Fri, Mar 03, 2017 at 09:13:12AM +0100, Nils Reuße wrote: > > > Theo Buehler <[email protected]> hat am 2. März 2017 um 22:44 geschrieben: > > > > > > On Thu, Mar 02, 2017 at 10:31:50PM +0100, Jan Stary wrote: > > > > current.html says to # rm /etc/pkg.conf > > > > after the switch to installurl(5). > > > > Should it also say to > > > > > > > > # rm /usr/share/man/man5/pkg.conf.5 > > > > > > yes. fixed, thanks > > > > I guess one should remove /etc/examples/pkg.conf then as well? > > I added that one, too, but I'll leave it at that. None of these files > does any harm if it's present.
Hi Jan, Nils, Theo and misc@, Yes, moreover so, there should be a file in examples listing mirrors for packages and snapshot downloads, that is getting synced from the respective database file. This file is then used as an example, for configuring the utilities used for package tools and snapshot tools. What I'm trying to say is, correct, we should not remove the example files, and possibly (if relevant) further extend the system upgrades management and maintenance tools to have snapshots related function. Also, we should have in mind people might prefer and/or need to have separate different download for snapshots and packages, depending on their upgrade and maintenance model, bandwidth, project involvement. And it is worth mentioning that for some machines auto upgrades from snapshots from local disk is mandatory including installer response. That should enable fully automated or offline upgrades capabilities, for all people following development always running latest snapshot. Kind regards, Anton
