On Fri, February 29, 2008 1:53 am, Adam Kennedy wrote: > Christopher J. Madsen wrote: >> Adam Kennedy wrote: >> >>> This now means that installing modules from the tarball has a different >>> result from installing the module from version control. >>> >> >> True, but if you install from version control, there's always the >> possibility that you've modified the module. This makes it clear that >> you haven't installed the official released version. >> > In the version case at least... what about OTHER ways the file might be > modified, that could have a material impact on the behaviour of the > module?
But that's *all* I intend to do. Just because there are many changes that should never be made at Build distdir time, it doesn't follow that no changes may be made there. Maybe this should be named Module::Build::AutoVersion or Module::Build::SpreadVersion. It takes the version number and release date from the official locations and copies them to all the other places they should appear. I don't like having a bunch of VC log entries that say things like "copied version number from module into README". This module is supposed to make those mechanical updates without leaving droppings in VC. -- Chris Madsen [EMAIL PROTECTED] -------------------- http://www.cjmweb.net --------------------
