Hi Ales, Yes, I'm talking about release tarballs.
And, yes, that is quit easy indeed ;-) However, one should have a makefile. I guess that make uses the files in the working directories, and does not create a tarball from the files inside the CVS repository. I have the impression that git uses the files from within the repository, since there is no makefile for my pcb-dxf-HID I'm currently coding, as compiling it goes into the general pcb make flow by modifying the toplevel makefile et al. It could be that git checks if the files in the working directories are in sync with the files inside the repository and then uses the files in the working directories, my knowledge of the internals of git do not go this far. I could check out all this behaviour tonight ;-) Just my EUR 0.02 Kind regards, Bert Timmerman. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ales Hvezda Sent: Tuesday, March 20, 2007 12:37 PM To: gEDA developer mailing list Subject: Re: gEDA-dev: Souce Contreol of big architectural projects [snip] > git-archive --format=tar --prefix=some/prefix/ HEAD | gzip > ball.tar.gz > > This is much more easier than creating a tarball from a cvs repository. > Are we talking about making the release source tarballs? If so, then building them is one command: make distcheck Doesn't get much easier than that. :) -Ales _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
