[
https://issues.apache.org/jira/browse/THRIFT-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771177#comment-16771177
]
Michael C. Butler commented on THRIFT-4804:
-------------------------------------------
I've looked into how to customize what is provided on packagist.org (the
default source for all composer package installs) and it appears that it cannot
be customized except through using the {{.gitattributes}} file with the
export-ignore directive for certain files and directories. I recommend this
being set up at least for the tests, docs, and development only files, however
it shouldn't be used to exclude non-PHP release data since it is language
agnostic and I'm not sure how those other code files are being distributed.
It's unfortunate but it seems as long as it's all in a shared repository, all
the source code languages will be distributed in the PHP composer install. An
alternate way to solve this would be to mirror the repository's releases to a
sub repo, such as apache/thrift-php and then serve that on composer under
apache/thrift-php, and it would contain only PHP specific code. That may
introduce other challenges though.
> Add only PHP code to the packagist.org composer package
> -------------------------------------------------------
>
> Key: THRIFT-4804
> URL: https://issues.apache.org/jira/browse/THRIFT-4804
> Project: Thrift
> Issue Type: Improvement
> Components: PHP - Library
> Affects Versions: 0.11.0, 0.12.0
> Reporter: Michael C. Butler
> Assignee: James E. King III
> Priority: Minor
>
> We install apache/thrift PHP client library via composer (example: composer
> require apache/thrift:0.12) and after installing, we noticed that the entire
> apache/thrift git repo is there, along with all the C/C++, Go, Java, Python,
> and so on, code. Because composer and packagist are strictly a PHP thing, is
> it possible to strip out the unrelated items to the packagist deployment?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
