Skip to content
This repository has been archived by the owner on Jan 13, 2022. It is now read-only.

Dropping the -v4 suffix from the repo & Packagist #638

Closed
SammyK opened this issue Aug 19, 2016 · 15 comments
Closed

Dropping the -v4 suffix from the repo & Packagist #638

SammyK opened this issue Aug 19, 2016 · 15 comments

Comments

@SammyK
Copy link
Contributor

SammyK commented Aug 19, 2016

Let's finally knock out the conversation that started way back in #411 and drop the -v4 from this repo name and Packagist. It's causing a lot of confusion with devs learning the Facebook PHP SDK for the first time so it'll be good to finally fix this. :)

We'll need help from Vivek on this one, but step one would be rename the repo in GitHub then point Packagist to the new repo name. Vivek: Here's the direct edit link on Packagist.

Then we can discuss renaming the package on Packagist to facebook/sdk. I believe this is done by abandoning facebook/php-sdk-v4 and updating the name in composer.json to facebook/sdk and resubmitting. @yguedidi @stof Is that right?

@yguedidi
Copy link
Contributor

Looks good to me :)

@yguedidi
Copy link
Contributor

But I'd suggest facebook/graph-sdk for packagist package name haha

@SammyK
Copy link
Contributor Author

SammyK commented Aug 20, 2016

But I'd suggest facebook/graph-sdk for packagist package name haha

Yeah, that's a good idea since that would disambiguate it from the ads SDK and any other PHP SDK's @ Facebook.

Ping @viv001 :)

@viv001
Copy link
Contributor

viv001 commented Aug 20, 2016

Sounds good guys! I will have a look on Monday and follow up on this thread :)
One thought though - Is there a reason we want to drop "php" from the package name? Like why not facebook/php-graph-sdk (I'd also consider facebook/php-graph-api-sdk) ?

@SammyK
Copy link
Contributor Author

SammyK commented Aug 20, 2016

Sweet - thanks @viv001!

Is there a reason we want to drop "php" from the package name?

It's just to remove some redundancy. Packagist only hosts php packages so there's no need for the prefix. :)

@stof
Copy link

stof commented Aug 22, 2016

@SammyK the process of updating is indeed right.
And +1 for removing the php redundancy in the composer package name (the github repo can of course keep it as there are other repositories)

@SammyK
Copy link
Contributor Author

SammyK commented Aug 22, 2016

Thanks @stof! :)

Perhaps we could rename the repo to match the name on Packagist but with a php- prefix.

Packagist: facebook/graph-sdk
GitHub: facebook/php-graph-sdk

@stof
Copy link

stof commented Aug 22, 2016

Looks good to me

@viv001
Copy link
Contributor

viv001 commented Aug 22, 2016

Update: Changed the github repo name
Waiting on previous owner of the corresponding packagist to grant me admin access to the package. Shall change the url and the name on it once I have the privileges.

@SammyK
Copy link
Contributor Author

SammyK commented Aug 22, 2016

Yay! Thanks @viv001! :)

viv001 added a commit that referenced this issue Aug 22, 2016
Changing the repo name to php-graph-sdk as discussed in #638
@viv001
Copy link
Contributor

viv001 commented Aug 22, 2016

Update 2: Updated composer.json and switched packagist to use the new package. Also set up corresponding github service hook for auto-update.
@SammyK, @yguedidi : Can you confirm everything is as expected and close this? :)

@SammyK
Copy link
Contributor Author

SammyK commented Aug 22, 2016

Yes! Works perfectly on my tests! Once @yguedidi confirms, we can close this one out. :)

@viv001 One more quick suggestion. The the old facebook/php-sdk suggests using the facebook/php-sdk-v4 package.

screen shot 2016-08-22 at 6 37 47 pm

Can we update this one on Packagist to point to the new package as well? :)

@viv001
Copy link
Contributor

viv001 commented Aug 23, 2016

Done :)

@yguedidi
Copy link
Contributor

Looks good! We finally remove it!! :)

@SammyK
Copy link
Contributor Author

SammyK commented Aug 23, 2016

Thanks for everyone's help on this! ❤️

@SammyK SammyK closed this as completed Aug 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants