[fdo-internals] Why tarballs are so huge ?
traian.stanev at autodesk.com
Thu Aug 23 10:34:32 EDT 2007
Another thing in this vein is the directory structure in the vault. The www directory is not necessary for development and getting it (many thousands of files) always takes a huge chunk of time. MapGuide has a better structure where all the sources are in a single directory alongside www so that one can map svn directly to the directory (MgDev) rather than trunk itself, thus skipping the www directory.
One might argue that you only need to get that once, but I get clean source often enough for this to be a problem for me (I sometimes pay for overuse of bandwidth at home) and also, clogging my file system with thousands of unnecessary files.
The same can be said for all the unit test files in the vault, which are interspersed in between code.
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Thursday, August 23, 2007 10:28 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Why tarballs are so huge ?
Thanks for the feedback. I will consider your request and see what can be done.
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Helio Chissini de Castro
Sent: Wednesday, August 22, 2007 7:31 PM
To: fdo-internals at lists.osgeo.org
Subject: [fdo-internals] Why tarballs are so huge ?
I was questioning when doing packages for all fdo providers why we have all resources inside main fdo tarballs..
Is almost 150 Mb of sources, and real code is just a fraction of that.
How about create separated tarballs for code and test resources ? Would be a lot easier to make packages and distribute then..
Just my 2c's
Helio Chissini de Castro
Brasil/South America Primary Contact
fdo-internals mailing list
fdo-internals at lists.osgeo.org
More information about the fdo-internals