mvpmc dongle naming conventions for GBPVR

[mvallevand]

In an earlier post someone suggested adopting a better naming convention for the dongles and zips and I am quite willing to change it to match what you want.

Currently there are three naming conventions

dongle.bin.mvpmc-YYYYMMDD for the nightlies stored as is on mvpmc.org
dongle.bin.mvpmc-0.3.3 for the current version on sourceforge
and I just zip up a dongle.bin in dongle.zip for the alpha's to make life really easy, no real change required.

To add a little more confusion because the link from the survival guide links to another file donglex2a.zip note that it contains (by mistake) dongle.bin.mvpmc-20070830

With 0.3.4 coming out soon I definitely want to ask sub to link to 0.3.4 on sourceforge at http://sourceforge.net/project/showfiles..._id=103474 but I feel that currently we just have binaries which some people won't know how to download. I see adding a zip file dongle.bin.mvpmc-0.3.4.zip but what name do you want to see inside for the actual dongle.

One consideration might be that the file should end in .bin to match sub's search logic in config.exe.

Martin

[sub]

One consideration might be that the file should end in .bin to match sub's search logic in config.exe.

I think that would be worth while...

[nia]

As the suggestee(!) I naturally support this

I personally would prefer the actual file as well as the .zip to be named by somehow including yyyymmdd. The dongle itself inside the zip should probably be a .bin as you suggest. Personally I rename them in the OS, so I don't care too much what part of the filename to rename, but others seem to prefer the config-way, so they should be happy with .bins ...

If main releases are named as x.y.z in stead of yyyymmdd is a fine way to distinguish the more stable releases.

To have an easy rename as well as an easy sorting (also for keeping the .bin files grouped when extension sorting), naming it "yyyymmdd-mvpmc-dongle.bin" could be a suggestion?

/Niels