Date: Fri, 15 Nov 1996 18:47:46 +0800 From: Peter Wemm <peter@spinner.DIALix.COM> To: Paul Richards <p.richards@elsevier.co.uk> Cc: Poul-Henning Kamp <phk@critter.tfs.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: <199611151047.SAA08113@spinner.DIALix.COM> In-Reply-To: Your message of "15 Nov 1996 10:40:15 GMT." <57iv77skts.fsf@tees.elsevier.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Richards wrote:
> Poul-Henning Kamp <phk@critter.tfs.com> 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.
>
> but if the compat2x.tgz is built as part of the build why the
> does it need to go into cvs as a uuencoded file. Can't it just be
> pulled from the obj directory to wherever it goes in the release.
That's what I was saying... As soon as the release code is taught how to
get the compatxx.tgz file from the obj dir (rather than .tgz.uu from the
source dir), all traces of the .tgz.uu and corresponding ,v files can go
away.
Cheers,
-Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611151047.SAA08113>