Development > Newbie Coding

Switch from svn to git without redownloading everything?

<< < (4/13) > >>

Kildor:
I`ll wait until «git-conversion» will be finished. May be at winter?

And will rsync helps to update repo?

Really, it is funny first day, or two. But when this happen all month — it is a bit annoying.

ManicMiner:
For my part there are two issues that could be addressed:

1. Imagine you were someone who doesn't know the first thing about SVN or GIT... and you went here: http://ufoai.ninex.info/wiki/index.php/Download. Compare and contrast, to the relatively painless, user-friendly walkthrough that Muton's build tool had going for it.  

2. IMHO, the availablility of UP-TO-DATE playable dev builds for people who aren't developers, has totally dropped off the agenda since you switched to GIT.

Only a couple of weeks ago, there was someone complaining about RF bugs in the 2.3 game (which had been done to death). That person got given a response along the lines of, "download the source and fix it yourself".

We all knew there were builds out there that resolved that particular bug, begging the question why doesn't someone just update the OFFICIAL download link with a more recent release candidate, instead of mocking every poor noob who's only doing what I'd expect any newcomer to do in the first instance, i.e. download the game from the OFFICIAL link, play it, and report their findings on the forum instead of trawling through the forum for a nightly build and giving that a go?

FWIW I compiled 2.4 from the last SVN, and I've been handing it round the office to them as wants to play the game, and feedback's been great. But since we don't have occasional Muton prebuilds anymore and my build's now a month past its sell-by date, and I've been told there's no point offering that for download to anyone who's interested, what's the plan?

Is this game being developed for gamers, as well as programmers?

bayo:
I am sorry, this comment is out of scope.

Sorry i dont see the point 1. Both Git and SVN are for devs. Kildor is a dev. Yes it is harder for non coder to use Git, anyway we want to use more branches, more merges... then Git is really need. The conversion SVN->Git create at least 3 big problem which make Kildor sad (and me, and maybe every body). Anyway it is need.

2. That's not really our problem, i explain, we never officially maintain it. Only the community do this painful job. If they dont have time to maintain build, to download the new source code, we dont have any more time to do it for them. Anyway we are working on a nightly build bot for all OS + build map + unittest + installer... and so on. Then we know it is a need, and we have all hands on this problem.

And then in few times we should have more 2.4-dev release... every... night?

DarkRain:

--- Quote from: Mattn on September 28, 2010, 08:23:34 am ---anyone tried the rsync method? in theory you should not need to run the PC the whole night, in theory you should be able to continue the git download by entering the same (rsync-)command again.

--- End quote ---

Haven't tried myself but if anyone wants to try you should add the option --partial-dir=$DIR_TO_PLACE_TEMP_FILES_IN to the rsync command given by mattn -- there are some big *.pack files in the repo (I know at least one is around 3 gigs) without this option rsync will download whole files wich means that if it's interrupted in the middle of downloading a big file it will start downloading it from the begining the next time rsyn is called -- with this option it should resume from where it was interrupted last time

(other option of interest may be --progress)

keybounce:
Alright, here's a simple question:

With SVN, it was relatively easy to download just the 2.3 branch, or just the 2.2.1 branch.

It was relatively easy to switch between the 2.3 and 2.2.1 branch for a long time; eventually, due to problems with the (then-out-of-date svn tool on Mac os 10.5.8) svn program, it was easier to just have two separate directory trees.

But I never had to worry about downloading the stuff I didn't want.

I could make local modifications, and generally they would work fine as new updates were fetched; when conflicts were found, it was fairly loud.

How would I go about only fetching just the 2.3 stuff with git, assuming
1: I have git, and
2: I've never touched it yet

How would I go about switching between the 2.3 branch and the trunk? What if I wanted to deal with the 2.4 branch when it is eventually tagged as such?

How are my local modifications handled? How are conflicts handled? How does rewinding to an earlier version, and back again, work? (This is where the version on Mac 10.5.8 stank. )

What if I wanted to take pieces from 2.3 and pieces from 2.4?
Or, equally, pieces from 2.2.1 and pieces from 2.3?

(Actually, that last one is probably not a Git question, 2.2.1 probably doesn't exist in git.)

Navigation

[0] Message Index

[#] Next page

[*] Previous page