help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Scheme package installation script


From: Gábor Boskovits
Subject: Re: Scheme package installation script
Date: Fri, 18 Jan 2019 08:55:03 +0100

Hello,

<address@hidden> ezt írta (időpont: 2019. jan. 18., P, 3:48):
>
> Hi all. I maintain my own emacs configuration designed to be integrated
> into guix. One of the parts of maintaining a configuration is package
> management, which I of course rely on Guix to do (rather than pulling
> from MELPA directly). There are many packages that need to be installed
> before my configuration can work, so naturally I devised a meta-package
> of sorts. The issue with this meta package is that I am inheriting the
> hello base package because I am not sure how to bypass needing a source
> to pull from. There is likely a better way to do this meta-package sort
> of deal. Does anybody have any ideas?
>
> (define-public emacs-configuration
>    (package
>     (name "emacs-configuration")
>     (version "0.0.4")
>     (source
>      (origin
>       (inherit (package-source hello))))
>     (build-system gnu-build-system)
>     (inputs
>      `(,@(package-inputs hello)))
>     (propagated-inputs
>      `(("bear" ,bear)
>        ("cquery" ,cquery)
>        ("emacs" ,emacs)
>        ("emacs-all-the-icons" ,emacs-all-the-icons)
>        ("emacs-cider" ,emacs-cider)
>        ("emacs-clojure-mode" ,emacs-clojure-mode)
>        ("emacs-company" ,emacs-company)
>        ("emacs-company-irony" ,emacs-company-irony)
>        ("emacs-company-lsp" ,emacs-company-lsp)
>        ("emacs-company-quickhelp" ,emacs-company-quickhelp)
>        ("emacs-cquery" ,emacs-cquery)
>        ("emacs-diff-hl" ,emacs-diff-hl)
>        ("emacs-dired-k" ,emacs-dired-k)
>        ("emacs-doom-modeline" ,emacs-doom-modeline)
>        ("emacs-doom-theme" ,emacs-doom-themes)
>        ("emacs-ess" ,emacs-ess)
>        ("emacs-flycheck" ,emacs-flycheck)
>        ("emacs-flycheck-irony" ,emacs-flycheck-irony)
>        ("emacs-geiser" ,emacs-geiser)
>        ("emacs-gitpatch" ,emacs-gitpatch)
>        ("emacs-guix" ,emacs-guix)
>        ("emacs-helm" ,emacs-helm)
>        ("emacs-helm-bibtex" ,emacs-helm-bibtex)
>        ("emacs-helm-c-yasnippet" ,emacs-helm-c-yasnippet)
>        ("emacs-helm-flycheck" ,emacs-helm-flycheck)
>        ("emacs-hl-todo" ,emacs-hl-todo)
>        ("emacs-lsp-mode" ,emacs-lsp-mode)
>        ("emacs-lsp-ui" ,emacs-lsp-ui)
>        ("emacs-magit" ,emacs-magit)
>        ("emacs-magit-org-todos-el" ,emacs-magit-org-todos-el))
>     (home-page
>      "https://git.sr.ht/~brettgilio/.emacs.d";)
>     (synopsis
>      "N/A")
>     (description
>      "N/A")
>     (license #f)))
>
>

Just to inquire, what is the benefit for you to put this to a package
instead of having it in a file, and include that in the user manifest.
Are you installing this as a system package?

Best regards,
g_bor



reply via email to

[Prev in Thread] Current Thread [Next in Thread]