From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: William Hubbs <williamh@gentoo.org>
Subject: [gentoo-dev] [PATCH 0/2] introduce new eclasses to handle go modules
Date: Sat, 21 Sep 2019 17:10:30 -0500 [thread overview]
Message-ID: <20190921221032.10777-1-williamh@gentoo.org> (raw)
All,
after some further discussion, I decided to split the eclass.
The go-module eclass in this thread would be used if your upstream
project vendors its dependencies and the go-module-vendor eclass would
be used otherwise.
Thanks,
William
William Hubbs (2):
go-module.eclass: new eclass for go modules
go-module-vendor.eclass: new eclass for go modules that do not vendor
eclass/go-module-vendor.eclass | 133 +++++++++++++++++++++++++++++++++
eclass/go-module.eclass | 79 ++++++++++++++++++++
2 files changed, 212 insertions(+)
create mode 100644 eclass/go-module-vendor.eclass
create mode 100644 eclass/go-module.eclass
--
2.21.0
next reply other threads:[~2019-09-21 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 22:10 William Hubbs [this message]
2019-09-21 22:10 ` [gentoo-dev] [PATCH 1/2] go-module.eclass: new eclass for go modules William Hubbs
2019-09-21 22:10 ` [gentoo-dev] [PATCH 2/2] go-module-vendor.eclass: new eclass for go modules that do not vendor William Hubbs
2019-09-22 6:02 ` Michał Górny
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=20190921221032.10777-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