<head></head><body>Ah, thanks for your really clear answer !<div><div>Don't you think you can add something about the "repository-url" parameter in the packagist page ?</div><div><div><br></div><div class="nylas-n1-signature"><table style="color: rgb(34, 34, 34); line-height: normal; font-family: Arial, Verdana, Helvetica; font-size: 12px;"><tbody><tr><td style="font-family: arial, sans-serif; margin: 0px; padding-right: 10px;"><img src="https://ci6.googleusercontent.com/proxy/5huatbswCsplm-xcN3pABLVIIj8hcmR1D5tc9nteAtN1pl7eV4jVx431M68RJaB1hx5aB-JFXq24slWiZpRxi2dZPYWi_Y5v9Q=s0-d-e1-ft#http://www.elao.com/images/corpo/logo_red_small.png" alt="Logo Elao" height="60" width="60"></td><td style="font-family: arial, sans-serif; margin: 0px;"><div style="font-size: 16px; color: rgb(243, 65, 65); font-weight: bold;">Florian REY</div><div style="margin-bottom: 3px;">Développeur Symfony 2 Sénior - <a href="https://twitter.com/Elao" target="_blank" style="color: rgb(0, 0, 0);">@Elao</a></div>E-mail : <a href="mailto:florian.rey@elao.com" target="_blank" style="color: rgb(0, 0, 0);">florian.rey@elao.com</a> - Site internet : <a href="http://www.elao.com/" target="_blank" style="color: rgb(0, 0, 0);">http://www.elao.com</a><br>Paris / Lyon / Montpellier - Tel : +33 (0)4 82 53 37 19</td></tr></tbody></table></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Jan 18 2016, at 3:57 pm, Michal Čihař <michal@cihar.com> wrote:
<br>
<p>Hi</p>
<p>Dne 18.1.2016 v 13:12 Florian Rey napsal(a):<br>> as far as i can see, composer support is "kind of" active on the<br>> github repository (see:<br>> https://github.com/phpmyadmin/phpmyadmin/commit/0429a10426bef1925c670c515d792205825649df) <br>> <br>> But the package itself, through packagist, is available (at least)<br>> three times:<br>> <br>> * The "main" package (as it uses the same name,<br>> "phpmyadmin./phpmyadmin", as in the composer.json in the<br>> github repo): https://packagist.org/packages/phpmyadmin/phpmyadmin<br>> o Declared as abandonned (although the suggestion is to use... the<br>> same repo :))<br>> o Maintained by a phpmyadmin core team member<br>> o Outdated (it looks like the git hooks has not been set)<br>> * The wp-cloud: https://packagist.org/packages/wp-cloud/phpmyadmin<br>> o Updated (Manually ? Git hooks ?)<br>> o Not maintained by a core team member<br>> * The shapecode: https://packagist.org/packages/shapecode/phpmyadmin<br>> o Avialable on bitbucket, not github<br>> o Updated (Manually ? Git hooks ?)<br>> o Not maintained by a core team member<br>> <br>> My question is: what is the official policy regarding phpmyadmin and<br>> Composer/Packagist ?<br>> Does it sounds crazy to have the main package on packagist "officialy"<br>> supported, not abandonned anymore, with correct git hooks to have<br>> automatic version updates handling ?</p>
<p>Yes, it would be great. Unfortunately it's not easy with current state<br>of Packagist. That's why the Packagist package is abandoned and our<br>documentation describes recommended way to install phpMyAdmin using<br>composer:</p>
<p><a href="http://docs.phpmyadmin.net/en/latest/setup.html#installing-using-composer">http://docs.phpmyadmin.net/en/latest/setup.html#installing-using-composer</a></p>
<p>The whole problem is that we do some postprocessing on release time,<br>what can not be achieved with Packagist - it can only take git<br>repository as is. See<br>https://github.com/phpmyadmin/phpmyadmin/issues/11508 for more details.</p>
<p>-- <br>Michal Čihař | <a href="http://cihar.com">http://cihar.com</a> | <a href="http://blog.cihar.com">http://blog.cihar.com</a></p>
</blockquote></body>