From nobody Tue Jul 18 06:13:19 2023 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 4R4pYG670mz4mqBX for ; Tue, 18 Jul 2023 06:13:38 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 4R4pYF0rDhz3h9r for ; Tue, 18 Jul 2023 06:13:37 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-bff27026cb0so5486273276.1 for ; Mon, 17 Jul 2023 23:13:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689660816; x=1692252816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VeFWFwR9mujBB9pEjThVMWhFqP0hPlzWccL12YaA0KU=; b=U00yc4TiEwSOAx5iPlW4yEmxjyPzupqRDvW/0brgoA1eEZTd+Aj0ZkhKFi9UPP9REA 2UPm3N+Tzgpynds+ET5kofYv16X6nOEBMiA3PjtlklVn4ptYACatiefnvl0nWUfLlxzg RaycuZRtPVz8WsV8+u79t6oUCAuEaREKpr4aZXAvHXz9ew3Q8Smo91GkgQ1HkkAUx7Ek RMVWh8l7e4JowmD+7R4p75BV32uE/HpMi9dCw6mBdf3pnp07QVdm++9mnt8xDafErAIR 0HCsyI4DKQO4rfq+LgXiJzQkTRPM5LpNyzxC7Nv/Y4pCo+PO7wtEs32D97TljbVjGXU5 ZXiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689660816; x=1692252816; h=cc: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=VeFWFwR9mujBB9pEjThVMWhFqP0hPlzWccL12YaA0KU=; b=BrwN2/rseSxdutOOdT1wEr2tLysGAUOTvVXX91yL5EPbUaGqGjn7W1uYdG0paSib5i rB5MRiGAXjoaLhDgdG2/3xLvQcYn+Ye9i7uFSnSNJFz1rjaHBE0yK+mT26oCMqTFJzwH zsKyIZwuZXZ8JwKiU0EPu/mYiY6EskuCMxyQSAtpIXyUXUVKKOD1IOljA9jkOMhn5RMr bn28ggAY9OZhPWqrjDbriAhNHFMemanKeEf8Hn1Aq8yBVZQhtzd1mP26u1mB5/7F3ES9 EtG++/q/LkDnmKoCBPn03fE5SbyOBbq3pI19E5ZaPqX5wpuijFT8i7OoGF0C+cqnNyDo xwkw== X-Gm-Message-State: ABy/qLaHMMwIs0rDsDx4wdUTP6k7F225affORDRJdimtgVXNkO/bxUbg QryL6h60JNy/fhCnoK1R04EQYRVhr8t8H+Tfwx0Rq7q/ X-Google-Smtp-Source: APBJJlG1juXDfoCEfcSLH2kR3IXfnYxqMk2buODZIAvk0aw52rYLb+TUbA6T92V1W0/bJCGHIK5CD5NVJUxdxI1ShOE= X-Received: by 2002:a25:b909:0:b0:caa:78bc:e60 with SMTP id x9-20020a25b909000000b00caa78bc0e60mr13032673ybj.22.1689660816274; Mon, 17 Jul 2023 23:13:36 -0700 (PDT) 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: <67AAFD7F-CE3C-4051-ADE9-0646BCC16143.ref@yahoo.com> <67AAFD7F-CE3C-4051-ADE9-0646BCC16143@yahoo.com> In-Reply-To: <67AAFD7F-CE3C-4051-ADE9-0646BCC16143@yahoo.com> From: Kevin Oberman Date: Mon, 17 Jul 2023 23:13:19 -0700 Message-ID: Subject: Re: Can someone please post a concise list of things maintainers are supposed to do? To: Mark Millard Cc: stb@lassitu.de, FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000beb8980600bcd07a" X-Rspamd-Queue-Id: 4R4pYF0rDhz3h9r X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000beb8980600bcd07a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2023 at 7:31=E2=80=AFAM Mark Millard wr= ote: > From: Stefan Bethke wrote on > Date: Mon, 17 Jul 2023 07:04:11 UTC : > > > every time I submit a PR to update a port I maintain, I get conflicting > instructions about how to fill in the PR. This is really annoying, and so= me > committers apparently feel they will not move forward in processing the P= R > unless some bureaucratic bullshit is done. > > > > Can the ports team please provide a concise, definitive list on how a > maintainer is supposed to fill in a port update PR, so this nonsense stop= s? > > It might be useful to report the specific conflicting instructions > that you have received and to ask that the "definitive list" at least > resolve the specific conflicts. Otherwise the list might miss some > issues that you ran into. Right now there is no way for someone > generating a list to know up front if they have covered all your > example issues. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.co m This is an old issue. Many years ago I submitted a new port for the weird modem in an IBM ThinkPad. The committer who picked up the ticket insisted that some scripting involved be rewritten in Perl. I did so and finally got the port committed. Less than two weeks later it was announced that perl would be removed from the base system and that port scripts needed to be converted to sh. While I applaud the removal of perl, I asked what the "rules" were for structuring a port. Never got an answer. At least we now have portlint that eliminates a lot of these issues. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000beb8980600bcd07a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jul 17, 2023 at 7:31=E2= =80=AFAM Mark Millard <marklmi@yaho= o.com> wrote:
From: Stefan Bethke <stb_at_lassitu.de<= /a>> wrote on
Date: Mon, 17 Jul 2023 07:04:11 UTC :

> every time I submit a PR to update a port I maintain, I get conflictin= g instructions about how to fill in the PR. This is really annoying, and so= me committers apparently feel they will not move forward in processing the = PR unless some bureaucratic bullshit is done.
>
> Can the ports team please provide a concise, definitive list on how a = maintainer is supposed to fill in a port update PR, so this nonsense stops?=

It might be useful to report the specific conflicting instructions
that you have received and to ask that the "definitive list" at l= east
resolve the specific conflicts. Otherwise the list might miss some
issues that you ran into. Right now there is no way for someone
generating a list to know up front if they have covered all your
example issues.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com
=C2=A0
This is an old issue. Many years ago I submitted a new port for the weir= d modem in an IBM ThinkPad. The committer who picked up the ticket insisted= that some scripting involved be rewritten in Perl. I did so and finally go= t the port committed. Less than two weeks later it was announced that perl = would be removed from the base system and that port scripts needed to be co= nverted to sh. While I applaud the removal of perl, I asked what the "= rules" were for structuring a port. Never got an answer. At least we n= ow have portlint that eliminates a lot of these issues.
--
Kevin Oberman, Part time kid herder and reti= red Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB9= 8AFA78E3B78C1694B318AB39EF1B055683
--000000000000beb8980600bcd07a--