[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#37478] [PATCH] Support canonical guix environment -l guix.scm.
From: |
Jan Nieuwenhuizen |
Subject: |
[bug#37478] [PATCH] Support canonical guix environment -l guix.scm. |
Date: |
Sat, 05 Oct 2019 11:25:06 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Ludovic Courtès writes:
>> I often find myself typing `guix environment -l guix.scm' in the Guix
>> source root and thought IWBN no make that "just work". WYDT?
>
> IWBN, but…
>
>> -(define-module (guix))
>> +(define-module (guix)
>> + #:use-module (guix git-download)
>> + #:use-module (guix gexp)
>> + #:use-module (guix packages)
>> + #:use-module (gnu packages package-management))
>
> … the (guix) module is a public module, and it must not depend on
> anything but the (guix …) modules it imports.
>
> So unfortunately we can’t just do that.
Hmm, and is there a difference between compile-time and run-time? I do
not understand the rules well enough here...
So I guess that something vaguely this (I really don't like the
command-line "parsing" bit, just a thought experiment)
--8<---------------cut here---------------start------------->8---
;; Naive command-line parser: are we running from Guix source tree
;; guix build -f guix.scm
;; guix environment -l guix.scm
;; then return guix@git package
(when (and (file-exists? "guix/gexp.scm")
(let ((len (length (command-line))))
(and (> len 3)
(let ((tail (list-tail (command-line) (- len 3))))
(or (equal? tail '("build" "-f" "guix.scm"))
(equal? tail '("environment" "-l" "guix.scm")))))))
(let ((source-dir (dirname (current-filename))))
((@ (guix packages) package)
(inherit (@ (gnu packages package-management) guix))
(version "git")
(source ((@ (guix gexp) local-file) source-dir
#:recursive? #t
#:select? ((@ (guix git-download) git-predicate) source-dir))))))
--8<---------------cut here---------------end--------------->8---
is also not possible? It is also starts to look like a kludge and hard
to get right...bah :)
> Perhaps we could have a ‘.guix.scm’ file though, or
> ‘build-aux/guix.scm’, something like that?
Yes...I was hoping that we could offer/advise something standardized
that all guix'ified upstreams could/would use. I think that I've seen
`.guix.scm', but also a `guix.scm' that returns a manifest, so usage
would be `guix environment -m guix.scm', and no way to build the package
itself from git.
Once Guix is blessed `the GNU System' (any day now ;-) we need to have a
a thought-through proposal to amend standards.texi anyway.
Greetings,
janneke
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug#37478] [PATCH] Support canonical guix environment -l guix.scm.,
Jan Nieuwenhuizen <=