Grpc: Split PHP into sub-repo for composer

Created on 6 Apr 2017  路  2Comments  路  Source: grpc/grpc

As composer has a strict one-package-per-repository rule, the only way to avoid pulling in a ~50MB package for a ~300KB PHP directory is to split the php package into its own repository.

Can we make a subtree-split for php (grpc/grpc-php)? This could be mirrored and versioned automatically, and is already being done for other composer packages for php (see https://github.com/googlecloudplatform/google-cloud-php vs https://github.com/googlecloudplatform/google-cloud-php-bigquery)

lanphp

Most helpful comment

  • [x] Create a grpc/grpc-php repository. Mark as READ-ONLY and disable issues.
  • [ ] Add scripts to src/php/bin to push to this repository in the master branch from travis on every commit using a subtree split of src/php/lib
  • [ ] Add script for tagging/versioning grpc/grpc-php using a VERSION file (see this example) and set the initial version to 1.4.7 for backwards compatibility.
  • [x] Move composer.json inside src/php/lib and update autoloading. The package name will the stay the same.
  • [x] Add generic README under src/php/lib pointing to grpc/grpc

All 2 comments

  • [x] Create a grpc/grpc-php repository. Mark as READ-ONLY and disable issues.
  • [ ] Add scripts to src/php/bin to push to this repository in the master branch from travis on every commit using a subtree split of src/php/lib
  • [ ] Add script for tagging/versioning grpc/grpc-php using a VERSION file (see this example) and set the initial version to 1.4.7 for backwards compatibility.
  • [x] Move composer.json inside src/php/lib and update autoloading. The package name will the stay the same.
  • [x] Add generic README under src/php/lib pointing to grpc/grpc
Was this page helpful?
0 / 5 - 0 ratings