2023年7月7日发(作者：)

Comparison of SOS vs. CVS command line functionalityThe commands are grouped in terms of similar actions1Finding out the management state of various files1.1Is my data base up to date?

1.2Are there new files for me?

1.3Have I modified any files?

1.4Do I have any files that are not managed?

The following command answers these questions without modifying any local -n -q update –dAPsoscmd update –i

/* shows what would be updated, but changes nothing */The following command answers the same questions without bothering with local

unmanaged files such as temporary files or tool -nq update -dAP |grep -v "?"soscmd update –i

/* shows what would be updated, but changes nothing */

1.5Finding the status of all the files in a directory. What are the versions of all files are they up to date, etc. this is more detailed

information than the summary information shown statussoscmd history1.6Finding the status of a specific file. What is the version of this file is it up to date, etc. this is more detailed information than

the summary information shown status soscmd history 2Getting new versions of files2.1Getting a specific version, make it sticky so it will not

inadvertently update -r1.2 UNDER INVESTIGATION..

2.2Get latest version of everything, bypass sticky tagsWithout a file name does it for all files in the directory tree downward, or with arguments

limits its scope to a file or update –Asoscmd update2.3Get new directories from that have been added to the

update –dsoscmd create - add new files and/or dirs to the project repositoryThe above two commands are commonly combinedcvs up –AdThese 2 options cannot be combined in sosAlternatively you can also ask CVS to clean up (prune) empty directoriescvs update –dAPsoscmd delete to delete

2.4Get a specifically tagged set of filescvs up -r RELEASE_3soscmd update –le.g soscmd update –t 09/05/30 soscmd update –t 09/05/30 14:45:223Comparing versions of files3.1Compare latest in CVS repository with current version in

dir

tkdiff

tkdiff can be used but only after exporting a previous must specify both versions to use tkdiff with SOS.

< tkdiff file_1 file

/* both versions must exist in the workarea */soscmd exportrev usbcore.v/7 usbcore.v/2 usbcore.v/1 Export revisions '7', '2', and '1' of file 'usbcore.v'.soscmd userev usbcore.v/7

userev replaces the version in the workarea with the version

difference between 'userev' and 'exportrev' is that 'exportrev' does not replace the selected file with the new revision. It places the selected revision under a file name created by appending the revision number to the actual file name. You would 'export' a revision only if you want to look at a previous revision for reference but do not really want to use itor

cvs diff soscmd diff [pathname(s)]Displays the difference between two revisions of the same may specify up to two pathnames which refer to two revisions of

the same you specify only one pathname then the second one is assumed as

follows: If the file is checked out then this is used. If the file in not checked out then the revision currently in the workarea is used.3.2Compare a specific version with current version in dir

tkdiff -r1.7

See section 3.1 above the ORcompares v1.7 in CVS repository with current version in dir

orcvsdiff -r1.7 See section 3.1 below the ORcompares v1.7 in CVS repository with current version in dir

3.3See the changes between any two versionscvs diff -r1.4 -r1.5 soscmd diff file_rev_1 file_rev_103.4Look at all the changed from the first versioncvs diff –rHEAD soscmd diff file_rev_1 file_rev_103.5Read through the log messages to understand the reasons

for changescvs log soscmd history 4Returning edited files to the repository for other to seeSometimes this is called checking in or committing changes.4.1Check in a single file with a meaningful “message”cvs commit -m "message" soscmd ci -aLog="Got rid of synthesis warnings." Check-in and assign the 'Log' attribute the value: Got rid of synthesis warnings.4.2Check in a group of files with a meaningful “message”cvs commit -m "message" The following command will check in multiple files ONLY if they are

modified and each file will get the log message…soscmd ci -sco -aLog="Got rid of synthesis warnings." DEL2.v following command will check in multiple files whether they are

modified or ci -sco -F -aLog="Got rid of synthesis warnings." DEL2.v

following command will check in multiple files whether they are

modified or not. All files get the log message and also tag all

files with the attribute label = ci -sco -F -aLog="Got rid of synthesis warnings."

-achange_summary="GOLD." DEL2.v d ci -sco -aLog="Got rid of synthesis warnings." Check in all files which are currently checked out in this work area and assign the 'Log' attribute the value: Got rid of synthesis ci -achange_summary="Instantiated adder." -rev101 Check in '' and assign the 'change_summary' attribute the value: Instantiated adder. Make the number of the new revision to be 101 without regard to what the current revision ci -sco -achange_summary="No warnings!" -aLog="Got rid of synthesis warnings." Check in all files which are currently checked out in this work area and assign the 'Log' attribute the value: Got rid of synthesis warnings.

and the 'change_summary' attribute the value: No warnings!soscmd ci -Nco -Ncg -sw -F -T"gold silver" -achange_summary="Test" -aLog="Test" Check in all files that are writable

even if they are not checked out

(-sw will only select writable files). Force if there is no change. Attach the tags 'gold' and 'silver' to the new revision after checkin. Do not print any information messages. Do not get the checked in file back to the client's

workarea.4.3Check in all files in a directory with a meaningful “message”cvs commit -m "message" soscmd ci -aLog="Message." *.v Check in all the files with the '.v' extension in the current working directory. Add Message to the log for each

file.

Only modified files will be checked-in.

soscmd ci -F *.vhd Check in all the files with the '.vhd' extension in the current working directory

Even if no changes have been made.5Creating additional copies of a project for

experimental purposesCvs –d checkout -d The only way to clone a project is to create a new project version.

That’s easy to do. Also, there is a script

$CLIOSOFT_DIR/bin/sos_ that can take and export selected files

from one project to another

including version history.

So, it would be easy to experiment with a new project and then import the

sources into the main project if wanted. You could also continue to work on

the new project and leave the main project as the base for another

experiment.

I believe this gives you more flexibility than SE FROM Cliosoft: Branches…If you have many changes then you are probably better off cloning

the project. However, let me explain how branches work with a

simple example.

Let us say you want to create a 'low power' version of a product.- Take a snapshot of the current state of the project. Say rel_1.

- Define a branch say low_power.

- Users working on the low power version would do the following:

+ Set default branch to low_power.

+ Set revision search order to low_power, rel_1.

- Any object they checkout will get checked out on the low_power

branch and so all changes are made on the branch.- The RSO will ensure that you will get the low_power branch if

there

are changes to a file otherwise the version in the snapshot

rel_1.

- Other users can continue development on the 'main' this helps. Regards,

Srinath

6Tag a group of filesTag a group of files (or the entire project) to know what fields were used for a test or to

know what set is expected to work tag soscmd tag -ntested *.v Add the tag 'tested' to the current revisions (i.e. revisions in your workarea) of all the files with the extension '.v'

in the working directory. The tag must be declared

before

it can be used. See

definetag - define/declare new tags or modify tags----------------------------------------------------------------USAGE soscmd definetag [-aDescription="comment"] [-aSticky="yes|no"] [-mod] [-P] DESCRIPTION Before you tag a revision with a symbolic name the tag name must be defined or declared. This ensures that you do not accidentally use an incorrect name. This command lets you define new tag names or modify existing tag NTS -aDescription="comment" Optional description comments to be associated with the a tag to be created or modified. -aSticky="yes|no" Optional attribute Sticky to be associated with the a tag to be created or modified. If Sticky attribute is set to "yes" then a tag once applied cannot be moved by using tah tag command. User would have to first backoff the tag and then retag. So if admin wants to control retagging of sticky tags then they can remove definetag and backoff-tag frmo the MEMBER role. Default value if this option is notnot specified it "no". -mod Argument to specify that a tag is being modified and not created. If this argument is not specified it is assumed that the tag is to be created. -P Define tag for the specified project(s). If project name is the special keyword 'All', then tags are defined for all projects (primary and reference). Multiple '-P' options are allowed. If this option is not specified, the tags will be defined in the primary project. List of space separated tag names to be Once a tag is defined you can associate this symbolic name with any revision of files or directories. Tags, branches, and snapshots are in the same name space and are referred to as 'labels'. So names of tags, branches, and snapshots have to be ES soscmd definetag tested Define a tag with the name 'tested'. Sticky attribute defaults to "no". soscmd definetag -aSticky="yes" sticky_test Define a tag with the name 'sticky_test' and also make it a sticky tag. soscmd definetag gold silver bronze Define three tags with the names 'gold', 'silver', and 'bronze'. soscmd definetag -mod -aDescription="Rev has passed unit tests" unit_tested Modify the description of a tag with the name 'unit_tested' with the given tag - give a symbolic name to a revision----------------------------------------------------------------USAGE

soscmd tag [-n] [-B] [select options] [pathnames]DESCRIPTION Gives a symbolic tag or name to the selected revisions of files and directories. If a previous revision of the file or directory has the same tag then the tag is 'moved' to the current NTS -n Specify the name of the tag to associate with the selected revisions. At least one tag name must be provided with the tag command. You may use multiple '-n' options. -B Back off the Tag from the selected revisions. [select options] pathnames These are selection options. Refer to help for the 'select' command. The selections in the SOS window will change to the selection specified by these options. If no selection option or pathnames are provided then the command will be performed on the current selections in the SOS To add a tag, the tag name must have been previously defined in SOS. Tags, branches, and snapshots are in the same name space and are referred to as 'labels'. So names of tags, branches, and snapshots have to be ES soscmd tag -ngold Tag the currently selected revisions of files and directories in the SOS window with the name 'gold'. soscmd tag -ntested *.v Add the tag 'tested' to the current revisions (i.e. revisions in your workarea) of all the files with the extension '.v' in the working directory. soscmd tag -ngold testbench.v/main Tag the latest revision of 'testbench.v' on the main branch of development as 'gold'. soscmd tag -nsynthesize link.v/8 phy.v/23 Tag revision '8' of 'link.v' and revision '23' of 'phy.v' as 'synthesize'. soscmd tag -ngold -ntested . Tag the current revision of the working directory both 'gold' and 'tested'. soscmd tag -ngold -B testbench.v Remove the tag 'gold' from the current revision of 'testbench.v'.7Dealing with conflicts and onally two people are editing the same version of the same file for different

reasons. When this occurs, CVS will allow both people to check in (commit). If the

changes are on different lines, cvs will properly merge the changes. If the changes are on

overlapping lines, CVS will warn the second person and give guidance as to the

differences on the situation can only arise if the SOS concurrent checkout capability is being used.

To enable concurrent check-out do the following: soscmd co –C Enable concurrent checkout. If you have this option then you will be able to checkout a file even if someone else already has the same revision checked out. soscmd ci -ma -mm -mo These are mutually exclusive options. They specify what sort of merge to do when you are trying to checkin a file and new revisions of this file have been introduced since you checked it out.

-ma --> Do an automatic merge with the latest revision Checkin will be aborted if conflicting changes are detected. -mm --> You have already done a manual merge with the latest revision and would just like to record that a merge was done. -mo --> You are not interested in merging and would like to check in your file as is. If you use this option you are probably overriding changes made by someone else.-------------------------------------------------------------------------------------------------8PC interface for local copies on has a windows client WinCVS, this allows for copies of a project to be on a laptop

and be edited. It have full functionality of CVS and is used for some se from Cliosoft Support –Windows Client is available in do have a Windows client. You can download it from our website.

It looks the same as the Unix/Linux client but has some platform

related restrictions such as not being able to create linked ent people in the project can use different platforms.

Typically most of our users run the server on Linux but have

some users who use Windows to manage software, RTL, docs, PPTs etc.-------------------------------------------------------------------------------------------------Response from Cliosoft Support for Other SOS issues:Watching files

--------------

This feature does not exist directly but can be implemented using

example you could make file attribute User1 be a list of people who

want to watch a file.

Then set a trigger on any type of action you want watched to send an

email to the list of users in you would like to know more details let us lly you would have to write a script to set/remove/list watch

from side authentication

--------------------------

SOS supports server side authentication via PAM (Pluggable Authentication Modules).

To use this, the server host must be set so a PAM confid file is created for that, the admin can turn ON server authentication using this is set, any client connecting to the server will be prompted for

username/passwd. The credentials will be authenticated by the server using this helps. We can demonstrate these capabilities and help you set it up.

Regards,Srinath.