This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: setup v2.573.2.3: Postinstall: "abnormal exit: exit code=126"


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
| I think it's a good idea to just let _update-info-dir take care of this.
| It's going to run anyway so you end up just running install-info twice.

Well, there is the "unsupported" case of only updating an external
repository (e.g. Ports) without updating from the distro as well, but
I'm not sure that it's worth all the extra effort to support that case.

I'll make the relevant change to cygport before the next release, and
I've attached a patch to htdocs/setup.html as well.


Yaakov


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkifxmUACgkQpiWmPGlmQSNUwwCg2PliTFvPF2y0GQB8mJ4KtQIk
Fg4AoOjUTONfCjIpW0qCsv49ToOb1d26
=8zm4
-----END PGP SIGNATURE-----
--- htdocs/setup.html.orig	2008-08-10 23:50:20.538727400 -0500
+++ htdocs/setup.html	2008-08-10 23:50:32.429352400 -0500
@@ -357,7 +357,6 @@
 	<li>In your binary package, include a file /usr/share/doc/Cygwin/foo-vendor-suffix.README containing (at a minimum) the information needed for an end user to recreate the package. This includes CFLAGS settings, configure parameters, etc. </li>
 	<li>In your binary package include a directory /usr/share/doc/foo-vendor/ that includes any binary-relevant vendor documentation, such as ChangeLog's, copyright licence's, README's etc. </li>
 	<li>If you are not creating your package from an installed virtual root, be sure to check that the file permissions are appropriate. </li>
-	<li>If you have any 'info' documention in your package, run install-info as part of your post-install script </li>
 	<li>If the package has any global settings (ie in files in /etc) that are not overrideable on a per user basis (sshd, as a daemon, is an example of this) do not include the relevant config files in your package. Instead include in your post-install script to install the settings files. Be sure that if you would overwrite an already present file that the user is offered the choice of keeping their own or overwriting with your defaults. </li>
 	<li>Ensure that your package handles binary only systems, textmode only systems, and hybrid systems correctly. </li>
       </ul>

--
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/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]