From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: harini.ramakrishnan@microsoft.com, eilong@mellanox.com,
pallavi.kadam@intel.com, dmitrym@microsoft.com,
ophirmu@mellanox.com, tbashar@mellanox.com, fady@mellanox.com,
talshn@mellanox.com, navasile@linux.microsoft.com,
ranjit.menon@intel.com, ocardona@microsoft.com,
jizh@microsoft.com, dev@dpdk.org
Subject: Re: [dpdk-dev] winget: Windows package manager
Date: Sat, 23 May 2020 04:01:17 +0300 [thread overview]
Message-ID: <20200523040117.1e90c11f@sovereign> (raw)
In-Reply-To: <4418256.1QQvuuqPaM@thomas>
On Fri, 22 May 2020 11:32:05 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> Hi,
>
> Now there is an official package manager in Windows:
> https://devblogs.microsoft.com/commandline/windows-package-manager-preview/
>
> Who wants to build a DPDK package?
>
> Where the manifest should be hosted? We used to have a directory pkg/...
AFAICT from docs and GitHub, winget is not a package manager, but more like a
console client for downloading and running readily-available installers.
It does not provide a package format or package build infrastructure like RPM,
DEB, etc do. It doesn't even have a concept of dependency or an installation
script, it cannot even download an archive and extract it. What it has is a
repository with MS-approved manifests and lots of open questions (how are
these packages verified? who maintains them? what is update procedure?).
Winget repository contains no build tools for DPDK on Windows (Ninja, Clang,
MinGW-w64; it has Python for Meson, though). These are the ones we may want
manifested first.
IMO, Chocolatey is a way to go for Windows GSG, for it is mature and its
package database contains everything needed.
--
Dmitry Kozlyuk
prev parent reply other threads:[~2020-05-23 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 9:32 Thomas Monjalon
2020-05-23 1:01 ` Dmitry Kozlyuk [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=20200523040117.1e90c11f@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=eilong@mellanox.com \
--cc=fady@mellanox.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=jizh@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=ophirmu@mellanox.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=tbashar@mellanox.com \
--cc=thomas@monjalon.net \
/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).