Mark,
The things we've seen on KiCad over the last 10 years--I don't think I'll
ever say anything "doesn't need testing" again.
OTOH--I removed it and the packaging went through fine.
Fine by me if it gets removed.
On Tue, Dec 22, 2015 at 12:27 PM, Mark Roszko wrote:
> >I will put "make a pat
> On 22 Dec 2015, at 19:27, Mark Roszko wrote:
>
>> I will put "make a patch that removes the OS X packaging from tree" on the
>> bottom of my list, so it can be a (slow) race :)
>
> Its dead unused packaging which hasn't had an edit in 6 years:
> https://github.com/KiCad/kicad-source-mirror/t
>I will put "make a patch that removes the OS X packaging from tree" on the
>bottom of my list, so it can be a (slow) race :)
Its dead unused packaging which hasn't had an edit in 6 years:
https://github.com/KiCad/kicad-source-mirror/tree/master/packaging/mac-osx/dmg-generator
You have your own
If someone else can prepare a patch that removes the OS X packaging from
the tree, I will test it. I will put "make a patch that removes the OS X
packaging from tree" on the bottom of my list, so it can be a (slow) race :)
Adam Wolf
On Sat, Dec 12, 2015 at 7:24 AM, Nick Østergaard wrote:
> I t
I think it will be find ot remove the windwos stuff, because it is
easier to maintain outside the source. And it is currently not used by
the package build anyway.
2015-12-11 17:48 GMT+01:00 Wayne Stambaugh :
> I'll leave the decision to remove the /package folder up to the package
> devs. If the
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 co
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 co
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
8 matches
Mail list logo
