From nobody Wed Mar 16 13:56:21 2022 X-Original-To: freebsd-arch@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 B40441A2F1E0 for ; Wed, 16 Mar 2022 13:56:41 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) (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 4KJWzD3t0Hz3Fcv; Wed, 16 Mar 2022 13:56:40 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f52.google.com with SMTP id h63so2355262iof.12; Wed, 16 Mar 2022 06:56:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=t8nj0KQo7LfQxIyd2vYrElyCkFcoLv2kg0dvdCY+8hM=; b=ppujAq7H65sPKP2IaaQkLMV3iPaywj8HG34HINoqxtaZ6BqUrvXKvf5PNKh4HlsWeS LiXOx+aCrsr2Dg0wLF523uZxhKoBNcf/m28NgM7T5ZTJINafWuzd72KvVKgHMQv7qJ5i 8y/phojztMadEf93ll1Z9oecQ5/eo8CkaC8pXL/uwyIbihzZcOio6ejuCL6VSxZTArt3 k1SWkF590OaSns12otE/evqPFXEQB+O1Xui5CBjFeMngNASBhUxKwf70eTtuD+xc1000 R0IzLr4d8goXXyeIXWsaOuXWFUwft5oi4LOMjGRitFj4Hxkgr/bOCuh8ZREMq5hl2Gqq NLmA== X-Gm-Message-State: AOAM532jKzHr8zZTaCRzPRexs2Vz5YHhw1Ski3Cr5vZlwm2uXG7h8N3O FY504WuNQ6llcZBOaBhUBPKNMNe083iOBMSFDIorzkc7 X-Google-Smtp-Source: ABdhPJws2fzDYap4kUpiJtH5qTaRPnOqFNA0CmR90Sl/xHvvQ0u4K73gZsCdpWzSXhYP+ry+pqonMbPSce5o2IO0NNc= X-Received: by 2002:a02:a081:0:b0:317:b141:29ca with SMTP id g1-20020a02a081000000b00317b14129camr25039739jah.275.1647438994340; Wed, 16 Mar 2022 06:56:34 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Wed, 16 Mar 2022 09:56:21 -0400 Message-ID: Subject: Re: LGPL code in /usr/tests? To: Warner Losh Cc: Alan Somers , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4KJWzD3t0Hz3Fcv X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.52 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-0.29 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RCVD_TLS_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_SPAM_LONG(0.48)[0.476]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.52:from]; NEURAL_HAM_MEDIUM(-0.77)[-0.771]; MLMMJ_DEST(0.00)[freebsd-arch]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.52:from]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Mon, 3 Jan 2022 at 13:06, Warner Losh wrote: > > All of that is covered by our existing practice of storing LGPL code in s= rc/gnu/lib. We cover it in the handbook already. Since it is publicly avail= able forever, storing it there will have no impact that's any different tha= n libdialog or libreadline has has in the past. gnu/ isn't the right place - build infrastructure exists in src/gnu/lib, but the GPL/LGPL source itself lives in contrib/diff and contrib/dialog. Those two are the only remaining GPL/LGPL userland components, and both are on the way out. I suspect the right place for the proposed library's build infrastructure is beside the tests that will use it.