unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: 45368@debbugs.gnu.org
Subject: [bug#45368] [PATCH core-updates 0/3] Help2man updates
Date: Thu, 07 Jan 2021 12:00:56 +0100	[thread overview]
Message-ID: <87a6tlhuzb.fsf@gnu.org> (raw)
In-Reply-To: <87r1my10bx.fsf@gmail.com> ("Miguel Ángel Arruga Vivas"'s message of "Wed, 06 Jan 2021 17:45:06 +0100")

Hi!

Miguel Ángel Arruga Vivas <rosen644835@gmail.com> skribis:

> Sorry for the delay.  I've pushed these changes from 4343ca8ba5 to
> cfe606572d, with an additional TODO comment on 378df42fc5 about the
> not-so-translated manual pages.

Cool.

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> If the problem is just the generation of help2man’s own documentation
>> when cross-compiling, perhaps we need to add itself as a native input
>> when cross-compiling?
>
> Yup, that sounds the cleanest solution.  Nonetheless...
>
>> Anyhow that doesn’t sound like a showstopper to me.
>
> It currently isn't at all, as it says as soon as I tried:
>
>   [...] build system `perl' does not support cross builds
>
> Also, they use a LD_PRELOAD library for the translation, which seems
> suspicious too.

Hmm OK.

>> Yes, that’s a good idea.  There’s already a procedure to generate a
>> locale package IIRC.  We just have to make sure its result is properly
>> memoized so that performance doesn’t suffer.
>
> I was thinking about the implicit input "locales" and replacing it with
> a package generated based on the arguments provided to the build system,
> but I guess you're thinking about build-locale from (gnu build locale)
> and its usage for the system locales on (gnu system locale).  Should it
> be then another derivation at (guix build-system gnu) level?  Any
> pointer about this is more than welcome.

I was actually thinking about a variant of ‘make-glibc-utf8-locales’
that… never got committed?!

  https://issues.guix.gnu.org/44075#7

The patch you proposed there LGTM.  Looks like you forgot to commit it.
:-)

Ludo’.




  reply	other threads:[~2021-01-07 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 13:01 [bug#45368] [PATCH core-updates 0/3] Help2man updates Miguel Ángel Arruga Vivas
2020-12-11 22:45 ` [bug#45368] [PATCH core-updates 1/3] gnu: Add perl-gettext Miguel Ángel Arruga Vivas
2020-12-11 22:46 ` [bug#45368] [PATCH core-updates 2/3] gnu: help2man: Add optional dependencies Miguel Ángel Arruga Vivas
2020-12-11 22:47 ` [bug#45368] [PATCH core-updates 3/3] gnu: help2man: Update to 1.47.16 Miguel Ángel Arruga Vivas
2021-01-03 15:12 ` [bug#45368] [PATCH core-updates 0/3] Help2man updates Ludovic Courtès
2021-01-06 16:45   ` Miguel Ángel Arruga Vivas
2021-01-07 11:00     ` Ludovic Courtès [this message]
2021-01-07 12:52       ` Miguel Ángel Arruga Vivas
2021-02-21 22:00         ` Ludovic Courtès
2023-10-21 19:45     ` bug#45368: " 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=87a6tlhuzb.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=45368@debbugs.gnu.org \
    --cc=rosen644835@gmail.com \
    /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).