Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register fork on Packagist #17

Open
amenk opened this issue Apr 21, 2018 · 6 comments
Open

Register fork on Packagist #17

amenk opened this issue Apr 21, 2018 · 6 comments

Comments

@amenk
Copy link

amenk commented Apr 21, 2018

Did you think about registering the fork on an own namespace on Packagist ?

@Yermo
Copy link
Owner

Yermo commented Apr 21, 2018

I am not familiar with Packagist. What is it?

@amenk
Copy link
Author

amenk commented Apr 21, 2018

It's the central registration of composer packages. https://packagist.org ..

To be done:

  1. Register on packagist for example as yermo

  2. Change package namespace in composer.json to yermo i.e.

    "name": "yermo/geophp-with-features",

  3. Submit the package on packagist

  4. [optional] register service hook as they show on packagist, so the package is auto updated on merges / pushes

Long story short: everybody can install the package using
composer require yermo/geophp-with-features

instead of the need to add the repository.

Thanks for the fork by the way :-)

@Yermo
Copy link
Owner

Yermo commented Apr 21, 2018

Oh. Right. Gotcha.

I've been very slow to adopt composer over here but I should join the 21st century at some point. Thanks for the suggestion.

It's cool to see someone using this library. If you run into any problems or have any suggestions, let me know.

@acorncom
Copy link

I'm interested in the above as well. I've got a few tweaks to make to the output of GeoJSON that I'll send over in a PR, but these changes are quite useful on my end too ...

@acorncom
Copy link

@Yermo any interest in registering on Packagist? I continue to use your updates on a project, would love to switch to using a registry with published assets vs pulling off of our Github fork of your project ...

@Yermo
Copy link
Owner

Yermo commented Jul 27, 2023

@acorncom Thanks for the reminder. I had completely forgotten to do this. I've submitted it. If you would. please check that it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants