From: "brettg@posteo.net" <brettg@posteo.net>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Scheme package installation script
Date: Thu, 17 Jan 2019 21:28:51 -0600 [thread overview]
Message-ID: <rpoihcn9tt4ng409bpaokjq7.1547782116085@email.lge.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Doh! Yes I knew this. I forgot about that. Thank you a ton.
Sent from my Sprint Phone.
------ Original message------From: Carlo ZancanaroDate: Thu, Jan 17, 2019 9:24 PMTo: brettg@posteo.net;Cc: help-guix;Subject:Re: Scheme package installation script
Hey Brett!
On Fri, Jan 18 2019, brettg@posteo.net wrote:
> 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?
I think gnome is a similar sort of meta-package. It has the
following structure:
(define-public gnome
(package
(name "gnome")
(version (package-version gnome-shell))
(source #f)
(build-system trivial-build-system)
(arguments '(#:builder (begin (mkdir %output) #t)))
(propagated-inputs
... lots of inputs here ...)
(synopsis "The GNU desktop environment")
(home-page "https://www.gnome.org/")
(description
"GNOME is the graphical desktop for GNU. It includes a wide
variety of
applications for browsing the web, editing text and images,
creating
documents and diagrams, playing media, scanning, and much more.")
(license license:gpl2+)))
I assume that will work for you, too.
Carlo
[-- Attachment #2: Type: text/html, Size: 2035 bytes --]
next reply other threads:[~2019-01-18 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 3:28 brettg [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-18 2:47 Scheme package installation script brettg
2019-01-18 3:23 ` Carlo Zancanaro
2019-01-18 7:55 ` Gábor Boskovits
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=rpoihcn9tt4ng409bpaokjq7.1547782116085@email.lge.com \
--to=brettg@posteo.net \
--cc=carlo@zancanaro.id.au \
--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.