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

AW: How to deal with libraries or components?

From: Robert Schneider <r.schneider_at_weingartner.com>
Date: 2005-07-08 11:09:36 CEST

Hm... I will have to make my own suggestions...

Could this be a solution:
When I know a module (whatever it is: dll, ocx, exe, ..) is used by an application (or another module) then the tag branches of the module should include a sub directory that has the compiled binary. The working copy of the application would reference the binary with the external property. Then I would know that the app uses a particular library and I could reproduce exactly this situation. A change of the library would only become visible to the app when I explicitly decide that the new tag branch x.x.x of the library has to be used (set with the externals). So _I_ have to determine the used library version for the app. Changes in the library are _not automatically_ reflected in the app project.

For the build process this would mean that I don't have to rebuild the modules since the compiled modules are already referenced by the application project.

Is this an approach? Please consider that I was talking about shared libraries or components. Would be interesting to know if it is different if modules are not shared but directly related to one application/project.

Robert

> -----Ursprüngliche Nachricht-----
> Von: Robert Schneider
> Gesendet: Freitag, 08. Juli 2005 07:35
> An: users@subversion.tigris.org
> Betreff: AW: How to deal with libraries or components?
>
>
>
> Tor has responded. Is there no one else how has an idea?
> I thought this would know most people here. Or are those
> questions too off-topic?
>
> Any suggestions or hints are appreciated very much!
>
> Robert
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Robert Schneider
> > Gesendet: Donnerstag, 07. Juli 2005 08:54
> > An: users@subversion.tigris.org
> > Betreff: How to deal with libraries or components?
> >
> > 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
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 8 11:12:40 2005

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