[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Arx-users] Arx 2.2.4 mv/rm bombs on commit

From: Walter Landry
Subject: Re: [Arx-users] Arx 2.2.4 mv/rm bombs on commit
Date: Tue, 06 Dec 2005 10:31:36 -0800 (PST)

Kevin Smith <address@hidden> wrote:
> Walter Landry wrote:
> > Hmm.  The error message could still stand some improvement.  Internal
> > errors are for things that should never happen.  I have changed the
> > error to
> > 
> > ERROR: I can not find the parent of this file in the manifest.  Did you=
> >  forget
> > to add its parent directory?
> >    <filename>
> Definitely an improvement, but could it be even friendlier? How did we 
> get to this situation, anyway? Is it by moving an archived file into an 
> unarchived directory?

That is one way.  It can also happen by adding a file in an unarchived
directory, or using "rm --id" on the parent.

> Can ArX detect the problem at the point it becomes a problem, and
> tell the user specifically at that point?

It would not be that hard to detect.  The only issue is that it forces
you to have your project tree in a commit'able state at all times.
For example, you might try moving some files into a new, separate
directory.  If it doesn't work out, then you can simply move them
back.  If ArX complained that the new directory is not add'ed, you
would have to remember to "rm --id" the new directory, and there is no
way for ArX to remind you.  This is just extra work imposed by using

Moreover, it is never going to be the case that the tree will always
be in a commit'able state anyway.  People will use "/bin/rm" and
"/bin/mv", or they will forget to add files.

The question then becomes whether it is more annoying to have to fix
up the commit at the end, or to do extra work while manipulating the
tree.  My bias is to make people think about ArX more during the
commit stage, and less during the hacking, tree manipulation stage.
When you are hacking, dealing with ArX is an annoyance.  People will
try all sorts of wacky things when implementing features or fixing
bugs.  Once it all works and they are ready to commit, then they are
more amenable to dealing with ArX's demands.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]