Re: Space Constrain

Guten Tag Les Mikesell,
am Donnerstag, 12. Januar 2012 um 18:26 schrieben Sie:

> We have a lot of component libraries that we
> want to include in larger projects without recompiling each build
> (i.e. we want to run known/tested instances) and have been including
> the binaries in tags so the headers and shared libs are versioned
> together.

What's your problem at all? That you must version the same pre
compiled libraries as a tag in each of your projects? Are the
libraries such big that you run out of space?

> It''s clearly the wrong thing to do, but it works.

I don't think so, if it saves you time and guarantees the use of
tested library versions, I would do the same. My in approach in my
company is to use a separate Repository for all kinds of libraries,
just version the source code and each developer has to build them on
his machine on it's own. The IDE just references the built libraries.
But we don't have that many libraries and whenever we can't build any
library on our own, I version them pre compiled, too.

If one just copiess old library versions on updates etc. one can save
a lot of disk space.

> How
> can you enforce getting exactly the right things in a parallel
> repository that has only the headers and libs that will work the same
> way for external references?

Use tags and/or fixed revisions in your external definition.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow