Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Levi_Backgammon]

Depending on what Toady's wishes are, this suggestion may be considered pretty inconsiderate. Apologies in advance.

Some people might know about the Subversion repository system: A collection of files can be put onto a special server, from which many users can download in a special way that is especially suited for files that undergo many, many revisions, like DF. I've been looking at the development logs, and I'm fascinated. Perhaps if Toady is not against the idea we users can help set up a repository for him so people who wish to test the very newest features outside of official releases can do so.

The short version about why SVN is better than a plain download is because it's so convenient. The server tracks file changes and which files are changed, which translates to much, much shorter downloads and much, much easier updating. When you update, ONLY the files that have been changed are downloaded. Depending on what we'll be using this for, you may be avoiding 50-Mb downloads, instead just having to download a few hundred Kb. Users running a *nix system (Or a Mac) can simply type "svn checkout [url of SVN repository] [destination directory]" into the terminal and get the newest revisions, and updating is equally easy, simply type "svn update" when in the relevant directory. Worry not, Windows users, TortoiseSVN makes it even easier with a GUI, just right-click a folder and select "SVN Checkout" once you've installed Tortoise, enter the link, and everything gets done for you. Updating is similar, right-click and select "SVN Update". You can even update select files or directories, so for example if there was a userbase-created data repository you could get just a specific type of data or just update one file you needed.

What's everyone think?

[Capntastic]

A:  Toady would only be releasing compiled versions to the public, so I don't see how the downloads would be shrunk.

B:  During longer work cycles like this one, Toady pretty much guts the game into a mostly unplayable state while he tinkers with things.

[Tack]

Agreed on both counts. Also, this save game might break save compatibility. I wouldn't want to have to have my save compatibility broken three, four times whenever I download almost updates.

Other than that, It's a really good Idea.

Other than that, it means that toady would have to spend extra time at the end of the mini updates, making it compatible with dwarf fortress. The more time it takes for updates to come out, the less I liek the idea. Sorry, I'm impatient at the least.

[Bricks]

I'd like to see this, too, but seeing as how it's not an open-source project, it would probably not be a great move.  I'm looking forward to when updates can be more frequent, encompassing 1-3 months of work.

[Sir Finkus]

I don't really see the need for it to be honest.  The dwarf fortress install is only 5.5 MB, and that's the big version with the music.  It seems like it would be more a pain in the ass than just downloading the latest version.

While it would be interesting to look at the intermediate versions, they probably wouldn't be very playable. 

[Sweedumz]

What really would be nice is a GIT based version system for the mods. Things like graphics mods and custom creature/civilisations, etc. Done right and you could have a distributed system for auto installation of various adds ons for the game.

[Maggarg - Eater of chicke]

I do not like SVN.

[chucks]

There is already a git repository for battlechamps.

[lucusLoC]

how about a versioned repository for mods? that way you could still get those hilarious broken releses that i keep reading about without having to dig up old links. we could also do away with the annoing zip files.