When to create new repository

[Doug G]

Somehow, the "repository" concept continues to occasionally throw me for a
loop. Here is my understanding:

If I am going to make a major change to a component that involves the files
belonging to that component, should I create a new repository for it? From
my understanding, multiple versions of a component, e.g. V1.0 and V2.0, can
exist in the component database at the same time, but there is no
"versioning" of repositories, so V2.0 had better use a different repository
so that its files do not overwrite those of V1.0. Is this correct?

Doug Gordon
FANUC Robotics America

 

[Slobodan Brcin \(eMVP\)]

Hi Doug,

I find it also little strange to use, but I will tell you what I have seen
and how I use it.

If my memory serve me well. When you create two different components over
time that use same repository, and you provide different files with them
when you try to import that component in CDBM old repository folder will be
emptied and your new files will be copied.

So in case that you update your component you can provide folder with all
files old and new ones (with different names). Very hard to track and
impossible to uninstall.

You should better create different repository for each version (unless you
want to overwrite it). And associate all repositories and components with
one package.
This way you can uninstall at any time components that you want (new or old)
and their repositories. And in case that you want to do complete uninstall
of every version you can remove package and it will clean everything.

Regards,
Slobodan