Date: Sat, 9 Dec 2017 17:02:40 +0100 From: Johannes Lundberg <johalun0@gmail.com> To: Greg V <greg@unrelenting.technology> Cc: freebsd-x11@freebsd.org Subject: Re: Some updates to Wayland stuff Message-ID: <CAECmPwu-1Yj%2BggD4iQ70O2AjRVy8qpHQpC=WWi0TTNVdosfn5A@mail.gmail.com> In-Reply-To: <3719ff97-052e-b7b0-3585-acb21a6bb794@unrelenting.technology> References: <CAECmPwvHKnfukzvoZj_in5BGNEB3jJNZOaTYDKJ93WUjNhGRMw@mail.gmail.com> <d85a04cb-cfb5-df96-814f-db1ede592125@unrelenting.technology> <CAECmPws4M%2BxuaGbbBHeGpA%2BDaa8g16oKSkGgx=xf-U1eqTS58g@mail.gmail.com> <3719ff97-052e-b7b0-3585-acb21a6bb794@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 9, 2017 at 4:59 PM, Greg V <greg@unrelenting.technology> wrote: > On 12/09/2017 18:50, Johannes Lundberg wrote: >> >> We should have a common repository for all Wayland stuff. I suggest yours >> :) > > Yeah, I'm always open to pull requests. >> >> Maybe now with flavors we can get wayland enabled gtk30 in ports as well? > > It's enabled in the Gnome team's repo, which I have merged into mine. > > https://github.com/freebsd/freebsd-ports-gnome/tree/gnome-3.26 > > I don't think flavors are necessary here, Wayland is already getting enabled > by default in many ports. > Honestly it should be straight up made non-optional, always build Wayland > support everywhere by default. Yeah my idea too but got some serious resistance to that... >> >> Or maybe we should just switch to ravenports if that's easier to work >> with? > > What's ravenports? A very interesting project! *nix ports consolidated. http://www.ravenports.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAECmPwu-1Yj%2BggD4iQ70O2AjRVy8qpHQpC=WWi0TTNVdosfn5A>