Notices on the modules page (due to fake info file)

This is a result of the project module on drupal.org padding our fake info file with 'project information'. Due to the fact that we now have a fake .module file (to prevent SimpleTest breakage) Drupal thinks there is a module and tries to load it (Hurray for qa.drupal.org vs. drupal.org...). Because there is no name in the info file, the errors above arise. And an empty entry comes up on the modules page.
(By the way, that's not a WSOD :) )
It's not critical, because the module is fully usable as is, but should be fixed nonetheless.
Since this is a non-issue in the long-term anyway (the .module file will go eventually...) I decided to commit this little patch, which just adds
hidden = TRUE
to our fake info file. I double checked that it removes all notices and also the empty entry on the modules page.

http://drupal.org/cvs?commit=436094

Thanks Eons for reporting this issue. Please wait for at least 12 hours and then try out the new development snapshot to see if the problem persists.

Let's also rename "example" into "libraries_example". "example" is clobbering a namespace we do not own.

Do you only mean the .info and .module files or all files in there?
In #919632: Allow library information to be stored in info file I proposed to rename the info file to example_info_file.info, so that the library name comes up as 'example_info_file' which is consistent with e.g. 'example_undetected'.

We can leave the other example library files as is, because they do not participate in any system. The .info + .module files, however, are discovered by Drupal's module system, so right now, we potentially override/replace another module that happens to use the internal name "example".

Interestingly, this will be the major problem with the .info file support... projects/modules are not able to just put them somewhere, because they always lead to this auto-detection problem. Right now, the only way I could see to allow modules to provide .info files for libraries would be to put them in a "hidden" directory; i.e., starting with a dot/period; e.g., ./.libraries.

Technically, one could say that this is a bug in Drupal core and SimpleTest... the sole existence of an innocent .info file should not trigger any errors. :-|

1. I just realized that we can achieve the naming consistency and still name the file libraries_example.info by declaring name = example_info_file in the info file. We're basically hacking our own API that way, but...

2. ... those are definitely bugs, coming from the viewpoint of Libraries API. On the other hand, how is Drupal supposed to 'know' that one .info file in */modules/* is a module and another isn't? At least I couldn't think of a solution first-hand. We should still open a bug report for that, though, I think.

3. In contrib, we still have the option to simply force .info files into */libraries/ directories. While that would alleviate the above problem, it is not as comfortable in terms of simply downloading a module. Maybe we can end-up leveraging some new distro/packaging tools for that.

Of course, the existing 'example.info' and 'example.module' would have to be removed when committing.

+++ tests/example/libraries_example.info	15 Oct 2010 13:02:48 -0000
@@ -0,0 +1,11 @@
+; Because Drupal thinks this in a module's .info file, it is in the 'libraries'

Typo in s/in/is/

Aside from that, ready to fly - thanks!

Powered by Dreditor.

Committed the attached patch (Notice I also changed "...file for a library..." to "...file of a library..."

http://drupal.org/cvs?commit=436518