Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: srcpkgs/: clean up lots of Go packages
Date: Fri, 19 Feb 2021 16:07:45 +0100	[thread overview]
Message-ID: <20210219150745.P_3F0inBadvZzU_372-DM7RH350LnPrHjFNrQ5nIVKo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28863@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 699 bytes --]

There's a merged pull request on the void-packages repository

srcpkgs/: clean up lots of Go packages
https://github.com/void-linux/void-packages/pull/28863

Description:
Depending on git for building can sometimes happen due to issue #27690,
where instead of using the unpacked tarball, Go clones the package's
repository itself, since the tarball we provided doesn't contain the
go_import_path we pass to it in the command line.

Since we should require as few dependencies as possible, and this
measure can help catch issues of building the wrong version of a Go
package, we remove git from hostmakedepends where possible.

I'm still pulling in packages that do this, will take a while.

      parent reply	other threads:[~2021-02-19 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 22:20 [PR PATCH] [WIP] srcpkgs/: most Go packages shouldn't have git in hostmakedepends ericonr
2021-02-19  2:27 ` [PR PATCH] [Updated] " ericonr
2021-02-19  3:34 ` ericonr
2021-02-19  4:32 ` ericonr
2021-02-19 15:07 ` [PR PATCH] [Updated] srcpkgs/: clean up lots of Go packages ericonr
2021-02-19 15:07 ` ericonr [this message]

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=20210219150745.P_3F0inBadvZzU_372-DM7RH350LnPrHjFNrQ5nIVKo@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).