Bug 181872

Summary:	Large parts of the installation does not respect prefix
Product:	[Unmaintained] bindings	Reporter:	Allan Sandfeld <kde>
Component:	general	Assignee:	kde-bindings
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bugzilla.kde, opensource
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Dump of installation

Description Allan Sandfeld 2009-01-25 15:40:10 UTC

Version:            (using KDE 4.2.0)
Installed from:    Compiled From Sources

When configuring and installing kdebindings, some paths are set completely wrong. The has the consequence of installing parts of the module in places it does not belong. The bugs seems to be mainly in the Ruby and PyKDE4 bindings.

The wrong paths that I've noticed is:
/usr/local/lib/site_ruby
/usr/lib/python2.5/site-packages/PyKDE4
/usr/share/sip/PyKDE4

Comment 1 Allan Sandfeld 2009-01-25 15:42:37 UTC

Created attachment 30590 [details]
Dump of installation

This is a dump of the installation. The prefix was set to /opt/kde-4.2.

Any file installed to another prefix, especially those installed to system-prefix are installed incorrectly and breaks the system.

Comment 2 Ben Boeckel 2009-01-25 20:24:39 UTC

It seems as though the following does not use CMAKE_INSTALL_PREFIX:

ruby/qtruby/CMakeLists.txt:
SET(CUSTOM_RUBY_SITE_ARCH_DIR ${RUBY_SITE_ARCH_DIR} CACHE DIR "custom installation directory for ruby binary extension" )
SET(CUSTOM_RUBY_SITE_LIB_DIR ${RUBY_SITE_LIB_DIR} CACHE DIR "custom installation directory for ruby extension" )

python/pykde4/CMakeLists.txt:
PYTHON_INSTALL(${CMAKE_CURRENT_BINARY_DIR}/pykdeconfig.py ${PYTHON_SITE_PACKAGES_DIR}/PyKDE4)

Maybe these are getting in the way of having the prefix set correctly. I'm not sure, but maybe this needs fixing in Python and Ruby CMake configs?

Comment 3 Pino Toscano 2009-02-05 12:59:20 UTC

For PyKDE there is bug #174806.

Comment 4 Justin Zobel 2021-03-09 05:24:38 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 5 Mathieu Jobin 2022-12-22 06:53:19 UTC

QtRuby only existed for Qt4 and Korundum, which never got updated for 5.x

This is unmaintained and any effort towards QtRuby for Qt6 will be from scratch.

Therefore, closing this ticket