Cellview contains added and unmanaged files

Why does a new cellview contain only added and unmanaged files?

If the raw Perforce or Subversion status of a cellview lists some files that are added and some unmanaged files, it's probably a new cellview (of certain types) which has not yet been checked in. Checking in the cellview should add the unmanaged files and commit everything.

VersIC uses the Cadence triggers to add new cellviews to the DM system. For the most common types of cellview (layout, schematic, symbol) VersIC will add and checkin the new cellview when this trigger runs.

However, some types of cellview are not complete when the create trigger fires, so the trigger adds only the cellview files that exist but does not check them in because it is not yet a valid cellview. The remaining files are added and committed the first time the cellview is checked in.

This means that between creating a new cellview and checking it in for the first time, Perforce and Subversion output will show a cellview which is only partially managed. This is expected and is handled transparently by VersIC.

Cellview types which are known to behave this way include:

• adexl
• config
• physConfig
• text
• verilog