[rauld]

Hi,
I want to get the latest-and-greatest 1.6.x version of OpenFOAM. I used the git command as shown on the download page (git clone http://......., git pull). Does this get the complete 1.6.x version or just the changes since the 1.6 tarball?

Thanks,
Russ

[henry]

"git clone" downloads the complete git repository of OpenFOAM-1.6.x and "git pull" downloads the updates since your last pull.

H

[rauld]

Thank you for the reply.
So to be clear, performing this step:

git clone http://repo.or.cz/r/OpenFOAM-1.6.x.git

Will create a local directory called OpenFOAM-1.6.x that contains the most up-to-date versions of all the files found in the tarball - the complete package.

And performing this step inside the OpenFOAM-1.6.x directory:

git pull

Will obtain any and all updates to the files in the project.

Is this correct? The reason I ask is that a colleague suggested that I would have to obtain the 1.6 tarball, and manually patch it with the patch files obtained via git.

[henry]

You are correct, you do not need to download and install OpenFOAM-1.6 first, however you might find it useful to download the ThirdParty packs from 1.6 for use with 1.6.x as these are not included in the git repository.

H

[gschaider]

Originally Posted by henry

You are correct, you do not need to download and install OpenFOAM-1.6 first, however you might find it useful to download the ThirdParty packs from 1.6 for use with 1.6.x as these are not included in the git repository.

I noticed that in the thirdparty-tarball there is a .gitignore that indictates that all the "glue" you wrote to make that stuff usable for OF is under git-control. Would it be possible to publish the 1.6-branch of that repository, too?

People could then

1. clone the repository to ThirdParty-1.6.x
2. untar the downloaded tarball into that directory
3. do a 'git checkout' to revert any files overwritten by the untarring

that would make it possible to easily push fixes in the ThirdParty-stuff (I know they don't happen as often as in the other parts, but it would be nice)

Bernhard

[henry]

We have put our various ThirdParty build scripts under git here but not the whole of the ThirdParty source tree as we do not need version control for those source because we do not or only very rarely change them. I agree that it would be convenient if the whole of ThirdParty could be downloaded using git but it does seem like overkill to use an advanced distributed version control system simply as a download protocol. We are still considering the options but for the moment the best thing to do is to download the release pack of ThirdParty sources.

H

[mwild]

How about a separate ThirdParty-repository, which you then pull in as a Git submodule?

Michael

[henry]

ThirdParty is a very large source tree which does not need to be under version control because we do not change these sources so why is using git to download it better than scp, ftp, http or any other protocol?

H

[mwild]

True. But then, are GCC and OpenMPI really required in the ThirdParty pack? Those are huge, and readily available on all Linux systems I know of... And if GCC-4.3+ or OpenMPI are not available, you still could provide a script to fetch and build those.

[henry]

We did consider providing download scripts but it adds complexity and maintenance problems so for now we decided to stick with supplying a complete ThirdParty pack as we had done for the 1.5 release.

H

[gschaider]

Originally Posted by henry

We have put our various ThirdParty build scripts under git here but not the whole of the ThirdParty source tree as we do not need version control for those source because we do not or only very rarely change them. I agree that it would be convenient if the whole of ThirdParty could be downloaded using git but it does seem like overkill to use an advanced distributed version control system simply as a download protocol. We are still considering the options but for the moment the best thing to do is to download the release pack of ThirdParty sources.

H

My suggestion was NOT to make the whole Thirparty available under GIT (I know that this is an overkill). The pull/untar/checkout in connection with the .gitignore would mean that only some kilobytes are under source-control (I was only refering to these when talking about fixes. Other software would have still been installed via Tars)

Bernhard