You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was getting an install error in Debian when running sudo make install due to an incorrect xfce panel plugins directory ("directory does not exist" error).
I'm running Debian Jessie, in which xfce4-panel looks for plugins in /usr/lib/xfce4/panel-plugins
In your makefile, you specify plugin directory as: /usr/lib/xfce4/panel/plugins
Relevant file in your repo: xfce4-i3-workspaces-plugin/panel-plugin/Makefile.am, lines 14 and 47.
I just checked on my Arch installation and I have both the panel/plugins/ and panel-plugins directory under /usr/lib/xfce4. However, based on the howto on panel plugins you linked, I think I should convert my plugin to a proper external one following the instruction on that page. The problem is that it might break compatibility with XFCE4 installations that are < 4.4.
Hi, first off thanks for the great package!
I was getting an install error in Debian when running
sudo make install
due to an incorrect xfce panel plugins directory ("directory does not exist" error).I'm running Debian Jessie, in which xfce4-panel looks for plugins in
/usr/lib/xfce4/panel-plugins
In your makefile, you specify plugin directory as:
/usr/lib/xfce4/panel/plugins
Relevant file in your repo:
xfce4-i3-workspaces-plugin/panel-plugin/Makefile.am
, lines 14 and 47.This does appear to be distro dependent. Arch Linux uses
/usr/lib/xfce4/panel/plugins
(see here: https://www.archlinux.org/packages/extra/i686/xfce4-panel/files/) while Debian uses/usr/lib/xfce4/panel-plugins
judging by my very vanilla installation.Based on Xfce 4.4 documentation, they use the
/usr/lib/xfce4/panel-plugins
directory structure, so maybe that could be default https://wiki.xfce.org/dev/howto/panel_pluginsEDIT: Best way to fix for Debian is to symlink /usr/lib/xfce4/panel/plugins to /usr/lib/xfce4/panel-plugins
The text was updated successfully, but these errors were encountered: