fenics team mailing list archive

[Martin Sandve Alnæs <martinal@xxxxxxxxx>]

Comments on removal of files:

a) Reference data for regression tests can't be removed from the
repository. With a significantly larger unit test suite the number of
regression tests could safely be reduced, but that is a lot of work. We
could strip older versions of reference files and re-add fresh ones.

b) The list contains files like Changelog, CMakeLists.txt from the build
system which obviously need to be retained, as well as meshes used by demos.

c) In any event we should keep checked in the few generated files that are
part of the dolfin source, so _building_ dolfin does not have dependencies
to the entire fenics toolchain.

d) How does the build system know when to/which files to regenerate? I
guess calling ffc as part of the building of C++ demos is no worse than the
jitting in Python demos. This will add quite a bit to the demo/test build
time though.

Martin


On 21 March 2013 21:58, Anders Logg <logg@xxxxxxxxx> wrote:

> On Thu, Mar 21, 2013 at 06:52:58PM +0100, Johan Hake wrote:
> > Nice work!
> > So this is how git get so fast, we first remove all the large files ;)
>
> Yes, exactly.
>
> I didn't think it would be such a hassle. I was imagining a simple
> conversion (which took just a few minutes to figure out), but then
> suddenly we are in the git camp and need to rewrite our history to
> present a beatiful repository to the world. :-)
>
> >> I have done some work on cleaning up the DOLFIN repository.
> >>
> >> - All data files have been removed from the lp:dolfin bzr repository.
> >>
> >> - All generated code has been removed from the lp:dolfin bzr repository.
> >>
> >> - With the help of Jed Brown's git-fat, I have generated a list of
> >>  files that I suggest we strip from the history (once the new
> >>  conversion has taken place).
> > How will this affect the possibility to compile legacy versions of
> > dolfin to test for example speed ups? Are these done with cached
> tarballs?
>
> Those can be built (with a lot of effort) using the tarballs, and the
> converted unchanged repository as well as the present bzr repository
> will be stored for eternity on the web server.
>
> What needs to happen now before we can make the transition is:
>
> 1. Get the buildbot green again. It is broken as a result of some
> renaming and removing of files that the buildbot needs to generate.
>
> 2. Release 1.2.
>
> 3. Get comments from Florian or anyone else interested in merging in
> converted repos on the Git side.
>
> 4. Get comments from developers on the list of proposed files to be
> deleted from the history.
>
> --
> Anders
>
>
> >> Please look at the files to be removed here (files_to_strip.txt):
> >>
> >>  https://gist.github.com/alogg/5213171
> >>
> >> Btw, is there some equivalent of the Gist thing for Bitbucket? I found
> >> it very convenient for sharing the above data. Actually, I couldn't
> >> figure out any other convenient way to do it.
> >>
> >> Garth is on his way to Australia, Florian needs some time to think
> >> about what this means for conversion of branches (like his FFC
> >> branch), Johannes is about to make a new release and I need feedback
> >> on the file removal. So the new message is to keep on working on the
> >> Launchpad repositories (with focus on cleanup and bug fixes) until
> >> this has settled, and I'll run the final script for conversion of the
> >> repositories again when we have worked out all the issues.
> > Sounds good.
> > Johan
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~fenics
> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fenics
> More help   : https://help.launchpad.net/ListHelp
>