On 2022-05-17 9:09, Stefan Esser wrote:
Am 17.05.22 um 06:19 schrieb Mel Pilgrim:
On 2022-05-16 20:14, Peter Beckman wrote:
[...]
Consider that it is something the installer needs to do, or build the
package as a deterministic set of packages already installed.
Yes, that's exactly the point
Am 17.05.22 um 06:19 schrieb Mel Pilgrim:
> On 2022-05-16 20:14, Peter Beckman wrote:
[...]
>> Consider that it is something the installer needs to do, or build the
>> package as a deterministic set of packages already installed.
>
> Yes, that's exactly the point I'm stuck on. The fetch-extract-f
On 2022-05-16 21:19, Mel Pilgrim wrote:
On 2022-05-16 20:14, Peter Beckman wrote:
PHP is an interpreted language, Unless there are compiled portions, there
is no porting necessary.
There are many reasons to port a PHP application. Bringing in extensions
and
tracking those dependencies, for e
On 2022-05-16 20:14, Peter Beckman wrote:
PHP is an interpreted language, Unless there are compiled portions, there
is no porting necessary.
There are many reasons to port a PHP application. Bringing in
extensions and tracking those dependencies, for example. I've also seen
a bunch of appli
PHP is an interpreted language, Unless there are compiled portions, there
is no porting necessary.
You're just running 'php composer.phar install' yes?
How does the "application" run? Is it just a directory that is configured
as a root directory for a webserver?
If so, look at www/wordpress or
Composer is a github-centric dependency management tool for PHP
applications. It works very well on its own, but I'm having trouble
figuring out how to integrate it with pkg building.
The composer workflow is:
1. Clone the PHP application repo, which has a composer.json file
2. Download compo
