Works like a charm. I didn't even expect it to compile when I saw yellow warnings saying something like "This is almost certainly NOT what you want!". :) Thanks a lot for the package.
Is actually using Connman as a network manager a viable choice? |
Thank you Ryan for work!
|
Quote:
|
I have been able to not reinstall already installed software (such as orc, gstreamer1, lua...). But now when going further the script stops with an error :
liborc is not found in /usr/lib64 (I have it in /usr/local/lib). |
Quote:
Code:
echo p | |
Quote:
|
Quote:
I have been used orc and lua for many years, for example orc is used in clementine, ffmpeg, mplayer, mpv, opencv, vlc and so on. All this is built from source and I don't make slackware packages. And then installed in a directory (/app) and links are made to /usr/local, using a very useful program called 'spill'. In this way I do not touch at all my slackware system. I think that it would be better if it was not assumed that a dependency is installed in a fixed place. In general configure scripts don't do that, and try to find where the dependency is. |
Quote:
|
For some reason I am having a Brain Fart (again)!
My Enlightenment e19 works awesome and last night I managed to create links/icons to Apps from my App tree and put them on my desktop! Now I for the life of me can not recall how! Since when does drag and drop not work?! |
Has there been any changes to this process? I am thinking of installing E19.
|
I just updated it for 1.12.3/0.19.3.
Everything should work the same, check the README. :-) |
Quote:
==================[ begin snip ]================================== checking for EDBUS... no configure: error: Package requirements (ecore >= 1.7.10 eina >= 1.7.10 dbus-1 >= 0.62) were not met: No package 'ecore' found No package 'eina' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables EDBUS_CFLAGS and EDBUS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. e_dbus: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: sbopkg: process_package: Unknown response: "p". (Y)es to continue, (N)o to abort, (R)etry the build?: sbopkg: process_package: Unknown response: "". (Y)es to continue, (N)o to abort, (R)etry the build?: sbopkg: process_package: Unknown response: "". .... (Y)es to continue, (N)o to abort, (R)etry the build?: sbopkg: process_package: Unknown response: "p". (Y)es to continue, (N)o to abort, (R)etry the build?: sbopkg: process_package: Unknown response: "". (Y)es to continue, (N)o to abort, (R)etry the build?: sbopkg: process_package: Unknown response: "". ... keeps repeating have to manually break. ==================[ end snip ]================================== I followed the instructions in the README... so ... am i missing something? |
Quote:
|
Obviously you have sbopkg installed. I messed up the build order when I switched to the SBo e_dbus. I'll have a fix out soon, just testing it now.
|
Quote:
|
All times are GMT -5. The time now is 07:59 AM. |