gEDA-dev: gschem modifications

[Peter Clifton]

On Fri, 2006-07-21 at 10:04 -0400, DJ Delorie wrote:
> > I'd appreciate advice on better working practices, as to seperate
> > out my changes, I now need to checkout the new CVS, make a diff
> > between that and my work (after cleaning the build files (.o etc)
> > out), then sort out the chances which I have made, so I can then end
> > up with a patch for each group of new functionality / changed
> > behaviour I've been working on.
> 
> Just run "cvs diff" in your working directory.  It will compare what
> you've got to what the repository has, and tell you the differences.
> 
> FYI I suggest "cvs diff -U 3 -p" to get some context.

That works well for the existing files, but doesn't give any output for
the new x_compselect.c I moved the component selector into.

I found a reference on google that you should "cvs add ..." the file,
then do the diff, but this negates the benefit of me just taking a diff
of my local changes.

(I have no write access to CVS, and for the time being am happy with
this arrangement - I'd like to learn how to use CVS properly before even
considering asking for access).

As the new component selector isn't 100% finished yet, and might not be
to everybody's liking - e.g. No close button other than from the window
manager etc.. as I want to turn it into a dock, perhaps I should keep
that a local patch.

Any ideas how best to keep some changes local, whilst not getting out of
date with changes in the CVS tree? (Should I go RTFM with a CVS FAQ?)

> Search the archives for posts from me about the database thing.  I've
> mentioned it before.  Also see http://www.gedasymbols.org/csv.html for
> a rough "portable" format.

Format looks good. It might need something more "relational" depending
on what features are requested of it / size of database / etc..

Hope to chat during the code-sprint if I can make it in.

Peter