From: Ricardo Wurmus <rekado@elephly.net>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: help-guix@gnu.org
Subject: Re: guix environment ad-hoc manifests
Date: Thu, 22 Oct 2020 17:16:21 +0200 [thread overview]
Message-ID: <87tuumthoa.fsf@elephly.net> (raw)
In-Reply-To: <20201022163832.3618d9d9@pantherx.org>
Reza Alizadeh Majd <r.majd@pantherx.org> writes:
> On Thu, 22 Oct 2020 13:53:10 +0200
> Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> Reza Alizadeh Majd <r.majd@pantherx.org> writes:
>>
>> > it would also be great to be able to pass list of ad-hoc packages,
>> > using a manifest file, something like --ad-hoc-manifest switch. or
>> > maybe there is such option already available that I missed.
>>
>> What would that look like? Just a file containing package names?
>>
>
> yes, a possible use-case would be to provide a development
> environment for a software which is not packaged yet. during
> development phase, we could easily update this manifest file and
> include third-parties we need to use.
But isn’t this exactly what you can use a manifest file for already?
“guix environment” not only accepts a file that describes a package, but
also a manifest.
--
Ricardo
next prev parent reply other threads:[~2020-10-22 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 9:09 guix environment ad-hoc manifests Reza Alizadeh Majd
2020-10-22 11:53 ` Ricardo Wurmus
2020-10-22 13:08 ` Reza Alizadeh Majd
2020-10-22 15:16 ` Ricardo Wurmus [this message]
2020-10-24 7:35 ` Reza Alizadeh Majd
2020-10-22 16:22 ` zimoun
2020-10-24 7:52 ` Reza Alizadeh Majd
[not found] <mailman.85.1603382448.9180.help-guix@gnu.org>
2020-10-22 20:05 ` Zelphir Kaltstahl
2020-10-22 20:17 ` zimoun
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=87tuumthoa.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=r.majd@pantherx.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 read-only IMAP folder(s) and NNTP newsgroup(s).