A maintainer has no rights to create links. Only a project owner can do that. But you should know.
But that was probably exactly the goal with your request. I thought to myself before.
Decorating yourself with strange feathers is not the best way. I know such guys well enough.
But be happy with it.
PS: neochat, at least until now, is one of the worse matrix clients. Something like snoring slowly.
I can understand that he feels that way.
But there is a story behind it.
If you are interested, I can send you an email.
Here we let it rest and finish the topic.
Indeed.
From the build log of the current package in network:messaging:matrix:
[ 81s] CMake Warning:
[ 81s] Manually-specified variables were not used by the project:
[ 81s]
[ 81s] BUILD_STATIC_LIBS
[ 81s] CMAKE_COLOR_MAKEFILE
[ 81s] CMAKE_Fortran_FLAGS
[ 81s] CMAKE_INSTALL_DO_STRIP
[ 81s] CMAKE_MODULES_INSTALL_DIR
[ 81s] CMAKE_VERBOSE_MAKEFILE
[ 81s] LIB_SUFFIX
[ 81s] USE_BUNDLED <--------------------------
Likewise for the maintainers of network:messaging:matrix: please link kquickimageeditor from KDE:Extra as well, we want to maintain that one too and it has been packaged (from the ground up, I wasn't aware there was one here) to conform to the KDE packaging guidelines.
See the comments in https://build.opensuse.org/package/show/KDE:Extra/neochat
Maintainer have no rights to link. Please do it for me.
Sorry, but we as no maintainer don't have these rights either.
Maybe delete the package and create a link? There might be a better way, but I don't know.
A maintainer has no rights to create links. Only a project owner can do that. But you should know. But that was probably exactly the goal with your request. I thought to myself before. Decorating yourself with strange feathers is not the best way. I know such guys well enough. But be happy with it. PS: neochat, at least until now, is one of the worse matrix clients. Something like snoring slowly.
A link is just a "_link" file inside the package, so package maintainers can also create links.
OK. Did it. But it doesn't work with osc on the command line. Or does it?
It should, but it might require
osc linkpac -fto work on an existing package.The
_linkfile looks good, but on https://build.opensuse.org/package/show/network:messaging:matrix/neochat?expand=0, you need to delete all other files as they overwrite the ones from the linked package otherwise.@ecsos, you're now set as maintainer of KDE:Extra/neochat as well
That certainly was not my goal.
And TBH, I find your assertions to be rather offensive.
I just wanted to bring this to an acceptable end.
I can understand that he feels that way. But there is a story behind it. If you are interested, I can send you an email. Here we let it rest and finish the topic.
Who is "he" now?
Do you mean me, or somebody else?
BTW, speaking of "Decorating yourself with strange feathers".
It was you that took my work and submitted it without asking or even crediting me: SR#528666
Thank you again.
But this is so low, I actually didn't want to go down to your level...
Sorry.
Yes. It was my misstake, I explain it and I excuse me. With he I mean I can understand you.
I accept your apologies.
But next time, please think a bit before you submit such comments.
Thank you.
Oh, and I just read everything again, maybe I misunderstood some things and overreacted a bit....
I want to say sorry for that.
This drops
DUSE_BUNDLED=OFF- what does that do?A number of other packages in n:m:m, like nheko, have this switch to disable bundled libraries. But this option is non-existent in neochat.
Indeed.
From the build log of the current package in network:messaging:matrix:
[ 81s] CMake Warning:
[ 81s] Manually-specified variables were not used by the project:
[ 81s]
[ 81s] BUILD_STATIC_LIBS
[ 81s] CMAKE_COLOR_MAKEFILE
[ 81s] CMAKE_Fortran_FLAGS
[ 81s] CMAKE_INSTALL_DO_STRIP
[ 81s] CMAKE_MODULES_INSTALL_DIR
[ 81s] CMAKE_VERBOSE_MAKEFILE
[ 81s] LIB_SUFFIX
[ 81s] USE_BUNDLED <--------------------------
LGTM then
Likewise for the maintainers of network:messaging:matrix: please link kquickimageeditor from KDE:Extra as well, we want to maintain that one too and it has been packaged (from the ground up, I wasn't aware there was one here) to conform to the KDE packaging guidelines.