On 06/06/2011 03:50 PM, Miles Gould wrote:
On Sat, Jun 4, 2011 at 12:12 PM, Steffen Schuldenzucker
<[email protected]> wrote:
using darcs to write my bachelor thesis, I repeatedly hit the following
problem: When I write a proof that refers to some other theorem, I want to
make sure that this theorem does actually exist.
When managing a source code repository, the problem should be similar. In
short, I want to specifiy dependencies which guarantee that pulling my patch
will lead to a consistent state again.
I think it's worth asking how much of an actual *problem* you've been
finding this. Do you often find yourself pulling patches and getting a
non-compiling source tree because of some missing dependency? How much
time have you wasted because of this issue?
It is a theoretical question. As I am writing my thesis alone and this
is a pretty linear process, I haven't really been hit by the issue at all.
But I imagined that, in a larger project with many collaborators, it
gets annoying quickly. Which seems to be wrong.
-- Steffen
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
