|
Post by finrau on Feb 6, 2011 22:10:40 GMT -5
OH GOD! I almost hit delete project lol. Yeah okay, so using google code's generated command was just a bad idea. The problem was the --user *email* which naturally didn't exist since it was my email. I also ended up using repo-browser to get to the root directory. Careful now, dont recompute the basic hash key.
|
|
|
Post by finrau on Feb 6, 2011 22:24:39 GMT -5
if you all would like the extra help go ahead and add me to the project as well.
|
|
|
Post by zenzou on Feb 6, 2011 23:19:54 GMT -5
Nothing truly concrete will happen until Daisy releases the next public open source. There's also the chance that we find a better SVN than google and everything gets migrated over, but until then it's just getting a working SVN and anyone/everyone who wants to help out gets familiar with the system. Edit: Okay that commit took forever, but it's done. If people could please try to "checkout" a copy of my branch and compare it to the files of the 1/3/11 open source from otherworldtoday.proboards.com/index.cgi?board=download&action=display&thread=40that would be great. As I said earlier, I deleted all the .swf files, so those should be the only things missing. If all is good, then I did it correctly and, and we can just wait for Daisy. I'll also try to keep my first post in this thread up-to-date with info on how to access the the SVN using Tortoise. Feel free to let me know if I missed anything.
|
|
|
Post by zenzou on Feb 7, 2011 0:26:45 GMT -5
So does anyone have any alternatives to GoogleCode that they'd like to suggest? I'm personally sitting on sourceforge, but I'd like to hear what you all think, and then maybe get Daisy's input as well.
|
|
|
Post by daisy_strike on Feb 7, 2011 6:33:55 GMT -5
I really don't know anything about subversion and am trying to play catch up. The google was just and old toy I tried a long time ago. But at this point we really do need to set up something to move the game to a community game. So suggestions are my best friend... and 2gb seems small.
Daisy
|
|
|
Post by docclox on Feb 7, 2011 7:02:32 GMT -5
Sourceforge is good - I've used them before. I just hate the application process. They don't have quotas, bt they do have an honour system - keep disk usage to a minumum, clean up unneeded data, etc, etc. They don't mind adult oriented projects, but they don't like people serving adult images from an SF web account (having had porno dudes take advantage in the past, I gather).
Sourceforge also have more than one version control option. So you don't need to use svn - they support CVS (bit old now) git and mercurial (know nothing about it). I'd probably stick with svn, failing that, git - although I should add that I've never used it for anything non-trivial.
GitHub would be the other option I'd consider. Only supports Git and I can't find anything about usage caps, though.
Both SourceForge and GitHub are need the project to be formally released under an open source licence. So that's BSD or GPL or somesuch, not just "anyone who wants can see the source code". Github does have non-open options, but they cost money.
|
|
|
Post by docclox on Feb 7, 2011 7:10:14 GMT -5
Looks good. Couple of missing files, but they're ones that I made. We're going to have to merge all this stuff back again at some point, but as you say, we really need a source release as a starting point. Merging is going to be a pain.
|
|
|
Post by zenzou on Feb 7, 2011 12:39:26 GMT -5
As long as the only missing files are the .swf files then we should be good.
|
|
|
Post by finrau on Feb 7, 2011 15:38:19 GMT -5
There is also launchpad for bzr based revision control. They also do allow you to use without a screening process a closed source license. No usage caps.
My suggestion would be to create two separate projects on google code. One for the code, and one for the .swf files.
|
|
nerio
New Member
Posts: 4
|
Post by nerio on Feb 7, 2011 16:06:12 GMT -5
Jesus, I did that to a customer project once. All I'll say is - have backups Good idea removing the compiled files - no version control software is particularly good with binary files, and there's no real reason to have them in there. I'd suggest keeping it that way, and excluding the compiled files from updating by using svn ignore. It'll make the repo much more manageable, and you can always compile it locally.
|
|
|
Post by zenzou on Feb 8, 2011 1:39:19 GMT -5
Alright, since I don't see anyone posting any issues, I'm going to assume: A) No one else is actually looking B) It's working fine. I'm hopping it's B, since at 12am PST, I'm going to merge my "branch" with "trunk".
|
|
|
Post by docclox on Feb 8, 2011 2:36:53 GMT -5
Alright, since I don't see anyone posting any issues, I'm going to assume: A) No one else is actually looking B) It's working fine. I'm hopping it's B, since at 12am PST, I'm going to merge my "branch" with "trunk". You do that, I'll take a branch from that and update it with my stuff
|
|
|
Post by daisy_strike on Feb 8, 2011 3:57:36 GMT -5
Okay so I got check out to work pretty easy now how do I upload my current version... and next time only upload the changed files with out having to sort them myself.
Any ideas... Total novice at this stuff.
Daisy
|
|
|
Post by zenzou on Feb 8, 2011 4:02:50 GMT -5
Done. I didn't actually use the merge command however, since the difference between the two versions is so great. How does merge handle removed files? [Edit] Did you checkout the entire SVN or just trunk? One method would be to make a "Daisy" folder under branch, and then put all your files in it. Once that's done hit "SVN Commit..." and follow the prompts. It should upload if done correctly.
A good method is to have two folders in different places: One with the files that you edit, and one with the version you want to upload/commit.
|
|
|
Post by docclox on Feb 8, 2011 4:16:50 GMT -5
Okay so I got check out to work pretty easy now how do I upload my current version... and next time only upload the changed files with out having to sort them myself. Any ideas... Total novice at this stuff. Basically: - Check out the code,
- Edit the code
- Any new files, right click on them and choose "Add" from the svn part of the context menu
- Right click the folder and choose "commit"
- Watch all that data stream back to the server
- To update from the server, right click the folder and choose "update"
I agree with zenzou that it's probably best if you work in a branch and merge changes into the trunk, but let's get you committing first. (And a truly up to date
|
|