From debbugs-submit-bounces@debbugs.gnu.org Sat Apr 16 13:39:57 2022 Received: (at 53765) by debbugs.gnu.org; 16 Apr 2022 17:39:57 +0000 Received: from localhost ([127.0.0.1]:34265 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nfmOr-0002BA-7F for submit@debbugs.gnu.org; Sat, 16 Apr 2022 13:39:57 -0400 Received: from mout-p-102.mailbox.org ([80.241.56.152]:41311) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nfmOp-0002Ax-7o for 53765@debbugs.gnu.org; Sat, 16 Apr 2022 13:39:55 -0400 Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:105:465:1:4:0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4KggSN2kTzz9sTC; Sat, 16 Apr 2022 19:39:48 +0200 (CEST) From: Reily Siegel DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=reilysiegel.com; s=MBO0001; t=1650130786; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=t8agxo5hVyaE+2OIQ2hgNzQFyKS6F0KA4/JBMfeyqEM=; b=iVJ5xqbobpdDc1I70DfLYwT6AmtJq13Ofg8BXm833dPdgXSVowHGTNRgcOoq3vun3ozGJ+ SeSEJR7aLdUcjSBHA+bWPU3R6Yv+m+MDfy/dxWu92LWjmARUjFh1C9wnBuZPBVTwcRQt5x 6SH0Yoe5CADXnmjvp7dGrhwqCbbAFDuCOuJIDMl1Zyb6IU1lP5a5bi0tPatMxcyTaxQrId ieSJWB8eqi15xwIUgMWOzJ713DtsH4X/Ovf5FCj70MUIX2hHsBr2VQAeUL1i4wHc1ZsmO+ uLPQ0S+WupwrLOUjtZw9FCnX8d5duny5cGSVnc/+HGPSIYbD2tq8z841SxRVUA== To: Maxime Devos , 53765@debbugs.gnu.org Subject: Re: [bug#53765] V3 Patches In-Reply-To: References: <87zgkmlad7.fsf@reilysiegel.com> <242fe49e1d65869b2eb72f64041e3e08ef57702e.camel@telenet.be> Date: Sat, 16 Apr 2022 19:39:40 +0200 Message-ID: <87tuatgc6b.fsf@reilysiegel.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 53765 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Maxime Devos writes: > Apparently the aws things aren't very useful and they can be patched > out? That is exactly what I did with the first patch I sent for clojure-tools, which was accepted. However, this causes the tools to print warnings on startup, as well as removing the feature of accessing S3 repositories. I suppose these warnings could be patched out, given that the work to packages the dependencies has already been done, I see no reason to not resolve the issue, given that the links you sent me to Debian seem to believe all of these dependencies fit the requirements of free software. Elana Hashman writes: > These deps are all open source as far as I can tell, but given that it's > a lot of work to enable commercial/proprietary development I personally > do not want to spend volunteer time on it. I would not block someone > from volunteering to work on this, particularly with a commercial > sponsor, but I don't think it'd be a great use of time for e.g. a GSoC > student. To be clear, I am not working on these patches on behalf of a commercial sponsor, but because it didn't feel right to me to package the library with significant functionality missing, especially not in the long term. Maxime Devos writes: > Well, the (original?) source (the JSON files) seems to be free software, > but if there is no free compiler for the source (and worse, there is > only a single compiler and it can only be used by a single entity > (cognitect)), wouldn't that make the software, from a practical > perspective, non-free? It is my personal opinion that this is not a compilation, but a translation. All this "compiler" is doing, as far as I can tell, is reading the JSON source, and outputting an equivalent source in EDN format. This seems completely fine to me, as nothing then prevents the user of this library from editing the EDN source, which is equivalent to the JSON source. In fact, since this is a Clojure library, the EDN source is probably the preferred form for editing for people who are likely to use it. > gnu.org words this in more detail at > . This seems to focus on instances when some important software freedom is lost. I can't see anything that would give guidance on what to do when all freedoms are preserved, as they seem to be here. -- Reily Siegel