From nobody Sun Feb 18 10:37:06 2024 X-Original-To: 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 4Td2DJ4S0fz5CCkF for ; Sun, 18 Feb 2024 10:37:20 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 4Td2DH50HCz4H5l for ; Sun, 18 Feb 2024 10:37:19 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=JOe4p6nN; spf=pass (mx1.freebsd.org: domain of aryeh.friedman@gmail.com designates 2a00:1450:4864:20::530 as permitted sender) smtp.mailfrom=aryeh.friedman@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-564372fb762so1002200a12.0 for ; Sun, 18 Feb 2024 02:37:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708252637; x=1708857437; 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=5jJBBTG2HAS/ddmrlgHfRSlZcjqMZWr3AfZU+kT/BsU=; b=JOe4p6nN4IlsRqGwz10w6lFuym9/xXGAeAVokum5r6W7K+Gxqwn4Mqfe4x6m1HsENc x6oVTQwXbGfovktK9g1vJ3LoqmLHT92RNkfzpxyE4EVQaEbFhlx6GjAXHtfNP4SzrJFJ W5/fJimBUgrRMvNiHj9AXe8ti43tXy21NKqckUeOYT7Xx0In9QxrmbBHgyOX3MAF8YGG DSjeOsmMg8JCijNbFf1QGTj4hBXMpPxdErzDTb3JzCyfjqQmShyQqz9aSauLxOFyh0QI b5+3KTbST2Mcc04aCuKvoqjcYPJWObXU7DPSW+e7czoD7+tMZaR5CpKWo75EPJNhDzcf CtHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708252637; x=1708857437; 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=5jJBBTG2HAS/ddmrlgHfRSlZcjqMZWr3AfZU+kT/BsU=; b=HK41aZ+cLqQ+G/GQsthd7qGuk5K7pG6EdMv4TDXnfLtRFii7nxwL3tLT9Bgm90gJc2 5bP3WbSKxbY0dNn7R3TO5rtJcdUwbvswfEZPmhMI7sMNGjBJ7VFXnzC8ygCnar/Tshj8 6XJi80NTdFgHapev3jwDH5ecLUvGx1uLeGo4+GJ5WLaQAXU8+N7h/ztYaM8V2Jl48KrG QBMxXAOMHxz3akHYWAOQ8h1uhxMKywszu/NmqIOCFTgerah8G125vOEiVXuflqROzfju 3o8Lud1/f5aW8oInhBqObAz+3MGGcEu208HOohlgQo61tTZqFPyNrUAETUwZBgEZ73I3 viXw== X-Gm-Message-State: AOJu0YyMPgsr+aovkzX9PnUnrFmqe+WXj5W9xZQbl64j6Agrg98O4SEZ Z1fg1A415/NW9EHsXBsKtktijhRBq5aCAHLM3mGENN/W9X9tA01IIQNN+HiXzRC1chaVvCS8n7c imPtGYQl5iTBj3UWNBmfPCCcBRg9uufGG X-Google-Smtp-Source: AGHT+IGcHTemE08XhjVIw5ZaqbZ0/oxS1R30sRCC/e8wIVYvYod6/tGpRA+IN6iI2ClukXkqAGAXyuFxvoBGGAH7Ef0= X-Received: by 2002:a17:906:7155:b0:a3e:5de6:701d with SMTP id z21-20020a170906715500b00a3e5de6701dmr821330ejj.50.1708252637414; Sun, 18 Feb 2024 02:37:17 -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: <4ekno7iwxvdlw4xeholcrxuuazmcstxkqyidrz27ni43lzu6wg@3ro6r5b2vhoi> From: Aryeh Friedman Date: Sun, 18 Feb 2024 05:37:06 -0500 Message-ID: Subject: Re: Re: FreeBSD ports community is broken To: ports@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Td2DH50HCz4H5l X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.16 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; 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:c]; NEURAL_HAM_SHORT(-0.16)[-0.162]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[ports@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::530:from] 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= ?