From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: rav1e AV1 encoder
Date: Thu, 27 Feb 2020 12:26:13 -0500
Message-ID: <20200227172613.GB30619@jasmine.lan>
References: <20200225200823.GA31497@jasmine.lan>
 <DB522B9E-7343-4B56-A8FA-9E83CAB30AB8@asu.edu>
 <20200226041429.GA1225@jasmine.lan> <20200226070905.GD12956@E5400>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:50989)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <leo@famulari.name>) id 1j7MvS-0001HH-Rf
 for guix-devel@gnu.org; Thu, 27 Feb 2020 12:26:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <leo@famulari.name>) id 1j7MvR-0008Sh-LX
 for guix-devel@gnu.org; Thu, 27 Feb 2020 12:26:18 -0500
Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:47257)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <leo@famulari.name>) id 1j7MvR-0008Qy-Fh
 for guix-devel@gnu.org; Thu, 27 Feb 2020 12:26:17 -0500
Content-Disposition: inline
In-Reply-To: <20200226070905.GD12956@E5400>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org

I'm wondering if I can just push the crates as a single commit, after
inserting them alphabetically and fixing any cosmetic issues, and also
handling the semver-compatible package updates.

I know that we don't usually do this when adding packages to an existing
module. We do add packages en masse when creating a new module.

The reason I'm asking to make an exception to our policy of one package
or update per commit are that it will be a ton of work (several full
days at least) to add software that is already working fine on the
wip-rav1e branch.

I don't see what value this additional labor will give to Guix users,
including developers. At least, I don't think the value of individual
commits will outweigh the value of my labor in this case.

What do you all think?