Never mind about that. Or use something neutral, not SVN.
Agreed. Something like
amule-snap-$DATE.arj 
or
amule-devsrc-$DATE.tar.bz2 -- since the
important information is that it's a dump of the most-current developer code.
There couldn't be a
less critical piece of information than what VC it was pulled out of, something that won't ever differentiate the file or give the downloader any sort of choices/direction.
(Unless the core devteam goes completely schizoid and decides to maintain the codebase in multiple competing VC systems simultaneously.)
...Ooh! 
| | Battlin' Version Control!
Just the thing to spice up the build process! This could be even more thrilling than Extreme Coding!
Does our intrepid source-build adventurer choose to...
- Download the source exported from SVN, bravely charging into battle against an army of little .svn directories!?! (Is the filesystem's inode table strong enough to hold their weight?!?)
- Trust that the CVS snapshot was generated from the HEAD, and not some obscure branch of the tree? (Will UploadBandwidthThrottler.cpp revision 1.3.1.1.4.1.0.57 really compile and link in?!?)
- Say a silent prayer to whatever deity she/he {worships, fears, owes money to}, and have faith that all 17 of the project's git servers are properly in sync? (Stay tuned to find out if the snapshot changes depending which continent the tarball was generated from!!!)
|
All kidding aside, just toss the VC-system ident from the filename. The rest of these "suggestions" would obviously be an
awful idea IRL.
...Except for the part about using ARJ files!
(...I can't believe I registered just to post this. And HOLY CRAP it's a pain in the arj to approximate [indent] using tables.)
