From: jbranso@dismail.de
To: "phodina" <phodina@protonmail.com>, "help-guix" <help-guix@gnu.org>
Subject: Re: Reuse package output for new package
Date: Tue, 11 Oct 2022 19:17:19 +0000 [thread overview]
Message-ID: <1d2c666a416f422bff722fd35cfcaef6@dismail.de> (raw)
In-Reply-To: <mbC9ENU0zZNm23imdkx9uMPsKxXQx3A00B4rXg3WmnfO9WEQXAnexNm2pojdCQNTWVV6H3_ht5vKrIx5qquZ5BsZ2w1U8xdl7r5IwbXHsvc=@protonmail.com>
September 13, 2022 12:28 AM, "phodina via" <help-guix@gnu.org> wrote:
> Hi,
>
> is there a way to create a new package by reusing the output of the original derivation and just
> add files to the new package into the new output?
>
> The usecase is PhotoGimp [1] which is set of files which are added to an already built gimp
> package.
>
Huh, I've never heard of this. But that's an awesome use case!
> There standard way is to inherit the package and add these files but that will result in rebuilt,
> right?
I believe that it would, but I'm not the genius guix hacker that
*insert the name of a genius guix hacker here*.
> Alternative idea is to use copy-build-system and copy the already created package files into the
> output. Then just add additional files.
>
> However, there's also a draw back if the original package contains hardcoded variable. But this
> would be only problem if I specify something in the #:phases, correct?
>
> The main idea here is to save the computing resources on packages that take long time and their
> behviour can be changed by plugins/config files etc.
>
> Of course the simplest way to use [1] it is to unpack the content of the home dir but IMHO that's
> not the correct way how to package this program.
>
> [1] https://github.com/Diolinux/PhotoGIMP
>
> ----
> Petr
I say give one of your methods a try. Post some code back here when you run into
trouble. :)
Joshua
prev parent reply other threads:[~2022-10-11 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 4:27 Reuse package output for new package phodina via
2022-10-11 19:17 ` jbranso [this message]
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=1d2c666a416f422bff722fd35cfcaef6@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=phodina@protonmail.com \
/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.