From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6C8DF138334 for ; Fri, 13 Sep 2019 15:50:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1F1C0E0C83; Fri, 13 Sep 2019 15:50:25 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C6B70E0BD8 for ; Fri, 13 Sep 2019 15:50:24 +0000 (UTC) Received: from whubbs1.gaikai.biz (unknown [100.42.103.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: williamh) by smtp.gentoo.org (Postfix) with ESMTPSA id 9621834B11A; Fri, 13 Sep 2019 15:50:22 +0000 (UTC) Received: (nullmailer pid 3407 invoked by uid 1000); Fri, 13 Sep 2019 15:50:04 -0000 From: William Hubbs To: gentoo-dev@lists.gentoo.org Cc: William Hubbs Subject: [gentoo-dev] [PATCH 0/1] Introduce new eclass to handle go modules (round 2) Date: Fri, 13 Sep 2019 10:49:50 -0500 Message-Id: <20190913154951.3360-1-williamh@gentoo.org> X-Mailer: git-send-email 2.21.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 9571fc9d-84cd-4041-a210-692a9fc74449 X-Archives-Hash: 7a1ca3f5b0dadb55fe2420be3227dd32 This version shows both methods of handling vendor tarballs mentioned on the previous thread. The first method, while it removes the src_prepare function, forces a maintainer to re-pack a new vendor tarball for every release. The second method allows a maintainer to decide when a new vendor tarball is needed. An ebuild using this would look the same as in the previous round, so I'm not including any examples. William Hubbs (1): go-module.eclass: introduce new eclass to handle go modules eclass/go-module.eclass | 100 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 eclass/go-module.eclass -- 2.21.0