Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xgfconfig(1) [debian man page]

XGFCONFIG(1)						      General Commands Manual						      XGFCONFIG(1)

NAME
xgfconfig - configuration program for Xgridfit SYNOPSIS
xgfconfig options [list] DESCRIPTION
Xgfconfig selects XSLT processors and RELAX NG validators for Xgridfit to use; it can also be used to specify a new Xgridfit base direc- tory. Xgridfit maintains lists of validators and processors; on starting, it consults these lists and runs the first validator and processor it can find. Xgfconfig reorders these lists so that your preferred programs are looked for first. Xgfconfig may be invoked in one of these forms: $ xgfconfig --processors processor-list $ xgfconfig --validators validator-list $ xgfconfig --xgridfit-dir /xgridfit/directory $ xgfconfig --show The first of these selects processors (one or more of libxslt, lxml, xsltproc, saxon-6, saxon-9, xalan-j, xalan-c, 4xslt); the second selects validators (one or more of libxml2, lxml, jing, msv, rnv); the third specifies a complete path to the Xgridfit base directory (use it if you have installed Xgridfit in your own account rather than system wide); the fourth displays the current configuration. Several of the processors and validators that Xgridfit knows about are Java programs; for these, Xgridfit needs the name and location of a .jar file (by default it assumes certain standard file names, found in /usr/share/java). Specify this with a hash-mark followed by a com- plete path-name for the file. Here are sample command lines: $ xgfconfig -p saxon-9#/usr/local/share/java/saxon9he.jar lxml $ xgfconfig --config=config.xml -V rnv msv#/home/me/java/msv.jar The second of these commands stores the configuration in the file config.xml in the current directory. (When it starts, Xgridfit looks first for a file config.xml in the current directory; failing that, it looks for ~/.xgridfit/config.xml (Linux/Mac) or some-path (Windows); finally it looks in the Xgridfit base directory before giving up and using the default configuration.) An Xgridfit configuration file is a simple XML file, easily editable by users. The entries in it should be all but self-explanatory. OPTIONS
--config The configuration file to read or write. If this is not specified, Xgfconfig will search in the standard places (see above) for an existing configuration file for which the user has write privileges. Failing that, it will create a configuration file in the directory ~/.xgridfit (Linux/Mac) or some-dir (Windows). If the user is root or has administrative privileges, Xgfconfig will create the file in the Xgridfit base directory. -h, --help Display a help message and exit. -p, --processors The list following the options is a list of processors. -s, --show Display the current configuration and exit. -V, --validators The list following the options is a list of validators. -x, --xgridfit-dir Following the options is the full pathname of the Xgridfit base directory. SEE ALSO
fontforge(1), xgridfit(1), ttx2xgf(1), xgfupdate(1). AUTHOR
Xgfconfig was written by Peter Baker <psb6m@virginia.edu>. This manual page was written by Peter Baker 2010-01-16 XGFCONFIG(1)

Check Out this Related Man Page

MAVEN(1)							   User Commands							  MAVEN(1)

NAME
Maven - Creates a link in /usr/share/maven-repo for an existing jar. SYNOPSIS
mh_linkjar [option]... [pom] [dest_jar] [link]... DESCRIPTION
Create symlinks for a jar installed by other means. The symlinks created include links to the jar in /usr/share/maven-repo, at the correct location for Maven. It can also create additional links to the jar, usually located in /usr/share/java. Where [pom] is the location of the POM associated with the jar to install. GroupId, artifactId and version will be extracted from this file. [dest_jar] is the path of the installed jar, usually located in the usr/share/java folder. [link] is an additional link to the jar to install, usually there should be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging guidelines. Note that there is no need to specify those particular links if the --java-lib option is used. OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain this jar file -e<version>, --set-version=<version>: set the version for the jar, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules Maven rules are used here to extract the groupId, artifactId and version from the POM file. -l --java-lib: Optional, if given it will install the jar into /usr/share/java to comply with the Debian Java specification. The jar will be installed as /usr/share/java/$name-$version.jar and a versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo -n<name> --usj-name=<name>: Optional, the name to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the artifact id found in the POM. -j<version> --usj-version=<version>: Optional, the version to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the version found in the POM. -s --no-usj-versionless: Optional, don't install the versionless link in /usr/share/java. This flag is used only when the -l or --java-lib option is given. -c<classifier> --classifier=<classifier>: Optional, the classifier for the jar. Empty by default. -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results --skip-clean-pom: don't clean the pom, assume that a previous action ran mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)
Man Page