There is no need to remove old versions unless you are low on space. In my case, I always leave the old versions in my internal repository and just update my projects to use the new versions. If I have to switch to developing on an old branch that depended on old versions of libraries, then they are still available and everything still builds. New development depends on the new versions and everything works very will in that way.
However, for 3rd party or open source libraries I always specify an explicit release version. For internal libraries I usually just leave it as latest.integration except when making a production release where I will switch it to a specific release version of the internal libraries as well. Regards, -Roberto On Wed, Jan 13, 2016 at 01:07:28PM +0800, Jammy Chen wrote: > Hello > > I have question need your guys help. for example, for my product previous > release, we used 3rd party lib A version 1.0 and it store in the > repository, but for current or next release, we may uptake to 3rd party lib > A version 2.0 or replace to another open source, in this case we need > remove 3rd party lib A version 1.0 from the repository? > > if Yes, the previous release build will not work as 1.0 is not available. > If no, how do I track the libs in repository and is they are being used? > > Thanks -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com