OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 09-Feb-2004 09:50:16
Branch: HEAD Handle: 2004020908501600
Modified files:
openpkg-re todo.txt
Log:
log known issue: Debian v3.1 install-info causing info.dir trouble
(background, discussion, workaround)
Summary:
Revision Changes Path
1.177 +62 -0 openpkg-re/todo.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/todo.txt
============================================================================
$ cvs diff -u -r1.176 -r1.177 todo.txt
--- openpkg-re/todo.txt 9 Feb 2004 08:49:24 -0000 1.176
+++ openpkg-re/todo.txt 9 Feb 2004 08:50:16 -0000 1.177
@@ -138,6 +138,68 @@
2.) convert/recreate your ndbm databases.
+ o Debian v3.1 install-info causing info.dir trouble
+
+ - fact:
+ the "sarge" release includes a install-info application which
+ works a bit different than the install-info applications on almost
+ any other OS. They claim their application saw the world first and
+ assume the rest of the world will change and become compatible,
+ work around that issue or eliminate their name duplication. The
+ install process of applications detecting presence of install-info
+ but assume the non-debian way leads to two known problems:
+
+ 1.) a "info.dir" will be created. That file will make it into
+ the RPM package and later inhibits package installations as
+ file conflicts are detected when subsequent installs also
+ provide that file.
+
+ 2.) when the build process is run as root, it alters data below
+ /var on the build host. When the build process is run as
+ non-root, it might fail at that point.
+
+ Our choices discussed were:
+
+ - include "common world" install-info in OS:
+ not possible. We are not involved in Debian release engineering.
+
+ - drop support for OS not offering "common world" install-info:
+ not acceptable. [see ndbm issue]
+
+ - drop support for application requiring "common world" install-info:
+ not acceptable. Many prominent CORE and BASE applications are
+ affected.
+
+ - port applications to use "Debian install-info":
+ bad idea to port common world to the exception, no matter if the
+ exception is right or wrong.
+
+ - provide "common world" install-info for OS:
+ fixing/enhancing the OS itself is beyond the scope of OpenPKG.
+ It would also break a huge number Debian packages.
+
+ - use OpenPKG install-info
+ not acceptable as a quick hack. We tried and we believe it is
+ possible. In the end it's a matter of overloading existing vendor
+ utilites (i.e. cp|mv|rm|chmod|chown|chgrp) with OpenPKG tools.
+ This is our prefered solution as it will fix other things like
+ chown(1) interception on "make install". However, we simply gave
+ up as the complexity of the changes are huge. In the end, it just
+ a matter of setting PATH correctly at the correct time. While
+ evaluating the latter, we found inconsistencies in RPM internals
+ which have to be cleaned up to allow implementation of hooks which
+ eventually provide overload functionality. We must assume that
+ such changes will have lots of side effects which take months to
+ clean up. REJECTED SCOPE CREEP.
+
+ - workaround
+ the requirement to have OpenPKG v2.0 build binary RPMs on Debian
+ v3.1 is to have the Debian install-info either not installed at
+ all or temporary replaced by /bin/true, i.e. using:
+
+ # mv /usr/sbin/install-info /usr/sbin/install-info.debian
+ # ln -s /bin/true /usr/sbin/install-info
+
REJECTED SCOPE CREEP (but needs to be discussed post release)
o decide whether *-2.0.0.(src.)rpm should require: openpkg-2.0.0-2.0.0 or not
and why (not)
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
