From: Vivien Kraus via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 62181-done@debbugs.gnu.org
Subject: bug#62181: [PATCH v2 1/2] gnu: gnulib: Reset the shebangs.
Date: Sat, 18 Mar 2023 10:06:16 +0100 [thread overview]
Message-ID: <3880c33b6100a0c0ad8839459311c5abebd29efe.camel@planete-kraus.eu> (raw)
In-Reply-To: <87fsa3vylf.fsf@gnu.org>
Hi!
Le vendredi 17 mars 2023 à 22:48 +0100, Ludovic Courtès a écrit :
> > * gnu/packages/tls.scm (guile-gnutls) [phase patch-more-shebangs]:
> > Fix how
> > autogen.sh invokes gnulib-tool, and how configure.ac invokes git-
> > version-gen,
> > so as not to rely on shebangs.
>
> [...]
>
> > + (substitute* "autogen.sh"
> > + (("\\$gnulib_tool \\$gnulib_tool_options")
> > + "sh $gnulib_tool $gnulib_tool_options"))
>
> … this is still needed: GNULIB/bin/gnulib-tool, which has a correct
> shebang, is *not* used, and instead GNULIB/src/gnulib/gnulib-tool is
> used.
>
> Should we remove GNULIB/bin/gnulib-tool? Or should we remove the
> other
> one?
If we could have different outputs, one for bin/gnulib-tool and one for
the gnulib source, then it would be better: the default output would
retain no references, and the :bin output would only need a bash-
minimal to run gnulib-tool. So packages that call gnulib-tool directly
would add both outputs as native-inputs, and packages that use
bootstrap.conf would only need the default output.
Would that help solve the problem introduced by the bash-minimal
reference?
Anyway, I’m not sure the copy-build-system allows for different
outputs.
What do you think?
Vivien
next prev parent reply other threads:[~2023-03-18 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 8:34 bug#62181: Gnulib package keeps references to clisp, Python, Perl, and Bash Ludovic Courtès
2023-03-14 10:36 ` bug#62181: [PATCH 0/2] " Vivien Kraus via Bug reports for GNU Guix
2023-03-14 8:58 ` bug#62181: [PATCH 1/2] gnu: gnulib: Reset the shebangs Vivien Kraus via Bug reports for GNU Guix
2023-03-16 10:43 ` Ludovic Courtès
2023-03-14 10:33 ` bug#62181: [PATCH 2/2] gnu: guile-gnutls: Do not expect gnulib shebangs to work Vivien Kraus via Bug reports for GNU Guix
2023-03-16 10:48 ` Ludovic Courtès
2023-03-16 10:56 ` Vivien Kraus via Bug reports for GNU Guix
2023-03-16 10:41 ` bug#62181: [PATCH 0/2] Re: bug#62181: Gnulib package keeps references to clisp, Python, Perl, and Bash Ludovic Courtès
2023-03-16 10:54 ` Vivien Kraus via Bug reports for GNU Guix
2023-03-16 19:41 ` bug#62181: [PATCH v2 0/2] Drop references to other store items in /src, with better style Vivien Kraus via Bug reports for GNU Guix
2023-03-14 8:58 ` bug#62181: [PATCH v2 1/2] gnu: gnulib: Reset the shebangs Vivien Kraus via Bug reports for GNU Guix
2023-03-17 21:48 ` Ludovic Courtès
2023-03-18 9:06 ` Vivien Kraus via Bug reports for GNU Guix [this message]
2023-03-14 10:33 ` bug#62181: [PATCH v2 2/2] gnu: guile-gnutls: Do not expect gnulib shebangs to work Vivien Kraus via Bug reports for GNU Guix
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=3880c33b6100a0c0ad8839459311c5abebd29efe.camel@planete-kraus.eu \
--to=bug-guix@gnu.org \
--cc=62181-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=vivien@planete-kraus.eu \
/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).