What about geeqie ?
|
For the time being, you can use the SlackBuild to build your own.
I like geeqie a lot, it has several improvements over gqview. I hope it will become part of mainstream Slackware one day :) |
Quote:
|
I haven't tried it yet. Will give it a shot next weekend and will post the experience.
|
Done
It's done, Pat has included geeqie in current and removed gqview :)
|
Yep, good news :)
|
Nice ... I tried it, got some free time finally. Seems good. But GQView is still my favorite.
|
Quote:
|
Quote:
Quote:
So what is it that you're missing in geeqie? |
Quote:
|
One more happy person that geegie is being added. I don't care for gqview and started with geegie a few months ago. I take lots of photos of grandkids and it works great for me. Thanks for adding it.
john |
slightly offtopic but since we're talking about geeqie I decided to try it myself. First, I compiled it using SBo script and later using the official slackbuild (one in -current). Both of them put geeqie libraries in /usr/lib even for 64-bit (I'm using Slackware64-13.0 with multilib). Even the 64-bit geeqie package in current has libraries in /usr/lib. I'm not an expert so may be someone can explain it.
|
Since I'm the author of the SlackBuild for geeqie on SBo, I guess I owe you an explanation ;)
The "libraries" are installed in /usr/lib even in the 64-bits version, as they are not really "libraries", but just some shell scripts. Since shell scripts do not differ between 32-bits & 64-bits, they can stay in /usr/lib for both versions. The same situation occurs with some other packages, even some included in standard Slackware64. |
Quote:
|
Those shell scripts should go into /usr/libexec -maybe adjusting the configuration options would accomplish it.
|
All times are GMT -5. The time now is 08:52 AM. |