Packagist repository out of date

[kevinkhill]

Packagist repository out of date

[kevinkhill]

I don't know it isn't automatically pulling my updates... I will do it manually

[kevinkhill]

Updated 👍

[BadChoice]

Just fixed another laravel issue when using the facades :P

Do any of you what is the best way to develop packages? I'm always doing the fixes in my project in the vendor folder, and then coping it in another project and I forgot things there...

[kevinkhill]

The way I work on my packages (or contributing) is like this: I have a test app, or my current project in one folder, like *~/projects/app*Then in another folder I have my libraries, or forks of libraries, in *~/libraries/fontawesomephp*This way, I can use composer to map to my locaI copies of the libraries, and I don't have to mess with the downloaded vendor versions. Using my composer.json file, I just add a PSR-4 directive, mapping the local path to the namespace. { "autoload": { "psr-4": { "Khill\\FontAwesomePHP\\":"../fontawesomephp/src/" } } } This way I can hack on a library, or develop a new one while testing it in an app. If it is a fork then I can just commit, push, and create a pull request. If it is my package, I can just push it and tag it on github.

…

On Tue, Mar 21, 2017 at 3:29 AM, Jordi Puigdellívol < ***@***.***> wrote: Just fixed another laravel issue when using the facades :P Do any of you what is the best way to develop packages? I'm always doing the fixes in my project in the vendor folder, and then coping it in another project and I forgot things there... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQPXJL34ARENvztpt0MH1IgjVOaynLXks5rn6aggaJpZM4MgjNY> .

-- *Kevin Hill* KHill Designs <http://khilldesigns.com> Github Profile <https://github.com/kevinkhill>

[kevinkhill]

I guess I should include that I don't add them the the require section, because them composer would download them and then there would be conflicting versions.

…

On Tue, Mar 21, 2017 at 12:43 PM, Kevin Hill ***@***.***> wrote: The way I work on my packages (or contributing) is like this: I have a test app, or my current project in one folder, like *~/projects/app*Then in another folder I have my libraries, or forks of libraries, in *~/libraries/fontawesomephp*This way, I can use composer to map to my locaI copies of the libraries, and I don't have to mess with the downloaded vendor versions. Using my composer.json file, I just add a PSR-4 directive, mapping the local path to the namespace. { "autoload": { "psr-4": { "Khill\\FontAwesomePHP\\":"../fontawesomephp/src/" } } } This way I can hack on a library, or develop a new one while testing it in an app. If it is a fork then I can just commit, push, and create a pull request. If it is my package, I can just push it and tag it on github. On Tue, Mar 21, 2017 at 3:29 AM, Jordi Puigdellívol < ***@***.***> wrote: > Just fixed another laravel issue when using the facades :P > > Do any of you what is the best way to develop packages? I'm always doing > the fixes in my project in the vendor folder, and then coping it in another > project and I forgot things there... > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#16 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAQPXJL34ARENvztpt0MH1IgjVOaynLXks5rn6aggaJpZM4MgjNY> > . > -- *Kevin Hill* KHill Designs <http://khilldesigns.com> Github Profile <https://github.com/kevinkhill>

-- *Kevin Hill* KHill Designs <http://khilldesigns.com> Github Profile <https://github.com/kevinkhill>

[BadChoice]

Wow, that sounds really good, this way you can have each package in its own folder and have them related, thank you so much I'll try this approach and see how it works,

My only concern, is that the app is not a test, but the real one, then you have to handle that require/local things to not mess with the production one right?

[kevinkhill]

If you are going that route, then you should add your fork of the library as a source in composer, so when you require "vendor/lib" it won't try to get it from packagist, but use your fork source instead. This way you can keep your changes in with your app, you can push your changes to the upstream, hoping they will get merged and all is well.

Try giving this a read and see if it helps you

[kevinkhill]

Just closing the issue, not our discussion 😄

[BadChoice]

Wow, that link is exactly what I needed, thank you so much! I won't do any more mistakes in you package then hahaha

BTW can you update the version in packagist? Thanks!