On Wed, 2013-11-13 at 18:22 +0100, Dominique Leuenberger a.k.a. Dimstar wrote:

Hi, and welcome! Thanks :)

Quoting Ikey Doherty :

...

Checking through openSUSE 13.1 I can see that Wayland seems partially supported, however not through the GTK (and related libs) stack. Notably I can see that the following packages do not have wayland enabled (--enable-wayland-backend)

Indeed. As Wayland was not a declared goal, we did not spend any effort (even on this silly patch) to fix the build. For the GNOME Team, building is only half the rent: it also needs to be tested and latest there is where we lacked resources.... apologies for that. Makes sense, I'm no stranger to the effort in maintaining packages, so I wouldn't disagree with the decision.

...

* gtk3 * cogl * clutter As far as I can tell the only stopping point in this chain was enabling Wayland support in GTK3, due to an old patch (from gtk3.7) being used in the gtk3 package. I've pushed to Factory [1] in the hopes this will then allow the rest of the packages to have the Wayland backend support enabled.

Seen and considered your patch. I will, in the end, likely reject the submission though, as I have an update to latest GTK+ pending, where the patch is also enabled again. Fair enough, no sense in duplication.

...

My reasons are entirely selfish, I need the Wayland backend active to test Budgie [2] via Weston on openSUSE13.1, but that aside, I cannot see any particular reason to not have the backend enabled, especially once you consider the fact that the GTK3 libraries are already dynamically linked to the wayland libraries.

True.. the reason here is only: no time... and nobodoy doing testing with us. I'm sure with you on board, this will all be better now :) I can contribute what time I have, though admittedly I also suffer from extremely limited time, full time job. Very same reason I had to stop development on SolusOS. With that said, if you got anything to throw at me, I'll do what I can.

...

Happy to do this work myself, hit a bit of a roadblock in terms of "where do I push?" as there seems to be no pattern in what repository is used (gtk3 I had to use GNOME:Factory, clutter required openSUSE:Factory but indeed thats a lot of build deps I do not want to test on openSUSE13.1 as its about to become stable. Can't seem to submit cogl anywhere)

Actually, nothing pushes directly to openSUSE:Factory. There is always a devel project in front. Luckily, for you, the packages above are all part of the GNOME Stack.. so GNOME:Factory shall do it. In doubt, just ask for a specific package (you can ask osc): Makes a bit more sense, I'll just nag various folks on IRC when I encounter an issue :)

...

osc maintainer clutter Defined in project: GNOME:Factory bugowner of clutter : os-gnome-maintainers

so: the project is GNOME:Factory, and os-gnome-maintainers are the friendly bunch of geeks looking after it. Friendly bunch of geeks ftw. Liking osc, kinda should've spotted that one..

...

Any help on quickly implementing Wayland support in openSUSE would be much appreciated!

'quickly'.. you should have joined like 2 month earlier.. that's about when we froze 13.1... Heh, 2 months earlier I had my own distro :P Now I'll try to share myself with openSUSE, as it were.

Dominique

Cheers, Ikey Doherty -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, 2013-11-18 at 00:50 +0200, sirdeiu wrote:

On 2013-11-13 19:45, Ikey Doherty wrote:

...

On Wed, 2013-11-13 at 18:22 +0100, Dominique Leuenberger a.k.a. Dimstar wrote: Hi, and welcome! Thanks :)

Quoting Ikey Doherty :

...

Checking through openSUSE 13.1 I can see that Wayland seems partially supported, however not through the GTK (and related libs) stack. Notably I can see that the following packages do not have wayland enabled (--enable-wayland-backend)

Indeed. As Wayland was not a declared goal, we did not spend any effort (even on this silly patch) to fix the build. For the GNOME Team, building is only half the rent: it also needs to be tested and latest there is where we lacked resources.... apologies for that. Makes sense, I'm no stranger to the effort in maintaining packages, so I wouldn't disagree with the decision.

...

* gtk3 * cogl * clutter As far as I can tell the only stopping point in this chain was enabling Wayland support in GTK3, due to an old patch (from gtk3.7) being used in the gtk3 package. I've pushed to Factory [1] in the hopes this will then allow the rest of the packages to have the Wayland backend support enabled.

Seen and considered your patch. I will, in the end, likely reject the submission though, as I have an update to latest GTK+ pending, where the patch is also enabled again. Fair enough, no sense in duplication.

...

My reasons are entirely selfish, I need the Wayland backend active to test Budgie [2] via Weston on openSUSE13.1, but that aside, I cannot see any particular reason to not have the backend enabled, especially once you consider the fact that the GTK3 libraries are already dynamically linked to the wayland libraries.

True.. the reason here is only: no time... and nobodoy doing testing with us. I'm sure with you on board, this will all be better now :) I can contribute what time I have, though admittedly I also suffer from extremely limited time, full time job. Very same reason I had to stop development on SolusOS. With that said, if you got anything to throw at me, I'll do what I can.

...

Happy to do this work myself, hit a bit of a roadblock in terms of "where do I push?" as there seems to be no pattern in what repository is used (gtk3 I had to use GNOME:Factory, clutter required openSUSE:Factory but indeed thats a lot of build deps I do not want to test on openSUSE13.1 as its about to become stable. Can't seem to submit cogl anywhere)

Actually, nothing pushes directly to openSUSE:Factory. There is always a devel project in front. Luckily, for you, the packages above are all part of the GNOME Stack.. so GNOME:Factory shall do it. In doubt, just ask for a specific package (you can ask osc): Makes a bit more sense, I'll just nag various folks on IRC when I encounter an issue :)

...

osc maintainer clutter Defined in project: GNOME:Factory bugowner of clutter : os-gnome-maintainers

so: the project is GNOME:Factory, and os-gnome-maintainers are the friendly bunch of geeks looking after it. Friendly bunch of geeks ftw. Liking osc, kinda should've spotted that one..

...

Any help on quickly implementing Wayland support in openSUSE would be much appreciated!

'quickly'.. you should have joined like 2 month earlier.. that's about when we froze 13.1... Heh, 2 months earlier I had my own distro :P Now I'll try to share myself with openSUSE, as it were.

Dominique

Cheers, Ikey Doherty

This is off-topic but I'm curious why did you choose openSUSE to continue ? Especially if you dropped your own distro. What has drawn you to openSUSE ?

Despite developing my own distro for so long, I still have the same requirements of other users. I want to be able to use a system, I want it to just work and stay the hell out of my way :) What I also needed, however, was an open and welcoming developer community. User or not, I'm still a developer and need that connection. For me, openSUSE is fitting the bill. Fair enough? :) - Ikey -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, 2013-11-18 at 01:22 -0800, macpacheco wrote:

The current wayland version available on 13.1 Final is too old for any valid testing. Wayland is evolving too quickly. Hopefully with 13.2 Wayland/Weston will be updated to the latest release. I tried Wayland on 13.1 once, and it crashed my system. Looking forward to full Wayland support soon. I would have to slightly disagree with this statement. openSUSE 13.1 ships with Wayland 1.2.1, which although perhaps slightly older (August) it is not too old for use.

The last major API changes to have real effect were between 1.1 and 1.2, when Wayland moved to wl_surface everywhere. I remember it quite well as I had to port my Weston plugin (my old consort-desktop experiment) to the latest SDK changes. Note that GTK3.10 works fine with Wayland 1.2.1, I would not have suggested it if I had not tested it :) Note that I have not requested *GNOME Wayland support*, rather Wayland support within the toolkit, i.e. GTK, Cogl and Clutter. Enabling the backend in no way impacts on the security or stability of the packages, but does allow both users and developers to experiment with Wayland support, before it is then fully supported by GNOME itself in 3.12. Another strong motivation for this is there are still a number of upstream GNOME applications that need porting to Wayland and testing, it would be nice if people using openSUSE could help with reporting bugs upstream and even porting applications, as Wayland support is an incredibly important goal for GNOME3.12. Kind Regards, Ikey

-- View this message in context: http://opensuse.14.x6.nabble.com/openSUSE-13-1-Wayland-tp5003179p5003490.htm... Sent from the opensuse-factory mailing list archive at Nabble.com.

--------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.