Closed
Description
Maybe related to #9830
I was able to package composer in a cheesy way by using guix's copy-build-system. All this does is patch the shebangs and move it into the profile's /bin directory where it can be found on path.
Turns out one cannot "just simply patch a shebang" because it causes the resulting composer executible to fail some Sha512 checksum. Fair enough!
Any suggestions for how to properly update the hash? Let me know if I'm off base here.
Fatal error: Uncaught PharException: phar "/gnu/store/pymc4ippfvhlhk1sf5vbg7sdih6h70jg-php-composer-2.4.1/bin/composer" SHA512 signature could not be verified: broken signature in /gnu/store/pymc4ippfvhlhk1sf5vbg7sdih6h70jg-php-composer-2.4.1/bin/composer:28
Stack trace:
#0 /gnu/store/pymc4ippfvhlhk1sf5vbg7sdih6h70jg-php-composer-2.4.1/bin/composer(28): Phar::mapPhar('composer.phar')
#1 {main}
thrown in /gnu/store/pymc4ippfvhlhk1sf5vbg7sdih6h70jg-php-composer-2.4.1/bin/composer on line 28