You are not logged in.
I'm using i3 wm and would like to install this package: netctl-gui
and use it's Qt frontend for netctl but not install the KDE packages.
Would that be possible?
Last edited by hamhock (2018-02-24 16:14:07)
Offline
Yes.
Somehow I doubt that's your actual question, though.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Somehow I doubt that's your actual question, though.
I should have said, If it's possible, but a hassle, I won't bother
# note: another user of the laptop needs an easy to use gui for connecting to wifi, i.e., no typing commands in a terminal
another possibility is if I can get a script i have to launch from an i3 keybinding.
the wifi.sh works when i run it in xterm,
wifi.sh
#!/bin/bash
sudo iw dev wlp1s0 scan | grep SSID
sudo wifi-menu -obut when I run it via bindsym, the wifi-menu is graphically messed up and confusing - a lot different visually than when just run in terminal.
~.i3/config
bindsym $sup+w exec xterm -hold -e ~/bin/wifi.shLast edited by hamhock (2018-02-20 04:22:51)
Offline
You can automate the process of connecting your preferred wifi network, to avoid any manual connections.
Or If you need to choose network manually everytime, there are other network managers with gtk based gui, like networkmanager/wicd/connman/wifi-radar etc.
Arch is home!
https://github.com/Docbroke
Offline
ok, using 'uxterm' instead of 'xterm' solved the weird display issue.
~.i3/config
bindsym $sup+w exec uxterm -hold -e ~/bin/wifi.shwould still like to know how to install netctl-gui without the KDE packages - the other user user (wife) may prefer it.
Offline
You can automate the process of connecting your preferred wifi network, to avoid any manual connections.
Or If you need to choose network manually everytime, there are other network managers with gtk based gui, like networkmanager/wicd/connman/wifi-radar etc.
yes, netctl does a great job of automatically switching to preferred wifi networks.
i just need a gui interface to it occassionlly rather than installing an entirely new network manager.
Offline
I should have said, If it's possible, but a hassle, I won't bother
That's not at all what I was implying. It's quite trivial: install the package.
I don't get your question, there are no runtime KDE dependencies for netctl-gui. So can you install netctl-gui without KDE dependencies: yes. So why are you posting here instead of just doing so? I gather you ran into some sort of problem trying to build/install it, but as you've not told us anything about that problem, we can't possibly help.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I don't get your question, there are no runtime KDE dependencies for netctl-gui. So can you install netctl-gui without KDE dependencies: yes. So why are you posting here instead of just doing so? I gather you ran into some sort of problem trying to build/install it, but as you've not told us anything about that problem, we can't possibly help.
when I ran makepkg to install netctl-gui-qt4, I became concerned about the installation of kdelibs and a few other KDE packages. so I stopped the install at that point.
warning: dependency cycle detected:
warning: phonon-qt4-gstreamer will be installed before its phonon-qt4 dependencyPackages (17) aspell-0.60.6.1-5 attica-qt4-0.4.2-4 docbook-xml-4.5-6 docbook-xsl-1.79.2-4 enchant-2.2.1-1 hspell-1.4-1 jsoncpp-1.8.4-2 libdbusmenu-qt4-0.9.3+16.04.20160218-1 libvoikko-4.1.1-1 media-player-info-23-1
phonon-qt4-4.9.1-5 phonon-qt4-gstreamer-4.9.0-4 polkit-qt4-0.112.0+git20180107-1 rhash-1.3.5-2 automoc4-0.9.88-8 cmake-3.10.2-2 kdelibs-4.14.38-3
this laptop is a converted chromebook with a 15GB internal SSD, so i'm always concerned about installing more than I really need.
Offline
kde packages are only a makedep not a runtime dependency. So to use the PKGBUILD as is you'd need to temporarily install a few kde packages, but they can be removed immediately after the build (e.g., use `makepkg -ris`).
Alternatively, if you cant tolerate those being installed even temporarily, I suspect the plasma/kde build deps are only required for other packages in that PKGBUILD. So you could edit the PKGBUILD to be netctl-gui only and never need to install any kde packages.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Offline
Thank you - I think I'll install it later today.
Anybody annoyed if I change this to Qt5?
I wouldn't - do you have plans to change to Qt5 in the near future?
Offline
kde packages are only a makedep not a runtime dependency. So to use the PKGBUILD as is you'd need to temporarily install a few kde packages, but they can be removed immediately after the build (e.g., use `makepkg -ris`).
thank you - I'll give it a try and compare with qnetctl-git.
Offline
I'll upload a Qt5 version in a couple of hours.
I also need to revisit the code, I've not used it for ages ;-)
Offline
I installed both netctl-gui and qnetctl, but was unable to get them to work. I'm sure it was due more to my ineptitude than the quality of the packagaes.
Instead of spending more time on trying to figure them out, I wrote a simple script to solve my situation.
netctl-auto works fine for first 2 scenarios, but not #3
1. exisiting profile: connects automatically to best existing profile
2. new profile: wifi-menu -o works well for creating new profiles
3. existing profile with new password: this was an issue for my wife (without learning how to edit /etc/netctl/profile to update a password)
I wrote this script to deal with issue #3 as well as an alternative to #2 (wifi-menu) if know the SSID want to connect to.
alias wifi='sudo wifi.sh '
wifi ssid passkey#!/bin/bash
ssid=$1
pass=$2
cat > /etc/netctl/$ssid <<- EOF
Interface=wlp0s29u1u1
Connection=wireless
Security=wpa
IP=dhcp
ESSID=$ssid
key=$pass
EOFso this is working for my situation while staying with netctl, but i'm open to other alternatives or advice on my script.
Last edited by hamhock (2018-02-23 18:04:45)
Offline