X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 5 Feb 2015 07:40:58 -0600 (CST) From: mskala AT ansuz DOT sooke DOT bc DOT ca X-X-Sender: mskala AT localhost DOT localdomain To: geda-user AT delorie DOT com Subject: Re: Footprint generation.... was: Re: [geda-user] FOSDEM In-Reply-To: Message-ID: References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <20150202152654 DOT GA13336 AT cuci DOT nl> <54CFD589 DOT 9040702 AT xs4all DOT nl> <20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> <20150204073758 DOT Horde DOT czAmF2JsXvWH254t3K1lrw2 AT webmail DOT in-berlin DOT de> <201502041241 DOT t14Cfd30005029 AT envy DOT delorie DOT com> User-Agent: Alpine 2.02 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.74 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, 5 Feb 2015, Stuart Brorson wrote: > > important and valuable. It seems a shame that gEDA once had that ability > > and now basically doesn't. > > Also, the path most people take w.r.t. defining similar footprint sets > is to use scripts or programs to generate families of footprint files > all at once. For example, John Luciani maintains a fabulous website > containing lots of footprints he generated using Perl: Yes, and I've got my own Perl scripts to automatically generate suites of symbol files containing the attribute data that the FAQ says I shouldn't want. It appears that anyone who is using these tools, as I am, must become a toolsmith to build the necessary features that aren't included. We're all doing that for ourselves individually. Aren't such scripts exactly the kind of "workflow automation" that people are wishing, in this thread, gEDA would supply instead of forcing us all to build for outselves? Whether the scripts are run online, with their output captured by pipes, or offline to generate files written to disk, is not the point. The point is that gEDA used to have a feature for this, and it has been deprecated without a suitable, or any, replacement. I don't know a clearer description for such a situation than that gEDA has taken a step backwards. -- Matthew Skala mskala AT ansuz DOT sooke DOT bc DOT ca People before principles. http://ansuz.sooke.bc.ca/