Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
already added to CONFIGURE_ENV by bsd.pkg.mk. Also some minor cosmetic
changes.
|
|
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
+ include distfile filesizes in distinfo
|
|
|
|
|
|
is bumped to tcl-8.3.2nb1.
|
|
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.
|
|
not fail when tk is not present...
|
|
I guess a cup of coffee is in order before I continue...
|
|
ELF.
|
|
were:
0.7 - Tcl_Obj's support (first trial); now NUL-Bytes are allowed; strings
need not be terminated in the database (the 0.6-version would store
the terminating NUL's in keys as well as in data and RELIED on it!).
Now DB'S generated by other Programs (cross-checked with php3!) can
be read! (JG)
0.8 - Move to libtool/automake/autoconf and generate rpms for RedHat 6.2 (JE)
Tested with tcl8.3
|
|
master site. While here, USE_LIBTOOL and LTCONFIG_OVERRIDE, and adapt
to tcl-8.3.2.
|
|
|
|
for each of the continuation lines, rather than using backslashes to
continue a single, long definition. This makes it much easier to spot
pre-requisite packages and other dependencies.
|
|
|
|
|
|
|