This has been a pkglint warning for several years now, and pkglint can even
fix it automatically. And it did for this commit.
Only in lang/mercury, two passes of autofixing were necessary because there
were nested variables.
Problems found with existing distfile for superpi:
distfiles/super_pi-20030927/super_pi.tar.gz
No changes were made to the superpi/distinfo file.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
distfiles/eagle-lin32-7.4.0.run
It is more consistent with the tex.buildlink3.mk name. Also, if a package
really needs latex, it just has to set TEX_ACCEPTED to latex distributions
altough today, all TEX_ACCEPTED possibilities are latex distributions
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
- teTeX 1.0.x packages have been moved to teTeX1* directories.
- teTeX 2.0.x packages have been moved to teTeX* directories and their base
name has been changed to teTeX (instead of teTeX2).
2003-04-08, but the maintainers did not version the distfile. So make up
our own versioning, bump this to 4.0.1 and stick the distfile into a
DIST_SUBDIR (as suggested by agc@).
The SKaMPI-Benchmark is a suite of tests designed to measure the performance
of MPI. MPI (Message Passing Interface) is a machine independent standard to
provide an efficient interface to message passing libraries of different
parallel machines. The goal of SKaMPI is to create a database to illustrate
the performance of these different MPI implementations. This database should
allow to:
1. Decide how to implement portable and efficient MPI programs.
2. Predict the performance of MPI programs.
3. Describe supercomputers in terms of MPI.
