-
Notifications
You must be signed in to change notification settings - Fork 211
We need Laravel 5 support!! #260
Comments
I want to known, if the dev team have any plan to support laravel 5? |
Ardent looks unmaintained to me. Go and look elsewhere. |
@igorsantos07 are you still maintaining this repo ? Here is a lot of pull request pending there. |
Sorry men. However I'll be adding some people that offered help here! Sorry! Igor Santos
|
Thank you Igor, I hope things work out for you. Let's keep this repo alive, since it's a really (really) great package. |
I am try to fork this repo and just change the require for iluminate to version : 5 (because i think eloquent model in laravel 5 similar to laravel 4).. but i am not sure for this.. what do you think its work @igorsantos07 @laravelbook ? |
I'm going to clean up this repository this weekend or at most, during the If you want, create a PR, I'll take a look on it and release as a new Igor Santos
|
hay @igorsantos07 , that already exist PR for that #261 |
Not a big deal, as long it doesn't cause a division (as long this package gets back to maintenance as well, of course) |
@azizgithub I would also advise you to not release cloned packages to packagist. You can use your forked code and still maintain the original library reference. Take a look at the Composer docs on custom packages. |
Closing this issue as the subject may be discussed in #261, for cleanliness. |
"You can use your forked code and still maintain the original library 2015-05-10 1:55 GMT+07:00 Igor Santos [email protected]:
Best Regards *[Muh Aziz* Nugroho] |
@azizgithub by following the instructions from https://getcomposer.org/doc/05-repositories.md#loading-a-package-from-a-vcs-repository you would have to do two things:
Now, there is no need to register your forked project separately in packagist and composer automatically retrieves the dependency from your repo. |
Whats up with this? Are you planning to support Laravel 5? Currently composer install fails.
The text was updated successfully, but these errors were encountered: