./emulators/suse100_base, Linux compatibility package

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


Branch: CURRENT, Version: 10.0nb5, Package name: suse_base-10.0nb5, Maintainer: tonio

Linux compatibility package based on the SuSE Linux distribution.
Please visit http://www.suse.com/ for more information about SuSE
Linux.

This package supports running ELF binaries linked with glibc2 that
don't require X11 shared libraries.

DEINSTALL [+/-]
MESSAGE.DragonFly [+/-]
MESSAGE.FreeBSD [+/-]
MESSAGE.NetBSD [+/-]

Required to build:
[pkgtools/rpm2pkg]

Master sites: (Expand)


Version history: (Expand)


CVS history: (Expand)


   2009-06-05 13:20:27 by David Brownlee | Files touched by this commit (3)
Log message:
Enable PKG_DESTDIR_SUPPORT for suse100_*
   2009-01-29 11:15:40 by Stephen Borrill | Files touched by this commit (1)
Log message:
Add example fstab entry
   2009-01-29 10:45:39 by Joerg Sonnenberger | Files touched by this commit (3)
Log message:
Add message that for most binary programs a Linux compatible procfs is
needed.
   2007-11-30 15:18:09 by Roland Illig | Files touched by this commit (3)
Log message:
Horizontal lines consist of 75 characters, not more, not less.
   2007-08-23 23:50:23 by Johnny C. Lam | Files touched by this commit (2)
Log message:
Only invoke MAKEDEV to create devices if that script exists (which
doesn't on FreeBSD-6.x).

This fixes PR pkg/34817 and PR pkg/36081.
   2007-07-31 00:01:11 by Johnny C. Lam | Files touched by this commit (2)
Log message:
Replace for @LINUX_BASE@ in linux{,32}-mkpwd.  This only affected the
documentation at the head of the script, so I'm not going to bother
bumping the PKGREVISION for this.
   2007-07-30 16:42:43 by Johnny C. Lam | Files touched by this commit (4)
Log message:
Add definition for DIRNAME to the INSTALL scripts, which is needed when
creating the /emul/linux symlink on a system where /emul doesn't exist.
Problem noted by <wiz> in private email.

Bump the PKGREVISIONs of suse100_base and suse91_base (and also the
corresponding suse32 packages by implication).
   2007-07-30 02:01:06 by Johnny C. Lam | Files touched by this commit (4)
Log message:
Assume that the +ROOT_ACTIONS script is always executed from the
current working directory.  This should fix problems installing the
suse*_base and suse*_vmware packages as a privileged user.

When this package is installed as a privileged user, the +ROOT_ACTIONS
script is executed from ${WRKDIR}/.pkginstall before the package
metadata directory exists.