Our composer packages are still listed under the vendor piwik on packagist. As there is no way to rename them, we need to create new packages and mark the old ones as abandoned
I've already started and will try to rename the other over the next days
piwik/cache
-> matomo/cache
(https://github.com/matomo-org/component-cache/pull/17)piwik/decompress
-> matomo/decompress
(https://github.com/matomo-org/component-decompress/pull/12)piwik/device-detector
-> matomo/device-detector
piwik/ini
-> matomo/ini
(https://github.com/matomo-org/component-ini/pull/8)piwik/network
-> matomo/network
piwik/piwik
-> matomo/matomo
piwik/piwik-php-tracker
-> matomo/matomo-php-tracker
piwik/referrer-spam-blacklist
-> matomo/referrer-spam-blacklist
(#12518)piwik/searchengine-and-social-list
-> matomo/searchengine-and-social-list
(#12518)Renaming the php packages does only make sense with Matomo 4, so we can rename all namespaces and classes without the possibility to break any plugins. Imho it doesn't make sense to name the package matomo/*
but the classes would still need something like use Piwik\*
Hi, I'm willing to use the piwik/piwik package in my project so I'm wondering : if you rename it to matomo/matomo, will I still be able to use piwik/piwik in my composer.json or should I wait until you rename it and use matomo/matomo ?
@AndoniLarz what exactly are you going to use? It will take a while until we will rename this package, as we will likely do that in Matomo 4. As most of the remaining rename tasks will be done than. See #12420
Well I wanted to integrate this package into my Symfony project (using 3.2.13 but soon upgrading to 3.3 or 3.4), and I wanted to know if you were going to rename it promptly so I should wait a bit, or if you were going to let it named piwik for some time.
Of course if you have some advice about how I could integrate piwik/matomo in my Symfony project (so I don't have to use two servers), I'd be glad to hear !
Is it possible to create dummy packages? So piwik/piwik requires matomo/matomo?