unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Dariqq <dariqq@posteo.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	73028@debbugs.gnu.org,
	"Florian Pelz" <pelzflorian@pelzflorian.de>
Subject: [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system.
Date: Thu, 12 Sep 2024 07:12:22 +0000	[thread overview]
Message-ID: <c900bef7-915f-4e51-8de6-3f1665075240@posteo.net> (raw)
In-Reply-To: <87jzfhy9jf.fsf@gmail.com>

Hi,

On 12.09.24 02:56, Maxim Cournoyer wrote:
> Hi Dariqq,
> 
> Dariqq <dariqq@posteo.net> writes:
> 
>> Hi Maxim,
>>
>>
>> On 11.09.24 08:09, Maxim Cournoyer wrote:
>>> Hi Dariqq,
>>> Dariqq <dariqq@posteo.net> writes:
>>> That strikes me as odd; is it useful in practice?  Otherwise I'd
>>> rather
>>> we keep it undocumented, so that it can be removed without notice in a
>>> future cleanup (in a 'private API' way).
>>>
>>
>> Ludovic asked me to document the new parameter, so I added something
>> for the current behaviour.
>>
>> Because I don't think the message arrived at the original issue, i
>> copied below. I hope this is ok:
>>
>>> On 04.09.24 16:02, Ludovic Courtès wrote:
>>> AFAICS these changes are not sufficient because ‘configure’ in
>>> meson-build-system.scm does not honor #:out-of-source? (unlike
>>> ‘configure’ in gnu-build-system.scm).
>>> So if I’m not mistaken, you’ll need to change ‘configure’ as well.
>>> You can also update doc/guix.texi under “Build Systems” to mention
>>> this
>>> parameter.
>>> Last: ‘guix refresh -l meson’ shows that this is almost a
>>> world-rebuild
>>> change (23K dependents), so we’ll need to have this change in a separate
>>> branch.
>>> Could you send an updated patch?
>>> Thanks,
>>> Ludo’.
>>
>> I have sent this patch for the documentation part but am still unsure
>> what is meant by *sufficient* because meson cannot do in source
>> builds.
> 
> I'm still out of context; is there an original bug number to refer to to
> better understand what was the root problem being addressed?
> 

Sorry I should have added that. The problem I was trying to solve is 
https://issues.guix.gnu.org/70999.

TLDR is that meson-build-system was failing to find and install license 
files for many packages because it would search for licenses in the 
build directory rather than the source directory. (which might be 
against the terms of the license)

>> Maybe it should not be an option at all and instead be #t
>> unconditionally in 'install-license-files phase in meson-build-system?
> 
> Given most build phases of the gnu-build-system, which support
> #:out-of-source? are reused in the meson-build-system, this argument
> needs to be set to #t (which it currently is).  But perhaps there's a
> way to hide it from the users, perhaps via the 'private-keywords'
> variable defined in the 'lower' procedure of the (guix build-system
> meson) module (I haven't tested).
> 

Something like that might be a better solution. I am not sure how these 
'private-keywords' work: It looks like #:meson is one but you can 
definitly override the default meson being used. Also the 
private-arguments seem to get stripped from the arguments in the bag 
(not sure what that is exactly) so they might not be passed to the build 
phases


Would such a change require rebuilding (basically) everything given that 
currently all packages are already built with #:out-of-source? set to 
the default value #t?





  reply	other threads:[~2024-09-12  7:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 16:26 [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system Dariqq
2024-09-11  6:09 ` Maxim Cournoyer
2024-09-11 15:18   ` Dariqq
2024-09-12  0:56     ` Maxim Cournoyer
2024-09-12  7:12       ` Dariqq [this message]
2024-09-12 12:02         ` Maxim Cournoyer
2024-09-12 19:19           ` Dariqq
2024-09-14 13:41             ` Maxim Cournoyer
2024-09-19 14:07               ` Dariqq
2024-09-22  5:57                 ` Maxim Cournoyer

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=c900bef7-915f-4e51-8de6-3f1665075240@posteo.net \
    --to=dariqq@posteo.net \
    --cc=73028@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=pelzflorian@pelzflorian.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).