From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24260 invoked from network); 17 Jul 2023 12:15:11 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 17 Jul 2023 12:15:11 -0000 Received: (qmail 22360 invoked by uid 550); 17 Jul 2023 12:15:08 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 22321 invoked from network); 17 Jul 2023 12:15:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689596095; x=1692188095; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=y53neZW+36rFqZookg9pkteZfBGqpp26oJSlCkT+wmc=; b=GWVQcDXHmlIsDLYx0sqE5OklGoYjFmp50CUFtStKTdtsVO4xAndghdvWQM08ip/55e drlXS+cW49V1PuCKlHE8rLh4XYzoekNwMqhDe7YM2Bv2n6Yg6BEkkWDFYs4dlLJBbHKO JQaraJ9/9z2ieLMCF2jqRlyybvJF+K/cvC7Zzr4pKQb0GGlSeRGtjDFkMSubhBl3znTd Mcsl+mbQKSq0fIh8qk9qElOBgvK3dZ5eeGFRY+G5VVdkSoSwtoKNOLRK6L+UZfTgGeit KmF7FUqrVfq3ieiLfOt/y5ob2M3vo/bXHF4tbUj6Wj4CP4kRWM3UFnoEOQQP3F0YFF6W FOgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689596095; x=1692188095; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=y53neZW+36rFqZookg9pkteZfBGqpp26oJSlCkT+wmc=; b=kPH+qygh9BIFVyY17oOCmzey26Rq6OK/VvgLz5cUuExSxE34mFr5a/M0cTJ/8lS/LD 4SgKYnLC+5fnudQEXlqMdz/rVFYbdimyh6vOsserUkBroXHLjg/XYBomNXJqjJ6bRxuS /O+JhKtt/b6+tdFoPGAVwCENFZ1qraXLfKDkjoZo1hT76z/qghexye9z4JV76OqB3ibm 6ct4lPYzgJIBHWLoWFS1DkzH/7krw3/UBDD5L8hG+jeMC5GWKo3rkPT/ahhu1Z1XsFqT S1oRWyWOJAfldaWKuAPvW8XKj5jA6TdjEIYQEiIexHJr9SO+XkwnZmHaoJv68aX92Pqj sU1g== X-Gm-Message-State: ABy/qLZJt7fN4h8IYqmwStF5NDRcmb+P00Z84hFC97QNvHM8613sGO/F ashAQacSdsR1r/z73qWDHEj8dBhCd8VOuVHuryf/VLVLPZFmDg== X-Google-Smtp-Source: APBJJlHjcH9kTgs3ZLMM6IYfOlIP3SVET1j9HLN1PKAwJfo5l3p8yxOPYs/qYGXl20nqwDIl8xDMYFw2TX8V3Fvorcc= X-Received: by 2002:a17:90a:a58f:b0:263:e814:5d0f with SMTP id b15-20020a17090aa58f00b00263e8145d0fmr10924368pjq.41.1689596094865; Mon, 17 Jul 2023 05:14:54 -0700 (PDT) MIME-Version: 1.0 References: <20230717011758.55d20eae6e60835c5c7fe954@killthe.net> In-Reply-To: <20230717011758.55d20eae6e60835c5c7fe954@killthe.net> From: Daniel Gutson Date: Mon, 17 Jul 2023 09:14:42 -0300 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="0000000000000c66df0600adbf52" Subject: Re: [musl] musl -- FFS get your shit together, please --0000000000000c66df0600adbf52 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear Dave, Please file your comments in the issue tracker so they can be addressed separately, properly assigned, and track their status and therefore be planned for the next releases. El lun, 17 de jul de 2023, 03:15, Dave Blanchard escribi=C3=B3: > There's a lot to like about musl, but damn, there's some absolutely > ridiculous aspects also: > > 1) How in the hell are you going to make a MAJOR change like changing > #ifdefs from defined(_LARGEFILE64_SOURCE) || defined(_GNU_SOURCE) to just > defined(_LARGEFILE64_SOURCE) in a PATCH level increment, from 1.2.3 to > 1.2.4? What the hell is wrong with you? You just broke my entire build! Y= et > another patch had to be created on my end to UNDO this crazy change; the > only alternative was patching half the packages on my system to fix their > now-broken build! Do you know NOTHING about proper versioning??? > > 2) Did it occur to anyone involved in this project to maybe actually > organize and COMMENT the system header files, instead of just randomly > throwing a random assortment of shit into an .H file and calling it good? > The amount of duplicated, undocumented, assorted crap is pretty ridiculou= s > for a project that's supposed to be a FROM SCRATCH libc implementation! H= ow > about getting it right from the beginning, with a clean and organized > implementation, instead of starting off with a random pile of shit? Even > glibc is better organized, for fuck's sake! > > 3) Why in the hell does musl duplicate/change(!) internal structures from > Linux kernel headers instead of just #include'ing the damn Linux headers > (and relevant structures) and be done with it? > > 4) Would it kill you to add in various simple #defines and such in the > headers which greatly improve compatibility with GNU code, without actual= ly > requiring any support in the libc library code?? > > Between the above, plus the 6-7 "musl addon" support packages required to > be installed alongside to make my Linux system build with musl, at this > point I have essentially FORKED musl! > > Musl is clearly not designed with Linux workstation usage in mind! > > Dave > --0000000000000c66df0600adbf52 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Dave,

= =C2=A0 =C2=A0 Please file your comments in the issue tracker so they can be= addressed separately, properly assigned, and track their status and theref= ore be planned for the next releases.

El lun, 17 de jul de 2023, 03:15= , Dave Blanchard <dave@killthe.net> escribi=C3=B3:
There's a= lot to like about musl, but damn, there's some absolutely ridiculous a= spects also:

1) How in the hell are you going to make a MAJOR change like changing #ifde= fs from defined(_LARGEFILE64_SOURCE) || defined(_GNU_SOURCE) to just define= d(_LARGEFILE64_SOURCE) in a PATCH level increment, from 1.2.3 to 1.2.4? Wha= t the hell is wrong with you? You just broke my entire build! Yet another p= atch had to be created on my end to UNDO this crazy change; the only altern= ative was patching half the packages on my system to fix their now-broken b= uild! Do you know NOTHING about proper versioning???

2) Did it occur to anyone involved in this project to maybe actually organi= ze and COMMENT the system header files, instead of just randomly throwing a= random assortment of shit into an .H file and calling it good? The amount = of duplicated, undocumented, assorted crap is pretty ridiculous for a proje= ct that's supposed to be a FROM SCRATCH libc implementation! How about = getting it right from the beginning, with a clean and organized implementat= ion, instead of starting off with a random pile of shit? Even glibc is bett= er organized, for fuck's sake!

3) Why in the hell does musl duplicate/change(!) internal structures from L= inux kernel headers instead of just #include'ing the damn Linux headers= (and relevant structures) and be done with it?

4) Would it kill you to add in various simple #defines and such in the head= ers which greatly improve compatibility with GNU code, without actually req= uiring any support in the libc library code??

Between the above, plus the 6-7 "musl addon" support packages req= uired to be installed alongside to make my Linux system build with musl, at= this point I have essentially FORKED musl!

Musl is clearly not designed with Linux workstation usage in mind!

Dave
--0000000000000c66df0600adbf52--