search

imsnif / bandwhich

Terminal bandwidth utilization tool
MIT License
10.07k stars 299 forks source link

Tracking bandwich in downstream package repositories #287

Open luzpaz opened 1 year ago

luzpaz commented 1 year ago

Currently bandwhich is available in the following package repositories:

Packaging status

TODO

cyqsimon commented 1 year ago

Yes I can put this tracking table in README. I assume this is what you want?

luzpaz commented 1 year ago

Not necessarily but IMHO helpful. This was more of an invitation to get bandwhich in to more downstream package repos

Dragon1573 commented 1 year ago

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

cyqsimon commented 1 year ago

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 ¯\_(ツ)_/¯.

cyqsimon commented 1 year ago

Seems like I was too trigger-happy to close this issue. I'll reopen it for now.

luzpaz commented 1 year ago

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 ?

Alcaro commented 1 year ago

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.

cyqsimon commented 1 year ago

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.

user9931 commented 9 months ago

please add this dll at least on github packages's zip for windows (if there's some method to pack it inside an executable, it will be great).

cyqsimon commented 9 months ago

please add this dll at least on github packages's zip for windows (if there's some method to pack it inside an executable, it will be great).

Unfortunately, I would have to say no to this request. Redistribution is not something permitted by npcap's license, which we fully intend to respect. Please download npcap directly from https://npcap.com/.

Dragon1573 commented 9 months ago

@luzpaz - Since nmap.Npcap DOES NOT able to submit to the Windows Package Manager Public Repository, this package IS DEFINITELY NOT able to submit to WPMPR. That issue should be closed as "Not planned" and labeled with Blocking-Issue and Interactive-Only-Installer .

luzpaz commented 9 months ago

@Dragon1573 Thanks for the heads-up. Please feel free to label and close the downstream ticket in that case.