Hi! Would you consider changing lxqt-meta's dependencies on specific LXQt packages to say '>=lxqt-foo-${MY_PV}' instead of '=lxqt-foo-${MY_PV}*'? With the current '=' constraint, this prevents usage of -9999 packages, which in my case I want to pull in a fix for a qterminal rendering issue. The fix is spread over a bunch of commits, so it's easier to run git master than use /etc/portage/patches. RDEPEND=" =lxqt-base/lxqt-config-${MY_PV}* =lxqt-base/lxqt-globalkeys-${MY_PV}* =lxqt-base/lxqt-menu-data-${MY_PV}* =lxqt-base/lxqt-notificationd-${MY_PV}* about? ( =lxqt-base/lxqt-about-${MY_PV}* ) terminal? ( =x11-terms/qterminal-${MY_PV}* ) <etc etc...> " Some arguments against are that only qtermwidget and qterminal have 9999 versions currently and for this particular case I could set USE=-terminal instead, but it seems useful to allow 9999 in general. Asking in case you agree.
> but it seems useful to allow 9999 in general. Or if not -9999, consider "newer versions of specific packages to fix bugs."
Not sure I'd want to do that for the meta package. Could lead into some funny issues with mixing 9999 packages in for example indeed. You can always just not use the meta at all if you like to go adventurous. :] Or... use the 9999 meta. It has been pretty dang stable for me heh. I will ponder about this more though.
For the 9999s, I believe it is best to use 9999 for all the related packages together, and for bug fixes, as long as there is a point release, that is already allowed since '${MY_PV}*' here expands to '2.1*' for lxqt-meta-2.1.0 for example. Can always backport a patch if critical enough, and there is no point release upstream, but upstream usually does do those for important enough changes. I'll close this for now, but thank you for the report in any case!
