From nobody Mon Apr 17 13:34:59 2023 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 4Q0SjH1q6Bz45tyW for ; Mon, 17 Apr 2023 13:35:15 +0000 (UTC) (envelope-from sstallion@gmail.com) Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 4Q0SjG67jqz3KnG; Mon, 17 Apr 2023 13:35:14 +0000 (UTC) (envelope-from sstallion@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2a8bbea12d7so11265391fa.3; Mon, 17 Apr 2023 06:35:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681738511; x=1684330511; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=LnVzCa/EjCRbwgmtMrEk6TvvixcuTA7ye0C49ZkRea0=; b=M6ZMjqwmLcgdY4DX6yJvtwH+7tL42BMSrOLtbdV7zTpe+WR2Qj5kDi0jqFu92qm2YU syNkHXFAOv4X7V2NIwpH0t/dnVw8y/RLMKL8MmfYbTg1K4osR63A2ijB6Xx7/E2twtFV z/MzdwzOZtEvqbrL3FjOrH6Cv1Dy6S/Y4XbUtCs8+ptCzw6QsaKbK+GaVmATUzZ3vbVG oDStkhK4bu6ez+v2FdW4pWPr4fi76W7+3N0pt8b67KawnGlxO5fVJPk0HQqI5UmfyDZ7 qsqfiJ9LsS+SfBoFV2xDgAqX9hXkv9gGWAg39nfVM0DxO4FGbJUnA/t5K9r1d5cmB4ly cVIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681738511; x=1684330511; h=content-transfer-encoding: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=LnVzCa/EjCRbwgmtMrEk6TvvixcuTA7ye0C49ZkRea0=; b=J78HvcIKBb5CBALb67wzZBUjTBNAJDFY+Adyj/oATWF7pdwwSb02qhIT8VA5V5pR7b ZJfoTptncN/wf3LEyA8oSmtxffpMmg4Nbja5Pcaohg3h1Sgv+ON6AGa45/Il3UEULt4V IRQKIly7okwXmrNwzWlAxDnln5eqzaWuggnw5JpYM4yKJsFt/pDfRecXyZXnVBZvLGs7 9efKe3szr1FXTYHQClVzSzmVi4DqCOk2ArZqDlDSYzOaNewcmELY9I53IuQ45OSnmxz/ LgLPuZ8n5F+YgCCvs+Az5Y4gryuVjb6594JcnNs+jIrAheqTAqfLW/kG4HljYY5xg1Rc 8rGw== X-Gm-Message-State: AAQBX9d7tDJceD6+VYH/KAobhHUT8xiNXZ95XScXq5qZ29yYvUANwUlL G14XKQHkVCcYPvztBsZCc1NJeMVY+IZAh4rmiTMJhh4a X-Google-Smtp-Source: AKy350b6F0BAPzFqeg01PIs9p8ro36gthva1w0pgsAQCCSKiDx2Lai4UzMbtOWVU9iCUwy7U/udnfI1R5WURviZBsjc= X-Received: by 2002:ac2:46d2:0:b0:4ed:c8ba:dfae with SMTP id p18-20020ac246d2000000b004edc8badfaemr375728lfo.5.1681738510546; Mon, 17 Apr 2023 06:35:10 -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: <57c33575-269f-6ae6-b0e0-db20a119899b@FreeBSD.org> In-Reply-To: <57c33575-269f-6ae6-b0e0-db20a119899b@FreeBSD.org> From: Steven Stallion Date: Mon, 17 Apr 2023 08:34:59 -0500 Message-ID: Subject: Re: New Port Submission Issue To: Matthew Seaman Cc: ports@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q0SjG67jqz3KnG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, Apr 17, 2023 at 2:32=E2=80=AFAM Matthew Seaman wrote: > I'll certainly do that. Give me a little while to run some tests: > should be able to get this into the ports today. This bug report wasn't > actually picked up by anyone with any agency to commit anything: the > auto assignment to freebsd-ports-bugs@ just causes e-mails to go to a > mailing list in the hope of attracting the attention of a committer. Ah, that makes sense! For what it's worth, I'm more than happy to act as maintainer for this package. > One thing on initial read through of the code: why are you limiting this > to FreeBSD 13 or above? I can't see anything obvious that would stop > this working on FreeBSD 12, but that could just be me being blind. No worries. This is essentially a drop-in replacement for update_motd, so it relies on /var/run/motd versus /etc/motd. As controversial as that change was, I didn't want to muddy the waters further. Cheers, Steve