sfepy/sfepy — Issue #60: clear the mess in input/ and database/
Author: rc
Created: 2012-01-30 10:25:08+00:00
State: open

Each application should have its data in one place, separated from other
apps. Exception: common meshes used in tests and examples.

Migrated from http://code.google.com/p/sfepy/issues/detail?id=56

earlier comments

robert.cimrman said, at 2008-12-17T15:03:06.000Z:

We should probably remove more complex applications from the sfepy repo completely
and leave only the basic examples used for testing/introducing sfepy to people. The
applications could be distributed in another repo. The tarball, however, could still
be used to bundle all.

What do you think?

ondrej.certik said, at 2008-12-17T15:04:57.000Z:

+1, I just realized the same thing with hermes an hour ago and right now I am messing
with "git filter-branch" to filter out my commits into a new repo. We'll think about
that tomorrow in Pilsen.

robert.cimrman said, at 2008-12-17T15:15:18.000Z:

Yes, it's stupid having to commit every line commented in an input file which does
not change the code at all.

In sfepy, I would just remove the files - I do not care they rest in the history, but
if you have something more clever at hand, then why not.

robert.cimrman said, at 2009-03-05T10:33:44.000Z:

I am already using separate git repos for quantum and phono projects, the input files
in sfepy tend to lag behind. Let us remove them from sfepy - we should leave there
just the inputs used for the tests - and provide a separate download/git repo access
for the projects.

robert.cimrman said, at 2010-12-03T13:21:14.000Z:

The examples we have now are reasonably small, tested and maintained, so let's close this.