search

purplespider / silverstripe-file-listing

Basic Download Page functionality, based on an assets directory
BSD 3-Clause "New" or "Revised" License
5 stars 4 forks source link

Rename composer vendor prefix #1

Closed chillu closed 11 years ago

chillu commented 11 years ago

Hello! First of all, thanks for getting on board with Composer with us, and registering your module on Packagist! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)

We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (details). We'd like to ask you to change your vendor prefix accordingly by changing the name key in your composer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the "type": "silverstripe-module" metadata.

In order to ensure existing links to the module continue to work, please add a "replace" key to your composer.json:

"replace": {"<old-name>": "*"}

If you have created branches and releases containing a composer.json file, it is recommended that you push the change there as well (and create new releases). Once the name change is committed, force update the module on Packagist.

Thanks Ingo Schommer, SilverStripe Core Developer

purplespider commented 11 years ago

Hi Ingo,

Apologies, I'd actually come across the comment in the docs about this yesterday, and had already changed one of my modules, was planning to do the rest today. Thanks for the heads up on the "replace" key, I wasn't aware of that!

James

Purple Spider Web Design purplespider.com http://www.purplespider.com

On 27 February 2013 10:16, Ingo Schommer notifications@github.com wrote:

Hello! First of all, thanks for getting on board with Composerhttp://getcomposer.orgwith us, and registering your module on Packagist http://packagist.org! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)

We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (detailshttp://doc.silverstripe.org/framework/en/installation/composer#how-should-i-name-my-module). We'd like to ask you to change your vendor prefix accordingly by changing the name key in your composer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the "type": "silverstripe-module" metadata.

In order to ensure existing links to the module continue to work, please add a "replace" key http://getcomposer.org/doc/04-schema.md#replace to your composer.json:

"replace": {"": "*"}

If you have created branches and releases containing a composer.json file, it is recommended that you push the change there as well (and create new releases). Once the name change is committed, force update the module on Packagist.

Thanks Ingo Schommer, SilverStripe Core Developer

— Reply to this email directly or view it on GitHubhttps://github.com/purplespider/silverstripe-file-listing/issues/1 .

purplespider commented 11 years ago

All my modules have now been updated, Ingo.

Thanks James

Purple Spider Web Design purplespider.com http://www.purplespider.com

On 27 February 2013 10:21, James Cocker jc@purplespider.co.uk wrote:

Hi Ingo,

Apologies, I'd actually come across the comment in the docs about this yesterday, and had already changed one of my modules, was planning to do the rest today. Thanks for the heads up on the "replace" key, I wasn't aware of that!

James

Purple Spider Web Design purplespider.com http://www.purplespider.com

On 27 February 2013 10:16, Ingo Schommer notifications@github.com wrote:

Hello! First of all, thanks for getting on board with Composerhttp://getcomposer.orgwith us, and registering your module on Packagist http://packagist.org! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)

We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (detailshttp://doc.silverstripe.org/framework/en/installation/composer#how-should-i-name-my-module). We'd like to ask you to change your vendor prefix accordingly by changing the name key in your composer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the "type": "silverstripe-module" metadata.

In order to ensure existing links to the module continue to work, please add a "replace" key http://getcomposer.org/doc/04-schema.md#replace to your composer.json:

"replace": {"": "*"}

If you have created branches and releases containing a composer.json file, it is recommended that you push the change there as well (and create new releases). Once the name change is committed, force update the module on Packagist.

Thanks Ingo Schommer, SilverStripe Core Developer

— Reply to this email directly or view it on GitHubhttps://github.com/purplespider/silverstripe-file-listing/issues/1 .

chillu commented 11 years ago

Wow that was quick, thanks James :) On 27/02/2013, at 11:22 AM, James Cocker notifications@github.com wrote:

Hi Ingo,

Apologies, I'd actually come across the comment in the docs about this yesterday, and had already changed one of my modules, was planning to do the rest today. Thanks for the heads up on the "replace" key, I wasn't aware of that!

James

On 27 February 2013 10:16, Ingo Schommer notifications@github.com wrote:

Hello! First of all, thanks for getting on board with Composerhttp://getcomposer.orgwith us, and registering your module on Packagist http://packagist.org! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)

We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (detailshttp://doc.silverstripe.org/framework/en/installation/composer#how-should-i-name-my-module). We'd like to ask you to change your vendor prefix accordingly by changing the name key in your composer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the "type": "silverstripe-module" metadata.

In order to ensure existing links to the module continue to work, please add a "replace" key http://getcomposer.org/doc/04-schema.md#replace to your composer.json:

"replace": {"": "*"}

If you have created branches and releases containing a composer.json file, it is recommended that you push the change there as well (and create new releases). Once the name change is committed, force update the module on Packagist.

Thanks Ingo Schommer, SilverStripe Core Developer

— Reply to this email directly or view it on GitHubhttps://github.com/purplespider/silverstripe-file-listing/issues/1 .

— Reply to this email directly or view it on GitHub.