How to tell your OSS is ridiculously popular: people aren't 100% sure they didn't embed it, and tack on the software equivalent of "packaged in a facility where peanuts were also present" to the license list.
This watch contains software, so statistically probably contains at least traces of curl.
@danderson Interestingly, they did it with a misidentification of the curl license for another one.
It isn't MIT/X11 but ISC with "and/or" changed into "and", and the no-advertising clause of the X11 license appended.
I guess this is why many rock bands just end up with a slightly awkward name from a drinking session.
(Yeah I switched to french, less lag on subs)
screenshot_mpv:Girls Band Cry S01E07 VOSTFR 720p WEB x264 AAC -Tsundere-Raws (ADN)@00:05:35.982.png
@navi Which is one of the reasons why the oasis thing of just ignoring the upstream buildsystem is a bit appealing.
(Another being reviewability of the code involved, auto*hell configure scripts might as well be arcane assembly)
@navi Usually it just boils down to ${CC} -o ${P} *.c and few -D flags.
But yeah, you wouldn't do a full ports tree like that, but for something a bit like a BSD base system it makes sense and holy shit it's fast.
@a1ba@navi Just in case you're building from something prior to 4.3BSD or AT&T UNIX® System V Release 4 (aka SVR4, which you can grep for in ./configure scripts).
@a1ba@navi Best is when some of those excessive checks occasionally fail with modern compilers because they screwed the syntax (and of course hide compiler warnings…).