From: "Ludovic Courtès" <ludo@gnu.org>
To: Sarthak Shah <shahsarthakw@gmail.com>
Cc: "Pjotr Prins" <pjotr.public12@thebird.nl>,
"Gábor Boskovits" <gboskovits@gmail.com>,
"Guix Devel" <guix-devel@gnu.org>
Subject: Re: GSoC news
Date: Sun, 07 May 2023 23:36:44 +0200 [thread overview]
Message-ID: <87o7mvg6xf.fsf@gnu.org> (raw)
In-Reply-To: <CADBZEVnjqNG8Tv86JLUnNob6dAiE06Z+NLzVHAwtvvxpsLEFfw@mail.gmail.com> (Sarthak Shah's message of "Fri, 5 May 2023 03:35:43 +0530")
Hi Sarthak,
Sarthak Shah <shahsarthakw@gmail.com> skribis:
> Thanks for having me onboard!
> I hope that my project will prove useful to Guix.
Welcome on board!! Really happy to have you here.
> My project is about implementing Parameterized Packages, which will add
> optional Gentoo USE flag-like functionality to Guix packages. This will not
> only help reduce package size but also provide users with greater choice
> with how they'd like to use their packages. I believe that this should also
> help somewhat relieve the issue of the denseness of guix's dependency
> graphs, which was recently being discussed here on the mailing list.
>
> Due to the nature of this project, it will involve taking a lot of inputs
> from the Guix community, and thus you can expect a regular thread or two
> with updates/feature discussions on this topic in the mailing list.
Indeed! Like you write, there’s a lot of potential with parameterized
packages, and I’m confident you can make great strides in this area.
Oh, and ‘--with-configure-flags’ is already a success among HPC people
I’ve talked to! :-)
Cheers,
Ludo’.
next prev parent reply other threads:[~2023-05-07 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 19:22 GSoC news Gábor Boskovits
2023-05-04 19:57 ` Pjotr Prins
2023-05-04 22:05 ` Sarthak Shah
2023-05-05 13:55 ` Simon Tournier
2023-05-07 21:36 ` Ludovic Courtès [this message]
2023-05-08 2:02 ` Maxim Cournoyer
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=87o7mvg6xf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gboskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
--cc=shahsarthakw@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.