I preinstalled kwin and qutebrowser and pulled the wip-ports zip into 
/usr/ports/mystuff.  Using the recommended build order, everything seems to 
be building fine with the exception of on overlooked "make makesum" for 
lxqt-sudo.

I am starting to see packaging issues:

"Tigger# make install
===>  Checking files for qterminal-1.4.0
`/usr/ports/distfiles/lxqt/qterminal-1.4.0.tar.xz' is up to date.
>> (SHA256) lxqt/qterminal-1.4.0.tar.xz: OK
===> qterminal-1.4.0 depends on: qtermwidget->=1.4.0 - default 
qtermwidget-1.0.0p0 does not match
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2384 
'/usr/ports/pobj/qterminal-1.4.0/.dep-STEM-ge-1.4.0-x11-lxqt-qtermwidget': 
@...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2794 
'/usr/ports/pobj/qterminal-1.4.0/.extract_done': @cd 
/usr/ports/mystuff/x11/...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2233 
'/usr/ports/packages/amd64/all/qterminal-1.4.0.tgz': @cd 
/usr/ports/mystuff/...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2723 
'_internal-package': @case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$( 
mktem...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2702 'package': @:; 
cd /usr/ports/mystuff/x11/lxqt/qterminal && PKGPATH=x11/lxqt/...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2254 
'/var/db/pkg/qterminal-1.4.0/+CONTENTS': @cd 
/usr/ports/mystuff/x11/lxqt/qte...)
*** Error 2 in /usr/ports/mystuff/x11/lxqt/qterminal 
(/usr/ports/infrastructure/mk/bsd.port.mk:2702 'install': 
@lock=qterminal-1.4.0;  expor...)
Tigger# vi Makefile
Tigger# pkg_info | grep qterm
qtermwidget-1.4.0   the terminal widget for QTerminal" 
On Mon, 8 Jan 2024, Rafael Sadowski wrote:

Would you recommend completely replacing the current ports tree with wip-ports 
or is there some way to update the libraries that I did not catch in the 
porting guide?  I had similiar issues with lximage-qt and pcmanfm-qt - both 
fake installs built but had a mismatch.

Thanks

> On Sat Jan 06, 2024 at 11:46:42AM -0800, J. Scott Heppler wrote:
>>
>> Most of the CAD software is Qt Based and I've been running an OpenBSD Dual
>> Boot system with ArchLinux and LXQt.  Essentially, I tried to build the
>> lightest, CAD compatible environment possible.  With all of Rafael Sadows'
>> work, I suspect updating LXQt should be low hanging fruit.
>>
>> My own build uses kwin instead of openbox and the only issue I had was
>> turning off the animation eye candy without kwindowsystems installed.  It
>> was actually a ~/config file that I preserved before deleting kwindowsystem.
>>
>> The older meta-package brought in openbox and gtk dependencies that would be
>> unused code when using kwin.  Kwin should also be more wayland friendly
>> going forward.
>>
>> I think it's worth opening a discussion to set the meta-package structure
>> and get developers behind the project.  I'm not interested in spending days
>> generating patches only to have them ignored for months and go stale.
>>
>> If it can come together, I'll contribute some of the updates.
>> ---
>>
>> J. Scott Heppler
>>
>
> If you want to update and test LXQt 1.4.0 you can find an update diff
> here:
>
> https://github.com/sizeofvoid/wip-ports/commit/79f5e47c05c4a8341e7873dd850e2077ca5e7293
>
> In a Sunday evening mood I update LXQt to 1.4.0 just for fun. It's quite
> straightforward but I don't plan to continue here unless someone starts
> taking a look.
>
> https://twitter.com/sizeofvoid/status/1744090390892867838/photo/1
>
>

-- 
J. Scott Heppler

Penguin Innovations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


NOTICE: This e-mail message and any attachments may
contain legally privileged and confidential information intended
solely for the use of the intended recipients. If you are not an
intended recipient, you are hereby notified that you have
received this message in error and any review, dissemination,
distribution, copying, or other unauthorized use of this email
and any attachment is strictly prohibited. If you have received
this email in error, please notify the sender immediately and
delete the message and any attachments from your system.