Re: PhD using Composer - proof of concept and a few questions
| From: | Maciej Sobaczewski | Date: | Mon, 12 Dec 2016 20:41:26 +0000 |
| Subject: | Re: PhD using Composer - proof of concept and a few questions | ||
| References: | 1 2 3 | Groups: | php.doc php.doc |
| Request: | Send a blank email to phpdoc+get-969386456@lists.php.net to get a copy of this message | ||
Hi,
Just an update on the Packagist story. In short, step 2) above can be marked as done. Jordi Boggiano (from composer/packagist) has helped us out by talking to the maintainers of the packages that were using the "php" vendor name with a view to freeing up the name just for us. In fact, a bunch of the packages have already been moved. Also, we now have PhD on Packagist [1]. I added a composer.json to PhD so that we could add the package to Packagist, ahead of merging Maciej's branch when he thinks it is ready.thank you Peter! That's great news. I also like the approach of commiting composer.json ahead of merge. You're right it simplifies setting up a deployment process on our servers. I thought about it for a few hours. We have a couple of options: 1) $ composer global update php/phd dev-master It seems just wrong for me, now. Utilizing Packagist to fetch latest copy from git master seems to by highly overcomplicated. I thought it would be a good idea, initially, as it ensures we have
phd available globally, like currently.
2) We could set up "repositories" in COMPOSER_HOME/config.json to
map "php/phd" directly to a git repo. Skipping Packagist part
looks like an improvement for me.
3) We could install it locally (git pull && composer install) and
just symlink it like $ ln -s bin/phd /usr/bin/phd
What do you think? Does third approach sounds resonable to you? And
I also forgot to mention PEAR's box in my list message. Unless we want
it to use stable version instead of master, we need to reconfiure it
as well.
I actually think it is ready now. I would appreciate some tests or code
review, though.
Note, I'm currently the only maintainer of the package right now so we should definitely add more people to the list (for the "bus factor") and write down somewhere (on docs.php.net <http://docs.php.net>?) who has access there.I don't exactly know how Packagist handles it. It it would be possible, I'm willing to be one of the people assigned to the project (alongside with Hannes etc, of course). I think that doc.php.net can be used to store such info. Maybe an additional entry on https://wiki.php.net/systems/euk2? Cheers, Maciej.