conforming to a single project name BookMadeSimple vs book_made_simple [#829430]

I am not sure exactly where this difference comes in-- maybe just the name of your project on d.o vs your .info file name. When I use drush to download and install BMS, I have to do:

drush dl BookMadeSimple
drush en book_made_simple

I think more standard would be to de-camel the name of your d.o project name and to strip out the underscores in the filename. Not sure whether this is a real "problem" nor the best way to "fix it"-- I'm only sharing my experience and confusion.

Comments

Comment #1

MarcElbichon CreditAttribution: MarcElbichon commented 23 June 2010 at 07:02

You are right, drush dl seems to be based on CVS project name, and drush en on module name which are differents for BMS.
Unfortunatly, i can't rename CVS directory, and i don't want to change .info project name for compatibility issues.

Will ask to administrator to rename CVS repository.

Comment #2

texas-bronius CreditAttribution: texas-bronius commented 24 June 2010 at 03:41

Thanks!
Also prudent would be to learn what this does to the upgrade path-- would it totally dissociate the previous with the future names for, for instance, a drush up?

Comment #3

MarcElbichon CreditAttribution: MarcElbichon commented 24 June 2010 at 07:38

Is it very annoying for you ?
There are too many risks to change project name.

Are you agree to let in this state ?

Comment #4

texas-bronius CreditAttribution: texas-bronius commented 25 June 2010 at 17:49

I don't know the implications of changing a project name, but I believe it is always for the better to standardize to the naming convention. I think at the code level, there is at least the risk of missing a namespaced function or variable name, and the change to the upgrade path. At d.o/cvs, I haven't a clue what all might be affected, but certainly, for one, all the SEO built up around your current module name for this project page as well as, probably, usage statistics might be lost as this might appear as a new project (unless d.o maintainers would so graciously help sync it if need be).

For me, personally, it's not at all a major issue: I am so happy that this module was shared with the community, and we are all so spoiled to have this wealth of pre-baked development at our disposal! Now then, when a new version comes out, I might come visit this thread again... :D

Is there something I can/should do to help with the switch which might help you decide?

Thanks
-Bronius

Comment #5

MarcElbichon CreditAttribution: MarcElbichon commented 28 June 2010 at 07:52

Issue sent to webmaster to rename CVS directory (see #839206: Rename Git repository)

Comment #6

scottrigby

he/him

English

Brooklyn, NY

CreditAttribution: scottrigby commented 4 August 2011 at 21:45

Version:

6.x-2.3

» 7.x-3.x-dev

Since this is not going to happen (without freaking everyone out by creating a brand new project and marking this as unsupported per #839206-7: Rename Git repository), how about this – suggested by tim.plunkett:

switch the filenames on everyone, underscores are overrated

I'm not sure which is worse between an unsupported module warning (prompting all existing users to go download the new project), or an update where every file gets replaced… But i'm pretty sure I know what's worse than both of those: a module whose project namespace and module filename are different!

Anyone have opinion? We should pick an option and make a patch:

Create a new project book_made_simple (needs a hook_update_N() to migrate table data)
Or change every filename (book_made_simple.module => bookmadesimple.module)
Keep it like it is and break drush

Comment #7

clemens.tolboom

Dutch

Groningen, 🇳🇱/🇪🇺

CreditAttribution: clemens.tolboom commented 21 September 2012 at 13:10

It breaks project dependency too.

drush en rules_add_child No release history was found for the requested project (book_made_simple). [warning]
Module rules_add_child cannot be enabled because it depends on the following modules which could not be found: book_made_simple  [error]


drush dl bookmadesimple No release history was found for the requested project (bookmadesimple). [warning]

drush dl BookMadeSimple
Project BookMadeSimple (7.x-3.6) downloaded to /.../drupal/d7/www/sites/default/modules/BookMadeSimple.  [success]
Project BookMadeSimple contains a module named book_made_simple.

So please create a new project for D7 otherwise this will hints us all down to Drupal 10