This is the mail archive of the
mailing list for the Cygwin project.
Re: cygport suggestion: src_postinstall
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 11 Mar 2012 18:42:06 -0500
- Subject: Re: cygport suggestion: src_postinstall
- References: <4F5A7582.email@example.com> <4F5A8B16.firstname.lastname@example.org> <4F5A97FB.email@example.com> <4F5C3DD8.firstname.lastname@example.org> <4F5CA029.email@example.com> <4F5D2CDA.firstname.lastname@example.org>
On 2012-03-11 17:53, Ken Brown wrote:
On 3/11/2012 8:52 AM, Ken Brown wrote:
If you don't like my suggestion of providing src_postinstall, then
I think there should be a different way for cygport users to have
some control over the postinstall process. What about defining
variables (like PREPEMACS, etc.) that allow the user to turn the
__prep* functions on or off?
If you don't like this suggestion either, what about the attached
patch? The rationale is that if the compile and install steps have
produced some byte-compiled files, then there's no reason for cygport
to step in and do more.
Just because *some* files have been byte-compiled doesn't mean that
*all* possible files have been. So what about using "--eval
(batch-byte-compile `true)" instead of "-f batch-byte-compile"? That
will ignore any files that have already been compiled.