Differential D10971 Diff 26461 package.yml

Changeset View

Standalone View

package.yml

	name : qt5-tools			name : qt5-tools
	version : 5.15.3			version : 5.15.3
	release : 24			release : 25
	source :			source :
	- git\|https://invent.kde.org/qt/qt/qttools.git : 33693a928986006d79c1ee743733cde5966ac402			- git\|https://invent.kde.org/qt/qt/qttools.git : 33693a928986006d79c1ee743733cde5966ac402
	homepage : https://www.qt.io			homepage : https://www.qt.io
	license :			license :
	- GPL-3.0-or-later			- GPL-3.0-or-later
	- LGPL-2.1-or-later			- LGPL-2.1-or-later
	- LGPL-3.0-or-later			- LGPL-3.0-or-later
	- GFDL-1.3-or-later			- GFDL-1.3-or-later
	component :			component :
	- desktop.qt			- desktop.qt
	- demos : programming.library			- demos : programming.library
	summary : Qt5 QtTools Module			summary : Qt5 QtTools Module
	description: \|			description: \|
	Qt is a set of libraries for developing applications. This package contains base tools, like string, xml, and network handling.			Qt is a set of libraries for developing applications. This package contains base tools, like string, xml, and network handling.
	builddeps :			builddeps :
	- pkgconfig(libxslt)			- pkgconfig(libxslt)
	- pkgconfig(Qt5Qml)			- pkgconfig(Qt5Qml)
				- llvm-clang-devel
				GirtabluluUnsubmitted Not Done Inline Actions if you use the flag clang : yes should work as well Girtablulu: if you use the flag clang : yes should work as well
				livingsilver94AuthorUnsubmitted Done Inline Actions It's different. By including `llvm-clang-devel` we use GCC to build the package while allowing qdoc to use clang's parsing functions for its jobs. If we set `clang: yes`, we're both allowing qdoc to use clang (because we're still including `llvm-clang-devel`) AND we're building the whole package with clang. So if you're OK with building qt5-tools with clang, all great, otherwise including `llvm-clang-devel` is the right choice. livingsilver94: It's different. By including `llvm-clang-devel` we use GCC to build the package while allowing…
				livingsilver94AuthorUnsubmitted Done Inline Actions Another solution would be taking out libclang from `llvm-clang` and putting it into its own package, but that's something Core should decide. livingsilver94: Another solution would be taking out libclang from `llvm-clang` and putting it into its own…
				GirtabluluUnsubmitted Not Done Inline Actions no, we will do it your way. lets stay with all qt5 packages using gcc Girtablulu: no, we will do it your way. lets stay with all qt5 packages using gcc
	- vulkan-headers			- vulkan-headers
	patterns :			patterns :
	- demos : /usr/lib64/qt5/examples			- demos : /usr/lib64/qt5/examples
	- devel :			- devel :
	- /usr/bin			- /usr/bin
	- /usr/share/applications			- /usr/share/applications
	- /usr/share/icons			- /usr/share/icons
	- main :			- main :
	Show All 19 Lines