What about geeqie ?

Thom1b · 03-06-2010, 12:12 AM

Hi,

Slackware includes gqview, a pictures viewer not maintained since 2006. Geeqie is a fork of gqview and the first stable version is out since about 1 month, and it seems to be stable and good.
So what about remove gqview and add geeqie in next slackware ?

niels.horn · 03-06-2010, 07:07 AM

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

Thom1b · 03-07-2010, 01:46 AM

Quote:

Originally Posted by niels.horn

For the time being, you can use the SlackBuild to build your own.

Thanks, I know that

. I already use geeqie on my slackware. I just think it could be great to have it officially instead of gqview.

jedi_sith_fears · 03-07-2010, 01:48 AM

I haven't tried it yet. Will give it a shot next weekend and will post the experience.

Thom1b · 03-13-2010, 06:58 AM

It's done, Pat has included geeqie in current and removed gqview

niels.horn · 03-13-2010, 07:14 AM

Yep, good news

jedi_sith_fears · 03-16-2010, 07:45 AM

Nice ... I tried it, got some free time finally. Seems good. But GQView is still my favorite.

catkin · 03-16-2010, 07:59 AM

Quote:

Originally Posted by jedi_sith_fears

Nice ... I tried it, got some free time finally. Seems good. But GQView is still my favorite.

What are the differences that make GQView your favourite?

niels.horn · 03-16-2010, 05:01 PM

Quote:

Nice ... I tried it, got some free time finally. Seems good. But GQView is still my favorite.

Quote:

Originally Posted by catkin

What are the differences that make GQView your favourite?

Same question here... I used GQView for a long time and switched to geeqie when it was still in beta. I'm not missing anything, and my major problems have been resolved.
So what is it that you're missing in geeqie?

titopoquito · 03-17-2010, 07:18 AM

Quote:

Originally Posted by niels.horn

Same question here... So what is it that you're missing in geeqie?

I could imagine that jedi_sith_fears for example is thinking of the customized editor commands. This differs between gqview and geeqie and IMHO the geeqie way to handle this is more inconvenient, even with the new very basic editor to create the needed desktop files. That's the only bigger difference I can think about.

jbs1136 · 03-17-2010, 02:57 PM

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

tuxrules · 03-17-2010, 04:26 PM

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.

niels.horn · 03-17-2010, 06:31 PM

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.

tuxrules · 03-17-2010, 07:18 PM

Quote:

Originally Posted by niels.horn

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.

Thanks for the explanation

I was kinda thinking that myself.

gnashley · 03-18-2010, 02:17 AM

Those shell scripts should go into /usr/libexec -maybe adjusting the configuration options would accomplish it.