From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id GODTFSe8q2UK2wAA62LTzQ:P1 (envelope-from ) for ; Sat, 20 Jan 2024 13:27:19 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id GODTFSe8q2UK2wAA62LTzQ (envelope-from ) for ; Sat, 20 Jan 2024 13:27:19 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=hoDlg8st; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1705753639; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=7YP8zgiNWVKY85EgDkEoSvoFXycmlDGsh2EfjHD/S88=; b=DxAIz9T7FBUwoxW8ph5tB1/ROt7CJJcBtT1phQnwsHjjMUDh38hZtmLhOFlKQNOee8AFGX CXwu5Lr0TMROa1WFNCE+XYpsi1BXYKIoxnYQSL7v8cFC88nQNPRzDalcKWmDUiGGBtKAaX 5ngyUgDeJpzusBuFFcZ66nhTOaSm9ChDqmwuyy7jJXO5GKuyWp4o7AUxB34Mox0LRtO4+W z5kVHvBks6gZbLmX1UWYq35/W90zwTiTYuogGKcjRs1qj8cB0j5d0mj0VelcLYqs5nBU5s v6ST49TITonbGuQlxuXghtfRqTAX/o7lNJ+jPy+tDpFcaE24AfdXHtyAowh3lg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=hoDlg8st; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1705753639; a=rsa-sha256; cv=none; b=NynBrnLAZ6wedxyTpComx7Mxhtllb2UAl+SF/5i/scTYs7hJnJCGBDkH94ob5nem14ZJvw O4/GVo7griDbLPr3JHyBvLuLbWT1WeZ0NzELYyCV+xZK73tFLu2xFGktwTSlHw7yhLgyHs KdZ8YoUgpriiY2RNX891N190GheP/lM8o1CKWRhl5ayAkDtShGgOWniFWmUizl6j3U/emA +vSPYNoJDKTpueThAFVAfSWkVZcRrwt0xbph4WpPFH6MDl+zlP+mNaRZndAmookZc4CsnH m5b86UZU9Or+Z5lYKQS7F5P2Xhsab/BBT2rqpjoPICAKZ1aec4/rieqF0G39DA== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 276606A993 for ; Sat, 20 Jan 2024 13:27:18 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rRAQp-0008OC-A3; Sat, 20 Jan 2024 07:26:39 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rRAQn-0008O2-Ht for guix-devel@gnu.org; Sat, 20 Jan 2024 07:26:37 -0500 Received: from mail-lf1-x12f.google.com ([2a00:1450:4864:20::12f]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rRAQl-0001v1-Sz for guix-devel@gnu.org; Sat, 20 Jan 2024 07:26:37 -0500 Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-50e835800adso1906461e87.0 for ; Sat, 20 Jan 2024 04:26:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705753594; x=1706358394; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7YP8zgiNWVKY85EgDkEoSvoFXycmlDGsh2EfjHD/S88=; b=hoDlg8stPXI0GM9+s5GSds8dJcpBNcAD3IrYejMkYxD9eyFUgxdDubczk0UNl66f7K ZwL9jB5u2+VqZPfj0UI0YUiJTaMRwFWMLuvNRsZoS3z0E8O+emIX/umajbhyyK6STEXO WSczOIxiyBd4/IhpccdcoyyioqLBTncHy2yRtOGMr5XE04oY0cQq5TOguIpH0AGifspZ DapgW3BJealmrFVvEOFPLHFg985AZnC0XUlBCK6wf8voo4bhnkeEOzNABhteqZynu2XV 3/HNYzCcsGdCxmMi9EvOWMI1rqm6NQ0mbux1Lx4855otbPAEcdTnStXlXyKxuG1FIIEP eIyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705753594; x=1706358394; 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=7YP8zgiNWVKY85EgDkEoSvoFXycmlDGsh2EfjHD/S88=; b=wODc1YH+iVWMafyDVZCKw83K/tv3zHgzDSOOmJ6arX5qOD/M4SsTlPKUFEyQVQGKTl UDSxBc75GPR1ckz+DM0sjWSgFSg4JzBPhpiCj3S38DvF0xE0WQy1XircbscMgtuB0KxW 6nFozTc2CwaAe16lSvWY7TK2Xw+4YqjwVaS9Rm2sPlOGjrzHIUBVOT+4aPoK8CvwQ3gA 8LMR7eUKTKBS4ps1fTjjK6EdrLFJE+TJx5YzjjalzAK8FuUg7yTdCf/0uEsDAS034ZZ8 MNHtAdoSLIXFfoS1Jz2b/CGgdMS7em/UHVTe5Bit6rmHf8K7tnSRgKkJ+zlqOenaMFjr y4OA== X-Gm-Message-State: AOJu0YzL+kKbDHnlYu3j0bDjUSQ0QEubdHwxxnCJyPTH26viszCTkXsK ZwI4SQAOefpZks+8VCXFWv/id+Jxl8ksA/tUdB/cvnkyIAqethqupwch5uMvyk2GLrM8srWUWj+ kVIusIHIrFq6Rz33oey3LT8KR8gTUC5A9Cas= X-Google-Smtp-Source: AGHT+IHDaWVsYNlDOEqwwM30OuzK1wgvwdp2qdltddzFZi90oTgseQbzf8KGU3gl5HZnZHzOU3aGSLREWhtflT9Tcmg= X-Received: by 2002:ac2:464d:0:b0:50e:7324:cd41 with SMTP id s13-20020ac2464d000000b0050e7324cd41mr309449lfo.157.1705753593571; Sat, 20 Jan 2024 04:26:33 -0800 (PST) MIME-Version: 1.0 References: <87h6mrinnu.fsf@wmeyer.eu> <5d4663d5-8f33-0f2c-0a37-4d9946b04c27@mutix.org> In-Reply-To: <5d4663d5-8f33-0f2c-0a37-4d9946b04c27@mutix.org> From: Sharlatan Hellseher Date: Sat, 20 Jan 2024 12:26:22 +0000 Message-ID: Subject: Re: Golang mudules to follow common grouping To: "Christina O'Donnell" Cc: guix-devel Content-Type: multipart/alternative; boundary="00000000000004eda0060f5fb5f5" Received-SPF: pass client-ip=2a00:1450:4864:20::12f; envelope-from=sharlatanus@gmail.com; helo=mail-lf1-x12f.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -9.84 X-Migadu-Queue-Id: 276606A993 X-Spam-Score: -9.84 X-Migadu-Scanner: mx11.migadu.com X-TUID: L5DQ0ahz2R9I --00000000000004eda0060f5fb5f5 Content-Type: text/plain; charset="UTF-8" Hi Christina, > Would it be more organized if they was just one order: either > in alphabetical order or grouped by function? My suggestion > would be to use the file split to group by function and then sort > each file alphabetically. Do you know how it is arranged for other > languages? I've added comments in commentary section in the top of the file asking to keep packages alphabetically sorted seen in julia-xyz.scm as well. python-*.scm ordered semi random grouped closer to package purpose which require more thinking where to put a new one : -) > Another question I have: Is there any tooling that can help big package > migrations like this go faster? Eg. a script to split one big diff into > individual package moves with appropriate change-log entries. Good point her, I did manual split, with Emacs keyboard macros, magit history scan for copyright lines and manual check where package was used to include new module name. The split into golang-crypto is in review now and there would be 2 more common grouping: golang-compression and golang-build (or golang-extension). Rest packages which are hard to determine a group wound go to generic golang-xyz sorted alphabetically. Let me know your tooling which you familiar with I might think about some sort of automation. Thanks, Oleg --00000000000004eda0060f5fb5f5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Christina,

> Would it be more organized if they was just one order:= either
> in alphabetical ord= er or grouped by function? My suggestion
> would be to use the file split to group by function and then = sort
> each file alphabetical= ly. Do you know how it is arranged for other
> languages?

<= div dir=3D"auto">I've added comments in commentary section in the top o= f the file
asking to keep packages alphabetically so= rted seen in=C2=A0
julia-xyz.scm as well. python-*.s= cm ordered semi random grouped
closer to package pur= pose which require more thinking where to put a new one : -)

> Another questi= on I have: Is there any tooling that can help big package
> migrations like this go faster? Eg. a script to split one big di= ff into
> individual package moves with appropria= te change-log entries.

G= ood point her, I did manual split, with Emacs keyboard macros,
magit history scan for copyright lines and manual check where
package was used to include new module name.

The split into golang-crypto is i= n review now and there would be 2 more
common groupi= ng: golang-compression and golang-build (or
golang-e= xtension). Rest packages which are hard to determine a
group wound go to generic golang-xyz sorted alphabetically.

Let me know your tooling which you f= amiliar with I might think
about some sort of automa= tion.

Thanks,
Oleg

=
--00000000000004eda0060f5fb5f5--