mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] readline: Install libhistory.
Date: Sat, 17 May 2025 00:02:50 +0200	[thread overview]
Message-ID: <20250516220250.221478-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250513192818.3075825-1-christian.melki@t2data.com>

Thanks, applied as 8e28eab2722677cfe03ca8596e7b41af927f15d8.

Michael

[sent from post-receive hook]

On Sat, 17 May 2025 00:02:50 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> libhistory is part of readline and provided as a separate .so.
> It's fairly small (about 1/10:th of readline and around 40k on my machine).
> I don't see a big point in ignoring to install it, esp. since there is no
> builtin option to turn off the header installs and similar.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250513192818.3075825-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/readline.make b/rules/readline.make
> index 47b05fde9000..3bbf03051f0c 100644
> --- a/rules/readline.make
> +++ b/rules/readline.make
> @@ -55,6 +55,7 @@ $(STATEDIR)/readline.targetinstall:
>  	@$(call install_fixup, readline,DESCRIPTION,missing)
>  
>  	@$(call install_lib, readline, 0, 0, 0644, libreadline)
> +	@$(call install_lib, readline, 0, 0, 0644, libhistory)
>  
>  ifdef PTXCONF_READLINE_ETC_INPUTRC
>  	@$(call install_alternative, readline, 0, 0, 0644, /etc/inputrc)



      reply	other threads:[~2025-05-16 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 19:28 [ptxdist] [PATCH] " Christian Melki
2025-05-16 22:02 ` Michael Olbrich [this message]

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=20250516220250.221478-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox