unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gottfried <gottfried@posteo.de>
To: Martin Castillo <castilma@uni-bremen.de>, help-guix@gnu.org
Subject: Re: creating a manifest
Date: Sat, 18 Mar 2023 18:58:20 +0000	[thread overview]
Message-ID: <7b1623f3-8ed3-2111-09cb-b7fccd03a3bd@posteo.de> (raw)
In-Reply-To: <2e5ab249-c759-7fce-58e2-ebeeac7fbacc@uni-bremen.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 4054 bytes --]

Hi,
thank you very much for help.
I was reading the manual about manifests, but still I don’t understand 
everything what I have to do.

I created now through your help a manifest with 6 packages,
but I got an error message:

Profil mit 6 Paketen wird erstellt …
guix package: Fehler/mistake: rename-file: Ist ein Verzeichnis/is a 
directory

and it didn’t create the directories in my "Musik" directory, but 
besides it, so I have home/gfp/Projekte/EmacsManifest
					Musescore
					Musik	
					Musik.new
					Musik-1-link	

  I wanted to put it in the "Musik" directory in order to have a good 
structure.

1.
Is it possible to change this?
..................................................................
I did a:
guix package -p /home/gfp/Projekte/Musik -m
/home/gfp/Projekte/Musik/musik.scm

2.
What would I have to do instead, in order to put it in my "Musik" directory?
(to know for the next time, to create an other profile)


Kind regards

Gottfried



Am 18.03.23 um 12:48 schrieb Martin Castillo:
> 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
>  >

-- 

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

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

  parent reply	other threads:[~2023-03-18 18:59 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
2023-03-18 12:44   ` Martin Castillo
2023-03-18 18:58   ` Gottfried [this message]
     [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

  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=7b1623f3-8ed3-2111-09cb-b7fccd03a3bd@posteo.de \
    --to=gottfried@posteo.de \
    --cc=castilma@uni-bremen.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.
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).