Re: Re: PhD using Composer - proof of concept and a few questions

On 10 December 2016 at 01:57, Maciej Sobaczewski <sobak@php.net> wrote: > And yet I forgot about one more usage of PhD in our infrastructure... > edit.php.net. > > Yannick, do you know its server is capable of running Composer (PHP > 5.3.2+)? Do you see any possible problems in such change? > It looks like edit.php.net is on 5.3.10. > > Thanks, > Maciej. > > W dniu 09.12.2016 o 18:52, Maciej Sobaczewski pisze: > >> Hello. >> >> >> I would like to bring a topic to discussion - switching PhD (our docs >> building script) from PEAR to Composer. I briefly discussed it last year >> and Hannes (its creator) gave me green light to try it (with making it a >> monolithic package included). >> >> Today, I finally found some time to present you working proof of >> concept. You can find it at: >> https://github.com/Sobak/phd/tree/composer >> (diff of all changes made is available here - >> https://github.com/php/phd/compare/master...Sobak:composer) >> >> ATM it's not hosted on packagist so to install it locally as a Composer >> package you need to clone it, find (or create) COMPOSER_HOME/config.json >> and add: >> >> { >> "repositories": [ >> { >> "type":"vcs", >> "url":"D:\\WWW\\htdocs\\forks\\phd" >> } >> ] >> } >> >> Then you can $ composer global require php/phd dev-composer >> >> It should work exactly like before (try phd --help or phd --version to >> test it). Manual is building fine on my local machine (I didn't touch >> rendering/building logic at all). >> >> I would love to see that implemented on PHP.net. I think it would make >> releasing new versions much easier. But first, I need to ask a few >> questions (I allowed myself to cc systems@ as some of them are related >> to our infrastructure). >> >> 1) Do I understand it correctly that in fact PHP Manual is build only on >> two boxes? docs.php.net (euk2) and rsync (sc2)? >> >> 2) Are there any circumstances that prevent such change? Other than "it >> always worked", please ;) Composer requires only PHP 5.3.2 and that >> requirement is met on euk2 box - I don't know about sc2 though. >> >> 3) Assuming that we want such change. Under whose account should it be >> kept on Packagist. There is one named "php" but I don't think it belogs >> to any of us. Maybe new account like "phpnet" or "phpdotnet". Or maybe >> Hannes would like to have it assigned, as its main creator? >> > I spoke to Jordi Boggiano from composer/packagist, who said that he'll be happy to give us access (to the "php" vendor name). He just needs a repository URL (our github mirror) and a packagist.org username to link the package with (I can volunteer mine, just to get things moving). He also seemed open to talking to the owners of the existing packages with a view to getting them to change their vendor name; if exclusive use of the "php" vendor name is a thing that we would want to happen. >> 4) Any other problems I'm not aware of? >> >> 5) Any implementation suggestions/concerns? I would happily address >> them. Just please be aware that it's only a proof of concept at the >> moment. >> >> I'm hoping for a fruitfull discussion. Constructive criticism is always >> welcome, as well. >> >> Cheers! >> Maciej. >> > >