From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: William Hubbs <williamh@gentoo.org>
Subject: [gentoo-dev] [PATCH 0/1] Introduce new eclass to handle go modules (round 2)
Date: Fri, 13 Sep 2019 10:49:50 -0500 [thread overview]
Message-ID: <20190913154951.3360-1-williamh@gentoo.org> (raw)
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
next reply other threads:[~2019-09-13 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 15:49 William Hubbs [this message]
2019-09-13 15:49 ` [gentoo-dev] [PATCH 1/1] go-module.eclass: introduce new eclass to handle go modules William Hubbs
2019-09-13 15:58 ` William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190913154951.3360-1-williamh@gentoo.org \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox