unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Cairn" <cairn@pm.me>
Cc: 57326@debbugs.gnu.org
Subject: [bug#57326] [PATCH 0/7] gnu: Add hydroxide.
Date: Sat, 10 Sep 2022 08:51:53 +0100	[thread overview]
Message-ID: <CMSK3L1P0NK4.1B4K143ECDNEF@guix-aspire> (raw)
In-Reply-To: <nez--72Aa1EGVNVHLSjIR6-s4_NDJH0HsBI8_Vi22aUc1HqTs4dlUJNgrOI0TFwbnvSUAtqvDeC9Wzoiks-RP0ZF8Tj5uMHSZlLYSpJWrL8=@pm.me>

Hi Cairn, sorry for the delay!

On Mon Aug 29, 2022 at 1:23 AM BST, Cairn wrote:
> Could you explain why this is necessary? It doesn't seem to require it to build or run, at least for me. And do you mean for every package, or just this particular case?

This is because Go libraries (though not programs) are stored as source code in the
output directory and later fetched and rebuilt when you build one of their dependents.

So, if go-foo requires go-bar requires go-baz, go-bar will be rebuilt whenever go-foo
is built. But if go-bar doesn't use propagated-inputs, the go-baz dependency of go-bar
will be absent from the build environment.

In this case, we're talking about go-github-com-emersion-go-bcrypt depending on the
go-golang-org-x-crypto package; since x-crypto is probably already propagated in the
hydroxide build environment, as it's quite a common package, you don't see any issues;
but were you to write a package that solely depended on go-bcrypt, it'd fail to build
because x-crypto wasn't in the build environment.

> Sounds fine to me. Also, I'm just borrowing the description from the GitHub page. If you do think it should be changed though, what would be a good change?

IMO, the use of `vCard' as the object of that phrase without any further explanation
of what `vCard' is sounds a wee bit strange, so maybe something like:

  parse and format the vCard file format

Assuming vCard is a file format.

    -- (




  parent reply	other threads:[~2022-09-10  7:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 19:33 [bug#57326] [PATCH 0/7] gnu: Add hydroxide Cairn via Guix-patches via
2022-08-21 23:42 ` [bug#57326] [PATCH 1/7] gnu: go-github-com-emersion-go-imap: Update to 1.2.1 Cairn via Guix-patches via
2022-08-28  7:41   ` ( via Guix-patches via
2022-08-21 23:42 ` [bug#57326] [PATCH 2/7] gnu: Add go-github-com-boltdb-bolt Cairn via Guix-patches via
2022-08-28  7:44   ` ( via Guix-patches via
2022-08-21 23:43 ` [bug#57326] [PATCH 3/7] gnu: Add go-github-com-emersion-go-bcrypt Cairn via Guix-patches via
2022-08-28  7:47   ` ( via Guix-patches via
2022-08-21 23:43 ` [bug#57326] [PATCH 4/7] gnu: Add go-github-com-emersion-go-mbox Cairn via Guix-patches via
2022-08-28  7:51   ` ( via Guix-patches via
2022-08-21 23:43 ` [bug#57326] [PATCH 5/7] gnu: Add go-github-com-emersion-go-vcard Cairn via Guix-patches via
2022-08-28  7:52   ` ( via Guix-patches via
2022-08-21 23:44 ` [bug#57326] [PATCH 6/7] gnu: Add go-github-com-emersion-go-webdav Cairn via Guix-patches via
2022-08-28  7:53   ` ( via Guix-patches via
2022-08-21 23:44 ` [bug#57326] [PATCH 7/7] gnu: Add hydroxide Cairn via Guix-patches via
2022-08-28  7:56   ` ( via Guix-patches via
2022-08-28  7:59   ` ( via Guix-patches via
2022-08-29  0:23     ` [bug#57326] [PATCH 0/7] " Cairn via Guix-patches via
2022-09-08 14:18       ` Olivier Dion via Guix-patches via
2022-09-10  9:39         ` Cairn via Guix-patches via
2022-09-10  7:51       ` ( via Guix-patches via [this message]
2022-09-10  9:32         ` Cairn via Guix-patches via
2022-08-28  1:05 ` Olivier Dion via Guix-patches via
2022-08-28  1:13   ` Cairn via Guix-patches via
2022-10-14 23:04 ` [bug#57326] Delays Cairn via Guix-patches via
2022-11-27 16:31 ` [bug#57326] (No Subject) Tyler Wolf via Guix-patches via
2022-11-27 16:36   ` ( via Guix-patches via
2023-01-06 19:49     ` Olivier Dion via Guix-patches via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CMSK3L1P0NK4.1B4K143ECDNEF@guix-aspire \
    --to=guix-patches@gnu.org \
    --cc=57326@debbugs.gnu.org \
    --cc=cairn@pm.me \
    --cc=paren@disroot.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).