From: Martin Becze <mjbecze@riseup.net>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-patches <guix-patches-bounces+mjbecze=riseup.net@gnu.org>,
38640@debbugs.gnu.org
Subject: [bug#38640] [PATCH] Add ripgrep and many rust dependencies
Date: Wed, 18 Dec 2019 08:32:57 -0800 [thread overview]
Message-ID: <1e0988ded5edd72803b0660004614db0@riseup.net> (raw)
In-Reply-To: <CAKf5CqX-TrMcazUWGC0qPSp7PkpQfW2uKHkMoDbXUG_gxg4A=g@mail.gmail.com>
On 2019-12-17 17:10, John Soo wrote:
> HI everyone,
>
> I did some work on your review and have a couple questions before I
> submit the next patchset.
>
> * My questions for Martin:
>
>> I'm trying to convince everyone to leave in the crago-inputs
>> dependencies and add a "#:skip-build? #t" to the build arguments for
> all
>> source pakages. That way we don't have to specify the transient
>> dependencies at the top level package.
>
> I like this idea. I think I will do it if you don't mind. It's either
> that or add hidden? #t to the properties, right?
> Whether to add #skip-build? #t to the packages is the last piece of
> review I need to fixup.
So the ` hidden? #t ` also hides the package from (find-packages*)
functions in (gnu packages). I actully want to be able to search for and
use rust libraries with guix, so I prefer not to hide them.
next prev parent reply other threads:[~2019-12-18 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 19:08 [bug#38640] [PATCH] Add ripgrep and many rust dependencies John Soo
2019-12-16 21:04 ` Nicolò Balzarotti
2019-12-16 22:53 ` Martin Becze
2019-12-17 17:10 ` John Soo
2019-12-18 16:32 ` Martin Becze [this message]
2019-12-18 16:42 ` John Soo
2019-12-18 16:49 ` Martin Becze
2019-12-18 16:50 ` John Soo
2019-12-19 7:25 ` Efraim Flashner
2019-12-20 17:44 ` John Soo
2019-12-21 4:18 ` John Soo
2019-12-31 8:57 ` Efraim Flashner
2019-12-31 15:49 ` John Soo
2020-01-02 18:20 ` bug#38640: " Efraim Flashner
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=1e0988ded5edd72803b0660004614db0@riseup.net \
--to=mjbecze@riseup.net \
--cc=38640@debbugs.gnu.org \
--cc=guix-patches-bounces+mjbecze=riseup.net@gnu.org \
--cc=jsoo1@asu.edu \
/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).