Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Nov 1996 17:26:35 +0800
From:      Peter Wemm <peter@spinner.DIALix.COM>
To:        "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc:        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:  <199611150926.RAA07455@spinner.DIALix.COM>
In-Reply-To: Your message of "Fri, 15 Nov 1996 00:36:46 PST." <12335.848047006@time.cdrom.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" wrote:
> > This bloat took 1.3MB for the ctm update for the originals and the diffs
> > are presumably larger :-(.  The bloat is now 3.5MB in ncvs instead of
> 
> Yes, I know, and I fully expected this to happen.  However, I knew
> that Peter would kill me dead if I did the kind of repository fiddling
> necessary for avoiding this, and we never said that the road to
> -current would not occasionally have its bumps (I'd think that after
> the gdb import, 4MB would seem like a walk in the park :), so...
> 
> Oh well.

I have an alternative suggestion for how to reduce the impact of this, 
since the compat dists are going to be changeing on a semi-regular basis 
once 3.0 development cranks up and we bump a few library major versions.

[btw, if you were thinking of deleting the ,v files and re-importing them 
with the same version number as before, yes, your assessment of my 
reaction sounds pretty close... And I suspect John Polstra would be 
queueing up to take a shot at you too. :-) ]

> > only 1.75MB.  cvs is particularly unsuitable for managing uuencrufted
> > tarballs and /usr/src is a bad place to put them.
> 
> Well, perhaps, but I still think it's far less confusing conceptually
> to have them under /usr/src/release, even with the degree of pain
> entailed.
> 
> 					Jordan

I know CVS sucks at doing this sort of thing, but it sucks less when we 
can avoid changing the files where possible.

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.

It also means we can add/remove libraries from the dists by editing a file 
list.

I was going to suggest this before, but I don't have any idea how the 
release build works, so I don't know how hard it would be to connect up.  
But I guess it shouldn't be too hard if the compat dists are built as part 
of the rest of the world compile.  Theoretically, it should be a simple 
matter of grabbing the .tgz.uu files from the obj dir rather than the src 
dir.  I am happy to put this together if somebody else will do the release 
work...  Then we can nuke the rather large repository files.

Cheers,
-Peter





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611150926.RAA07455>