Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Upgraded man command Date: Wed, 24 Nov 2004 12:52:37 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Harig, Mark" To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id iAOI8vO1012480 > -----Original Message----- > From: Igor Pechtchanski > Sent: Wednesday, November 24, 2004 12:37 PM > Subject: RE: Upgraded man command > > Sure, but that'll only work if base-files is > reinstalled/upgraded at the > same time as the man package. If we want the man package to be > self-contained, we should add the same logic that's in > /etc/preremove/base-files.sh to /etc/preremove/man.sh. I submitted a bug report (#571). It mentions the possible (unintentional) dependency. > > Incidentally, the code that looks through the manifest file > and does the > comparisons can be factored out to something like > /etc/preremove/remove-defaults.sh, and then invoked from both > man.sh and > base-files.sh as "/etc/preremove/remove-defaults.sh > /etc/preremove/man-manifest.lst" or "/etc/preremove/remove-defaults.sh > /etc/preremove/base-files-manifest.lst", respectively. > Unless we ever get > a package called "remove-defaults", this should be safe to > do. The actual > script can be part of the base-files package (once setup is > changed to run > all preremove scripts first, before removing package contents). The creation of /etc/preremove/man-manifest.lst and factoring out common code sounds like a good idea to me. Please feel free to add this suggestion to Bug #571, if you want, or to create a new report. --- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/