linda is an simple library implementation of Linda parallel
programming system (http://www.cs.yale.edu/Linda/linda.html). To
write a parallel program with linda, you have to know only 6
functions: spawn, out, in, inp, rd and rdp with linda.
the scripts/ directory, it will be run automatically as part of
the build process, by bsd.pkg.mk. There are now exactly 5 packages
in pkgsrc which use this facility, and yet, for every package build,
the existence of a script is checked by bsd.pkg.mk once before the
target is executed, and once afterwards. This incurs needless
overhead.
Move the separate pre- and post- script handling out of bsd.pkg.mk into
the individual package Makefiles, where it's much more obvious what is
happening, anyway.
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
Changes include:
Added new dvt command, which allows you to open xterms to multiple hosts
and control them all via one input window.
Added new jsh command, which allows better job scheduling specifically
designed for parallel compiling.
Multiple bugfixes and enhancements. Much much faster execution.
says to use type time_t for ctime(3).
- Fix some format strings for 64 bit systems.
- use '?=' instead of '='when setting the command used for rsh/ssh so the
user can set it in mk.conf (PVM_SSH).
you can do something like:
make CC="gcc -pipe" PKG_FC="f77 -pipe" CFLAGS="-Wformat -g" FFLAGS="-g"
and still have pvm compile correctly.
Addresses PR pkg/12949 submitted by Thor Simon <tls@cs.stevens-tech.edu>.
Add PLIST.java (contains additional installed files if a javac is
present during build).
Modify Makefile to take the possible presence of a Java compiler
into account.
Convert most MESSAGE files to new syntax (${VARIABLE} gets replaced,
not @VARIABLE@, nor @@VARIABLE@@).
By default, substitutions are done for LOCALBASE, PKGNAME, PREFIX,
X11BASE, X11PREFIX; additional patterns can be added via MESSAGE_SUBST.
Clean up some packages while I'm there; add RCS tags to most MESSAGEs.
Remove some uninteresting MESSAGEs.
out of date - it was based on a.out OBJECT_FMT, and added entries in the
generated PLISTs to reflect the symlinks that ELF packages uses. It also
tried to be clever, and removed and recreated any symbolic links that were
created, which has resulted in some fun, especially with packages which
use dlopen(3) to load modules. Some recent changes to our ld.so to bring
it more into line with other Operating Systems also exposed some cracks.
+ Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain
the ELF symlinks.
+ Don't mess about with file system entries when handling shared objects in
bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will
have got it right, and have a much better idea than we do.
+ Modify PLISTs to contain "ELF symlinks"
+ On a.out platforms, delete any "ELF symlinks" from the generated PLISTs
+ On ELF platforms, no extra processing needs to be done in bsd.pkg.mk
+ Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on
a.out platforms
+ Update the documentation in Packages.txt
With many thanks to Thomas Klausner for keeping me honest with this.
