[Users] Using Fancy with Fedora 29 ?

[Paul Rolland (ポール・ロラン)]

Hello,

I've just finished upgrading from Fedora 21 to Fedora 29, and then
recompiled Claws to link to the new libraries... But fancy is not compiling
because I have no "webkit-1.0".

Anyone knows which F29 package provides webkit-1.0 ? In the meantime, I've
compiled with dillo, but I like the fancy plugin, the way to control if
external elements are loaded or not, etc...

If any Fedora user reads the list, please help ;)
I've tried the "yum whatprovides \*webkit-1.0.pc" but this is only
returning some mingw packages ;(

Thanks,
Paul

[Brian Morrison]

On Sat, 3 Nov 2018 19:57:01 +0100

Post by Paul Rolland (ポール・ロラン)
Anyone knows which F29 package provides webkit-1.0 ?

Yes, none, it's in the obsolete lists.

There is a fix. I used mock to rebuild the cairo libraries, you do need
to doctor the spec file and remove the bit that disables cairogl, I did
this:

#%if 0%{?fedora} > 26 || 0%{?rhel} > 7
#%global cairogl --disable-gl
#%else
%global cairogl --enable-gl
%global with_gl 1
#%endif

then created a new src rpm and rebuilt it with mock. I also altered the
version to make it slightly later than the distro version of cairo.

You can then download the webkitgtk rpms for Fedora 26 and install
them, I did this using rpm -ivh --nodeps to avoid things complaining.

Note that the reason Fedora has made webkitgtk obsolete is that it's
buggy in a security sense, so there is a risk due to installing it.

HTH.

[Paul Rolland (ポール・ロラン)]

Hello,

Thanks to all of you !

I've been carefully reading your mails and the security warnings related to
webkit-1... I'll continue with Dillo (which is awful, I agree), and will
open in a browser when needed.

Thanks to all for the very prompt replies !

Best,
Paul


On Sat, 3 Nov 2018 19:07:50 +0000

Post by Brian Morrison
On Sat, 3 Nov 2018 19:57:01 +0100

Post by Paul Rolland (ポール・ロラン)
Anyone knows which F29 package provides webkit-1.0 ?

Yes, none, it's in the obsolete lists.
There is a fix. I used mock to rebuild the cairo libraries, you do need
to doctor the spec file and remove the bit that disables cairogl, I did
#%if 0%{?fedora} > 26 || 0%{?rhel} > 7
#%global cairogl --disable-gl
#%else
%global cairogl --enable-gl
%global with_gl 1
#%endif
then created a new src rpm and rebuilt it with mock. I also altered the
version to make it slightly later than the distro version of cairo.
You can then download the webkitgtk rpms for Fedora 26 and install
them, I did this using rpm -ivh --nodeps to avoid things complaining.
Note that the reason Fedora has made webkitgtk obsolete is that it's
buggy in a security sense, so there is a risk due to installing it.
HTH.

--
Paul Rolland E-Mail : rol(at)witbe.net
CTO - Witbe.net SA Tel. [phone]
Les Collines de l'Arche Fax. [phone]
F-92057 Paris La Defense RIPE : PR12-RIPE

LinkedIn : http://www.linkedin.com/in/paulrolland
Skype : rollandpaul

"I worry about my child and the Internet all the time, even though she's
too young to have logged on yet. Here's what I worry about. I worry that 10
or 15 years from now, she will come to me and say 'Daddy, where were you
when they took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation

[Brad Rogers]

On Sat, 3 Nov 2018 19:57:01 +0100
"Paul Rolland (ポヌル・ロラン)" <***@witbe.net> wrote:

Hello Paul,

Post by Paul Rolland (ポール・ロラン)
recompiled Claws to link to the new libraries... But fancy is not
compiling because I have no "webkit-1.0".

A quick search indicates it went away in Fed27 for security reasons.

Same applies to Debian. It won't be in next stable, having been removed
from testing. The reasons being a) it's old (not a crime in itself) and
b) it's unmaintained.

At this point you have four choices:

Use the dillo plugin
Install the webkit stuff from source
Wait for fancy-plugin to be ported to webkit2
Do away with html viewer plugins altogether

Each has its own (de)merits. The third is option depends on whether such
a move is planned. I know nothing about that.

I could keep the old webkit packages necessary to build the fancy
plugin, but sooner or later, an update will force their removal. So I
decided to do away with html plugins altogether (dillo looks awful) in
Claws and just open anything that absolutely must be displayed as HTML in
a browser.

[Andrej Kacian]

On Sat, 3 Nov 2018 19:14:36 +0000

Post by Brad Rogers
Install the webkit stuff from source
Wait for fancy-plugin to be ported to webkit2
Do away with html viewer plugins altogether
Each has its own (de)merits. The third is option depends on whether such
a move is planned. I know nothing about that.

Yes, it is planned. However, since Webkit people have decided that
GTK2 is not good enough to work with Webkit2, this will have to wait
until Claws Mail is ported to GTK3. Work on that is ongoing, but could
of course use more manpower.

Regards,

[Brad Rogers]

On Sat, 3 Nov 2018 21:22:27 +0100
Andrej Kacian <***@claws-mail.org> wrote:

Hello Andrej,

Post by Andrej Kacian
Yes, it is planned. However, since Webkit people have decided that

Good to know. Thanks for the info.

Post by Andrej Kacian
GTK2 is not good enough to work with Webkit2, this will have to wait
until Claws Mail is ported to GTK3. Work on that is ongoing, but could

There's always something, isn't there?

Post by Andrej Kacian
of course use more manpower.

Sadly, my ability to program amounts to nil. Letting me loose on the CM
code would be disastrous.

[Andrej Kacian]

On Sat, 3 Nov 2018 20:50:42 +0000

Post by Brad Rogers

Post by Andrej Kacian
of course use more manpower.

Sadly, my ability to program amounts to nil. Letting me loose on the CM
code would be disastrous.

Well, the good thing is that we are in the stage where the GTK3 port
mostly works, and will soon need "user eyeballs" to find and report
things which don't work, or work differently than the main GTK2
version. In fact, I'm writing this e-mail in it, as the X-Mailer header
will show. :)

So, if you (generic you) can live without Fancy plugin, feel free to
check out the gtk3 branch from our git server, and give it a whirl.

Regards,

[Paul Rolland (ポール・ロラン)]

Hello Andrej,

On Sat, 3 Nov 2018 22:26:06 +0100

Post by Andrej Kacian
Well, the good thing is that we are in the stage where the GTK3 port
mostly works, and will soon need "user eyeballs" to find and report
things which don't work, or work differently than the main GTK2
version. In fact, I'm writing this e-mail in it, as the X-Mailer header
will show. :)
So, if you (generic you) can live without Fancy plugin, feel free to
check out the gtk3 branch from our git server, and give it a whirl.

Just done that, and it started... but do you have any reference that I
could you to convert my gtkrc-2.0 file to something that gtk3 understands ?
I've configured a dark theme that is matching my global destktop settings,
and default for gtk3 seems to be a light themes.

Any pointer/example would be appreciated ;)

Thanks,
Paul
--
Paul Rolland E-Mail : rol(at)witbe.net
CTO - Witbe.net SA Tel. [phone]
Les Collines de l'Arche Fax. [phone]
F-92057 Paris La Defense RIPE : PR12-RIPE

LinkedIn : http://www.linkedin.com/in/paulrolland
Skype : rollandpaul

"I worry about my child and the Internet all the time, even though she's
too young to have logged on yet. Here's what I worry about. I worry that 10
or 15 years from now, she will come to me and say 'Daddy, where were you
when they took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation

[Ralf Mardorf]

Post by Brad Rogers
Hello Andrej,
On Sat, 3 Nov 2018 22:26:06 +0100

Post by Andrej Kacian
Well, the good thing is that we are in the stage where the GTK3 port
mostly works, and will soon need "user eyeballs" to find and report
things which don't work, or work differently than the main GTK2
version. In fact, I'm writing this e-mail in it, as the X-Mailer
header will show. :)
So, if you (generic you) can live without Fancy plugin, feel free to
check out the gtk3 branch from our git server, and give it a whirl.

Just done that, and it started... but do you have any reference that I
could you to convert my gtkrc-2.0 file to something that gtk3
understands ? I've configured a dark theme that is matching my global
destktop settings, and default for gtk3 seems to be a light themes.
Any pointer/example would be appreciated ;)

First of all you need a GTK theme that still provides working themes
for GTK 2 and GTK 3. A lot of themes were discontinued by upstream.

If you have got a theme installed that does work for GTK3 as well as
GTK2, consider to manually edit $HOME/.config/gtk-3.0/settings.ini, to
fit to $HOME/.gtkrc-2.0.

[***@archlinux ~]$ grep -v \# .gtkrc-2.0

include "/home/rocketmouse/.gtkrc-2.0.mine"
gtk-theme-name="Arc-RM-Cornflower"
gtk-icon-theme-name="Sardi-Mono-Papirus-Colora-Havelock"
gtk-font-name="Cantarell 11"
gtk-cursor-theme-name="Paper"
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=1
gtk-menu-images=1
gtk-enable-event-sounds=0
gtk-enable-input-feedback-sounds=0
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle="hintfull"
gtk-xft-rgba="rgb"
[***@archlinux ~]$ grep -v \# .config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name=Arc-RM-Cornflower
gtk-font-name=Cantarell 11
gtk-icon-theme-name=Sardi-Mono-Papirus-Colora-Havelock
gtk-cursor-theme-name=Paper
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=1
gtk-menu-images=1
gtk-enable-event-sounds=0
gtk-enable-input-feedback-sounds=0
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb

[Paul]

On Sun, 4 Nov 2018 11:56:55 +0100

Post by Ralf Mardorf
First of all you need a GTK theme that still provides working themes
for GTK 2 and GTK 3. A lot of themes were discontinued by upstream.

No, Ralf. You are confusing 'you need' with 'it might be preferable
to use'.

[Ralf Mardorf]

Post by Paul

Post by Ralf Mardorf
First of all you need a GTK theme that still provides working themes
for GTK 2 and GTK 3. A lot of themes were discontinued by upstream.

No, Ralf. You are confusing 'you need' with 'it might be preferable
to use'.

My bad, you're right. I assume that users usually want a consistent
theme for all GTK apps and at least a similar theme for Qt apps and
perhaps even for tricky GTK GNOME apps. Btw. there is
https://github.com/PCMan/gtk3-nocsd for all those who might use GNOME
applications, but want to get at least a "normal" title bar for GNOME
apps, too.

Regarding my claim that Claws is unstable (on Arch, not Ubuntu 16.04
LTS), I experienced the same for SpaceFM GTK2 and _needed_ to migrate
to SpaceFM GTK3 on Arch Linux, to get rid of the issues. I'll test Claws
GTK3 port ASAP, too.

[Paul]

On Sun, 4 Nov 2018 12:56:49 +0100

Post by Ralf Mardorf
Regarding my claim that Claws is unstable (on Arch, not Ubuntu 16.04
LTS), I experienced the same for SpaceFM GTK2 and _needed_ to
migrate to SpaceFM GTK3 on Arch Linux, to get rid of the issues.
I'll test Claws GTK3 port ASAP, too.

That doesn't say what you claim to have experienced, so that still
doesn't answer my question.

Post by Ralf Mardorf
You better find another MUA, since soon or later Claws will be
broken on other systems, too.

You are just trolling here, it seems. If not, then please explain why
you've said this.

with regards

Paul

[Ralf Mardorf]

Post by Paul
On Sun, 4 Nov 2018 12:56:49 +0100

Post by Ralf Mardorf
Regarding my claim that Claws is unstable (on Arch, not Ubuntu 16.04
LTS), I experienced the same for SpaceFM GTK2 and _needed_ to
migrate to SpaceFM GTK3 on Arch Linux, to get rid of the issues.
I'll test Claws GTK3 port ASAP, too.

That doesn't say what you claim to have experienced, so that still
doesn't answer my question.

Post by Ralf Mardorf
You better find another MUA, since soon or later Claws will be
broken on other systems, too.

You are just trolling here, it seems. If not, then please explain why
you've said this.

Counterquestions: If there will be no issues with GTK 2 in the near
future for almost any GTK 2 based app, for what reason are you working
on a Claws GTK 3 port? Apart from the GNOME folks, several upstream
developers for good reasons prefer old faithful GTK 2 over GTK 3, so
they either sometimes discontinued their software or unwillingly
migrate to GTK 3. There might be still some projects that were neither
dropped, nor a migration is planed. Do they have got a future, if
they rely on GTK 2?

[Ralf Mardorf]

Post by Ralf Mardorf

Post by Paul

Post by Ralf Mardorf
Regarding my claim that Claws is unstable (on Arch, not Ubuntu 16.04
LTS), I experienced the same for SpaceFM GTK2 and _needed_ to
migrate to SpaceFM GTK3 on Arch Linux, to get rid of the issues.
I'll test Claws GTK3 port ASAP, too.

That doesn't say what you claim to have experienced, so that still
doesn't answer my question.

Post by Ralf Mardorf
You better find another MUA, since soon or later Claws will be
broken on other systems, too.

You are just trolling here, it seems. If not, then please explain why
you've said this.

Counterquestions: If there will be no issues with GTK 2 in the near
future for almost any GTK 2 based app, for what reason are you working
on a Claws GTK 3 port? Apart from the GNOME folks, several upstream
developers for good reasons prefer old faithful GTK 2 over GTK 3, so
they either sometimes discontinued their software or unwillingly
migrate to GTK 3. There might be still some projects that were neither
dropped, nor a migration is planed. Do they have got a future, if
they rely on GTK 2?

I forgot to mention that upstream sometimes migrates from GTK to Qt! A
famous example is LXDE.

[Andrej Kacian]

On Sun, 4 Nov 2018 13:55:52 +0100

Post by Ralf Mardorf

Post by Paul
On Sun, 4 Nov 2018 12:56:49 +0100

Post by Ralf Mardorf
Regarding my claim that Claws is unstable (on Arch, not Ubuntu 16.04
LTS), I experienced the same for SpaceFM GTK2 and _needed_ to
migrate to SpaceFM GTK3 on Arch Linux, to get rid of the issues.
I'll test Claws GTK3 port ASAP, too.

That doesn't say what you claim to have experienced, so that still
doesn't answer my question.

Post by Ralf Mardorf
You better find another MUA, since soon or later Claws will be
broken on other systems, too.

You are just trolling here, it seems. If not, then please explain why
you've said this.

Counterquestions: If there will be no issues with GTK 2 in the near
future for almost any GTK 2 based app, for what reason are you working
on a Claws GTK 3 port? Apart from the GNOME folks, several upstream
developers for good reasons prefer old faithful GTK 2 over GTK 3, so
they either sometimes discontinued their software or unwillingly
migrate to GTK 3. There might be still some projects that were neither
dropped, nor a migration is planed. Do they have got a future, if
they rely on GTK 2?

We're working on a GTK3 port to have way forward open. GTK2 will not be
around forever (unless someone forks and maintains it, which is
unlikely).

I do not expect us to stop releasing GTK2 version anytime soon, as
apart from not having Fancy, it is still fully working, and IMHO better
looking. Even after GTK3 version is fully finished (as much as
something like that can ever be "finished") and working, we will likely
just release both versions concurrently. Time will tell.

Or perhaps my pet project, Qt port, will take off and we will leave GTK
behind altogether. :)

With that being said, your counterquestions seem to me like an attempt
to change topic, and avoid having to explain your rather toxic remark.
Not cool.

Regards,

[Colin Leroy-Mira]

On 04 November 2018 at 14h20, Andrej Kacian wrote:

Hi,

Post by Andrej Kacian
With that being said, your counterquestions seem to me like an attempt
to change topic, and avoid having to explain your rather toxic remark.
Not cool.

Also I can't see why the existence of GTK3 would cause GTK2 to go
unstable all by itself.

[Brad Rogers]

On Sun, 4 Nov 2018 14:20:21 +0100
Andrej Kacian <***@claws-mail.org> wrote:

Hello Andrej,

Post by Andrej Kacian
I do not expect us to stop releasing GTK2 version anytime soon, as
apart from not having Fancy, it is still fully working, and IMHO better
looking.

Just downloaded, compiled and run the GTK3 branch. I think you're right
- GTK3 has a very different, and to my mind, rather clunky appearance
compared with GTK2. Toolbar buttons, in particular, take massive amounts
of space.

That said, it fired up fine, and worked well for the short period of
time I had it running. I'll fiddle with it more over the next few days.

[Ricardo Mones]

Post by Brad Rogers
On Sun, 4 Nov 2018 14:20:21 +0100
Hello Andrej,

Post by Andrej Kacian
I do not expect us to stop releasing GTK2 version anytime soon, as
apart from not having Fancy, it is still fully working, and IMHO better
looking.

Just downloaded, compiled and run the GTK3 branch. I think you're right
- GTK3 has a very different, and to my mind, rather clunky appearance
compared with GTK2. Toolbar buttons, in particular, take massive amounts
of space.

You may try to change your GTK3 theme and see if it improves.

Default theme makes widgets kinda bulky when you're used to GTK2,
perhaps to look better on hi-DPI, but that's just a wild guess of mine.

regards,

[Brad Rogers]

On Thu, 8 Nov 2018 16:18:36 +0100
Ricardo Mones <***@mones.org> wrote:

Hello Ricardo,

Post by Ricardo Mones
You may try to change your GTK3 theme and see if it improves.

Now why didn't I thnik of that? Definitely a step in the right
direction, thanks Ricardo.

Post by Ricardo Mones
Default theme makes widgets kinda bulky when you're used to GTK2,
perhaps to look better on hi-DPI, but that's just a wild guess of mine.

You may well be on the money there.

[Ralf Mardorf]

Post by Brad Rogers

Post by Ricardo Mones
You may try to change your GTK3 theme and see if it improves.

Now why didn't I thnik of that? Definitely a step in the right
direction, thanks Ricardo.

Consider to post screenshots, too.

The screenshots I already posted:

claws gtk2 Loading Image...
claws gtk3 Loading Image...

It's a customized Arc theme, after customizing it, I updated the
original theme, but never the customized theme.

I only found https://github.com/horst3180/arc-theme/issues/597, but it
seemingly doesn't covers the changes for the customized version shown by
the screenshots.

[***@archlinux ~]$ grep -v \# .gtkrc-2.0

include "/home/rocketmouse/.gtkrc-2.0.mine"
gtk-theme-name="Arc-RM-Cornflower"
gtk-icon-theme-name="Sardi-Mono-Papirus-Colora-Havelock"
gtk-font-name="Cantarell 11"
gtk-cursor-theme-name="Paper"
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=1
gtk-menu-images=1
gtk-enable-event-sounds=0
gtk-enable-input-feedback-sounds=0
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle="hintfull"
gtk-xft-rgba="rgb"
[***@archlinux ~]$ grep -v \# .config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name=Arc-RM-Cornflower
gtk-font-name=Cantarell 11
gtk-icon-theme-name=Sardi-Mono-Papirus-Colora-Havelock
gtk-cursor-theme-name=Paper
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=1
gtk-menu-images=1
gtk-enable-event-sounds=0
gtk-enable-input-feedback-sounds=0
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb

[Ralf Mardorf]

Post by Ralf Mardorf
I only found https://github.com/horst3180/arc-theme/issues/597, but it
seemingly doesn't covers the changes for the customized version shown
by the screenshots.

Oops, wrong link, it should read
https://github.com/horst3180/arc-theme/issues/406.

[Andrej Kacian]

On Thu, 8 Nov 2018 16:18:36 +0100

Post by Ricardo Mones

Post by Brad Rogers
On Sun, 4 Nov 2018 14:20:21 +0100
Hello Andrej,

Post by Andrej Kacian
I do not expect us to stop releasing GTK2 version anytime soon, as
apart from not having Fancy, it is still fully working, and IMHO better
looking.

Just downloaded, compiled and run the GTK3 branch. I think you're right
- GTK3 has a very different, and to my mind, rather clunky appearance
compared with GTK2. Toolbar buttons, in particular, take massive amounts
of space.

You may try to change your GTK3 theme and see if it improves.
Default theme makes widgets kinda bulky when you're used to GTK2,
perhaps to look better on hi-DPI, but that's just a wild guess of mine.

Some widgets have also been redesigned in GTK3 to be intentionally
bigger. Compare the spin button widgets and how efficiently they use
space:

Loading Image...
Loading Image...

Regards,

[Brad Rogers]

On Thu, 8 Nov 2018 16:49:53 +0100
Andrej Kacian <***@claws-mail.org> wrote:

Hello Andrej,

Post by Andrej Kacian
Some widgets have also been redesigned in GTK3 to be intentionally

Thanks Andrej. As suggested by Ricardo, I've changed themes (Why didn't
I think of that?), which goes along way to improving space usage.

[Ricardo Mones]

On Thu, 8 Nov 2018 16:49:53 +0100

Post by Brad Rogers
On Thu, 8 Nov 2018 16:18:36 +0100

Post by Ricardo Mones

Post by Brad Rogers
On Sun, 4 Nov 2018 14:20:21 +0100
Hello Andrej,

Post by Andrej Kacian
I do not expect us to stop releasing GTK2 version anytime soon, as
apart from not having Fancy, it is still fully working, and IMHO
better looking.

Just downloaded, compiled and run the GTK3 branch. I think you're right
- GTK3 has a very different, and to my mind, rather clunky appearance
compared with GTK2. Toolbar buttons, in particular, take massive
amounts of space.

You may try to change your GTK3 theme and see if it improves.
Default theme makes widgets kinda bulky when you're used to GTK2,
perhaps to look better on hi-DPI, but that's just a wild guess of mine.

Some widgets have also been redesigned in GTK3 to be intentionally
bigger. Compare the spin button widgets and how efficiently they use
https://developer.gnome.org/gtk2/2.24/spinbutton.png
https://developer.gnome.org/gtk3/3.22/spinbutton.png

Well, yes, there's a design component there where the minimalistic
heavily-packed arrows have become two complete buttons.

But to be fair that comparison should have been done with same font
settings, the gtk3 font size is way larger than the gtk2 font ;-)

regards,

[Brad Rogers]

On Sat, 3 Nov 2018 22:26:06 +0100
Andrej Kacian <***@claws-mail.org> wrote:

Hello Andrej,

Post by Andrej Kacian
So, if you (generic you) can live without Fancy plugin, feel free to
check out the gtk3 branch from our git server, and give it a whirl.

I must be doing something wrong, since I can't get it to compile here.
Certainly the fault is with me - Paul Rolland managed to compile the
GTK3 branch successfully.

When I've got more time, I'll investigate.

[Johan Vromans]

Post by Andrej Kacian
Yes, it is planned. However, since Webkit people have decided that
GTK2 is not good enough to work with Webkit2, this will have to wait
until Claws Mail is ported to GTK3. [...]

Does that mean that the GTK3 version will have fancy again?

[Andrej Kacian]

On Sun, 4 Nov 2018 20:57:10 +0100

Post by Johan Vromans

Post by Andrej Kacian
Yes, it is planned. However, since Webkit people have decided that
GTK2 is not good enough to work with Webkit2, this will have to wait
until Claws Mail is ported to GTK3. [...]

Does that mean that the GTK3 version will have fancy again?

Yes, that is the plan. :)

Regards,

[Ralf Mardorf]

Post by Paul Rolland (ポール・ロラン)
I've just finished upgrading from Fedora 21 to Fedora 29, and then
recompiled Claws to link to the new libraries... But fancy is not
compiling because I have no "webkit-1.0".
Anyone knows which F29 package provides webkit-1.0 ? In the meantime,
I've compiled with dillo, but I like the fancy plugin, the way to
control if external elements are loaded or not, etc...
If any Fedora user reads the list, please help ;)
I've tried the "yum whatprovides \*webkit-1.0.pc" but this is only
returning some mingw packages ;(

I'm not a Fedora user, however, for security reasons hopefully most
Linux distros dropped it already or will drop it as soon as possible. I
suspect that Fedora dropped it.

The distro I'm using dropped it a long, long time ago, but it's still
provided by a user repository for this distro.

If you should consider to compile it yourself, consider first to read
the pinned comments here: https://aur.archlinux.org/pkgbase/webkitgtk

An excerpt from the above link:

"Q3. Building takes too long time!

A3: WebKit is inherently big and complex. It can take up to 13.5 hours"

Anyway, while Claws 3.17.0 still is stable on Ubuntu 16.04.5 LTS, it's
nearly completely unusable, when running on Arch Linux and it was
already more or less unusable several release before, either when
installing it from official repositories, as well as when building it
from git, as I do for Ubuntu.

[***@archlinux moonstudio]# systemd-nspawn -q apt -qq list claws-mail-git
claws-mail-git/now 3.17.0-1 amd64 [installed,local]
[***@archlinux moonstudio]# pacman -Q claws-mail
claws-mail 3.17.1-1

Even if I ever should have used Fancy, I wouldn't try to build it.
You better find another MUA, since soon or later Claws will be broken on
other systems, too. On my machine there are no issues on my Arch
install, when using Sylpheed or Evolution.

YMMV!

[Ralf Mardorf]

Post by Ralf Mardorf
claws-mail-git
claws-mail-git/now 3.17.0-1 amd64 [installed,local]
claws-mail 3.17.1-1

Oops, time to upgrade to 3.17.1 on my Ubuntu install :D. However, on
Arch, a real rolling release, I don't rely on Claws anymore. It was
unstable for <= 3.17.0 and still is for 3.17.1.

[Paul]

On Sat, 3 Nov 2018 20:33:30 +0100

Post by Ralf Mardorf
Oops, time to upgrade to 3.17.1 on my Ubuntu install :D. However, on
Arch, a real rolling release, I don't rely on Claws anymore. It was
unstable for <= 3.17.0 and still is for 3.17.1.

What on earth are you talking about? I suspect that this is just FUD.

with regards

Paul

[pezcurrel]

Post by Paul
On Sat, 3 Nov 2018 20:33:30 +0100

Post by Ralf Mardorf
Oops, time to upgrade to 3.17.1 on my Ubuntu install :D. However, on
Arch, a real rolling release, I don't rely on Claws anymore. It was
unstable for <= 3.17.0 and still is for 3.17.1.

What on earth are you talking about? I suspect that this is just FUD.

Me too, I've been using Claws on Arch without any problem for so long.

Cheers

[Paul]

On Sat, 3 Nov 2018 20:20:49 +0100

Post by Ralf Mardorf
Anyway, while Claws 3.17.0 still is stable on Ubuntu 16.04.5 LTS,
it's nearly completely unusable, when running on Arch Linux and it
was already more or less unusable several release before, either
when installing it from official repositories, as well as when
building it from git, as I do for Ubuntu.

What are you talking about? This is news to me. What is the problem
with Claws Mail on Arch?

with regards

Paul

[Andrej Kacian]

On Sat, 3 Nov 2018 19:35:14 -0000

Post by Paul
On Sat, 3 Nov 2018 20:20:49 +0100

Post by Ralf Mardorf
Anyway, while Claws 3.17.0 still is stable on Ubuntu 16.04.5 LTS,
it's nearly completely unusable, when running on Arch Linux and it
was already more or less unusable several release before, either
when installing it from official repositories, as well as when
building it from git, as I do for Ubuntu.

What are you talking about? This is news to me. What is the problem
with Claws Mail on Arch?

I think it says more about Archlinux than about Claws Mail. :)

Regards,

[Brian Morrison]

On Sat, 3 Nov 2018 21:01:42 +0100

Post by Andrej Kacian

Post by Paul
What are you talking about? This is news to me. What is the problem
with Claws Mail on Arch?

I think it says more about Archlinux than about Claws Mail. :)

Meeeeeow! ;-)

[Paul]

On Sat, 3 Nov 2018 21:01:42 +0100

Post by Andrej Kacian
I think it says more about Archlinux than about Claws Mail. :)

OTOH, Claws Mail 3.17.1 is available here:
https://www.archlinux.org/packages/extra/x86_64/claws-mail/

with regards

Paul