all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Martin Castillo <castilma@uni-bremen.de>
To: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: creating a manifest
Date: Sat, 18 Mar 2023 12:48:49 +0100	[thread overview]
Message-ID: <2e5ab249-c759-7fce-58e2-ebeeac7fbacc@uni-bremen.de> (raw)
In-Reply-To: <a5cf651c-3bc5-d4ac-420c-c6b5e23289fd@posteo.de>

Hi,

Am 18.03.23 um 11:50 schrieb Gottfried:
 > Hi,
 >
 > I wanted to create a manifest for music,
 > 
.........................................................................................
 > my "musik.scm":
 >
 > ;; Manifest Musik Programme
 > (use-modules (gnu packages version-control))If this is the whole 
file, this use-modules is unnecessary.

 >
 > (specifications->manifest ’("Musescore '--with-branch=musescore=v3.6.2"
 > "Ardour" "Audacious" "Audacity" "OBS Studio" "VLC Media Player"))
The cryptic error message is about an unexpected character, namely
(specifications->manifest ’  <- this backtick
It needs to be the ascii >'<.

If you fix that, you get new errors.

If you read the info page "Writing manifests", you'll see you have to 
use the package names like when using `guix package -i musescore` etc. 
when using specifications->manifest.
guix search musescore would show you under `name:`, that the musescore 
package (in guix) is named in lowercase. Also OBS Studio is called obs, 
vlc is called vlc etc.

But you can not add cmdline args like --with-branch.

For that you need to instead create a new package definition for 
musescore version 3.6.2. The info page gives you an example, which you 
just adjust. Using guix edit musescore you see how musescore is defined. 
You can notice, there is a version field. So lets create a new package 
with adjusted version:

(define musescore-3.6.2
   (package
     (inherit musescore)
     (version "3.6.2")))

;; We create this manifest from a _package_, and not from a
;; _specification_ (which is just something like a string "musescore")
(packages->manifest (list musescore-3.6.2))


So now putting everything together:

;; Manifest Musik Programme
(use-modules (gnu packages music)
              (guix packages))


(define musescore-3.6.2
   (package
     (inherit musescore)
     (version "3.6.2")))

;; combine both manifest lists:
(concatenate-manifests
   (list
     (packages->manifest (list musescore-3.6.2))
     (specifications->manifest '("ardour" "audacious" "audacity" "obs" 
"vlc"))))


 >
 > 
..........................................................................................
 >
 > gfp@Tuxedo ~$ guix package -p /home/gfp/Projekte/Musik -m
 > /home/gfp/Projekte/Musik/musik.scm
 >
 > 
..........................................................................................
 > I got this message:
 >
 > /home/gfp/Projekte/Musik/musik.scm:4:26: error: #{\x2019;}#: unbound
 > variable
 > hint: Did you forget a `use-modules' form?
 >
 >
 > I surely made a mistake in my "musik.scm"
 > but playing around for hours
 > I prefer to ask.
 >
 >
 > Kind regards
 >
 > Gottfried
 >


  reply	other threads:[~2023-03-18 11:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 10:50 creating a manifest Gottfried
2023-03-18 11:48 ` Martin Castillo [this message]
2023-03-18 12:44   ` Martin Castillo
2023-03-18 18:58   ` Gottfried
     [not found]     ` <DFF79ED1-D430-4DE9-81C9-C1B146E1B84D@uni-bremen.de>
     [not found]       ` <ddb1213e-3864-bbdc-381d-aed8f9f4ace2@posteo.de>
     [not found]         ` <400c34f4-61e4-fc2e-f826-8b6d2c37f62b@uni-bremen.de>
     [not found]           ` <726a7642-df0b-495b-4b24-ce956533cba7@posteo.de>
     [not found]             ` <81AEB7B8-17C7-4484-90B6-BFEF5163B670@uni-bremen.de>
2023-03-25 12:49               ` Gottfried
2023-03-25 22:07                 ` Martin Castillo
2023-03-26  8:16                   ` Gottfried
2023-03-26 11:36                     ` Martin Castillo
2023-03-26 13:07                       ` Gottfried
2023-03-26 18:36                         ` Martin Castillo
2023-03-27 11:52                           ` Gottfried
2023-03-27 18:06                             ` Wojtek Kosior via

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=2e5ab249-c759-7fce-58e2-ebeeac7fbacc@uni-bremen.de \
    --to=castilma@uni-bremen.de \
    --cc=gottfried@posteo.de \
    --cc=help-guix@gnu.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.
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.