[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

How to deal with libraries or components?

From: Robert Schneider <r.schneider_at_weingartner.com>
Date: 2005-07-07 08:53:39 CEST

I'm still new to subversion and still wondering how to
organize the repository, the working copy and the build
process regarding libraries or components. Is there a
best practice or is there only one reasonable solution?

The situation is as follows (very common I guess...):
I have source code of some applications. There is also
source code of several libraries and components. Those
libs and comps are used by some of the first mentioned
applications (the binary files).

1. Should I use one or several repositories? Now, with
the current discussion "One repository to rule them all"
I am a bit confused.

2. This is the main question:
If I work on one of the applications how should
I connect to the needed libraries or components? Should
I include the source code of them within my working copy as
externals and should I compile them at the same time?
Or should I use the binary file that I have to fetch
from somewhere? How do you do this?

3. Next question is not svn anymore but I think someone
can answer it: At the build process, do you build all
from scratch? The application and all dependent libs and
comps? Or are already build parts cached somehow?

Two offtopic questions:
1. How do you organize your incoming
mailing list posts? Is it just a flat (endless) list?
2. Do you always have to type enter to get the line
wrap for the posts or do you have more intelligent
programs with an automatic line wrap? I have to use
outlook and I don't think it is such intelligent...

Thanks,
Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 7 08:56:44 2005

This is an archived mail posted to the Subversion Users mailing list.