On Sat, 2013-08-03 at 14:25 +0530, Sahil ModGill wrote: > I want to develop a version control tool (in open source) which can take > care of different versions of one component at execution time
Not sure what you are trying to say in the above sentence, particularly "execution time". As far as I know, version control means, a tool which maintains different versions of a file (mostly a source file). Are you talking about loading different version of a shared library at runtime? what do you mean by "component" here? > i.e. If one > application request for earlier version, system will automatically allocate > that component and if latest version is required, then that will be > provided by the model/system itself. Again, If "component" means "a source file" in the above sentence, then any version control system will provide the requested version. If "component" means "a shared library", then the application which needs previous version of a shared library should explicitly load it using "dlopen(3)". > This facility is available in .NET > technology in Microsoft. I don't know .N[EU]T, so I not able to understand what you mean by "component", "execution time" and "model/system" jurgons. Thanks, Mohan R _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc ILUGC Mailing List Guidelines: http://ilugc.in/mailinglist-guidelines
