> On Oct 29, 2021, at 10:12 AM, Frederic Cambus <f...@statdns.com> wrote:
>
> On Fri, Oct 15, 2021 at 07:20:00AM +0200, Rafael Sadowski wrote:
>
>> I could imagine the time is right, so soon after the release. I would
>> like to import initial wayland ports and thus also a new category
>> "wayland".
>>
>> I realise that it will take time for wayland to work, but that is not
>> important for now.
>>
>> Example: x11/kde-applications/spectacle
>>
>> Spectacle needs kwayland/qtwayland as a strong dependency (I can build
>> this) to be able to take screenshots under either X11 or wayland. Means
>> it is not needed at runtime but we can update it. (Currently stuck at a
>> very old version).
>>
>> Does this make sense to you? Is a new category OK for you?
>>
>> I would be very happy to receive feedback from all porters.
>
> Thanks for looking into this.
>
> I think it would make sense to import them if it makes your work on
> KDE easier. Also, being proactive regarding Wayland will allow to start
> upstreaming patches and ensure it at least keeps building on OpenBSD,
> so I view this as a good thing.
>
> The potential downsides I see is that those packages might be auto-
> detected at configure time by some of our existing ports, and some ports
> might need to be adjusted. Another question is how much time this will
> be adding to bulk builds, could you give some information about how long
> it takes to build those packages on your machine?
>
> No strong opinion regarding adding a new category, I noticed the other
> BSDs didn't seem to create a new category but this doesn't mean we
> shouldn't do it.
>
Sorry for not replying earlier. I was very happy to see these and would like to
play around with wayland so ok daniel@ to import and we can work on in the tree
as needed.
As for a new category, is it expected to grow beyond a few ports? We have this
weird java category which I think is pretty useless for example. Who cares if
something is written in Java (we don’t have perl, ruby, python categories).
Those ports should be in their functional categories.
Personally I would probably lean toward putting wayland under x11 and any
wayland ports not part of wayland itself in the right categories for those
ports. Unless (and I haven’t looked), the wayland platform ports are expected
to be numerous.
ps. I agree with comment above on things that might pick up wayland at config
time, although probably adding to the tree and getting into bulks could be a
good way to find out…
