Closed marcelmediact closed 4 years ago
Could you please explain how this will be a lot faster? There should be almost no difference in using packagist or using an extra repo to get a package via composer (e.g. one command extra for adding the github repo which results in a few lines added to the composer.json)
With the growth of the repository on "vcs" the slower it will get. This is due to the package being send through "vcs", which is done by sending individual files (including the all the git files). Through packagist an easier adoption of the package is not only feasible, but it is also being send in a zip format which makes it faster.
Managing repositories is a bit cumbersome as well as being slower.
But o.t.o.h. what's against adding it to packagist? It's nothing more than creating an account and submitting the github url. It'll auto-update when you push new versions to github.
It would be nice if the package will be available in packagist, it will simplify package installation and update via composer.
Any news on this? I'd really like to have this added to Packagist, as it makes it a lot more maintainable with several projects using a lot of different packages via VCS.
I'd like to bump this for the above-mentioned reasons. Please add it to Packagist.
Can you guys give an update on this issue? It's been a year now and we would all love this to be added to packagist.
Since there's no reply on this issue for over a year now and I really want this to be available, I just added it to my company's Packagist account (MediaCT). You can find it here from now on: https://packagist.org/packages/mailplus/mailplus-connector.
I know this will not be automatically updated, but this extension isn't updated that often at all, so I think this will do for now.
Would still like the guys at Spotler to start maintaining this though.
Still waiting for this...
@JKetelaar for now you can use my solution to make it work from packagist.
It's a solution... But I would rather prefer them to maintain and update it
I totally agree, but since they haven't responded to this for over a year now, I don't expect them to take action anytime soon. So until then, I'll ensure it will be up-to-date
Thanks @ArjenMiedema for your solution, it definitely isn't ideal. This is the same for PR #14, as they still haven't solved that one.
If this isn't working out properly, I will be moving to another product instead that keeps their software up-to-date.
We cannot add the package to packagist since the package is already there
@ArjenMiedema could you give me admin acces to that or could you remove the package so we can re-add it?
My username at packagist is the same as on github
@PaulBoss I gave you access to the package, so you should be able to link it.
I've linked the package and the hook is active. The latest release is also visible on packagist now.
Could you please add this package to https://packagist.org/ ? This would make the installation process a lot faster than through VCS.