lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2wmh8u7j2.fsf@gmail.com>
Date: Tue, 12 Nov 2024 09:26:57 +0000
From: Donald Hunter <donald.hunter@...il.com>
To: Jan Stancek <jstancek@...hat.com>
Cc: Jakub Kicinski <kuba@...nel.org>,  pabeni@...hat.com,
  davem@...emloft.net,  edumazet@...gle.com,  horms@...nel.org,
  netdev@...r.kernel.org,  linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] tools: ynl: two patches to ease building with rpmbuild

Jan Stancek <jstancek@...hat.com> writes:

> On Tue, Nov 12, 2024 at 12:52 AM Jakub Kicinski <kuba@...nel.org> wrote:
>>
>> One thing I keep thinking about, maybe you already read this, is to
>> add  some sort of spec search path and install the specs under /usr.
>> So the user can simply say --family X on the CLI without specifying
>> the fs full path to the YAML file. Would you be willing to send a patch
>> for this?
>
> I can look at adding--family option (atm. for running ynl in-tree).
>
> One thing I wasn't sure about (due to lacking install target) was whether
> you intend to run ynl always from linux tree.
>
> If you're open to adding 'install' target, I think that should be something
> to look at as well. It would make packaging less fragile, as I'm currently
> handling all that on spec side.

Hi Jan,

I am happy to work with you on adding an install target, plus some other
UX improvements like --family.

Thanks,
Donald.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ