Flex removing the pack recipe
Opened this issue · 2 comments
I have a custom recipes repository with one Flex pack ("type": "symfony-pack") and that pack has its own recipe to add a couple of files, nothing fancy.
On one of our machines, Flex unconfigures the recipe after requiring the pack, which means that the files are not added to the project. On other machines, the recipe is left installed and is not unconfigured which leaves the files installed. I can't figure out why would Flex work any differently on one machine, and the other way on all others. Can someone shed some light on this?
Example outputs:
On the machine which unconfigures the recipe:
Unpacking Symfony packs
- Unpacked netgen/symfony-skeleton
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 0 updates, 1 removal
- Removing netgen/symfony-skeleton (dev-master dae1d69)
Generating autoload files
119 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Symfony operations: 1 recipe (b856ae55b2b21b7d954c1f807aaee93f)
- Unconfiguring netgen/symfony-skeleton (>=1.0): From github.com/netgen/recipes:master
Executing script cache:clear [OK]
Executing script assets:install public [OK]
Executing script importmap:install [OK]
On other machines which leave the recipe installed:
Unpacking Symfony packs
- Unpacked netgen/symfony-skeleton
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 0 updates, 1 removal
- Removing netgen/symfony-skeleton (dev-master dae1d69)
Generating autoload files
119 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Run composer recipes at any time to see the status of your Symfony recipes.
Executing script cache:clear [OK]
Executing script assets:install public [OK]
Executing script importmap:install [OK]
is your symfony.lock committed in the repo, or do you have separate lock files on both machines ?
We're testing with instantiating from scratch, using symfony/skeleton, symfony/webapp-pack and then our pack, so no prior symfony.lock file.