all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Felix Lechner <felix.lechner@lease-up.com>, guix-devel@gnu.org
Subject: Re: Mystery of missing 'install' phase in guile-build-system
Date: Thu, 26 Sep 2024 23:26:36 +0200	[thread overview]
Message-ID: <5b2cf647-cc52-98b7-f4d4-6c592ad94b06@elenq.tech> (raw)
In-Reply-To: <87zfnu6rvc.fsf@lease-up.com>

Hi,

On 2024-09-26 23:13, Felix Lechner via Development of GNU Guix and the 
GNU System distribution. wrote:
> Hi,
> 
> A piece of software of mine using the guile-build-system runs tests
> after the 'install' phase.  A recent system update failed because there
> is no such phase.
> 
> Looking at the Guix source code, the 'install' phase never existed.
> Shouldn't every build system have that phase?
> 
> Why did the same package definition work three months ago?
> 
> Thanks for helping with this mystery!
> 
> Kind regards
> Felix
> 

The fast and simple answer is that the 'install phase is not mandatory. 
The build system defines which of the steps it uses and how, they don't 
need to have specific names.

A different question is how does the Guile build system find which files 
to install and where to install them. :)

It's a little bit late so I can't check it deeper but you should find 
how it is done in: guix/build/guile-build-system.scm

Good question btw!
Cheers,
Ekaitz


  reply	other threads:[~2024-09-26 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 21:13 Mystery of missing 'install' phase in guile-build-system Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-09-26 21:26 ` Ekaitz Zarraga [this message]
2024-09-27 16:00   ` Luis Felipe
2024-10-07 21:10   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.

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=5b2cf647-cc52-98b7-f4d4-6c592ad94b06@elenq.tech \
    --to=ekaitz@elenq.tech \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@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.