Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Am I mistaken, or isn't it project module that puts the version in the .info file during release packaging, meaning the version = VERSION
in mail_logger.info should not be there already?
Comment | File | Size | Author |
---|---|---|---|
#4 | status report screenshot | 105.96 KB | deekayen |
#3 | mail_logger-info.patch | 689 bytes | deekayen |
Comments
Comment #1
mokko CreditAttribution: mokko commentedI don't really know, but apparently you are right.
Be it as it may, in the dev version it is right and correctly says version = "6.x-1.x-dev"
If it works, I don't consider it a bug. Should we close it? Or remove the line with a patch?
Comment #2
litwol CreditAttribution: litwol commentedIf you check out source from CVS and a module uses 'version = VERSION' in it's info file then you will see in systems modules page something like 6.x-dev or equivalent. without it nothing will appear.
When packaging script on d.o creates a release it adds it's own version string with exact version number.
Either way this is not a bug neither a mistake.
Comment #3
deekayen CreditAttribution: deekayen commentedYou should be using http://drupal.org/project/cvs_deploy to show version numbers of CVS checkouts, not
version = VERSION
.Comment #4
deekayen CreditAttribution: deekayen commentedJust showing what happens when CVS Deploy is installed. The version in the .info file overrides CVS Deploy's feature to read the tag out of the CVS directory and reports a bogus version on the status screen with incorrect status.
Comment #5
deekayen CreditAttribution: deekayen commentedI know I'm already in the pest category when I re-open an issue, but I really think what I've proposed here is the proper way to do versioning. If it also helps, the documentation on .info format officially discourages use of version in .info files unless your project is hosted off the d.o infrastructure.
Comment #6
sjpatrick CreditAttribution: sjpatrick commentedI am also confounded by this module constantly and inaccurately reporting itself as unsupported.
As the suggested fix seems simple enough to implement, I fail to see why this is still an issue.
Comment #7
Dave ReidLooks good and confirmed.
Comment #8
deekayen CreditAttribution: deekayen commentedCommitted to DRUPAL-6--1.