Replies: 1 comment
-
At the moment, no. This is a restriction of Packagist and the Composer JSON spec really, and would need changes there; this would have far reaching consequences if not done carefully. One repo = one package. The key thing that PIE/Composer use to discriminate between extensions and "all other" PHP packages is the We are aware of this, as it also affects the Datadog extension; they also have all their PHP and C code in the same place. Unfortunately, I don't have a clear path forward here, without splitting the PHP and C code, but I am absolutely open to suggestions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I use the same repository for both extension and the PHP classes of the wrapper-library. It is single project and API of the extension is not supposed to be used independently.
Right now my
composer.json
uses namecouchbase/couchbase
, while the extension is named justcouchbase
.Is it possible to have
composer.json
that can decribe both PHP library and the extension?With
pecl
I can do it if I include PHP classes into the package, and they will be correctly installed intoinclude_path
.How to correctly achieve this with
pie
without repository split?Beta Was this translation helpful? Give feedback.
All reactions