Re: BLOBs in cvs

[Malcolm Tredinnick <malcolm commsecure com au>]

On Mon, Sep 02, 2002 at 05:49:21PM +0300, Yanko Kaneti wrote:
> On Mon, 2002-09-02 at 17:35, Peter Bowen wrote:
> > On Sun, 2002-09-01 at 09:30, Yanko Kaneti wrote:
> > > Currently there are a number of (relatively) big files in cvs that often
> > > make updating from cvs a bit of a problem. They also take space, and
> > > from what I've heard from cvs experts  they take large amounts of memory
> > > on the server whenever accessed.
> > > 
> > > To name a few, just from the web-devel-2 module  (size in Ks):
> > > 428	./content/projects/gup/hig/fop/lib/jimi.jar
> > > 680	./content/projects/gtp/style-guides/pdf/styleguide-ja.pdf
> > > 892	./content/projects/gup/hig/fop/lib/xalan-2.3.1.jar
> > > 928	./content/projects/gup/ut1_report.pdf
> > > 1660	./content/projects/gup/hig/fop/build/fop.jar
> > > 1696	./content/projects/gup/hig/fop/lib/xercesImpl-2.0.1.jar
> > > 1916	./content/projects/gup/hig/1.0/hig-1.0.pdf
> > > 2120	./content/projects/gup/hig/fop/lib/batik.jar
> > 
> > These are all reasonable to have in the web root.  jar and pdf files
> > are, presumable, designed to be viewed in the browser, and need to come
> > across with proper headers.
> 
> This doesnt make them appropriate for a cvs module imho.
> 
> It shouldnt be a big problem to move them elsewhere and repoint the *ml
> content to that.

I fail to see the problem here. Not a lot of people need to have the
web-devel-2 module checked out in its entirety. And those that do only
have to download the above files when they change. Now, admittedly, you
end up getting the whole file anew on every change because they are
binary files, but most of them just do not change that often to worry
about.

If you personally don't want them, but want the rest of web-devel-2, use
cvs's -I option.

There are real problems to be found with the GNOME CVS repository, but I
really don't think this is one of them.

Malcolm