all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Thaddäus Töppen" <thaddaeus.toeppen@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Problem using multiple manifest files
Date: Sat, 13 Oct 2018 06:08:05 +0200	[thread overview]
Message-ID: <878t32o5ei.fsf@elephly.net> (raw)
In-Reply-To: <CA+uB_kWYmonv+_0QJd8urWYvUDfqvRH4eJ8hW3RQYfReGvnjeQ@mail.gmail.com>


Hello Thaddäus,

> Hello Guix community,

welcome!

> When I use "guix package -m emacs.scm" it installs the packages and they
> are available. When I then install the next manifest file's packages, the
> "emacs.scm" packages are no longer available – the links in
> "~/.guix-profile/bin" have been removed.
>
> Am I correct in assuming, that only one manifest file can be installed at a
> time, thus all package definitions have to be in one file (or at least
> imported into a main-package-file)?

Yes, this is correct.  A manifest declares the contents of a single
profile.  By passing a manifest file to “guix package -m” you tell it to
only install the declared packages and remove everything else.

You can instantiate different manifest to different profiles by also
passing “-p /path/to/other/profile”.  You can combine them in a session
by source-ing each of the profiles’ “etc/profile” files.

> Also: If I have more (beginner) questions, should I drop them all in one
> mail or create separate threads

It’s better to send separate emails.

--
Ricardo

  reply	other threads:[~2018-10-13  4:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 21:50 Problem using multiple manifest files Thaddäus Töppen
2018-10-13  4:08 ` Ricardo Wurmus [this message]
2018-10-13 19:52 ` Mikhail Kryshen
2018-10-15 12:10   ` Ludovic Courtès
2018-10-20 19:53   ` Chris Marusich
2018-10-22 18:39     ` Mikhail Kryshen
2018-10-23  8:07       ` Chris Marusich

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=878t32o5ei.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=thaddaeus.toeppen@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.