gEDA-dev: gschem modifications

[Stuart Brorson]

> 
> On Fri, 2006-07-21 at 12:25 -0400, DJ Delorie wrote:
> > > 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.
> > 
> > "cvs add" works locally - you don't need to write to the repository to
> > use it.  Then, use "cvs diff -N ..." to include new files in the diff.
> 
> Unfortunatly, it refuses...
> 
> "cvs add x_compselect.c"
> 
> returns:
> 
> "cvs [server aborted]: "add" requires write access to the repository"

You need to have a CVS account for read/write access.  Ales can give
this to you.  However, I suspect he'll want you to e-mail patches
first, in order to build up trust.  Then, after a while he will give
you an acct.

Therefore, your best bet for now is this:

1.  Check the latest & greatest out of CVS and work on that.
2.  Do 'cvs diff' to see the difference between your work and what you
checked out.
3.  Submit patches by doing 'cvs diff' and then e-mailing the
resulting patch file to a gEDA developer with CVS access.  Do this
only when you have gotten something working.

I wonder if this method (i.e. the usual method) of getting involved in
an open-source project is discussed anywhere online? 

Stuart



> 
> I guess I'll find a workaround, perhaps getting two sets of sources,
> then add my changes to one, and produce a local diff using "diff".
> 
> I'll see if I can persuede CVS to checkout a copy at the same version as
> I started with... that would make things easier!
> 
> Peter
> 
> 
> 
> 
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>