View previous topic :: View next topic |
Author |
Message |
Arnaudv6 n00b


Joined: 18 Jul 2008 Posts: 46
|
Posted: Tue Oct 28, 2014 2:40 pm Post subject: xdg-open and the likes |
|
|
Hello fellows, here I tell about my life, feel free to skip the quotation :
Quote: | I recently stripped down my system. Objective gains we could argue on.
Still I feel enthusiastic about it and love gentoo the more.
Along the road it happened xdg-utils was no required dependency anymore and was unmerged.
I certainly do not miss link. And I have exo-open (pulled in by thunar) as a xdg-open alternative.
Code: | ln -s /usr/bin/exo-open ~/.local/bin/xdg-open
echo 'export PATH=$HOME/.local/bin:$PATH' >> ~/.config/openbox/environment | and url handling was back on track for my qt apps (trojita/qupzilla/qpdfview....)
|
Still I am wondering how we could handle this a hardened way :
plenty of packages rely on xdg-open and some do not, even though they practically do:
trojita/qupzilla/qpdfview won't open no link if xdg-open is not found.
Shall we create a virtual/open ebuild, that would require one of gvfs-open, kde-open, xdg-open or exo-open to be emerged ?
Shall we allow exo ebuild (and the likes) to symlink xdg-open to itself system-wide; based on a symlink USE flag ?
This question is to gain credit with the waxing of wayland and hopefully droping of X (and its utils) on most of our personal desktops.
It is not even clear to me if the matter shall be sorted out by the GUI toolkits (qt here) so they do not depend on xdg-open?
What do you guys think ? |
|
Back to top |
|
 |
Dominique_71 Veteran


Joined: 17 Aug 2005 Posts: 1940 Location: Switzerland (Romandie)
|
Posted: Tue Oct 28, 2014 6:03 pm Post subject: |
|
|
I see 2 things. First the xdg-open problematic. Even a software like mc is using it by default now, so I don't think it will disappear.
Second X will not disappear because wayland is coming. X and its extension is so huge I am very doubtful its compatibility layer will be completed some day. Which give us the same issue: X is here to stay. _________________ "Confirm You are a robot." - the singularity |
|
Back to top |
|
 |
Arnaudv6 n00b


Joined: 18 Jul 2008 Posts: 46
|
Posted: Wed Oct 29, 2014 3:24 pm Post subject: |
|
|
So what do you think shall be done with xdg-open then : just let mc require the xdg-utils implementation ?
About X, I think it still has many long years to live, but I hope desktop users that wish to do so could get rid of it in say a year,
when wayland compatible toolkit versions get stable in portage tree. |
|
Back to top |
|
 |
steveL Watchman

Joined: 13 Sep 2006 Posts: 5153 Location: The Peanut Gallery
|
Posted: Thu Oct 30, 2014 11:54 am Post subject: |
|
|
Arnaudv6 wrote: | So what do you think shall be done with xdg-open then : just let mc require the xdg-utils implementation ? |
Yup. |
|
Back to top |
|
 |
Dominique_71 Veteran


Joined: 17 Aug 2005 Posts: 1940 Location: Switzerland (Romandie)
|
Posted: Fri Nov 07, 2014 7:02 pm Post subject: |
|
|
Arnaudv6 wrote: | So what do you think shall be done with xdg-open then : just let mc require the xdg-utils implementation ? |
That's not a big dependency.
Quote: | About X, I think it still has many long years to live, but I hope desktop users that wish to do so could get rid of it in say a year,
when wayland compatible toolkit versions get stable in portage tree. |
A compatible toolkit is not the same thing at all than a X compatible layer. So again X will stay for more than 1 year. For me, the problem is not the toolkit, a decent t graphical server must be able to run any toolkit. But look at the window manager. I am a desktop user that like fvwm, and I will not stop to use it because it will not run on wayland, I will continue to use fvwm with fvwm-crystal, even if that imply I must shift to *BSD, which is not stressed to shift to break my good working OS.tm software (and wayland is not the only one in that case...). _________________ "Confirm You are a robot." - the singularity |
|
Back to top |
|
 |
Arnaudv6 n00b


Joined: 18 Jul 2008 Posts: 46
|
Posted: Thu Nov 13, 2014 11:53 am Post subject: |
|
|
Dominique_71 wrote: | That's not a big dependency. | To me it still is a non-wanted one.
xdg-utils pulls in x11-apps/xset which pulls in x11-libs/libX11.
Non of which I really mean to emerge just so mimetypes get handled.
I do not have any use for links/linx/w3m either.
Dominique_71 wrote: | I am a desktop user that like fvwm, and I will not stop to use it because it will not run on wayland, I will continue to use fvwm with fvwm-crystal, even if that imply I must shift to *BSD | Short answer : WMs are not a point under wayland.
And you can expect plenty of weston shells to mimic them.
I love openbox, only I will be very happy to drop it with X. |
|
Back to top |
|
 |
i4dnf Apprentice

Joined: 18 Sep 2005 Posts: 271 Location: Bucharest, Romania
|
Posted: Thu Nov 13, 2014 12:00 pm Post subject: |
|
|
Arnaudv6 wrote: |
[snip]
WMs are not a point under wayland.
And you can expect plenty of weston shells to mimic them.
I love openbox, only I will be very happy to drop it with X. |
Unless you use a sane implementation that forbids CSD's. _________________ "The only difference between me and a madman is that I am not MAD" (SALVATOR DALI) |
|
Back to top |
|
 |
Anon-E-moose Watchman


Joined: 23 May 2008 Posts: 6259 Location: Dallas area
|
Posted: Thu Nov 13, 2014 12:01 pm Post subject: |
|
|
So don't use xdg-utils or links, lynx, whatever.
You can sit around and wait for everything to be ported to wayland...somewhere in the far future.
Meanwhile the rest of us will happily keep on using what works now. _________________ UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
Back to top |
|
 |
Arnaudv6 n00b


Joined: 18 Jul 2008 Posts: 46
|
Posted: Thu Nov 13, 2014 12:30 pm Post subject: |
|
|
I filed up a bug in Qt-gui.
I feel a bit misunderstood though. To me it comes down to saying :
"Qt apps do not handle links ? No problem, let's call X in, for it sure comes with the crappiest xdg-open ersatz you can find around."
Anon-E-moose wrote: | So don't use xdg-utils or links, lynx, whatever. |
I can live with, for sure.
And I agree trying to get rid of those small (for now where X is mandatory) dependencies is pushing it a bit.
But that is part of gentoo fun To me at least. |
|
Back to top |
|
 |
steveL Watchman

Joined: 13 Sep 2006 Posts: 5153 Location: The Peanut Gallery
|
Posted: Thu Nov 13, 2014 2:29 pm Post subject: |
|
|
If "exo-open" suffices, you can always put xdg-open in package.provided (once you've installed the symlink to run exo-open as xdg-open.)
I just find it a bit odd to read "..pulls in libX11" as a no-no.
As for ditching your WM when wayland comes around, I won't be. In fact I'd prefer it if all the nubskool left X11 alone and switched their attention to wayland; however given past history, fdo are more likely to cripple X11 shortly before they enforce wayland on everyone, irrespective of choice. |
|
Back to top |
|
 |
Ant P. Watchman

Joined: 18 Apr 2009 Posts: 6920
|
Posted: Fri Nov 14, 2014 12:04 am Post subject: Re: xdg-open and the likes |
|
|
Arnaudv6 wrote: | Shall we create a virtual/open ebuild, that would require one of gvfs-open, kde-open, xdg-open or exo-open to be emerged ?
Shall we allow exo ebuild (and the likes) to symlink xdg-open to itself system-wide; based on a symlink USE flag ? |
It would be enough to simply split xdg-open into its own ebuild and fix other packages to depend on that. |
|
Back to top |
|
 |
Arnaudv6 n00b


Joined: 18 Jul 2008 Posts: 46
|
Posted: Fri Nov 14, 2014 8:10 am Post subject: |
|
|
Ant P. wrote: | It would be enough to simply split xdg-open into its own ebuild and fix other packages to depend on that. |
steveL wrote: | If "exo-open" suffices, you can always put xdg-open in package.provided (once you've installed the symlink to run exo-open as xdg-open.) |
Thanks guys, and combining your two solutions, we do no longer need to create a virtual/open ebuild like I proposed it seems. |
|
Back to top |
|
 |
|