From: Ricardo Wurmus <rekado@elephly.net>
To: Brett Gilio <brettg@posteo.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to modify GNOME
Date: Mon, 12 Nov 2018 07:27:43 +0100 [thread overview]
Message-ID: <87h8gmx128.fsf@elephly.net> (raw)
In-Reply-To: <87sh07qj55.fsf@posteo.net>
Hi Brett,
> Awhile back on the Guix-Devel list I proposed a question as to how to
> /best/ modify the GNOME package that gets pulled into the
> gnome-desktop-service. My reason for asking this is because a lot of
> what comes with GNOME (evince, epiphany, etc.) I do not have a use for,
> but I do not want to define an entirely new package as that would be
> quite sloppy.
Why would that be sloppy?
It is common to create variant packages by inheriting:
(define my/gnome
(package (inherit gnome)
(propagated-inputs
`(("this" ,this)
("that" ,that)))))
Can you show us what you tried?
--
Ricardo
next prev parent reply other threads:[~2018-11-12 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 23:39 How to modify GNOME Brett Gilio
2018-11-12 6:27 ` Ricardo Wurmus [this message]
2018-11-12 23:05 ` brettg
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=87h8gmx128.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=brettg@posteo.net \
--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).