> Speaking of files/symlinks created in postinstall scripts -- perhaps we > should come up with some unified mechanism for listing them. Some > postinstall scripts use /etc/preremove/<PKGNAME>-manifest.lst. > > The reason it may be useful to have a common mechanism is that "cygcheck > -c" could then use the manifest files in addition to the package listing > to check whether the package is complete. That would have caught, for > example, the man.conf problem reported recently on the main list.
Sounds good to me. The upcoming bash-3.0-5 now includes
/etc/preremove/bash-manifest.lst, and attached is a patch to g-b-s
to make it easier to build one (just add CYGWIN-PATCHES/manifest.lst).
I guess I should also update cygwin.com/setup.html - where is that
stored in CVS?
2005-07-05 Eric Blake <[EMAIL PROTECTED]>
* templates/generic-build-script (options): Add almostall,
help, version.
(help, version): New functions.
(install): Support manifest lists.
--
Eric Blake
gbs.patch
Description: Binary data
