[cygport - the Cygwin packaging tool] branch topic/phase-hooks, created. 0.35.5-10-g511672ab
Jon Turney via Cygwin-apps-cvs <[email protected]> Sun, 30 Nov 2025 14:00:01 +0000 (GMT)
| Newsgroups | gmane.os.cygwin.cvs.apps |
|---|---|
| Message-ID | <[email protected]> |
at 511672ab8c903544af770368ff93132334085956 (commit) https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=511672ab8c903544af770368ff93132334085956 commit 511672ab8c903544af770368ff93132334085956 Author: Jon Turney <[email protected]> Date: Thu Dec 29 16:09:42 2022 +0000 More https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=20f2b5120c95681f250c4049c7dc23650f347566 commit 20f2b5120c95681f250c4049c7dc23650f347566 Author: Jon Turney <[email protected]> Date: Thu Dec 29 13:31:11 2022 +0000 Add mechanism to allow cygclasses to register hooks for each phase Checks in free code in cygclasses are ill-advised: They get run whatever the subcommand is, and for nested source-ing of the cygport. Add a mechanism to allow cygclasses to register hooks, which can run on a particular subcommand. Use that to defer some compilation environment checks in cross and XXX cygclasses until the compilation phase. Also allow a user hook to be registered for that mechanism. https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=730bb642cf9e28c6ffce0de9f9bb48cd7c500e4f commit 730bb642cf9e28c6ffce0de9f9bb48cd7c500e4f Author: Jon Turney <[email protected]> Date: Mon Dec 19 13:35:59 2022 +0000 Provide an alternative mechanism to get files into $C Creating these files from a .cygwin.patch file works fine when building from an existing source package, it's less great for creating a source package from a VCS checkout. Provide a semi-useful default of including a Cygwin-specific README, if present. Extend gpg signing to include a manifest of the files listed here, since we would have signed the .cygwin.patch itself, if present. https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=b8a71fadf5092fd3f2a08c4ee813f9d6948f1f7d commit b8a71fadf5092fd3f2a08c4ee813f9d6948f1f7d Author: Jon Turney <[email protected]> Date: Mon Dec 19 13:28:56 2022 +0000 Document actions taken on files in $C Also note that .hint files in $C are obsolete, since we now have better ways supplying them, by automatic generation. I thought about declaring PKG.list files obsolete as well, but they perhaps still have a real use when "the contents of a package are too many or complicated to easily describe" in PKG_CONTENTS? https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=c4b7e94b25177522e580fddea53127283d869c42 commit c4b7e94b25177522e580fddea53127283d869c42 Author: Jon Turney <[email protected]> Date: Fri Dec 16 17:45:21 2022 +0000 Ignore errors in nested source-ing of cygport This avoids immediately terminating on calling the 'exit' built-in after any error in the source-ing (e.g. raised by free code in an inherited cygclass), which causes a silent exit now we that suppress stderr from that nested source-ing. We do this by writing "( stuff-which-may-exit ) || true". You might think that the extra subshell is not needed. I certainly did, (because the rules for the 'errexit' mode (which the subshell inherits) are that non-final commands in || lists don't cause an exit if they fail). I was baffled for a long time as to why it's needed until I realized that the 'exit' built-in causes the shell to exit, even when it succeeds. The '|| true' ensures that the substitution does not have a non-zero exit status, which is an error in the top-level shell. Fixes: aa665473aa7d ("Send informational messages to stderr") https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=0c4411c8ca236475175532c86167f755f0e09fd5 commit 0c4411c8ca236475175532c86167f755f0e09fd5 Author: Jon Turney <[email protected]> Date: Mon Dec 19 17:00:38 2022 +0000 Add a test of arch-invariant SRC_URI and PATCH_URI logic https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/cygport.git;h=9424f6b142ba725cf418edeec0e0daa456842c2f commit 9424f6b142ba725cf418edeec0e0daa456842c2f Author: Jon Turney <[email protected]> Date: Wed Dec 14 21:06:40 2022 +0000 More careful handling of source timestamps As suggested in [1], try harder to preserve timestamp information from the original files. This tries harder to retain remote timestamp of downloaded upstream files, and preserve timestamp of those, and of patch and cygport files when copying to the staging directory for the src archive. [1] https://cygwin.com/pipermail/cygwin-apps/2020-August/040407.html