SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This post is really to document a trial - given the sheer volume of these installs it doesn't seem to make much sense to debug it. I used the slackbuild.org directory and am not on current. I'm afraid I can't make an intelligent question out of this.
As mentioned in another thread, I was interested in seeing where enlightenment was compared to e-17, or at least that was my intent.
Per slackbuild for enlightenment-0.22.3 directions, dependencies are bullet, luajit, efl, lua, then enlightenment. I had slackbuilds for all and successfully installed packages successfully created, so they said . The lengthy compilations of bullet, efl, and enlightenment completed with a plethora of warnings, the number of which would seem to make reading logs a monumental chore but I'm taking a look.
enlightenment won't start - it didn't create its own enlightenment_start file and without that, it seems like a useless bunch of cruft dumped onto my laptop. google is strangely silent on enlightenment_start files.
I now have this bullet package onboard - maybe back to school for some physics brushups? Seems like an odd duck...
Ryan PC McQuen and Mats Tegner have been working on slackENLIGHTENMENT for several years to bring a "cutting edge Enlightenment for Slackware!". They've automated the process where all you need to do is clone the repo, cd into it, then run a script. You do need to have sbopkg set up and configured for 14.2, but otherwise, you just wait for your computer to chug along and finish installing everything for you.
Code:
git clone https://github.com/ryanpcmcquen/slackENLIGHTENMENT.git
cd slackENLIGHTENMENT/
sh enlighten-me.sh
Ryan PC McQuen and Mats Tegner have been working on slackENLIGHTENMENT for several years to bring a "cutting edge Enlightenment for Slackware!".
so I assume all the dependencies I installed are handled by sbo? bullet is a huge package, not to mention the efl libraries - gives lightweight a new meaning ...
I can't see how to clean up the mess I just installed except by reinstall - no logs (?)
so I assume all the dependencies I installed are handled by sbo? bullet is a huge package, not to mention the efl libraries - gives lightweight a new meaning ...
I can't see how to clean up the mess I just installed except by reinstall - no logs (?)
I believe all packages that are not a part of SBo are tagged with sEL. All the dependencies from SBo would be tagged like normal. But you can do an ls -ltr /var/log/packages/ to see the packages sorted with the newest ones on the bottom. Then just match up the dates to around when you ran the install and it should tell you what you can remove.
I've never really used enlightenment, I was just aware of this offering by them. If you do have problems with it, I'm sure they'd love to hear about it so they can try and fix the issues.
I believe all packages that are not a part of SBo are tagged with sEL. All the dependencies from SBo would be tagged like normal. But you can do an ls -ltr /var/log/packages/ to see the packages sorted with the newest ones on the bottom. Then just match up the dates to around when you ran the install and it should tell you what you can remove.
I didn't use SBo cuz I'm still learning, so that didn't help.
Quote:
I've never really used enlightenment, I was just aware of this offering by them. If you do have problems with it, I'm sure they'd love to hear about it so they can try and fix the issues.
I used your advice and sat watching this get built - took maybe almost an hour and had quite a few "Warnings" - this is deprecated, lib is older vers, and things which may get "clobbered" but it completed and seems to work fine so far - great job they did.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.