=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I do something I suspect many others do as well. I build NetBSD on a machi=
ne,=20
and rsync bits of the binary output around. This makes adding and upgradin=
g=20
machines trivial -- I only have to do the pkgsrc upgrade dance once, I can=
=20
test before doing it, and I don't need to actually remove packages on=20
production machines to upgrade them.
It used to be that checking out src/etc was mostly sufficient to be able to=
=20
upgrade /etc on the "client" machines, but now it seems I need a lot of=20
src/sys as well. Also, some files in /etc are stored in usr.bin, or other=
=20
directories.
Are other people doing this sort of binary push, or am I unique? If I am, =
I=20
can write something that can do the /etc upgrade, no matter how difficult i=
t=20
is becoming.
Last time I brought this up (saying that 'postinstall-fix' should work with=
out=20
an entire source tree present by putting the needed bits in /usr/ somewhere=
)=20
I got flamed and told I was wrong to want this. I'm willing to change how =
I=20
update my /etc, but checking out the entire source tree on 12 machines is=20
just silly.
=2D --Michael
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iD8DBQE/0u3xl6Nz7kJWYWYRAj3AAJ0SllAiAyaqe5To25WiL49ZTSrPrQCfdndT
=467gj99uyVwHeCOus9A9+wPc=3D
=3DVlB5
=2D----END PGP SIGNATURE-----