Package contains .gitignore file

Should modules have their libraries in sites/all/libraries? I don't understand why it's installing it in the module directory.

If libraries module is present then drush installs firePHP to sites/all/libraries. Otherwise, it installes within devel package.

Am willing to change this if there is an alternate consensus.

Writing patch to install to sites/all/libraries even if libraries.module is not enabled as that is reasonable before last-resorting to module directory...

I just spotted this .gitignore file.

Should modules be excluding files from peoples repo's? Is there best practice on this for Drupal? It seems to me like it should be 'repo/info/exclude'ed per repository so that it doesn't get distributed to all users.

Subscribing.

> Should modules be excluding files from peoples repo's?

I'm not terribly keen on a module making decisions about what I do with my project's git repo...

At the very least, if there's a very good reason for it, the .gitignore file should contain a comment explaining this very good reason.

Hi,

I am attaching a patch that "cleans" the .gitignore file

I needed to include such a patch to my makefiles so as not to have to remove the devel's gitignore every time I was building my platform that was causing my git repo to include unnecessary files

How about just removing the .gitignore file entirely?

FYI the patch in #7 should apply to all branches.

I'm up to not provide default .gitignore files, checking with Moshe :)

the patch of #7 it's working for me. The patch deleted the git ignore file.

The update manager refused to copy the dir because of .gitignore (debian) - left me alone halfway installation. everything had copied over except for the .info file. if that happens on more machines i would say its not minor ...

Can someone please RTBC this?

Thanks! That's one more RTBC for the next release.

Pushed to D8 and D7. Thanks.