nager ecosystem.
>>
>>
>>
>> Given Kicad breaks user projects, scripts, and data with major upgrades,
>> I have little sympathy for maintaining compatibility for distro
>> maintainers. It’s their problem if they need to backport a modern cmake.
>>
>>
>&
st in some liquor, but not
> the top shelf stuff since you'll want a bunch.
>
>
>
> I’m in too deep already
>
>
>
> Nimish
>
>
>
>
>
>
>
> *From: *devlist@kicad.org on behalf of Mark Roszko <
> mark.ros...@gmail.com>
> *Date: *Su
On Sun, Mar 19, 2023 at 1:11 PM Nimish Telang wrote:
> Hi,
>
> The current Kicad build cmake code is a man-made horror beyond my
> comprehension. It's clearly been accreted over the years without a lot of
> understanding of what cmake can do. Admittedly cmake itself is the cause of
> most of the
to backport a modern cmake.
· I'm just going to say you should invest in some liquor, but not the
top shelf stuff since you'll want a bunch.
I’m in too deep already
Nimish
From: devlist@kicad.org on behalf of Mark Roszko
Date: Sunday, March 19, 2023 at 9:59 PM
To:
> . There's a lot of zombie code being carried in the Kicad repo for
unclear gain
Welcome to the world of stuff that works and is low hanging fruit for a
bunch of people doing this out of their personal free time.
(Heck honestly at work, we wouldn't bother wasting our paid labor on
"zombie code" t
