Re: Broken: time/php-framadate in pkgsrc-current on NetBSD 9.0/x86_64

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Mon, Mar 17, 2025 at 05:48:06PM +0000, Emmanuel Dreyfus wrote:
> On Mon, Mar 17, 2025 at 11:24:07AM +0000, Taylor R Campbell wrote:
> > No, it is absolutely forbidden for the build to talk to the network.
> > All distfiles must be obtained during the fetch phase; any phases
> > after that must not use the network.
> 
> Right, by does anyone know how to split conposer's work into a fetch
> phase and a build phase?

Typing 'php composer offline mode' into google gave me:

https://prahladyeri.github.io/blog/2024/06/how-to-install-composer-packages-locally-offline.html

The first suggestion of which is:

--- begin quote ---
[1] The artifact way.

This is the more preferable way, especially if your goal is to store
the composer package files (*.zip) on your storage drive for long term
use. But do note that if you go this route, you will be responsible
for installing any dependency packages your app may have.

To do this, just edit your app’s composer.json file and add your
storage path in the repositories section:

"repositories": [
  {
    "type": "artifact",
    "url": "./packages"
  }
]

The ./packages could be any arbitrary local path on your
computer. When you specify this path, composer will look in this path
before trying to fetch the packages from https://packagist.org when
you run the composer require command. However, you can also disable
the packagist.org repository completely if you want.

Now where to get the actual composer packages? If you have recently
installed any package, you can find them in the composer cache
directory which is usually at
C:\Users\<username>\AppData\Local\Composer\files. Otherwise, you can
run composer require foo command so that the file is saved there and
you can save it to your storage. In theory, simply packaging the
parent directory of the repo source containing composer.json file
should also work but I haven’t tried that.

But remember that while installing, you must ensure to install
dependencies first. For example, if foo package depends on bar, you
must install bar first.

--- end quote ---

Cheers,
 Thomas