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.
you view, distribute, and print documents in Portable Document Format
(PDF)--regardless of the computer, operating system, fonts, or application
used to create the original file. PDF files retain all the formatting,
fonts, and graphics of the original document, and virtually any
PostScript(TM) document can be converted into a PDF file.
This is version 3 of the Adobe Acrobat Reader. The reason for adding acroread3
to the package collection when we also have acroread4 is that acroread4 does
not run in the current state (January 2000) of our SVR4 binary emulation. The
missing system calls are non-trivial. Hence I wanted to make sure sparc users
had a version of acroread. Note that acroread3 is available for sunos and this
version does correctly run under our SunOS emulation.
