The Distributed Queueing System is designed as a management tool to
aid in computational resource distribution across a network. DQS
provides architecture transparency for both users and administration
across a heterogeneous environment, allowing for seamless interaction
for multiple architectures. Highly mutable custom site configurations
are possible under DQS. This abilty to customize DQS leads to
effective resource distribution and increased network throughput.
The Distributed Queueing System is designed as a management tool to
aid in computational resource distribution across a network. DQS
provides architecture transparency for both users and administration
across a heterogeneous environment, allowing for seamless interaction
for multiple architectures. Highly mutable custom site configurations
are possible under DQS. This abilty to customize DQS leads to
effective resource distribution and increased network throughput.
XXX Only one of RPLAY.info and rplay.info info files is registered
in the Info directory file. This is because install-info(1)
is case insensitive when dealing with info file filenames.
Unless RPLAY.{info,texi} are renamed I do not see a clean way
to get around this...
Changes:
* Fix serious bugs around the destruction of hash context.
These may cause abort() in C library and the server will stop.
* Improve stability.
* Fix some bugs.
* Make this compile with Intel C++ Compiler.
* Make this compile with Sun Microsystems Forte C.
when a package use the buildlink2 framework but does not define
USE_MAKEINFO. Well it was not after all.
This caused annoying messages because missing's commands emit annoying error
messages when the script is invoked with only 'makeinfo' as argument
(typically run this way by configure scripts). And more it does not
handle makeinfo's '--output=...' argument.
I first thought that it could be used as a nice way to get ride of the need
for makeinfo when it was only dubiously run during build or installation
of a package. But it also has the annoying behavior of creating empty files
because of the typical automake generated Makefile target for info file
build.
Making the buildlink2's makeinfo hiding script only logging an error
and doing 'exit 1' is actually a better tool to spot the need for makeinfo.
Set the INFO_DIR to pvs/doc/release-notes where the info file
pvs-release-notes.info gets installed.
Patch the info file so install-info finds a section and an entry in it
for the directory file.
directory file remove it if it is empty i.e. if it contains only one
menu/entry line i.e. only one line starting with '*'.
This allow INFO_DIR to be set to a package specific directory while
not registering in the PLIST the Info directory file (${INFOR_DIR}/dir).
Registering such an Info directory file in the PLIST is not really
possible as a md5 signature of it holding the registered info entries
would be stored in PKG_DBDIR. At deinstall time this signature would not be
matched because the DEINSTALL script would have modified it by
un-registering the info files from it. Hence the package removal would
be reported as incomplete...
You are probably right if this looks like a hack to you...
