unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Reza Alizadeh Majd <r.majd@pantherx.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: guix environment ad-hoc manifests
Date: Sat, 24 Oct 2020 11:05:41 +0330	[thread overview]
Message-ID: <20201024110541.2a481783@pantherx.org> (raw)
In-Reply-To: <87tuumthoa.fsf@elephly.net>

On Thu, 22 Oct 2020 17:16:21 +0200
Ricardo Wurmus <rekado@elephly.net> wrote:

> > 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.
> 

Thank you for your response, there is just a point that I don't
understand.

- when we add a package to environment, all of package inputs will be
added to the environment.
- using --ad-hoc switch, package itself will be present in environment.

now I want to know add a series of packages using --manifest, add them
directly to the environment (like --ad-hoc), or add inputs for each
package to environment?  


Thanks
Reza

-- 
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/


  reply	other threads:[~2020-10-24  7:36 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
2020-10-24  7:35       ` Reza Alizadeh Majd [this message]
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=20201024110541.2a481783@pantherx.org \
    --to=r.majd@pantherx.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).