> Datum: Tue, 28 Feb 2012 14:06:14 +0100
> Von: Ulrich Eckhardt <[email protected]>
> An: [email protected]
> Betreff: Re: Subversion for object code
> > I know that subversion was not invented for that purpose
>
> I tend to disagree a bit, Subversion was intended to version non-textual
> resources, too, and you are not doing something that is unsupported and
> discouraged and left without support either.
>
>
> > but from our experience it seems that it actually works.
>
> Yes, I'd even call it common use, even though it's not the majority.
Quite interesting, these are good news.
> All files are binaries. The only issue here is the size they take,
> because every change requires some storage in the repository.
Did someone already made measurements how big the additional storage
consumption is for incremental commits of object files, e.g. created from C++
source?
> You probably already know the typical trunk/branches/tags hierarchy.
> Keep this hierarchy, but also keep it clean of object files, because
> merging and diffing them just doesn't work. Instead, add a fourth folder
> with release packages (e.g. bin).
OK, this we observe already (Actuallay we do not use fourth top-folder, but we
have a clear seperation of source and bin at some other level in the hierarchy)
> BTW: Another approach is to use a build server that e.g. runs nightly
> and stores the results on a network share.
This does not work in our situation because for some components we do not want
to use the latest but some stable older version.
Helmut
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
