Tracking bandwich in downstream package repositories
luzpaz opened this issue · comments
Yes I can put this tracking table in README. I assume this is what you want?
Not necessarily but IMHO helpful. This was more of an invitation to get bandwhich in to more downstream package repos
I think it's unable to add bandwhich
to winget
...
While downloading and installing bandwhich.exe
from official download site, this executable clould not launch without dynamic link library packet.dll
. The library should provided by the latest version (currently version 1.77
) of Npcap.
All packages that provided in winget
should be able to unattended/silent install. However, free version of Npcap is un-silent-able. Only paid version, which is Npcap OEM edition, provide silent installation. Download site of Npcap OEM should logged in with an authorized account (winget.exe
have no ability to do this, and this behaviour may violate Npcap's License).
For we can't submit bandwhich.exe
's dependency to winget
, we can't submit bandwhich.exe
it self to winget
either.
Related things
All packages that provided in
winget
should be able to unattended/silent install. However, free version of Npcap is un-silent-able. Only paid version, which is Npcap OEM edition, provide silent installation. Download site of Npcap OEM should logged in with an authorized account (winget.exe
have no ability to do this, and this behaviour may violate Npcap's License).
We ran into the same issue while setting up CI. In our case the developers of npcap were gracious enough to offer us the OEM installer, but it's strictly for CI purposes so the download link is confidential. Obviously this is not applicable for public packaging, so there's not much we can do here. Too bad I guess ¯\_(ツ)_/¯.
Seems like I was too trigger-happy to close this issue. I'll reopen it for now.
We ran into the same issue while setting up CI. In our case the developers of npcap were gracious enough to offer us the OEM installer, but it's strictly for CI purposes so the download link is confidential. Obviously this is not applicable for public packaging, so there's not much we can do here. Too bad I guess ¯_(ツ)_/¯.
Will this be an issue for getting bandwhich into Debian ?
Considering npcap is a Windows program and bandwhich uses something else on Linux, my guess is that no, that is not an issue for Debian.
Will this be an issue for getting bandwhich into Debian ?
Nope. Linux provides an API to these information via procfs, which needs no special dependencies.
Windows on the other hand... Well, Windows is Windows. I'll stop here.