You'd have to make 58 dummy commits to your repo. That's how SVN revision numbers work -- they count the number of commits made to the repo. If you want to use arbitrary version numbers (eg. "2.0") you can do that. You're not forced to use SVN revisions as your public-facing version numbers. Just use the desired version number/string as your tag name.
However, I would strongly recommend against using something that looks like a revision number but isn't a revision number. That's just going to end up causing confusion later on.
I put your project into the packager queue manually; nothing happened. If you made a local tag in Subversion, you'd have to push it to the server. Otherwise, you could go to the repository tab on your project and tag from there.
Your current alpha is r142, so the next alpha commit you make will be r143 - this is how Subversion works; it increments the revisions per commit. You cannot change this.
If you want to have no alpha versions, click the Repository tab, select Edit repository from the menu on the right side of the page, then change the packaging to "Release Only" or "Beta and Release Only".
Though, as Phanx said, you should be giving your tags meaningful names rather than aping the Subversion revision syntax - especially if you're using numbers that have absolutely nothing to do with the revisions themselves - or you're just going to confuse your users and/or yourself. The only exception would be if you committed an alpha that was revision 143, and then you named your tag r144-release (that would actually BE r144 in the repository).
Well my names were suppose to be the version of the mod, not the revision. So if I change it to beta and release only. Then when I upload a new version it won't put it up for download till I tag it with a name?
If I saw a list of versions that read "r142" "r143" "v200-beta" I would still assume that "200" was a revision number. In this case, your proposed "v200-beta" is not "version 200". It's "revision 144" -- in that you've made 144 commits to the source code -- or "version 2.0" -- in that it's the first release of a new major version -- or "version 4" -- in that it's your 4th Release tag -- or "version 37" -- in that it's the 37th tag.
Why do you want the version number to include "200" ? It could plausibly be "version 2.0" or maybe "version 20" if you're as liberal with major version numbers as Mozilla, but I don't think I've ever seen "version 200" used for anything. Such large numbers look like version-control revision numbers, period. If you don't want to use your SVN revision numbers, you should use something that actually looks like a version string: 2, 2.0, 2.0.4, 2.1, etc.
I've seen other mods use a simple version number. So for a long time I tried to keep revision and version the same. But with a recode it made sense to roll with 200. That way its easy for me to know hey you're using 200 instead of 144 or 145.
Changing it this late in the game may confuse. Calling it version 200. I think is fine, most people I don't think care anyway. Hell I don't even care with version numbers of mods I download. As long as its easy for me to tell I have the latest download.
Yes, but those mods are either (a) not using a version control system that uses incrementing integers as revision numbers, or (b) using "simple" version numbers that don't look like the revision numbers produced by their VC systems.
Obviously it's your choice, but I think you're just opening yourself up to a lot of unnecessary confusion. You yourself said most people don't care, so why not make things easier on yourself?
What happens once you actually have a revision 200, and someone downloads r200 and reports a bug -- if they just write "200" in their report, how do you know whether they're using "revision 200" or "version 200"? You don't. You can ask them, but if they're like most bug reporters, they won't reply, or they'll only reply months later at which time they'll have no idea what you're talking about. Or you can waste time digging around in both versions of your code trying to guess what could cause the problem they described; if they didn't provide an actual error message this is an even bigger waste of time. Even if they write "version 200" it's entirely possible they're actually using "revision 200" but wrote "version" because they're not a developer and don't know that those words mean different things.
(Also, I moved these posts to their own thread, since they've strayed significantly off the topic of "Torhal please kick the packager and/or finish rewriting it already")
Again : each time you modify your Subversion repository, the tool assigns it a new version number, actually called a revision number, which is linear : 1, 2, 3, ..., 144, and so on. You have no control over that. It is the way it works. (Other VCS use other convention.)
If you want to "name" a version, you have to create a tag. This is exactly what tags are for: associating an human-readable name to a version of your code. With Subversion, this is done by svn-copying your "trunk/" in a subfolder of "tags/", e.g. to create a "FOO" tag, you would do something like this:
svn copy svn://url-to-myrepository-root/trunk svn://url-to-myrepository-root/tags/FOO -m "Tagging as FOO."
(By the way, as you do this, you modify the repository, so this will create a new revision, with a incremented revision number.)
Hopefully, the wowace site provides a more convenient wait to do so: open the "Project management" dropdown and click on the "Tag repository" link. You can input "FOO" and "Tagging as FOO." there and the site will create the tag for you.
Until then, I was only speaking of Subversion. Now, the wowace packager comes into play:
The wowace packager automatically creates packages from commits in Subversion. By default, the settings is "alpha, beta and release" for new projects.
The packager has to pick a version name for the new packages. If it packages an "alpha", e.g. a simple commit to your "trunk/", it simply prefixes the revision number with "r", hence "r144".
However, if it detects a new tag, it will use the tag name instead: if you create a new tag "BAR", the version name will be "BAR", not "r145". There are some subtle rules to detect if a version is a beta or a release, but this can be changed afterwards on the site.
BTW, Torhal: there is no such thing as a local tag in Subversion, every is done on the online repository.
I set to beta and release so it doesn't package until I tell it to. I just tagged it as 2.00 beta. So takes that tag and appends it to GalvinUnitBars to make the file name. Not sure how you make the tag and filename the same. Or if I should bother. Yeah I dont know all the stuff on subversion. Its really complexed. I just learned enough to upload my mod.
So this is how it looks now. Got the 2.00 version number.
Yeah I dont know all the stuff on subversion. Its really complexed.
This complexity is an answer to the needs of people working together on big projects for years. It's not just "complexed" for the sake of it. It is actually quite powerful once you master it, even when you are the only developer.