Copyright (C) 2002-2020 Arnaud BERTRAND
web-site: http://apvsys.sourceforge.netapv-regtool
This is the most important administrative command. This is the command to use to register a tool (a version of a tool) in the ApVSys database.
The options enable the ApVSys administrator to tune the commands to register in the system.
apv-regtool -t toolname -v version [-v version] [-c -m -l -f -a]
[-u ] [-d -D] [-o otherOS] [ -r restriction_level ]
[ -i included-pattern ] [ -e excluded-pattern ]
[ -L username ]specifies the tool (toolname) to register.
Note: the toolname must be the name of the directory in $APVSYS_ROOT/OsName/vOsVersion containing the different versions of the tool (or an installation image: please read ap-linktool documentation)
e.g. to register gcc, under Solaris 8, the directory: /apvroot/SunOS/v5.8/gcc must contain the version(s) to (un)register.
specifies the version(s) to (un)register, this option can appear several times to register several versions of the same tool.
Note 1: the versionname MUST always begin with "v" (the letter "v")
Note 2: the versionname must be the name of the directory in $APVSYS_ROOT/OsName/vOsVersion/toolname containing the version of the tool to register.
Note 3: instead of "-t tool -v version", the syntax "-t tool/version" can also be used.
By default, everything (commands, manpages, infopages, libraries) are registered. this option enables the admin to select separately what must be registered.
This option is used to register the commands only ( the content of the bin directory )
By default, everything (commands, manpages, infopages, libraries) are registered. this option enables the admin to select separately what must be registered.
This option is used to register the libraries only ( the content of the lib directory )
By default, everything (commands, manpages, infopages, libraries) are registered. this option enables the admin to select separately what must be registered.
This option is used to register the manpages only ( the content of the man directory )
By default, everything (commands, manpages, infopages, libraries) are registered. this option enables the admin to select separately what must be registered.
This option is used to register the infopages only ( the content of the info directory )
This flag must be specified to UNREGISTER a version of a tool.
Note 1: To unregister a version, the installation directory $APVSYS_ROOT/OsName/vOsVersion/toolname/version STILL HAS TO EXIST. This directory can only be deleted AFTER the unregistration. If it was removed, apv-dbcheck would have to be used to clean-up the database properly. It takes more time but the result is the same, the tool will be properly removed.
Note 2: To -fully- unregister a version of a tool, the filter options ( -c,-l,-m,-f,-r,-i,-e ) CANNOT be used. It is of course possible to use these options to partially unregister a version of a tool.
This switch must be used to specify that the version to register ( the first one if several versions are specified) is registered in the CURRENT O.S. as the default version.
The same as -d but the version becomes the default for all the specified operating systems if several oprating systems are specified( see -o option)
This switch can be used to register the version(s) in several operating systems at the same time. The tool will always be registered in the current O.S. This option can appear several times. The argument must be OsName/vOsVersion (e.g. "SunOS/v5.8" )
It is sometimes interesting to (un)register only a subset of the entities (commands, manpages, ... ). With this option, only the entities matching regexp will be taken into account.
It is sometimes interesting to ignore a subset of the entities during a (un)registration. This is typically the case with tools containing the flexlm commands (lmstart, lmstat, lmdown,..). With this option, the entities matching regexp will be ignored.
This option is mandatory (for logging purpose) to keep log of who (un)registered what.
This option can filter the entities to register in function of previous versions of the same tool or in function of other installed tools. this option also gives the opportunity to register interactively each entity.
This is really interesting, when some commands are common with other tools, to tune the commands to register.
All the entities are registered and nothing will be prompted
If an entity is already registered for another tool, the registration automatically skips this entity automatically.
If an entity is registered for another tool, the registration prompts interactively what to do for this entity.
If an entity has never been registered for this tool (it assumes the registration of other version of the same tool), the registration skips this entity
If an entity has never been registered for this tool, the registration will prompt interactively what to do for this entity.
With this value, the registration will prompt interactively what to do for each entity.
print a short help message
> apv-regtool -t gcc -v 2.95.3 -d ## self-explain
> apv-regtool -t gcc -v 2.95.3 -u ## unregistrationIn the next example, gcc will be registered for the current OS, but also for the 2 other specified OS. If there is no directory gcc/v2.95.3 for these O.S., a link will automatically be created.
> apv-regtool -t gcc -v 2.95.3 -D -o SunOS/v5.7 -o SunOS/v5.8More complex but classical example. It assumes that the tool "ncsim" was previously installed with another ( or the same ) version and it does not register the entities beginning with "lm" ( typically the flexlm commands, which can be registered for the flexlm tool )
> apv-regtool -t ncsim -v 3.3s10 -r 21 -e "^lm"