I downloaded the 6.x-1.x version of the module, installed it on the latest version of Drupal core (from a cvs HEAD checkout) and get this message at admin/build/modules:

This version is incompatible with the 6.0-dev version of Drupal core.

The checkbox to enable the module is not visible.

Comments

greggles’s picture

per module update guide It just needs

core = 6.x

in the .info file.

hass’s picture

Status: Active » Closed (won't fix)

Download the -dev build. Packaging adds the line...

greggles’s picture

Status: Closed (won't fix) » Active

However, for sites that deploy Drupal directly from CVS, it helps if you commit this change to the .info files for your modules. This is also a good way to indicate to users of each module what version of core the HEAD of CVS is compatibile with at any given time.

I think that explains this. Adding it before the packaging script is a legitimate action.

I checked out the code because I want to be able to use the module, test out patches, etc. Also, there was no 6.x-1.x-dev package when I checked it out now that you have one this is less of an issue, but if you want anyone else to help test patches you should add it.

hass’s picture

As an example from past see http://drupal.org/cvs?commit=70657. It was documented to add a version tag for cvs users, and then all version tags have been removed from all projects months ago. I understand that this "core" line give more troubles then the version line, but we will end up with two lines and maybe the same issues. Have you seen any up-to-date docs about this "core" string?

hass’s picture

Status: Active » Fixed
greggles’s picture

thanks!

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.