Hi all,
I think that for pcb the "method" and "content" should be separated as
in geda-gschem and geda-symbols, that is:
one tarball for the pure pcb application {1} (with the GPL v2 or
better) and
a second tarball for the pcb footprints (with whatever license
applicable or required).
I have always considered "content" a responsibility of the user, not a
responsibility of the developers of the application.
It's up to the [commercial, hobby, educational] user to install (or not)
the tarball containing the footprints.
Even better, putting the "content" in a separate tarball frees the
developer community of their precious time invested in this thread.
Maybe there could be some sort of dialog to accept the license agreement
for the installation of the tarball containing the pcb footprints.
IMHO it should be the user's choice to goof up gsc2pcb or whatever
script/importer/application is run on the pcb layout when the pcb
footprints are not installed.
Another reason for this separation is that the pcb application code base
is in more turmoil than the footprints library (which should be pretty
stable if good checking before release of a particular footprint is
done).
OK, the m4 --> newlib change gave lots of additional footprints, I
consider this a one-time event.
{1} I could even imagine that guis/printers/exporters/importers chould
have their own tarball.
Just my EUR 0.02
Kind regards,
Bert Timmerman.
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
