Hi Yves;

Am Sonntag, 20. Juli 2014, 18:09:00 schrieb Yves Blusseau:
> Hi all,
> 
> actually the size of the git repository (i'm speaking of the "database" not
> the checkout) is about 3.5GB. It's really too big. The problem is that the
> "database" contain ALL the versions of "tar source files". So if someone
> need to clone our repository, he need to download at least 3.5GB of data.
> 
> What i propose is to remove all the external source tar files from the
> history and put them (at least the last one) in another git repository on
> SF. The source tar files will be download (if needed) from this new git
> repository (using the http protocol). With this, the bering-uclibc will
> contain only textfiles and some patch, and i think it will take only some
> MB. We will continue to create a sources.tgz file when we release a new
> version to meet the requirements of SF.
> 
> What do you think about this idea ? If you are ok, i can made the process to
> "clean" the repository and update the buildtool.cfg files to change the
> repo from local to SF.


The way I work is to copy the current repo to a local directory and use
as main server

<Server localrepo>                                                              
                                                            
        Type = filesymlnk                                                       
                                                            
        Serverpath = repo                                                       
                                                            
</Server> 

Whatever I do in the local directory it won't clash with changes in git vice 
versa I will not crash git :)

So if we do have two repos (one for the sources, one for the buildtool.* and 
patches etc) I prefer that buildtool will be able to still use local 
directories (in the first place) and only download from SF if sources are 
missing.

The main advantage using a local repo without the need to download more files 
than just checkouts are speed when doing rebuilds and offline developement.

Maybe I have to adjust the way I work, maybe you can refine the proposal to 
adjust to my habits? 

Anyone with another idea how to keep the git repo small, fullfill SF 
requirements to provide the sources as well and to have a fast buildenv 
without the need to download the big sources files for each rebuild?

kp

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to