Support building from a local directory / non-Packagist source

[TimWolla]

This would be useful to test if what I've written into composer.json is correct and whether the build actually works, before committing to my changes by pushing them into a public repository and submitting them to Packagist.

This includes both the test after the initial pie-ification and before submission to Packagist and also tests after adding or removing configure flags.

see https://phpc.social/@timwolla/113367860412703002

[asgrim]

Thanks - this should be possible once #48 is complete 👍

[asgrim]

With the PR #83, this becomes possible, and the following steps will enable you to download/build/install source code for a PIE package that has not yet been published to Packagist:

• Use PIE with work in progress branch asgrim:adapt-to-use-composer-installer (see PR Adapt to use composer installer #83)
• If you have not run PIE for the target PHP before:
  • Run pie info -v foo/bar:dev-pie (doesn't actually matter what command really)
  • First run will not work, but will have created an empty pie.json
• Locate pie.json for your target PHP, e.g. in ~/.config/pie/php8.3_<hash>/pie.json
• Update pie.json manually to add the repository for what you're trying to do:

Example for a GitHub repo:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/foo/bar"
        }
    ]
}

Example for a local repo:

{
    "repositories": [
        {
            "type": "path",
            "url": "/path/to/foo/bar"
        }
    ]
}

• Then you can use the package as normal, (using whatever version constraint is appropriate, e.g. foo/bar:* for local repo, foo/bar:dev-branch-name for a GH repo, e.g.:
  • bin/pie info foo/bar:dev-pie (useful for checking the ./configure options available in PIE)
  • bin/pie download -v foo/bar:dev-pie
  • bin/pie build -v foo/bar:dev-pie --enable-some-option
  • bin/pie install -v foo/bar:dev-pie --enable-some-option

Given the above possibility, maybe adding a new pie CLI option to combine (i.e. it would add the repository into pie.json for you), maybe something like:

• --path-repository=/path/to/foo/bar
• --vcs-repository=https://github.com/foo/bar

Usage examples:

• bin/pie install --path-repository=/path/to/foo/bar foo/bar:*
• bin/pie install --vcs-repository=https://github.com/foo/bar foo/bar:*

Since repository configuration can actually get quite advanced, I'm not sure we could get a fully comprehensive syntax in the CLI for defining all possible kinds of repositories, so maybe just providing the basics would suffice? I'm open to feedback on how we actually would do this though, perhaps there is a better way :D

[macintoshplus]

Is it possible to add a custom repository like private composer into the pie.json file?

It's to allow a repository to help distribute extension code sources or pre-built DLL. Especially the oldest extensions.

[asgrim]

Is it possible to add a custom repository like private composer into the pie.json file?

It's to allow a repository to help distribute extension code sources or pre-built DLL. Especially the oldest extensions.

I have not tried a private repo, feel free to try it, the above guide may help :)

[macintoshplus]

The minimal structure for the package is:

{
    "name": "smarty/smarty",
    "version": "3.1.7",
    "dist": {
        "url": "https://www.smarty.net/files/Smarty-3.1.7.zip",
        "type": "zip"
    }
}

For an extension, the dist key is the list of URLs of the prebuild DLL archive? or source code? or whatever?

I have this idea of JSON structure. Right?

{
    "name": "smarty/smarty",
    "version": "3.1.7",
    "sources": {
        "url": "https://www.smarty.net/files/Smarty-3.1.7.zip",
        "type": "zip"
        "reference": "tags/3.1.7"
    }
    "dist": {
        "url": "https://www.smarty.net/files/Smarty-3.1.7-8.4-ts-vs17-x86_64.zip",
        "type": "zip"
    },{
        "url": "https://www.smarty.net/files/Smarty-3.1.7-8.4-ts-vs17-x86.zip",
        "type": "zip"
    },{
        "url": "https://www.smarty.net/files/Smarty-3.1.7-8.4-nts-vs17-x86_64.zip",
        "type": "zip"
    },{
        "url": "https://www.smarty.net/files/Smarty-3.1.7-8.4-nts-vs17-x86.zip",
        "type": "zip"
    }
}

[asgrim]

@macintoshplus I am not sure what your latest comment means, or how it relates to building from different Composer repositories, which is what the OP is asking about. The sources and dist keys don't exist in composer.json. It sounds like you are trying to solve a separate problem, so please can you open a separate ticket :)

[macintoshplus]

Right @asgrim, I have open #110.