I'll leave the decision to remove the /package folder up to the package devs. If they are interested in keeping the platform specific package build stuff in the kicad source repo, I'm OK with that. I know that packaging stuff is maintained in the source tree by other projects.
The /new folder contains some code that I want to look at when I implement the new schematic and symbol library file formats. It may not be relevant since I'm going to embed the symbols in the schematic like we do with footprints in the board file. However, I also want to be able to reference external symbols as well so this code may yet prove to be useful. On 12/11/2015 1:11 AM, Mark Roszko wrote: > There are the /packaging/ and /new/ folders in the kicad source. Is > there any reason they are kept around? > > /packaging/ just has a >1 year old windows installer and a 5 year old > osx installer. Its handled out of tree anyway now in other repos. > > > the /new/ folder looks like an attempt at an eeschema rewrite but its > not going anywhere? > > > Source control is our friend and "dead" things should be exiled to the > history. > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
