nia writes:
> On Fri, Apr 15, 2022 at 08:05:54AM -0400, Greg Troxel wrote:
>> To me, the right behavior is to know if each file in etc has been put
>> there as a copy of a file that appeared in etc.tgz, and to change it to
>> the new version without prompting if so, and if not, to note to the us
On Fri, Apr 15, 2022 at 08:05:54AM -0400, Greg Troxel wrote:
> To me, the right behavior is to know if each file in etc has been put
> there as a copy of a file that appeared in etc.tgz, and to change it to
> the new version without prompting if so, and if not, to note to the user
> that it might n
I don't object at all, but I want to point out etcmanage, in pkgsrc,
(which needs xz help), and does the same thing. A more or less fatal
downside is that it is in perl, but I think it has very good semantics
about etc merging. I have not kept up with the other methods, but in
the past I found t
On Fri, Apr 15, 2022 at 10:56:00AM +0200, Martin Husemann wrote:
> On Fri, Apr 15, 2022 at 08:21:00AM +, nia wrote:
> > There's been a few discussions over the years about the need for a
> > usable-over-ssh binary upgrade tool for NetBSD, but they haven't gone
> > very far.
>
> I don't object
On Fri, Apr 15, 2022 at 08:21:00AM +, nia wrote:
> There's been a few discussions over the years about the need for a
> usable-over-ssh binary upgrade tool for NetBSD, but they haven't gone
> very far.
I don't object to your idea (and I have never used it).
My own prefered method requires non
There's been a few discussions over the years about the need for a
usable-over-ssh binary upgrade tool for NetBSD, but they haven't gone
very far. Users ask fairly frequently, and other than sysupgrade, the
best method is to implement sysupgrade manually with ftp and tar (and
this is required for
