I like the sound of that suggestion!

Perhaps we could have a separate BUILD_INFO file to do
so, rather than putting the info in the VERSION file,
so then you can tell instantly if the module you're
looking at has any info there?

Cheers,
Dave

--- Bryan <bryan@???> wrote:

> Hi,
>
> Just an idea: Creating a module is mostly straight
> forward, especially
> after you have done it a couple of times. But every
> so often you run into
> an application for which creating a module is a lot
> trickier: e.g.
> requires modification of configuration files in
> unexpected places and
> stored in remote corners.
>
> Eventually you succeed in creating the module. All
> is well. Until the
> release of a new update or version of that
> application. You set to work to
> create a new module and you find yourself scratching
> your head how you
> pulled it off the previous time. This because, true
> heroe as you are, you
> of course didn't make or take any notes! Agony and
> frustration just knock
> on your door for an extended stay.
>
> And here's the idea: What if we would extend the
> VERSION file with a
> field, labeled e.g. build_info, to store this
> information?
>
> This way, you only have to open up the old VERSION
> file for some pointers.
> And even better yet, if someone else would like to
> have a go at creating a
> new updated module for this application, they could
> open up the VERSION
> file and do it themselves.
>
> What says you, fellow dyners? Could this be a way
> for "agony and
> frustration" to skip your door because of the
> New-Version-file-inside
> badge shown?
>
>
> Bryan
>
-----------------------------------------------------
> "Er wordt hier veels te abstract gedingest!"
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://lists.dyne.org/mailman/listinfo/dynebolic
>

      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/