From: Donald Hunter <donald.hunter@gmail.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: stfomichev@gmail.com, kuba@kernel.org, jdamato@fastly.com,
pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] tools: ynl: add main install target
Date: Mon, 16 Dec 2024 14:09:17 +0000 [thread overview]
Message-ID: <m21py790tu.fsf@gmail.com> (raw)
In-Reply-To: <6e41a47b9ea5ede099d9ae7768fbceb553c6614d.1734345017.git.jstancek@redhat.com> (Jan Stancek's message of "Mon, 16 Dec 2024 11:41:44 +0100")
Jan Stancek <jstancek@redhat.com> writes:
> This will install C library, specs, rsts and pyynl. The initial
> structure is:
>
> $ mkdir /tmp/myroot
> $ make DESTDIR=/tmp/myroot install
>
> /usr
> /usr/lib64
> /usr/lib64/libynl.a
> /usr/lib/python3.XX/site-packages/pyynl/*
> /usr/lib/python3.XX/site-packages/pyynl-0.0.1.dist-info/*
> /usr/bin
> /usr/bin/ynl
> /usr/bin/ynl-ethtool
> /usr/bin/ynl-gen-c
> /usr/bin/ynl-gen-rst
> /usr/include/ynl/*.h
> /usr/share
> /usr/share/doc
> /usr/share/doc/ynl
> /usr/share/doc/ynl/*.rst
> /usr/share/ynl
> /usr/share/ynl/genetlink-c.yaml
> /usr/share/ynl/genetlink-legacy.yaml
> /usr/share/ynl/genetlink.yaml
> /usr/share/ynl/netlink-raw.yaml
> /usr/share/ynl/specs
> /usr/share/ynl/specs/devlink.yaml
> /usr/share/ynl/specs/dpll.yaml
> /usr/share/ynl/specs/ethtool.yaml
> /usr/share/ynl/specs/fou.yaml
> /usr/share/ynl/specs/handshake.yaml
> /usr/share/ynl/specs/mptcp_pm.yaml
> /usr/share/ynl/specs/netdev.yaml
> /usr/share/ynl/specs/net_shaper.yaml
> /usr/share/ynl/specs/nfsd.yaml
> /usr/share/ynl/specs/nftables.yaml
> /usr/share/ynl/specs/nlctrl.yaml
> /usr/share/ynl/specs/ovs_datapath.yaml
> /usr/share/ynl/specs/ovs_flow.yaml
> /usr/share/ynl/specs/ovs_vport.yaml
> /usr/share/ynl/specs/rt_addr.yaml
> /usr/share/ynl/specs/rt_link.yaml
> /usr/share/ynl/specs/rt_neigh.yaml
> /usr/share/ynl/specs/rt_route.yaml
> /usr/share/ynl/specs/rt_rule.yaml
> /usr/share/ynl/specs/tcp_metrics.yaml
> /usr/share/ynl/specs/tc.yaml
> /usr/share/ynl/specs/team.yaml
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
next prev parent reply other threads:[~2024-12-16 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 10:41 [PATCH v3 0/4] tools: ynl: add install target Jan Stancek
2024-12-16 10:41 ` [PATCH v3 1/4] tools: ynl: move python code to separate sub-directory Jan Stancek
2024-12-16 13:45 ` Donald Hunter
2024-12-16 10:41 ` [PATCH v3 2/4] tools: ynl: add initial pyproject.toml for packaging Jan Stancek
2024-12-16 13:52 ` Donald Hunter
2025-01-06 11:57 ` Jan Stancek
2024-12-16 10:41 ` [PATCH v3 3/4] tools: ynl: add install target for generated content Jan Stancek
2024-12-16 14:01 ` Donald Hunter
2025-01-06 11:35 ` Jan Stancek
2024-12-16 10:41 ` [PATCH v3 4/4] tools: ynl: add main install target Jan Stancek
2024-12-16 14:09 ` Donald Hunter [this message]
2024-12-16 22:58 ` Joe Damato
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=m21py790tu.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@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.
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 NNTP newsgroup(s).