X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Authority-Analysis: v=2.0 cv=T70Ovo2Q c=1 sm=0 a=6jktZp3dcHAl1vye2O6wCg==:17 a=jl9P3j1e7_0A:10 a=yqpquHFD9rMA:10 a=YW_e6Fk0WhoA:10 a=6WB07kdHjWAA:10 a=8nJEP1OIZ-IA:10 a=wR-FlJDvAAAA:8 a=py4ykTj1jEUA:10 a=2IhdwNTaG9s8DNZlEd8A:9 a=wPNLvfGTeEIA:10 a=6jktZp3dcHAl1vye2O6wCg==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 70.113.67.117 Message-ID: <50F4E4D1.3010802@ecosensory.com> Date: Mon, 14 Jan 2013 23:10:41 -0600 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] geda-skeleton-project: Lowering the cost of a starting a gEDA project References: <87wqvhd4tw DOT fsf AT gmail DOT com> <20130115013756 DOT 9917 DOT qmail AT stuge DOT se> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 01/14/2013 10:31 PM, Ouabache Designworks wrote: > Tool flows generate a ton of files. You do not want to create these files in a RCS repository because that will mean that you > now need a way to clean out these files between runs and the repository has to be set up to ignore them so that the hand full of > files that you are actually working on are easy to identify and won't get lost in the crowd. lndir clones an existing directory > from a repository makes it out of symbolic links. You run all your toolflows in the cloned workspace and nothing is every > generated into the repository. So that simplifies using your libraries, but what about keeping a snapshot of the symbols and footprints as they were the day that project completed a version and made fab data? It sounds like you are suggesting having your project dir not under a revision control system.