Skip to content

Cannot understand logic of refreshing one library's info and updating all libraries #1039

Description

@kvelaro

Hi

https://github.com/composer/satis/blob/main/src/Console/Command/BuildCommand.php: 251

Could anyone say me why would we need to update info of library static json files if we are refreshing only one library's info ? In my case its trim/logging and I'm building it using
build /IdeaProjects/backend/storage/app/satis/satis.json /IdeaProjects/backend/storage/app/satis/public --repository-url=https://gitlab.xxxxxxxx.com/packages/logging.git --repository-strict

Scanning packages
The fschmtt/keycloak-rest-api-client-php * requirement did not match any package
The laravel/framework 11.*||12.* requirement did not match any package
Creating local downloads in '/IdeaProjects/backend/storage/app/satis/public/dist'
Dumping package 'trim/logging' in version '25.27.001'.
Skipping 'trim/logging dev-master' (is dev)
Dumping package 'trim/logging' in version '25.33.001'.
Dumping package 'trim/logging' in version '25.11.001'.
Skipping 'trim/logging dev-feature/SMAD-929' (is dev)
Skipping 'trim/logging dev-release/25.32.001' (is dev)
Skipping 'trim/logging dev-release/25.33.001' (is dev)
Wrote packages to /IdeaProjects/backend/storage/app/satis/public/p2/brick/math.json
Wrote packages to /IdeaProjects/backend/storage/app/satis/public/p2/brick/math~dev.json
Wrote packages to /IdeaProjects/backend/storage/app/satis/public/p2/carbonphp/carbon-doctrine-types.json
...
...

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions