Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: JIN on January 10, 2011, 12:05:15 am
-
I'm willing to put up a torrent of all the latest installed build+media vps enhancement files if someone can create an SVF or par of all the files in a default installation, so that I can check the files against a default installation (to have a version to check against).
http://www.quickpar.org.uk/
http://www.quicksfv.org/
The freespace installer was slow and dl' was slow so I'm thinking a torrent would be good.
-
It's not a bad idea, but it depends on how many are willing to be long-term seeds for this thing. That, and updating is going to be a pain.
-
Updating is already a pain since dl speeds are atrocious, also the need to create new pilot files and/or reselect campaign on update is annoying I'm wondering if FS_OPEN guys can't fix this. As to dl'ing.. normally people like to dl a fresh install or over-write an old install. Plus having a torrent of all files you can just copy into your a copy of your FS2 directory just makes it a lot easier.
This is why I suggested SVF/pars so one can check to see if ones install is corrupted/different to just focus on the files that have changed so they know what to dl. When torrenting you can choose what files from the torrent to dl specifically and block the others if you need to.
-
Pilot file issues are already being fixed, as for the idea... it's a good thing, donwloading from a torrent is always better than downloading from an ftp source for me, given I can restart and stop the download at any moment.
-
It's not like it's hard... Someone just needs to zip up a default directory minus retail files, with separate zips (sharing the same file hierarchy) for the mod campaigns the installer had. Stick in a readme explaining where/how to extract it, where to put retail files, shove the whole thing into a torrent on demonoid or something, and voila.
I'm guessing that each final release or two will merit its own core files torrent, and patches can be distributed as smaller torrents meant to be drop-and-play.
-
The problem with torrents is that they keep being seeded after they should have been allowed to die. We still occasionally see people turning up with FSO 3.6.5 and that's over 4 years old!
But it is a good idea as long as people remember to let it die eventually. :p
-
Before I go off hunting, has anybody ever heard of hosting SVN over Bittorrent or some similar P2P system?
-
uhhh
wat
I am not certain that something like that is possible, or even a good idea.
-
Essentially I was hoping to find some method of distributing a read-only repository across multiple servers. Bittorrent+SVN was just the quickest way I could think to write it. I looked for a bit but couldn't find anything close.
Some people claimed it would be a security risk, but if the hash checking was governed by the "tracker(s)" then I don't see why it would be any riskier than Bittorrent is already.
I don't see why it would be a bad idea though. There's a desire to serve a ton of community files all in a single package, harnessing the power of p2p. The downside to doing this with current methods is that old torrents don't die. And for anybody involved in serving to upgrade to new releases, everybody needs to download it all again meaning new releases always start horribly slow, which is exactly the time when you actually need MORE seeds.
I'm just trying to think outside the box, maaaaaaaaaaaaaaaan :(
-
Essentially I was hoping to find some method of distributing a read-only repository across multiple servers. Bittorrent+SVN was just the quickest way I could think to write it. I looked for a bit but couldn't find anything close.
What you're looking for is distributed revision control.
http://en.wikipedia.org/wiki/Distributed_revision_control
SVN doesn't fall into that category, as it is centralized.