-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create packet for different distro (DEB, RPM, PKGBUILD) #1
Comments
temporary list of requirements: |
Also, it needs Wireless Tools version 30 (beta), latest stable version 29 doesn't fit. |
my understanding is Wireless Tool is "iw", and it still developed by the kernel mantainer: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git That part of the code is signed for rewrite anyway, so if you have suggestion for better library please let me know! |
No, these are different utils. Excerpt from Wikipedia article:
This project depends on old Wireless Tools currently, so rewriting it for iw seems would be OK |
i'll look into this, opefully i will have some time this weekend
2018-04-23 18:27 GMT+02:00 bam80 <notifications@github.com>:
… my understanding is Wireless Tool is "iw"
No, these are different utils. Excerpt from Wikipedia article
<https://en.wikipedia.org/wiki/Wireless_tools_for_Linux#Alternatives>:
The wireless tools package is currently considered deprecated; the
alternative being the more recent iw utility.
This project depends on old Wireless Tools currently, so rewriting it for
iw seems would be OK
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGE80ciy1edfd7Qjh43YOaYcH0KrrFk0ks5trgDngaJpZM4TeLgz>
.
|
i don't understand the statement about wireless-tools being deprecated. while the command-line debian oldoldstable (wheezy), released many years ago now, has |
My distro just ships something that stable :) |
Can it be distributed in distro-agnostic way, e.g. Flatpak? |
Yes i guess it could but i think after 3 years there should be no problem |
Commit 50befaa can b considered complete enought to be realeased on the wild
The text was updated successfully, but these errors were encountered: