Re: [arch-general] [arch-dev-public] [RFC] Add Wayland/Weston
On 02/12/2013 05:51 PM, Tom Gundersen wrote:
On Tue, Feb 12, 2013 at 5:42 PM, Andreas Radke <andyrtr@archlinux.org> wrote:
Am Sat, 9 Feb 2013 17:35:27 +0100 schrieb Andreas Radke <andyrtr@archlinux.org>:
Since cairo will also depend on that libegl then every system will pull in Wayland. Is this really needed? If we can't build it in a different way we directly need to move Wayland to extra.
-Andy
Bump.
If we agree that we want to start to support Wayland in Arch we need to move Wayland libs to the extra repo. Then I can build Mesa making use of it in libegl. This shouldn't harm anything else and wayland libs are a pretty small pkg (when we drop the static libs).
So who's going to move it to extra and wants to maintain it there? I could build it but will not use it myself anytime soon.
I'll be happy to maintain Wayland, so I'll take it over and move it to [extra].
-t
Hello, and thank you for adding Wayland into Extra. There is now another smaller problem. In order to make use of Wayland with GTK+3, libxkbcommon should be moved into extra first. Can anyone do that? Lot of GTK+3 apps can be ran in Weston using GDK_BACKEND=wayland.
On Wed, Feb 13, 2013 at 8:47 PM, Armin K. <krejzi@email.com> wrote:
On 02/12/2013 05:51 PM, Tom Gundersen wrote:
On Tue, Feb 12, 2013 at 5:42 PM, Andreas Radke <andyrtr@archlinux.org> wrote:
Am Sat, 9 Feb 2013 17:35:27 +0100 schrieb Andreas Radke <andyrtr@archlinux.org>:
Since cairo will also depend on that libegl then every system will pull in Wayland. Is this really needed? If we can't build it in a different way we directly need to move Wayland to extra.
-Andy
Bump.
If we agree that we want to start to support Wayland in Arch we need to move Wayland libs to the extra repo. Then I can build Mesa making use of it in libegl. This shouldn't harm anything else and wayland libs are a pretty small pkg (when we drop the static libs).
So who's going to move it to extra and wants to maintain it there? I could build it but will not use it myself anytime soon.
I'll be happy to maintain Wayland, so I'll take it over and move it to [extra].
-t
Hello, and thank you for adding Wayland into Extra. There is now another smaller problem. In order to make use of Wayland with GTK+3, libxkbcommon should be moved into extra first. Can anyone do that? Lot of GTK+3 apps can be ran in Weston using GDK_BACKEND=wayland.
Gtk or qt maintainers will move libxkbcommon (or others needed deps in extra) when they decide to use their wayland backend. Cheers, -- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A
2013/2/14 Sébastien Luttringer <seblu@seblu.net>
On Wed, Feb 13, 2013 at 8:47 PM, Armin K. <krejzi@email.com> wrote:
On 02/12/2013 05:51 PM, Tom Gundersen wrote:
On Tue, Feb 12, 2013 at 5:42 PM, Andreas Radke <andyrtr@archlinux.org> wrote:
Am Sat, 9 Feb 2013 17:35:27 +0100 schrieb Andreas Radke <andyrtr@archlinux.org>:
Since cairo will also depend on that libegl then every system will pull in Wayland. Is this really needed? If we can't build it in a different way we directly need to move Wayland to extra.
-Andy
Bump.
If we agree that we want to start to support Wayland in Arch we need to move Wayland libs to the extra repo. Then I can build Mesa making use of it in libegl. This shouldn't harm anything else and wayland libs are a pretty small pkg (when we drop the static libs).
So who's going to move it to extra and wants to maintain it there? I could build it but will not use it myself anytime soon.
I'll be happy to maintain Wayland, so I'll take it over and move it to [extra].
-t
Hello, and thank you for adding Wayland into Extra. There is now another smaller problem. In order to make use of Wayland with GTK+3, libxkbcommon should be moved into extra first. Can anyone do that? Lot of GTK+3 apps can be ran in Weston using GDK_BACKEND=wayland.
Gtk or qt maintainers will move libxkbcommon (or others needed deps in extra) when they decide to use their wayland backend.
Cheers,
-- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A
I just saw that wayland is a dependency of gtk3 in [testing] repo. Can wayland be just an OPTIONAL dependency?
On Sat, Feb 16, 2013 at 4:33 AM, Cai Iru <mytbk920423@gmail.com> wrote:
I just saw that wayland is a dependency of gtk3 in [testing] repo. Can wayland be just an OPTIONAL dependency?
No. And please don't make mountains out of molehills - wayland is just a 580KiB library.
On Sat, Feb 16, 2013 at 12:49 AM, Jan Steffens <jan.steffens@gmail.com> wrote:
On Sat, Feb 16, 2013 at 4:33 AM, Cai Iru <mytbk920423@gmail.com> wrote:
I just saw that wayland is a dependency of gtk3 in [testing] repo. Can wayland be just an OPTIONAL dependency?
No. And please don't make mountains out of molehills - wayland is just a 580KiB library.
Sorry for the 'molehill' kid, but Cai's still right, isn't him? As long as Wayland isn't a necessary dependency of gtk3 it shouldn't be marked as needed. I agree that 580KiB is nothing, just about the half of an old 3' 1/2 diskette, but this _isn't_ the right answer, at least this isn't a *serious* answer: no matter how does it weights, be it 580KiB or just 1KiB, if it's not a required dependency then the decision to ship it IS WRONG and in flagrant violation of the Arch's KISS principle. May be you should remember Jan that "a system isn't complete when you can't add anything more to it but rather else when you can't subtract anything else from it". Put in another way: "Ticking away the moments That make up a BLOATED day Fritter and waste the system In a BLOATER way" Bloat isn't about "size", it's just about design and bad decisions.
On Sat, Feb 16, 2013 at 8:25 AM, Martín Cigorraga <msx@archlinux.us> wrote:
Sorry for the 'molehill' kid, but Cai's still right, isn't him?
No, he is not. libgdk-3 links against wayland libraries. It will not run without those installed, independent of the actual backend used.
On Sat, Feb 16, 2013 at 4:31 AM, Jan Steffens <jan.steffens@gmail.com> wrote:
On Sat, Feb 16, 2013 at 8:25 AM, Martín Cigorraga <msx@archlinux.us> wrote:
Sorry for the 'molehill' kid, but Cai's still right, isn't him?
No, he is not. libgdk-3 links against wayland libraries. It will not run without those installed, independent of the actual backend used.
Then I apologize and you're right :) I'm totally missing something here since I haven't found Wayland as a required dependency for libgdk-3 on the other two distributions I was working with.
On 16 February 2013 13:36, Martín Cigorraga <msx@archlinux.us> wrote:
On Sat, Feb 16, 2013 at 4:31 AM, Jan Steffens <jan.steffens@gmail.com> wrote:
On Sat, Feb 16, 2013 at 8:25 AM, Martín Cigorraga <msx@archlinux.us> wrote:
Sorry for the 'molehill' kid, but Cai's still right, isn't him?
No, he is not. libgdk-3 links against wayland libraries. It will not run without those installed, independent of the actual backend used.
Then I apologize and you're right :) I'm totally missing something here since I haven't found Wayland as a required dependency for libgdk-3 on the other two distributions I was working with.
Martin, that is obviously because we're trying to do this early, in preparation for Wayland when it becomes "production-ready" (so we can plug and play instead of falling into a mess right then and there). -- GPG/PGP ID: C0711BF1
On Sat, Feb 16, 2013 at 8:36 AM, Martín Cigorraga <msx@archlinux.us> wrote:
I'm totally missing something here since I haven't found Wayland as a required dependency for libgdk-3 on the other two distributions I was working with.
I guess what you are missing is the fact that wayland is optional at compile-time, but if enabled it is required on run-time. This is how almost all libraries work. HTH, Tom
participants (7)
-
Armin K.
-
Cai Iru
-
Jan Steffens
-
Martín Cigorraga
-
Rashif Ray Rahman
-
Sébastien Luttringer
-
Tom Gundersen