From nobody Sun Feb 18 10:39:28 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Td2H34wDLz5CD12; Sun, 18 Feb 2024 10:39:43 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Td2H30P1tz4Hmc; Sun, 18 Feb 2024 10:39:43 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=EumyU+Hc; spf=pass (mx1.freebsd.org: domain of aryeh.friedman@gmail.com designates 2a00:1450:4864:20::129 as permitted sender) smtp.mailfrom=aryeh.friedman@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-512b2adc0e3so138732e87.0; Sun, 18 Feb 2024 02:39:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708252780; x=1708857580; darn=freebsd.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Qe4WFMS0mNvget5wd4sW4WLPmFwNbPFGI3+0226MOqs=; b=EumyU+Hcqoe3O4gVmBM9WRv68zQSapBgiusopq7BamxNTrPKalf/GUvNJYEyFYCbdk pdG0WB1CvdU3lHiyc/DJ7gvDxzFTgfD5nghXuBesx8Fl8oNbBBB7rEDnxd3UGToj23uM UNCqh+1dkIFgvqXot6FW+VFNHa/02GhV+YaKPF5AESK+qW80rxC47IHn9AkSS+XLXF9g ocNa/lBYn9+7y4KJui9ff4/ceqfgI4YZDJh2TQPHKRFKVPyIv13nTuQvt6g7gNHtyWx1 Gqx+81F+QKiYrsMYmsUz8514+nAIIFpzK7vKYY56qkPsllweWeWgpfOgPneQpeR655uy gEXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708252780; x=1708857580; h=content-transfer-encoding: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=Qe4WFMS0mNvget5wd4sW4WLPmFwNbPFGI3+0226MOqs=; b=rsYs9xVHbL65FHo7nTfE3PtoGrPM9W8ZuHceLqqZ+Ivpf3UrPeDOjMIkquJMDN6d4R pL7oVRvthoWAfetGlHvVeC0WAdzNbd1wW/rSuv8PVs07v88T5n3jhe33Z/XsTFkqtlcS oDHLKklfUmg+eNdB7TIK9a1x3W3kp+fJvjKXFx7X5bZPf022gSFOFLj2pinZngs2y0Bd wN5PAUfS8CBFpZEAeAWG69fAngsDcBOPJm+5lW2BO7rM1GCybz3KQzRiHicw0vpDVP8J 9MvuXUU2UAqULNZf+cWlQCZf4vXz2e/hbhdyaNbyNDOuILDgi47vLeYFouR4wK7NcR7E JicQ== X-Forwarded-Encrypted: i=1; AJvYcCXYd7ZUTS9JUiGfdETdBp56otU9pwgpYFJJWMNqw7dFdlAWm3NJQaitbvmnYffkJaIrUJEdQiVyw5cgvtUkgkTJpqN/ZFFpAjFNw7YZSqlDZVbDWaMghiDKV3SIqdNg7KEL9lfE1SOfOFgjajSng8KC88NNP22K2cYFC0rObTOuhO6y1aFBxC3mit7wdUQMs8GzKP+qkJtUl/ZO66KMkqxmk2cfgzSGUHEZvRIA8AOGlONCNpcQhSN9cbi3+jFd X-Gm-Message-State: AOJu0YzF0n5peXYtpA3Qz4MMlvd+rMPJO0yecdQwmUCbCaInlbvnn/jE /zz9IwJWh5/pcNwJW/sE1PzFh7F04pi7JYj/dinLQA2p9y8CBhi/YBJcT0fhijMz3LNSaK+TwN4 pyPu5JBv3f3i9QopFc513n8jKoRLZWhld X-Google-Smtp-Source: AGHT+IHNCVRiG1Zfsue1PXHfp/gAscILl5jafLNRrNYThcFxzN64G6KsaIkwlKJsvuZ9/M0OWn8G+weqZJ+/PW3totQ= X-Received: by 2002:a05:6512:124f:b0:512:8d8f:db7a with SMTP id fb15-20020a056512124f00b005128d8fdb7amr6610584lfb.65.1708252780016; Sun, 18 Feb 2024 02:39:40 -0800 (PST) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <20240218015843.34c5d078@rimwks.local> <7q6ep7m2eee6yqtxftlwkhuwdkssd74vjow55txms7lkokazfu@grrqllhefges> <20240218174921.a8082649142dd43a469bebfa@dec.sakura.ne.jp> <4ekno7iwxvdlw4xeholcrxuuazmcstxkqyidrz27ni43lzu6wg@3ro6r5b2vhoi> In-Reply-To: From: Aryeh Friedman Date: Sun, 18 Feb 2024 05:39:28 -0500 Message-ID: Subject: Fwd: Re: FreeBSD ports community is broken To: conduct@freebsd.org, Ed Maste , FreeBSD Ports ML , core@freebsd.org, vishwin@freebsd.org, zirias@freebsd.org, manu@freebsd.org, Gleb Popov Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Td2H30P1tz4Hmc X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.68 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.68)[-0.678]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MLMMJ_DEST(0.00)[conduct@freebsd.org,freebsd-ports@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCPT_COUNT_SEVEN(0.00)[8]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::129:from] Forwarding to all original recipients because of being blocked from the -ports@ list (see below for details) but no maintainer should *EVER* be blocked from that list ---------- Forwarded message --------- From: Aryeh Friedman Date: Sun, Feb 18, 2024 at 5:37=E2=80=AFAM Subject: Re: Re: FreeBSD ports community is broken To: On Sun, Feb 18, 2024 at 5:16=E2=80=AFAM Felix Palmen w= rote: > > * Tomoaki AOKI [20240218 17:49]: > > [a lot about automotive regulations] > > That's a nice example how comparisons of entirely different domains > almost always go completely wrong. I guess you have never heard of software engineering? Also the OP is 100% right there is a lot of "brokenish" in the ports community for example no maintainer should ever be banned from -ports@ but I have been for reasons never explained to me and thus am at a severe disadvantage when asking for help (like how to switch from yacc to bison without errors and such). > > To start with, cars (and especially individual parts) typically aren't > subject to consumer customizations, and if they are, it's way outside > the manufacturer's responsibility. Here, we were talking about breakage > that only happened when you customized your port builds. We aren't > talking about security-relevant breakage either. Yes they are customized all the time. What do you think "options"? (same for planes.) And sadly (speaking as the maintainer of 3 different ports [devel/aegis, devel/fhist, devel/tailor and when I get time to unbreaking it and taking maintership devel/cook]) there has to good customizations that can be done after market without breaking the ports (for example we use the actual tools above significantly then how they where designed to be used but due to being the maintainer still need to maintain the orginal behavior also) > > As explained in the PR as well, of course we add (temporary) workarounds > to *individual* ports when it seems necessary. We certainly don't add > workarounds to the framework itself unless it's perfectly clear there > will be no other way. Not even considering yet that just fiddling with > CFLAGS has the potential to break a lot of other things when done > globally. The framework has been broken for a long time. It should not require prodiere running on a supermassive machine to work (in many cases portmaster and make install recursion fail where prodiere works). Also there needs to be a more automated process to review new ports and maintership changes. But I think this is more a case of skinny chefs than purposeful/toxic flame wars. > All I have left to say is seeing a toxic thread like this is a very > frustrating experience. So, I'll now move on to something else. So the solution is to sweep it under the rug til it is too late to be fixed= ?