[jdong]

Also, I'd like your opinions. I want to release RPMs/Debs for mcc. There are a number of ways I could do this:


(1) Package them, then host them on Sourceforge with a licensing disclaimer (though C-Bot's license agreement is non-existant)
(2) Write scripts that'll take a Windows pre-installed mcc18 tree and package them, on users' PC's.
(3) Write scripts that can take the C-Bot executable and repackage it. This is most certainly the most complicated approach for me...
(4) (3), but with the extra merit

So which will it be?

(1) has some licensing issues, but no concrete, black-and-white issues that I can see.
(2) Is simple to do -- it is fast for me to write, but it requires users to have a copy of Mcc18 and Windows installed, which is not always a pretty assumption. Plus, it now has to go finding and mounting Windows partitions, which users often will not feel comfortable with!
(3) Is complicated for me to do. the EXE is a sfx zip, so it's pretty easy to unpack. However, it has no directory structure, and all the filenames are in caps.
(4) is the hardest... I need to figure out what this "demo stamp" is that the trial EXE looks for.

(2-4) would install like how Macromedia Flash and ms TT core fonts do under Linux: The package is virtually empty, and it fetches the contents on-the-fly.