Date: Fri, 15 Nov 1996 08:09:10 -0700 From: Warner Losh <imp@village.org> To: Poul-Henning Kamp <phk@critter.tfs.com> Cc: Peter Wemm <peter@spinner.dialix.com>, "Jordan K. Hubbard" <jkh@time.cdrom.com>, Bruce Evans <bde@zeta.org.au>, cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-user@freefall.freebsd.org Subject: Re: cvs commit: src/release/compat compat1x.tgz.uu compat20.tgz.uu compat21.tgz.uu Message-ID: <E0vOPtG-0004uR-00@rover.village.org> In-Reply-To: Your message of "Fri, 15 Nov 1996 10:38:24 %2B0100." <5288.848050704@critter.tfs.com> References: <5288.848050704@critter.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <5288.848050704@critter.tfs.com> Poul-Henning Kamp writes: : >So, I suggest we nuke the .tgz.uu files (in src and ncvs) and instead pull : >in things like libc.so.2.2.gz.uu and so on. And build compat2x.tgz under : >the obj tree somewhere. This means that trivial changes like pathnames in : >the tarballs are reduced to a one line change in the makefile or build : >scripts. : : yes, this is my vote too. Before we go and check in binary files uuencoded, the new CVS+RCS groks binary files w/o the needed UUBLOAT. My first choice would be to not have them in the tree at all. My second is to just have the binaries, and my third would be to have them uuencoded. And if you stored the raw libraries in the cvs tree, then you could do exactly as Peter and Poul suggest... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0vOPtG-0004uR-00>