Re: Anjuta2 renaming status



I tried to diff scaffold but couldn't figure out how to get it to
reflect the files whoes name had changed so instead I have tarred up the
directory.  You can get the file at
http://www.martianrock.com/scaffold.tar.gz

I have also put up my name changing python script at 
http://www.martianrock.com/change_name.py

to use it make it executable and then place it in an empty directory. 
Place any projects which you wish to rename in this directory.  

./change_name.py <old_name> <new_name>

This will go ahead and change everything but the directory names.  It
will print out which directories you need to change.  The reason I don't
do it automaticly is because you can't change directory names while
traversing them.  Later I might implement a function at the end that
uses a list of directories needed to be renamed.

to change Anjuta2 to Scaffold this has to be run twice:
./change_name.py anjuta scaffold
./change_name.py scaffold2 scaffold

It would be nice to see these changes go in as soon as possible so we
don't get stuck having to rename patches :-)

--
J5

On Fri, 2003-07-25 at 03:50, jeroen wrote:
> Hi John,
> 
> On 25 Jul 2003, John (J5) Palmieri wrote:
> 
> > Well I wrote a quick python utility to help in the renaming and also
> > have something to show the small python learning group I am part of.
> > Imagine my supprise when the newly renamed scaffold compiled and
> > installed on the first try.  Python rocks.  There is still a bit more to
> > do before I feel like diffing and submitting it.  One problem that pops
> > up is one of the external plugins (too tired to check which one right
> > now) uses one function from anjuta2.  Either this function should be put
> > into gbf or not used at all.  I also have to make sure I don't munge up
> > the CVS directories since the module name is still anjuta.  I have code
> > in my python script to ignore some files and directories but for some
> > reason it does not work.  If I can work out these things I can have a
> > patch against CVS by tomorow.  If not then by the end of the weekend.
> 
> Cool stuff! Could you post the python script to the list? I'm interested
> how it works as well :)
> 
> > I belive changing the CVS module would be as easy as the gnome CVS
> > maintainer renaming the directory.  So the big question is are we set on
> > scaffold as the name.  As another user has brought up the name Scaffold
> > does not stroke the imagination like Anjuta does.  I personaly like
> > Scaffold but since the name change was so easy I see no reason not to
> > open it up again to other suggestions.
> 
> I don't think we can just rename the module (not sure though). I think we
> need to create a new module from scratch. I'll try and contact a cvs admin
> tonight/this weekend to find out how this is supposed to work.
> 
> > It is ultimatly up to you Jeroen.
> 
> I've pretty much chosen the Scaffold name and i don't see any reasons why
> we shouldn't use that.
> 
> Jeroen
> 
> _______________________________________________
> gnome-devtools mailing list
> gnome-devtools gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-devtools




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