Please provide version information within file backup_migrate.info file.

This is only a convenience when looking at the version information within Drupal page /admin/build/modules.

Thanks

Jeff in Seattle

Comments

jeff00seattle’s picture

jeff00seattle commented
Title: Version information in backup_migrate.info » NO version information in backup_migrate.info
ronan’s picture

ronan commented
Status: Active » Postponed (maintainer needs more info)

I'm afraid I don't understand. Version info is usually added by the packaging scripts on drupal.org (and as far as I can tell they're good on the latest dev) What info specifically is missing?

jeff00seattle’s picture

jeff00seattle commented
Issue tags: +.info file

Actually, quite surprisingly, my suggestion is discouraged for drupal-contributed modules as your backup_migrate module:
Writing .info files (Drupal 6.x)

SO, that this module does NOT have my suggestion is the correct way for the backup_migrate.info file to be.

However, If it was my GREAT module and it was a custom non-contributed, then I would put in the following extra lines within backup_migrate.info as I do to my modules:

; $Id: backup_migrate.info,v 1.1.6.1 2008/09/02 16:07:51 ronan Exp $
name = Backup and Migrate
description = "Backup or migrate the Drupal Database quickly and without unnecessary data."
core = 6.x

php = 5.1
package = "Site Management Tools"
version = "6.x-2.x-dev"
project = "backup_migrate"
datestamp = "1244586000"
  1. version will put a value within the Version column within /admin/build/modules page.
  2. package Instead of putting in the full drupal-contributed subgroup Other, you should start a new one called Site Management Tools
ronan’s picture

ronan commented

Did you download the packaged tarball or check the module out from cvs? If you downloaded the tarball, then versioning info should be in there already. I just downloaded it and got:

; Information added by drupal.org packaging script on 2009-06-05
version = "6.x-2.x-dev"
core = "6.x"
project = "backup_migrate"
datestamp = "1244160168"

I could put a package in there, but I'm not really interested in making up my own group just for this one module. Too many modules do this and it doesn't help organization of the modules screen any to have each module in it's own group. If there's an established group in use by other modules I'd be happy to add that to my info file.

Thanks for the feedback

jeff00seattle’s picture

jeff00seattle commented

I used the packaged tarball.

ronan’s picture

ronan commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)
Issue tags: -.info file

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

Issue tags: +

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.