All core modules have repeating version name with version value of the first VERSION

; $Id: ping.info,v 1.3 2006/11/21 20:55:35 dries Exp $
name = Ping
description = Alerts other sites when your site has been updated.
package = Core - optional
version = VERSION

; Information added by drupal.org packaging script on 2008-01-29
version = "5.7"
project = "drupal"
datestamp = "1201565404"

The version name should not put in the info file by hand.

CommentFileSizeAuthor
VERSION.patch14.12 KBclemens.tolboom

Comments

webernet’s picture

webernet commented
Status: Active » Closed (won't fix)

This is done intentionally to aid users who deploy directly from CVS.

clemens.tolboom@drupal.org’s picture

clemens.tolboom@drupal.org commented
Version: 5.7 » 7.x-dev
Status: Closed (won't fix) » Active

I still would vote against this 'to aid users who deploy directly from CVS'.

As stated in http://drupal.org/node/101009 it is discouraged to use version altogether.

Instead I would patch drupal_parse_info_file instead. This would make the info files better machine readable as there is no 'business rule' in it.

Does this makes sense?

lilou’s picture

lilou commented
Category: bug » task
Status: Active » Closed (won't fix)

The version string will be added by drupal.org when a release is created and a tarball packaged. However, if your module is not being hosted on the drupal.org infrastructure, you can give your module whatever version string makes sense.

Users getting their modules directly from CVS will not have a version string, since the .info files checked into CVS do not define a version. These users are encouraged to use the CVS deploy module to provide accurate version strings for the admin/build/modules page for modules in directories checked out directly from CVS.