creating a manifest

creating a manifest

[Gottfried]

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

Hi,

I wanted to create a manifest for music,
.........................................................................................
my "musik.scm":

;; Manifest Musik Programme
(use-modules (gnu packages version-control))

(specifications->manifest ’("Musescore '--with-branch=musescore=v3.6.2" 
"Ardour" "Audacious" "Audacity" "OBS Studio" "VLC Media Player"))

..........................................................................................

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

Re: creating a manifest

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

Re: creating a manifest

[Martin Castillo]

I noticed an error.

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

While building guix says it's downloading musescore-4.0.1. Maybe it 
switches to the respective branch before building.

I even tried explicitly writing the origin entry of
(define musescore-3.6.2
   (package 

     (inherit musescore) 
 

     (version "3.6.2")
     (source
      (origin
        (method git-fetch)
        (uri (git-reference
              (url "https://github.com/musescore/MuseScore")
              (commit (string-append "v" "3.6.2"))))
        (file-name (git-file-name "musescore" "3.6.2"))
        (sha256
         (base32 "0x2aahpbvss3sjydcq6xdh198fmslgypixmd2gckfwjqzady662y"))
        (modules '((guix build utils)))
        (snippet
         '(begin
            ;; Remove unused libraries...
            (for-each delete-file-recursively
                      '("thirdparty/freetype"))
            ;; ... and precompiled binaries.
            (delete-file-recursively "src/diagnostics/crashpad_handler")
            (substitute* "src/diagnostics/CMakeLists.txt"
              (("install") "#install"))))))))

guix shell -m manifest.scm still says 4.0.1 and executing mscore fails:
[env]$ mscore --version
QEventLoop: Cannot be used without QApplication
QEventLoop: Cannot be used without QApplication
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even 
though it was found.
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, 
offscreen, vnc, xcb.

Abgebrochen

So seems like in this case it's not so easy. (Well the current guix 
packaged version is 4.0.1 so a major version change happened.)

One could try using the older package definition, which is available in 
the git history of guix. Commit 6a54715988aee884bbb5f81e1b718a27ff771ec4 
is the newest change to musescore with 3.6.2. 
9f93bcd1862c76d7ff30da6f712c9bd2912b8346 switched to 4.0. So it's parent 
commit should have the newest dependencies which might work with current 
guix.
I don't have time right now, but you might want to copy such an older 
package definition into your manifest.scm

Martin

Re: creating a manifest

[Gottfried]

[-- 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 --]

Re: creating a manifest

[Gottfried]

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

Hi,

Today I wanted to update my manifest with
musescore-3.6.2, ardour, audacity, obs, vlc.

and it wanted to build musescore 4.02 (the current new version).

I stopped it immeadiately.

I was wondering why the update didn’t want to keep musescore-3.6.2
even though the version 3.6.2 is clearly in the manifest.

If so, I can never update this manifest
or I create a separate musescore-3.6.2 profile
with only that package, which I will never update.



Kind regards

Gottfried


>> Am 19.03.23 um 16:44 schrieb Martin Castillo:
>>> Hi,
>>>
>>> Am 19.03.23 um 12:05 schrieb Gottfried:
>>>> Hi,
>>>>
>>>> thanks very much for your help. I appreciate it very much.
>>>>
>>>>> Does musescore work? What version is installed with this manifest I sent you? mscore --version or so should tell you the version.
>>>>
>>>> I checked:
>>>> gfp@Tuxedo ~$ guix shell -p /home/gfp/Projekte/Musik/guix-profil
>>>> gfp@Tuxedo ~ [env]$ mscore --version
>>>> QEventLoop: Cannot be used without QApplication
>>>> QEventLoop: Cannot be used without QApplication
>>>> MuseScore4 4.0.1
>>>>
>>>> It installed the version 4.0.1 (the new version) unfortunately.
>>>> I don’t know why?
>>>
>>> I don't know either. I'm a guix beginner, too, and probably my way of redefining an old version of musescore was to simple?
>>>
>>> Here is the musescore definition copied from an older guix including all use-modules (some of which are unnecessary, but I don't know how to quickly find out which ones are which):
>>>
>>> ;; Manifest Musik Programme
>>> (use-modules (gnu packages music)
>>> ; necessary for musescore
>>>            (guix packages)
>>>            (guix licenses)
>>>            (guix git-download)
>>>            (guix build-system qt))
>>>     (use-modules (gnu packages audio))
>>>     (use-modules (gnu packages linux)) ; for alsa-utils
>>>
>>> ; partly necessary
>>>     (use-modules (gnu packages admin))
>>>     (use-modules (gnu packages algebra))
>>>     (use-modules (gnu packages apr))
>>>     (use-modules (gnu packages autotools))
>>>     (use-modules (gnu packages assembly))
>>>     (use-modules (gnu packages backup))
>>>     (use-modules (gnu packages base)) ;libbdf
>>>     (use-modules (gnu packages bash))
>>>     (use-modules (gnu packages benchmark))
>>>     (use-modules (gnu packages bison))
>>>     (use-modules (gnu packages boost))
>>>     (use-modules (gnu packages build-tools))
>>>     (use-modules (gnu packages cdrom))
>>>     (use-modules (gnu packages code))
>>>     (use-modules (gnu packages check))
>>>     (use-modules (gnu packages cmake))
>>>     (use-modules (gnu packages compression))
>>>     (use-modules (gnu packages cpp))
>>>     (use-modules (gnu packages crypto))
>>>     (use-modules (gnu packages curl))
>>>     (use-modules (gnu packages cyrus-sasl))
>>>     (use-modules (gnu packages datastructures))
>>>     (use-modules (gnu packages docbook))
>>>     (use-modules (gnu packages documentation))
>>>     (use-modules (gnu packages emacs))
>>>     (use-modules (gnu packages file))
>>>     (use-modules (gnu packages flex))
>>>     (use-modules (gnu packages fltk))
>>>     (use-modules (gnu packages fonts))
>>>     (use-modules (gnu packages fontutils))
>>>     (use-modules (gnu packages freedesktop))
>>>     (use-modules (gnu packages game-development))
>>>     (use-modules (gnu packages gnupg))
>>>     (use-modules (gnu packages gettext))
>>>     (use-modules (gnu packages ghostscript))
>>>     (use-modules (gnu packages gl))
>>>     (use-modules (gnu packages glib))
>>>     (use-modules (gnu packages gnome))
>>>     (use-modules (gnu packages gnunet))
>>>     (use-modules (gnu packages gpodder))
>>>     (use-modules (gnu packages graphics))
>>>     (use-modules (gnu packages graphviz))
>>>     (use-modules (gnu packages gstreamer))
>>>     (use-modules (gnu packages gtk))
>>>     (use-modules (gnu packages guile))
>>>     (use-modules (gnu packages haskell))
>>>     (use-modules (gnu packages icu4c))
>>>     (use-modules (gnu packages image))
>>>     (use-modules (gnu packages imagemagick))
>>>     (use-modules (gnu packages java))
>>>     (use-modules (gnu packages libffi))
>>>     (use-modules (gnu packages libevent))
>>>     (use-modules (gnu packages libusb))
>>>     (use-modules (gnu packages lirc))
>>>     (use-modules (gnu packages llvm))
>>>     (use-modules (gnu packages man))
>>>     (use-modules (gnu packages mp3))
>>>     (use-modules (gnu packages mpd))
>>>     (use-modules (gnu packages ncurses))
>>>     (use-modules (gnu packages netpbm))
>>>     (use-modules (gnu packages pcre))
>>>     (use-modules (gnu packages pdf))
>>>     (use-modules (gnu packages perl))
>>>     (use-modules (gnu packages perl-check))
>>>     (use-modules (gnu packages perl-web))
>>>     (use-modules (gnu packages php))
>>>     (use-modules (gnu packages pkg-config))
>>>     (use-modules (gnu packages protobuf))
>>>     (use-modules (gnu packages pulseaudio)) ;libsndfile
>>>     (use-modules (gnu packages python))
>>>     (use-modules (gnu packages python-build))
>>>     (use-modules (gnu packages python-check))
>>>     (use-modules (gnu packages python-compression))
>>>     (use-modules (gnu packages python-web))
>>>     (use-modules (gnu packages python-xyz))
>>>     (use-modules (gnu packages qt))
>>>     (use-modules (gnu packages rdf))
>>>     (use-modules (gnu packages readline))
>>>     (use-modules (gnu packages rsync))
>>>     (use-modules (gnu packages sdl))
>>>     (use-modules (gnu packages serialization))
>>>     (use-modules (gnu packages sphinx))
>>>     (use-modules (gnu packages sqlite))
>>>     (use-modules (gnu packages stb))
>>>     (use-modules (gnu packages tcl))
>>>     (use-modules (gnu packages texinfo))
>>>     (use-modules (gnu packages tex))
>>>     (use-modules (gnu packages time))
>>>     (use-modules (gnu packages tls))
>>>     (use-modules (gnu packages version-control))
>>>     (use-modules (gnu packages video))
>>>     (use-modules (gnu packages vim))       ;for 'xxd'
>>>     (use-modules (gnu packages web))
>>>     (use-modules (gnu packages webkit))
>>>     (use-modules (gnu packages wm))
>>>     (use-modules (gnu packages wxwidgets))
>>>     (use-modules (gnu packages xdisorg))
>>>     (use-modules (gnu packages xml))
>>>     (use-modules (gnu packages xorg))
>>>     (use-modules (gnu packages xiph))
>>>     (use-modules (gnu packages golang))
>>>     (use-modules (gnu packages lua))
>>>
>>>
>>> ;; copied from  guix ced3be2b562866b82f97a530cd66610c84c381f7
>>> (define-public musescore-3
>>>     (package
>>>       (name "musescore")
>>>       (version "3.6.2")
>>>       (source
>>>        (origin
>>>          (method git-fetch)
>>>          (uri (git-reference
>>>                (url "https://github.com/musescore/MuseScore")
>>>                (commit (string-append "v" version))))
>>>          (file-name (git-file-name name version))
>>>          (sha256
>>>           (base32 "0szvb6mlzy9df9lrq546rrpixa480knzij1wgh6ilflxz87q048q"))
>>>          (modules '((guix build utils)))
>>>          (snippet
>>>           ;; Remove unused libraries.
>>>           '(begin
>>>              (for-each delete-file-recursively
>>>                        '("thirdparty/freetype"
>>>                          "thirdparty/openssl"
>>>                          "thirdparty/portmidi"
>>>                          "thirdparty/qt-google-analytics"))))))
>>>       (build-system qt-build-system)
>>>       (arguments
>>>        `(#:configure-flags
>>>          `("-DBUILD_TELEMETRY_MODULE=OFF" ;don't phone home
>>>            "-DBUILD_WEBENGINE=OFF"
>>>            "-DDOWNLOAD_SOUNDFONT=OFF"
>>>            "-DMUSESCORE_BUILD_CONFIG=release"
>>>            "-DUSE_SYSTEM_FREETYPE=ON")
>>>          ;; There are tests, but no simple target to run.  The command used to
>>>          ;; run them is:
>>>          ;;
>>>          ;;   make debug && sudo make installdebug && cd \
>>>          ;;   build.debug/mtest && make && ctest
>>>          ;;
>>>          ;; Basically, it requires to start a whole new build process.
>>>          ;; So we simply skip them.
>>>          #:tests? #f))
>>>       (inputs
>>>        (list alsa-lib
>>>              freetype
>>>              `(,gtk+ "bin")               ;for gtk-update-icon-cache
>>>              jack-1
>>>              lame
>>>              libogg
>>>              libsndfile
>>>              libvorbis
>>>              portaudio
>>>              portmidi
>>>              pulseaudio
>>>              qtbase-5
>>>              qtdeclarative-5
>>>              qtgraphicaleffects
>>>              qtquickcontrols2-5
>>>              qtscript
>>>              qtsvg-5
>>>              qtxmlpatterns))
>>>       (native-inputs
>>>        (list pkg-config qttools-5))
>>>       (synopsis "Music composition and notation software")
>>>       (description
>>>        "MuseScore is a music score typesetter.  Its main purpose is the creation
>>> of high-quality engraved musical scores in a WYSIWYG environment.
>>>
>>> It supports unlimited staves, linked parts and part extraction, tablature,
>>> MIDI input, percussion notation, cross-staff beaming, automatic transposition,
>>> lyrics (multiple verses), fretboard diagrams, and in general everything
>>> commonly used in sheet music.  Style options and style sheets to change the
>>> appearance and layout are provided.
>>>
>>> MuseScore can also play back scores through the built-in sequencer and SoundFont
>>> sample library.")
>>>       (home-page "https://musescore.org")
>>>       (license gpl2)))
>>>
>>> ;; combine both manifest lists:
>>> (concatenate-manifests
>>>     (list
>>>       (packages->manifest (list musescore-3))
>>>       (specifications->manifest '("ardour" "audacious" "audacity" "obs" "vlc"))))
>>>
>>>
>>> I hope this works.
>>
> 
> You say directories, but those are probably symlinks. The guix-profile points to guix-profile-2-link. If that is correct you can delete the guix-profile-1-link. The next time guix gc is called it will actually delete the files belonging to the first generation of that profile.
> When you rerun guix shell (to update the softwares) with that profile a guix-profile-3-link will be created and guix-profile will link to that. You then may delete guix-profile-2-link.

-- 




[-- 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 --]

Re: creating a manifest

[Martin Castillo]

Hi,

please send the command you used to update the profile and the manifest file inside the profile, i.e. home/gfp/Projekte/Musik/guix-profil/manifest.scm

Martin

Re: creating a manifest

[Gottfried]

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

Hi,

> Am 25.03.23 um 23:07 schrieb Martin Castillo:

>> Hi,
>> 
>> please send the command you used to update the profile and the manifest file inside the profile, i.e. home/gfp/Projekte/Musik/guix-profil/manifest.scm
>> 
>> Martin

This was the command I used to upgrade the profile
(because I deleted one package: ardour
in my main profile, so I wanted to install it in this profile)

~$ guix package --upgrade --profile=/home/gfp/Projekte/Musik/guix-profil

-----------------------------------------------------------------------------

here the musik.scm:

;; Manifest Musik Programme
(use-modules (gnu packages music)
; necessary for musescore
          (guix packages)
          (guix licenses)
          (guix git-download)
          (guix build-system qt))
   (use-modules (gnu packages audio))
   (use-modules (gnu packages linux)) ; for alsa-utils

; partly necessary
   (use-modules (gnu packages admin))
   (use-modules (gnu packages algebra))
   (use-modules (gnu packages apr))
   (use-modules (gnu packages autotools))
   (use-modules (gnu packages assembly))
   (use-modules (gnu packages backup))
   (use-modules (gnu packages base)) ;libbdf
   (use-modules (gnu packages bash))
   (use-modules (gnu packages benchmark))
   (use-modules (gnu packages bison))
   (use-modules (gnu packages boost))
   (use-modules (gnu packages build-tools))
   (use-modules (gnu packages cdrom))
   (use-modules (gnu packages code))
   (use-modules (gnu packages check))
   (use-modules (gnu packages cmake))
   (use-modules (gnu packages compression))
   (use-modules (gnu packages cpp))
   (use-modules (gnu packages crypto))
   (use-modules (gnu packages curl))
   (use-modules (gnu packages cyrus-sasl))
   (use-modules (gnu packages datastructures))
   (use-modules (gnu packages docbook))
   (use-modules (gnu packages documentation))
   (use-modules (gnu packages emacs))
   (use-modules (gnu packages file))
   (use-modules (gnu packages flex))
   (use-modules (gnu packages fltk))
   (use-modules (gnu packages fonts))
   (use-modules (gnu packages fontutils))
   (use-modules (gnu packages freedesktop))
   (use-modules (gnu packages game-development))
   (use-modules (gnu packages gnupg))
   (use-modules (gnu packages gettext))
   (use-modules (gnu packages ghostscript))
   (use-modules (gnu packages gl))
   (use-modules (gnu packages glib))
   (use-modules (gnu packages gnome))
   (use-modules (gnu packages gnunet))
   (use-modules (gnu packages gpodder))
   (use-modules (gnu packages graphics))
   (use-modules (gnu packages graphviz))
   (use-modules (gnu packages gstreamer))
   (use-modules (gnu packages gtk))
   (use-modules (gnu packages guile))
   (use-modules (gnu packages haskell))
   (use-modules (gnu packages icu4c))
   (use-modules (gnu packages image))
   (use-modules (gnu packages imagemagick))
   (use-modules (gnu packages java))
   (use-modules (gnu packages libffi))
   (use-modules (gnu packages libevent))
   (use-modules (gnu packages libusb))
   (use-modules (gnu packages lirc))
   (use-modules (gnu packages llvm))
   (use-modules (gnu packages man))
   (use-modules (gnu packages mp3))
   (use-modules (gnu packages mpd))
   (use-modules (gnu packages ncurses))
   (use-modules (gnu packages netpbm))
   (use-modules (gnu packages pcre))
   (use-modules (gnu packages pdf))
   (use-modules (gnu packages perl))
   (use-modules (gnu packages perl-check))
   (use-modules (gnu packages perl-web))
   (use-modules (gnu packages php))
   (use-modules (gnu packages pkg-config))
   (use-modules (gnu packages protobuf))
   (use-modules (gnu packages pulseaudio)) ;libsndfile
   (use-modules (gnu packages python))
   (use-modules (gnu packages python-build))
   (use-modules (gnu packages python-check))
   (use-modules (gnu packages python-compression))
   (use-modules (gnu packages python-web))
   (use-modules (gnu packages python-xyz))
   (use-modules (gnu packages qt))
   (use-modules (gnu packages rdf))
   (use-modules (gnu packages readline))
   (use-modules (gnu packages rsync))
   (use-modules (gnu packages sdl))
   (use-modules (gnu packages serialization))
   (use-modules (gnu packages sphinx))
   (use-modules (gnu packages sqlite))
   (use-modules (gnu packages stb))
   (use-modules (gnu packages tcl))
   (use-modules (gnu packages texinfo))
   (use-modules (gnu packages tex))
   (use-modules (gnu packages time))
   (use-modules (gnu packages tls))
   (use-modules (gnu packages version-control))
   (use-modules (gnu packages video))
   (use-modules (gnu packages vim))       ;for 'xxd'
   (use-modules (gnu packages web))
   (use-modules (gnu packages webkit))
   (use-modules (gnu packages wm))
   (use-modules (gnu packages wxwidgets))
   (use-modules (gnu packages xdisorg))
   (use-modules (gnu packages xml))
   (use-modules (gnu packages xorg))
   (use-modules (gnu packages xiph))
   (use-modules (gnu packages golang))
   (use-modules (gnu packages lua))


;; copied from  guix ced3be2b562866b82f97a530cd66610c84c381f7
(define-public musescore-3
   (package
     (name "musescore")
     (version "3.6.2")
     (source
      (origin
        (method git-fetch)
        (uri (git-reference
              (url "https://github.com/musescore/MuseScore")
              (commit (string-append "v" version))))
        (file-name (git-file-name name version))
        (sha256
         (base32 "0szvb6mlzy9df9lrq546rrpixa480knzij1wgh6ilflxz87q048q"))
        (modules '((guix build utils)))
        (snippet
         ;; Remove unused libraries.
         '(begin
            (for-each delete-file-recursively
                      '("thirdparty/freetype"
                        "thirdparty/openssl"
                        "thirdparty/portmidi"
                        "thirdparty/qt-google-analytics"))))))
     (build-system qt-build-system)
     (arguments
      `(#:configure-flags
        `("-DBUILD_TELEMETRY_MODULE=OFF" ;don't phone home
          "-DBUILD_WEBENGINE=OFF"
          "-DDOWNLOAD_SOUNDFONT=OFF"
          "-DMUSESCORE_BUILD_CONFIG=release"
          "-DUSE_SYSTEM_FREETYPE=ON")
        ;; There are tests, but no simple target to run.  The command 
used to
        ;; run them is:
        ;;
        ;;   make debug && sudo make installdebug && cd \
        ;;   build.debug/mtest && make && ctest
        ;;
        ;; Basically, it requires to start a whole new build process.
        ;; So we simply skip them.
        #:tests? #f))
     (inputs
      (list alsa-lib
            freetype
            `(,gtk+ "bin")               ;for gtk-update-icon-cache
            jack-1
            lame
            libogg
            libsndfile
            libvorbis
            portaudio
            portmidi
            pulseaudio
            qtbase-5
            qtdeclarative-5
            qtgraphicaleffects
            qtquickcontrols2-5
            qtscript
            qtsvg-5
            qtxmlpatterns))
     (native-inputs
      (list pkg-config qttools-5))
     (synopsis "Music composition and notation software")
     (description
      "MuseScore is a music score typesetter.  Its main purpose is the 
creation
of high-quality engraved musical scores in a WYSIWYG environment.

It supports unlimited staves, linked parts and part extraction, tablature,
MIDI input, percussion notation, cross-staff beaming, automatic 
transposition,
lyrics (multiple verses), fretboard diagrams, and in general everything
commonly used in sheet music.  Style options and style sheets to change the
appearance and layout are provided.

MuseScore can also play back scores through the built-in sequencer and 
SoundFont
sample library.")
     (home-page "https://musescore.org")
     (license gpl2)))

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

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

Re: creating a manifest

[Martin Castillo]

Hi,

Am 26.03.23 um 10:16 schrieb Gottfried:

>>> please send the command you used to update the profile and the 
>>> manifest file inside the profile, i.e. 
>>> home/gfp/Projekte/Musik/guix-profil/manifest.scm
>>>
>>> Martin
> 
> This was the command I used to upgrade the profile
> (because I deleted one package: ardour
> in my main profile, so I wanted to install it in this profile)
> 
> ~$ guix package --upgrade --profile=/home/gfp/Projekte/Musik/guix-profil

Like you, I would expect that to work, but I read the info page again. 
It says about --upgrade:

   Note that this upgrades package to the latest version of packages
      found in the distribution currently installed.

And the latest version of musescore is 4.0.2, so it tries to install that.

So I guess the right command would be:

guix package -m /home/gfp/Projekte/Musik/musik.scm --profile 
/home/gfp/Projekte/Musik/guix-profil


> 
> -----------------------------------------------------------------------------
> 
> here the musik.scm:
> 

I actually meant /home/gfp/Projekte/Musik/guix-profil/manifest and not 
/home/gfp/Projekte/Musik/musik.scm, but now I don't need it anymore.

Martin

Re: creating a manifest

[Gottfried]

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

Hi,
thank you very much for your help.

I am learning day by day how to use Guix.

1.
I understood till now that creating manifests mean several packages in 
one manifest, like in my music profile: ardour, audacity, audacious, 
musescore.

2.
When I was opening that profile I used musescore, I had to close it and 
then open audacity and so on.
It seems to me I can’t open several packages at once.
Or I don’t know how to do it, if possible.

3.
Now I realised that to create a manifest means one package, only 
musescore, or only emacs with all its emacs packages.

4.
Then upgrading the manifest/one profile
would not be a problem.

5.
What would be the difference to have several profiles in my main profile
without haveing guix home,

or to have several profiles in Guix home?



Kind regards

Gottfried


Am 26.03.23 um 13:36 schrieb Martin Castillo:
> Hi,
> 
> Am 26.03.23 um 10:16 schrieb Gottfried:
> 
>>>> please send the command you used to update the profile and the 
>>>> manifest file inside the profile, i.e. 
>>>> home/gfp/Projekte/Musik/guix-profil/manifest.scm
>>>>
>>>> Martin
>>
>> This was the command I used to upgrade the profile
>> (because I deleted one package: ardour
>> in my main profile, so I wanted to install it in this profile)
>>
>> ~$ guix package --upgrade --profile=/home/gfp/Projekte/Musik/guix-profil
> 
> Like you, I would expect that to work, but I read the info page again. 
> It says about --upgrade:
> 
>    Note that this upgrades package to the latest version of packages
>       found in the distribution currently installed.
> 
> And the latest version of musescore is 4.0.2, so it tries to install that.
> 
> So I guess the right command would be:
> 
> guix package -m /home/gfp/Projekte/Musik/musik.scm --profile 
> /home/gfp/Projekte/Musik/guix-profil
> 
> 
>>
>> -----------------------------------------------------------------------------
>>
>> here the musik.scm:
>>
> 
> I actually meant /home/gfp/Projekte/Musik/guix-profil/manifest and not 
> /home/gfp/Projekte/Musik/musik.scm, but now I don't need it anymore.
> 
> Martin

-- 



[-- 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 --]

Re: creating a manifest

[Martin Castillo]

Hi,

Am 26.03.23 um 15:07 schrieb Gottfried:
> Hi,
> thank you very much for your help.
> 
> I am learning day by day how to use Guix.
> 
> 1.
> I understood till now that creating manifests mean several packages in 
> one manifest, like in my music profile: ardour, audacity, audacious, 
> musescore.

You mean `in one profile`? Correct.

> 2.
> When I was opening that profile I used musescore, I had to close it and 
> then open audacity and so on.
> It seems to me I can’t open several packages at once.
> Or I don’t know how to do it, if possible.

That's weird. What happens if you try to run a second program from the 
profile while the first one is still running?

Two ways that you can do it:
1) With two terminals:
    1. In the first one run:
       $ source ~/Projekte/Musik/guix-profil/etc/profile;
       $ mscore;
    2. In the the second terminal run:
       $ source ~/Projekte/Musik/guix-profil/etc/profile;
       $ vlc;

2) With one terminal:
       Run the first, (or all commands) in the background, so that the
       shell directly prompts you for the next command:
       $ source ~/Projekte/Musik/guix-profil/etc/profile;
       $ mscore &
       $ vlc &
       $


> 3.
> Now I realised that to create a manifest means one package, only 
> musescore, or only emacs with all its emacs packages.

No, that's not always right. The manifest you posted in this thread 
contains multiple packages and you created a profile with all those 
packages.

> 4.
> Then upgrading the manifest/one profile
> would not be a problem.

There can be multiple packages be in one profile, created by one 
manifest, and using this command it should be no problem to update all 
packages, but keeping musescore at version 3:
 >> guix package -m /home/gfp/Projekte/Musik/musik.scm --profile
 >> /home/gfp/Projekte/Musik/guix-profil

> 
> 5.
> What would be the difference to have several profiles in my main profile
> without haveing guix home,

What do you mean by having several profiles in your main profile?
AFAIK there is no way to put one profile inside another.
Do you mean several packages in one profile?

> or to have several profiles in Guix home? 

I never used guix home. I cannot answer that.

Re: creating a manifest

[Gottfried]

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

Hi,

thanks very much for your help.

1.
> When I was opening that profile I used musescore, I had to close it 
>>> and then open audacity and so on.
>>> It seems to me I can’t open several packages at once.
>>> Or I don’t know how to do it, if possible.

Sorry, this was my mistake.

the terminal doesn’t show the "prompt" (I don’t know how it is called)
gfp@Tuxedo ~ after opening one package
only if I enlarge the terminal, than it shows up.
-----------------------------------------------------------------------------
2.
> Two ways that you can do it:
>> 1) With two terminals:
>>     1. In the first one run:
>>        $ source ~/Projekte/Musik/guix-profil/etc/profile;
>>        $ mscore;
>>     2. In the the second terminal run:
>>        $ source ~/Projekte/Musik/guix-profil/etc/profile;
>>        $ vlc;
>> 
>> 2) With one terminal:
>>        Run the first, (or all commands) in the background, so that the
>>        shell directly prompts you for the next command:
>>        $ source ~/Projekte/Musik/guix-profil/etc/profile;
>>        $ mscore &
>>        $ vlc &
>>        $
>> 

with the first and second possibility you mentioned
I can open several packages, which is good.

But it opened Musescore 4.0.2, which shouldn’t.
and I don’t understand why.

and there are loads of messages:
> gfp@Tuxedo ~$ guix shell -p ~/Projekte/Musik/guix-profil
> gfp@Tuxedo ~ [env]$ mscore &
> [1] 5761
> gfp@Tuxedo ~ [env]$ ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> qrc:/qml/palettes/PaletteTree.qml:772:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> ScoreFont::draw: invalid sym 0

I don’t know what to do with them.

3.
with the command:
gfp@Tuxedo ~$ guix shell -p ~/Projekte/Musik/guix-profil

it opened Musescore 3.6.2   which I want, and that is in that manifest 
installed.

But with this command there are messages:

> gfp@Tuxedo ~ [env]$ ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> qrc:/qml/palettes/PaletteTree.qml:772:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> ScoreFont::draw: invalid sym 0


I don’t know what that means.
---------------------------------------------------------------------
4.
>> What would be the difference to have several profiles in my main profile
>> without haveing guix home,
> 
> What do you mean by having several profiles in your main profile?
> AFAIK there is no way to put one profile inside another.
> Do you mean several packages in one profile? 

I didn’t know how to call it.
I meant by "main profile" the profile which I had in the beginning after 
installing Guix.
before I created other profiles.
(/home/gfp/.config/guix/current
/home/gfp/.guix-profile)
How do you call it?
my "dot profiles"?

gfp@Tuxedo ~$ guix package --list-profiles
/home/gfp/Projekte/EmacsManifest/guix-profil
/home/gfp/Projekte/GNUCash/guix-profil
/home/gfp/Projekte/Lilypond/guix-profil
/home/gfp/Projekte/Musescore/guix-profil
/home/gfp/Projekte/Musik/guix-profil
/home/gfp/Projekte/Photoflare/guix-profil
/home/gfp/.config/guix/current
/home/gfp/.guix-profile

--------------------------------------------------------------
5.
to hack on Guix is quite difficult without having studied


kind regards

Gottfried



Am 26.03.23 um 20:36 schrieb Martin Castillo:
> Hi,
> 
> Am 26.03.23 um 15:07 schrieb Gottfried:
>> Hi,
>> thank you very much for your help.
>>
>> I am learning day by day how to use Guix.
>>
>> 1.
>> I understood till now that creating manifests mean several packages in 
>> one manifest, like in my music profile: ardour, audacity, audacious, 
>> musescore.
> 
> You mean `in one profile`? Correct.
> 
>> 2.
>> When I was opening that profile I used musescore, I had to close it 
>> and then open audacity and so on.
>> It seems to me I can’t open several packages at once.
>> Or I don’t know how to do it, if possible.
> 
> That's weird. What happens if you try to run a second program from the 
> profile while the first one is still running?
> 
> Two ways that you can do it:
> 1) With two terminals:
>     1. In the first one run:
>        $ source ~/Projekte/Musik/guix-profil/etc/profile;
>        $ mscore;
>     2. In the the second terminal run:
>        $ source ~/Projekte/Musik/guix-profil/etc/profile;
>        $ vlc;
> 
> 2) With one terminal:
>        Run the first, (or all commands) in the background, so that the
>        shell directly prompts you for the next command:
>        $ source ~/Projekte/Musik/guix-profil/etc/profile;
>        $ mscore &
>        $ vlc &
>        $
> 
> 
>> 3.
>> Now I realised that to create a manifest means one package, only 
>> musescore, or only emacs with all its emacs packages.
> 
> No, that's not always right. The manifest you posted in this thread 
> contains multiple packages and you created a profile with all those 
> packages.
> 
>> 4.
>> Then upgrading the manifest/one profile
>> would not be a problem.
> 
> There can be multiple packages be in one profile, created by one 
> manifest, and using this command it should be no problem to update all 
> packages, but keeping musescore at version 3:
>  >> guix package -m /home/gfp/Projekte/Musik/musik.scm --profile
>  >> /home/gfp/Projekte/Musik/guix-profil
> 
>>
>> 5.
>> What would be the difference to have several profiles in my main profile
>> without haveing guix home,
> 
> What do you mean by having several profiles in your main profile?
> AFAIK there is no way to put one profile inside another.
> Do you mean several packages in one profile?
> 
>> or to have several profiles in Guix home? 
> 
> I never used guix home. I cannot answer that.



[-- 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 --]

Re: creating a manifest

[Wojtek Kosior via]

[-- Attachment #1: Type: text/plain, Size: 3979 bytes --]

> and there are loads of messages:
> > gfp@Tuxedo ~$ guix shell -p ~/Projekte/Musik/guix-profil
> > gfp@Tuxedo ~ [env]$ mscore &
> > [1] 5761
> > gfp@Tuxedo ~ [env]$ ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > qrc:/qml/palettes/PaletteTree.qml:772:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > ScoreFont::draw: invalid sym 0  
> 
> I don’t know what to do with them.

It's quite common that GUI applications produce quite a lot of text
output when run from the command line. You can get rid of that text by
replacing lines like

    command-name &

with lines like

    command-name >/dev/null 2>/dev/null &

This redirects the *standard output* and *standard error output* of the
new process to your system's local black hole. Additionally, if you
don't want the processes started with "&" to be killed when you close
the terminal window, you can use the "disown" shell builtin after
spawning each process. So, in your terminal you could now write

    command-name >/dev/null 2>/dev/null &
    disown

You can also make it a bit shorter at the cost of adding a bit more
complexity. Feel free to ignore this option and its explanation if it
seems like too much of a black magic. So, you'd write in one line

    command-name >/dev/null 2>&1 & disown

The second occurrence of "/dev/null" got replaced with "&1" which is a
reference to already-assigned standard output destination. And the
newline before "disown" was removed because the shell already knows the
stuff after "&" is a separate command

Wojtek

-- (sig_start)
website: https://koszko.org/koszko.html
PGP: https://koszko.org/key.gpg
fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A

♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)


On Mon, 27 Mar 2023 11:52:20 +0000
Gottfried <gottfried@posteo.de> wrote:

> and there are loads of messages:
> > gfp@Tuxedo ~$ guix shell -p ~/Projekte/Musik/guix-profil
> > gfp@Tuxedo ~ [env]$ mscore &
> > [1] 5761
> > gfp@Tuxedo ~ [env]$ ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > qrc:/qml/palettes/PaletteTree.qml:772:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > ScoreFont::draw: invalid sym 0  
> 
> I don’t know what to do with them.


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