Replies: 1 comment
|
That isn't actually a simple thing to figure out, and since you said you don't want to use PIE to do this, you would have to reimplement a lot of the logic needed to work that out. The reason being is many extensions take different approaches; some are on Windows which needs specific URLs for their GitHub releases, some provide pre-compiled binaries for wide ranges of platforms and configurations which need to be detected, some provide pre-packaged source code bundles, and some provide nothing so we download the repository using something like GitHub API or using a git clone etc; it's not a simple thing to figure out as it needs a lot of logistics on the runtime system to work out which is the correct method to download an extension. Hope that helps! |
Uh oh!
There was an error while loading. Please reload this page.
I would like to obtain an HTTP URL for the tar package of the extension source code, similar to what pecl provides. I want to use wget/curl in a Dockerfile to download the code package and then compile it myself. I don't want to install the pie command-line tool. I checked https://packagist.org/packages but couldn't find any download links.
All reactions