[Mono-list] Some questions about shared assemlies, strong names...
Tue, 6 May 2003 11:59:23 -0400
Hey hey :)
Can I then propose a funky idea? Why not use a versioning system? The =
CVS replacement, subversion, has a nice library to access files inside =
it. So creating a wrapper should be easy. I think it doesn't have =
version information internally but instead revision numbers. Although, =
you can easily create branches which can contain the version =
information. For example,
svn copy latest/library.dll branch/version-1-0-1-2311/library.dll
Creates a branch of library.DLL inside version-1-0-1-2311. The =
repository is actually a Berkeley DB and the copy functionality is =
optimized. In the above case it would actually not even copy anything.
Using subversion also opens up the possibility of using a global =
repository instead of only a local one. This might actually be a feature =
which could help some enterprise clients and could also helped the =
installation process of complex and distributed systems.
Now, I did say it was a funky idea. It has some drawbacks: it adds =
dependency on the new system. However, in the future, subversion will be =
as common as CVS inside UNIX systems and it's always good to reuse as =
much as possible. In this case it might make sense to reuse a version =
control system to enable access to different versions of a library or an =
Cactus Commerce Software Developer * D=E9veloppeur de =
eBusiness. All Business. firstname.lastname@example.org
From: Paolo Molaro [mailto:email@example.com]=20
Sent: Tuesday, May 06, 2003 11:40 AM
Subject: Re: [Mono-list] Some questions about shared assemlies, strong =
On 05/05/03 Philippe Lavoie wrote:
> How is MONOPATH handling the versioning issue?
It isn't, that is why we're having this discussion:-)
firstname.lastname@example.org Monkeys do it better
Mono-list maillist - Monoemail@example.com