[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded swig 1.1.p883-3 (m68k) to ftp-master



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 10 Jan 2002 01:43:34 +0100
Source: swig
Binary: swig-doc-pdf swig-examples libswig1.1 swig
Architecture: m68k
Version: 1.1.p883-3
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k - bruno <buildd@bruno.fmepnet.org>
Changed-By: Torsten Landschoff <torsten@debian.org>
Description: 
 libswig1.1 - Runtime support libraries for swig generated wrappers
 swig       - Generate scripting interfaces to C/C++ code.
Closes: 67967 108039
Changes: 
 swig (1.1.p883-3) unstable; urgency=low
 .
   * debian/control: Split off package libswig1.1 for the runtime support
     libraries and have swig depend on it (closes: #67967).
   * debian/rules: Run dh_makeshlibs to generate a shlibs file for the
     new package (closes: #108039).
   * Runtime/Makefile.in: Change the suffix of shared libraries from .so
     to -1.1.so and provide the library name as soname as well to allow
     parallel installation of the runtime libraries.
   * debian/rules:
     + Don't run dh_suidregister (debhelper warning).
     + Kill invocation of dh_installmanpages (manpage installed by anyway
       by make install, installmanpages puts it in libswig1.1 as well).
   * debian/links: Add the symlinks for linking with the runtime libraries
     (libswigtcl.so -> libswigtcl-1.1.so etc.) and run dh_link in
     debian/rules.
   * debian/rules: Force python version to 2.1.
   * configure.in: Replace python1.5 by python2.1, rerun autoconf.
Files: 
 c19e033f55df1cadbe3e2b7ac74ce770 391678 interpreters optional swig_1.1.p883-3_m68k.deb
 1cc409217287f44c55779fa2f1d27042 40168 interpreters optional libswig1.1_1.1.p883-3_m68k.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Rick Younie <younie@debian.org>

iEYEARECAAYFAjxChrwACgkQEycGpQPNsdLkSwCfSXlPFc2R+IIyTDFZAnD9ClHQ
uqIAn3ZFFjtSbUaJzvXFJi3DS51m8da5
=HoLW
-----END PGP SIGNATURE-----




Reply to: