all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Reuse package output for new package
@ 2022-09-13  4:27 phodina via
  2022-10-11 19:17 ` jbranso
  0 siblings, 1 reply; 2+ messages in thread
From: phodina via @ 2022-09-13  4:27 UTC (permalink / raw)
  To: help-guix

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.

There standard way is to inherit the package and add these files but that will result in rebuilt, right?

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Reuse package output for new package
  2022-09-13  4:27 Reuse package output for new package phodina via
@ 2022-10-11 19:17 ` jbranso
  0 siblings, 0 replies; 2+ messages in thread
From: jbranso @ 2022-10-11 19:17 UTC (permalink / raw)
  To: phodina, help-guix

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-10-11 19:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-13  4:27 Reuse package output for new package phodina via
2022-10-11 19:17 ` jbranso

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.