./emulators/compat13, Shared libraries for NetBSD 1.3 compatibility

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 1.3.3nb3, Package name: compat13-1.3.3nb3, Maintainer: pkgsrc-users

This package supplies the user files needed to run dynamically linked
executables compiled under NetBSD 1.3.


Required to run:

Required to build:

Master sites: (Expand)

SHA1: 63d3d11db6336fb53483cc5944145c4e4591218c
RMD160: a449a828a92a74fb61972f43c42caace5e798aa6
Filesize: 323.616 KB

Version history: (Expand)

CVS history: (Expand)

   2009-06-14 19:51:11 by Joerg Sonnenberger | Files touched by this commit (120)
Log message:
Remove @dirrm entries from PLISTs
   2007-10-07 14:59:16 by OKANO Takayoshi | Files touched by this commit (33)
Log message:
fix obsolete URLs for www.NetBSD.org

close PR pkg/37071
reviewd by xtraeme@
   2006-10-19 21:37:38 by Thomas Klausner | Files touched by this commit (5)
Log message:
Mark as NO_SRC_ON_FTP -- files are already in MASTER_SITE_LOCAL.
   2006-05-23 00:22:05 by Johnny C. Lam | Files touched by this commit (49)
Log message:
Move the check-shlibs target from bsd.pkg.mk to bsd.pkg.check.mk where
it will live with other "check" targets run after package installation.

Get rid of SHLIB_HANDLING, whose meaning had mutated over the years
from one thing to another.  Currently, it is used to basically note
whether the system's "ldd" command can be usefully run on the package's
binaries and libraries.  Rename this variable to CHECK_SHLIBS_SUPPORTED
for more clarity.

CHECK_SHLIBS is now a variable set exclusively by the user in /etc/mk.conf
to note whether the check for missing run-time search paths is performed
after a package is installed.  It defaults to "no" unless PKG_DEVELOPER
is set.
   2006-05-11 20:58:40 by Bernd Ernesti | Files touched by this commit (1)
Log message:
Add missing RMD160 entries.
   2006-03-14 02:14:36 by Johnny C. Lam | Files touched by this commit (134)
Log message:
Modify the pkginstall framework so that it manages all aspects of
INSTALL/DEINSTALL script creation within pkgsrc.

If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts.  If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:


As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts.  By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).

In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework.  The only public variables relating to the templates are:


The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
   2005-12-29 07:22:26 by Johnny C. Lam | Files touched by this commit (597)
Log message:
Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.