unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Ade Malsasa Akbar <malsasa@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: [ASK] Failed Installing GTK+ Software Development Kit on GuixSD
Date: Mon, 06 Dec 2021 16:08:57 +0000	[thread overview]
Message-ID: <Mzzmhp46Om75j-dWszX38tUj2pf6Cm6mHCYQJZHYMd1DQfDziK-K1_ieT83Has2fQRHqeiBYq6i2cT27bt6CcKP9lMjOV51cGUsKlwh2GgM=@protonmail.com> (raw)
In-Reply-To: <a8dc887f-5410-a4ea-368b-431eab0d8899@disroot.org>


[-- Attachment #1.1: Type: text/plain, Size: 714 bytes --]

On Monday, December 6th, 2021 at 2:03 AM, Ade Malsasa Akbar via <help-guix@gnu.org> wrote:

> Hello, GNU Community!

Hi :) 


What you describe is a known reality (see https://issues.guix.gnu.org/37940). As Mark indicates in that report, you can work around the issue by using manifests.

For instance, to work on your Application project, you can do more or less something like this:

$ cd my-app
$ guix shell -m manifest.scm
$ RUN_YOUR_APP

That way Guix will create an augmented environment with all the packages listed in the manifest.scm file, where you can develop your application.

I have a real example if you would like to try: https://gitlab.com/luis-felipe/geteka

Hope that helps,

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

      reply	other threads:[~2021-12-06 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  2:03 [ASK] Failed Installing GTK+ Software Development Kit on GuixSD Ade Malsasa Akbar via
2021-12-06 16:08 ` Luis Felipe [this message]

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='Mzzmhp46Om75j-dWszX38tUj2pf6Cm6mHCYQJZHYMd1DQfDziK-K1_ieT83Has2fQRHqeiBYq6i2cT27bt6CcKP9lMjOV51cGUsKlwh2GgM=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=help-guix@gnu.org \
    --cc=malsasa@disroot.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).