all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, 65351@debbugs.gnu.org
Cc: "\(" <paren@disroot.org>
Subject: [bug#65351] [PATCH v2 1/7] gnu: cgit: Make git-source a native input.
Date: Wed, 04 Oct 2023 00:27:01 +0100	[thread overview]
Message-ID: <87o7hf1e4a.fsf@systemreboot.net> (raw)
In-Reply-To: <32d53de38b947de59749c6c63e4bf091e8bb4abf.camel@gmail.com>


Hi Liliana,

>> > This patch is broken and it doesn't appear to get fixed in 4/7.  If
>> > you want git-source to be in native-inputs, you need to use (or
>> > native-inputs inputs).
>> 
>> I'm not sure what you mean. I am able to build both cgit and cgit-
>> pink on my machine. The QA system also agrees with
>> me. https://qa.guix.gnu.org/issue/65351
> CI doesn't do cross-builds, it does simulated native builds, so you
> won't see the issue.

Ah, I see what you mean now. I have deleted the patch making git-source a
native input. I guess it's ok to leave it as an input since it doesn't
really matter in this case.

> Indeed, there is precedent.  However, when moving stuff around, such as
> in 1, you also need to update the dependent stuff, which you haven't
> done and which also causes more noise along the line.  In this series,
> you need three commits to basically get input handling "correct".  The
> intermediate commits are duds in terms of guix time-machine, which
> isn't great.

I have reworked the patchset into only 3 patches now. Let me know if
this is ok.

>> > In 7, you might want to use /bin/sh if the compatibility is meant
>> > for stuff that actually lands in the store.
>> 
>> /bin/sh doesn't work. I have tried. If I remember correctly, this is
>> to do with how the SHELL_PATH gets substituted into generated
>> scripts.
> For the record, what kind of generated scripts are we talking here? 
> Invoked at build time or sent to the store?

The cgit Makefiles are tightly coupled with git source code and the git
Makefiles. The generated scripts are wrapper scripts for git binaries
like git-shell, git-upload-archive, git-upload-pack, etc. As far as I
can tell, cgit does not use them at all. They are neither invoked at
build time nor are they sent to the store. They are only invoked at test
time, and that fails if you have SHELL_PATH=sh. This specifically
bothers only cgit-pink and not cgit since cgit does not run the test
suite.

SHELL_PATH is also directly executed as a shell in some parts of the
Makefile. For example,

--8<---------------cut here---------------start------------->8---
GIT-VERSION-FILE: FORCE
	@$(SHELL_PATH) ./GIT-VERSION-GEN
--8<---------------cut here---------------end--------------->8---

and

--8<---------------cut here---------------start------------->8---
config-list.h: Documentation/*config.txt Documentation/config/*.txt
	$(QUIET_GEN)$(SHELL_PATH) ./generate-configlist.sh >$@
--8<---------------cut here---------------end--------------->8---

That's why SHELL_PATH=/bin/sh fails since /bin/sh does not exist in the
build environment.

A v3 patchset follows.

Cheers!




  reply	other threads:[~2023-10-03 23:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 13:51 [bug#65351] [PATCH] gnu: Add cgit-pink Arun Isaac
2023-08-17 19:00 ` Liliana Marie Prikler
2023-08-17 19:16   ` ( via Guix-patches via
2023-08-17 20:20     ` Liliana Marie Prikler
2023-08-17 20:53       ` ( via Guix-patches via
2023-08-18  9:03         ` [bug#65351] [PATCH 1/7] gnu: cgit: Make git-source a native input Arun Isaac
2023-08-18 17:03           ` Liliana Marie Prikler
2023-08-21 14:22             ` Arun Isaac
2023-08-18  9:03         ` [bug#65351] [PATCH 2/7] gnu: cgit: Make bzip2, gzip and xz inputs Arun Isaac
2023-08-18  9:03         ` [bug#65351] [PATCH 3/7] gnu: cgit: Do not return #t from custom phases Arun Isaac
2023-08-18  9:03         ` [bug#65351] [PATCH 4/7] gnu: cgit: Use G-expressions Arun Isaac
2023-08-18 17:04           ` Liliana Marie Prikler
2023-08-21 14:27             ` Arun Isaac
2023-08-18 17:06           ` Liliana Marie Prikler
2023-08-21 14:26             ` Arun Isaac
2023-08-21 17:07               ` Liliana Marie Prikler
2023-08-21 17:13               ` ( via Guix-patches via
2023-08-24 10:59                 ` Arun Isaac
2023-08-18  9:03         ` [bug#65351] [PATCH 5/7] gnu: cgit: Use cc-for-target Arun Isaac
2023-08-18  9:03         ` [bug#65351] [PATCH 6/7] gnu: cgit: Add bash-minimal to inputs Arun Isaac
2023-08-18  9:03         ` [bug#65351] [PATCH 7/7] gnu: Add cgit-pink Arun Isaac
2023-08-18  9:00   ` [bug#65351] [PATCH] " Arun Isaac
2023-09-04  9:02 ` [bug#65351] [PATCH v2 0/7] " Arun Isaac
2023-09-04  9:02   ` [bug#65351] [PATCH v2 1/7] gnu: cgit: Make git-source a native input Arun Isaac
2023-09-04 17:09     ` Liliana Marie Prikler
2023-09-28  7:12       ` Arun Isaac
2023-09-28 16:16         ` Liliana Marie Prikler
2023-10-03 23:27           ` Arun Isaac [this message]
2023-09-04  9:02   ` [bug#65351] [PATCH v2 2/7] gnu: cgit: Make bzip2, gzip and xz inputs Arun Isaac
2023-09-04  9:02   ` [bug#65351] [PATCH v2 3/7] gnu: cgit: Do not return #t from custom phases Arun Isaac
2023-09-04  9:02   ` [bug#65351] [PATCH v2 4/7] gnu: cgit: Use G-expressions Arun Isaac
2023-09-04  9:02   ` [bug#65351] [PATCH v2 5/7] gnu: cgit: Add bash-minimal to inputs Arun Isaac
2023-09-04  9:02   ` [bug#65351] [PATCH v2 6/7] gnu: cgit: Use cc-for-target Arun Isaac
2023-09-04  9:02   ` [bug#65351] [PATCH v2 7/7] gnu: Add cgit-pink Arun Isaac
2023-10-03 23:59 ` [bug#65351] [PATCH v3 1/3] gnu: cgit: Update package style Arun Isaac
2023-10-03 23:59   ` [bug#65351] [PATCH v3 2/3] gnu: cgit: Fix cross compilation Arun Isaac
2023-10-05 12:48     ` [bug#65351] [PATCH] gnu: Add cgit-pink Ludovic Courtès
2023-10-05 16:39       ` bug#65351: " Arun Isaac
2023-10-03 23:59   ` [bug#65351] [PATCH v3 3/3] " Arun Isaac

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=87o7hf1e4a.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=65351@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=paren@disroot.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.