On 2023-06-18 05:10, Jeremy Sowden wrote:
>>> Yes, absolutely. Apologies for taking three weeks to reply.
>>>
>>> J.
>>
>> And I took two days ;)
This time took literally two weeks, haha. Dragged away by $work.
> You've gone a for a less elaborate build process for the shared library
> than I
On 2023-06-14, at 19:55:01 +0800, Blair Noctis wrote:
> On 2023-06-12 05:55, Jeremy Sowden wrote:
> > On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote:
> >> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote:
> >>> It occurs to me that it might make more sense for you to take the lead
>
On 2023-06-12 05:55, Jeremy Sowden wrote:
> On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote:
>> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote:
>>> It occurs to me that it might make more sense for you to take the lead
>>> in packaging linenoise since you have an interest in getting
On 2023-06-12 05:55, Jeremy Sowden wrote:
> On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote:
>> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote:
>>> It occurs to me that it might make more sense for you to take the lead
>>> in packaging linenoise since you have an interest in getting
On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote:
> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote:
> > It occurs to me that it might make more sense for you to take the lead
> > in packaging linenoise since you have an interest in getting it into
> > Debian. Would you like me to
On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote:
> It occurs to me that it might make more sense for you to take the lead
> in packaging linenoise since you have an interest in getting it into
> Debian. Would you like me to transfer ownership of the ITP bug to you?
> Happy to lend a hand
On 2023-05-14, at 15:00:06 +0800, Blair Noctis wrote:
> On 2023/5/14 03:24, Jeremy Sowden wrote:
> > I came across linenoise because of a request to support it in nftables.
> > The request came from someone who wanted to install nftables in a
> > resource-constrained environment where the existing
On 2023/5/14 03:24, Jeremy Sowden wrote:
> I came across linenoise because of a request to support it in nftables.
> The request came from someone who wanted to install nftables in a
> resource-constrained environment where the existing libreadline support
> was too heavyweight. In the case of
I came across linenoise because of a request to support it in nftables.
The request came from someone who wanted to install nftables in a
resource-constrained environment where the existing libreadline support
was too heavyweight. In the case of osquery, would it possible to go
the other way? Do
On 2023/5/9 04:20, Jeremy Sowden wrote:
> Thanks for the offer. :) I've cloned the osquery repo and it appears to
> use the C++ Linenoise NG fork:
No problem ;) It uses the -ng fork, but the fork's repo was archived in 2017,
which leads me back to the original. And
> which is what I started
On 2023-05-01, at 04:09:16 +0800, Blair Noctis wrote:
> It's been a few years since this ITP was filed. Do you still plan to
> package it? I'm packaging osquery which depends on this. Happy to
> help ;)
Thanks for the offer. :) I've cloned the osquery repo and it appears to
use the C++ Linenoise
Hi Jeremy,
It's been a few years since this ITP was filed. Do you still plan to package it?
I'm packaging osquery which depends on this. Happy to help ;)
--
Sdrager,
Blair Noctis
OpenPGP_signature
Description: OpenPGP digital signature
Package: wnpp
Severity: wishlist
Owner: Jeremy Sowden
* Package name: linenoise
Version : 1.0+git20180718.4a961c010872
Upstream Author : Salvatore Sanfilippo
* URL : https://github.com/antirez/linenoise
* License : BSD-2-Clause
Programming Lang: C
13 matches
Mail list logo
