New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
graphene: update to 1.10.0 #20289
graphene: update to 1.10.0 #20289
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,25 @@ | ||
# Template file for 'graphene' | ||
pkgname=graphene | ||
version=1.8.2 | ||
revision=2 | ||
version=1.10.0 | ||
revision=1 | ||
build_style=meson | ||
build_helper="gir" | ||
configure_args="-Dtests=false -Dbenchmarks=false | ||
-Dintrospection=$(vopt_if gir true false)" | ||
-Dintrospection=$(vopt_if gir true false) -Darm_neon=false" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I remember correctly NEON is not architectural in armv6 and armv7, so apart of circumventing the error we can ensure compatibility with all armv* devices regardless of the extensions present on their CPUs. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Neon was introduced with armv7 but support was optional. Void does not use neon for armv7 (with some exceptions). So for armv6 and armv7 this is ok, but it should not be disabled for armv8 / aarch64. |
||
hostmakedepends="pkg-config" | ||
makedepends="libglib-devel" | ||
short_desc="Thin layer of types for graphic libraries" | ||
maintainer="Enno Boland <gottox@voidlinux.org>" | ||
license="MIT" | ||
homepage="https://github.com/ebassi/graphene" | ||
distfiles="${GNOME_SITE}/graphene/${version%.*}/graphene-${version}.tar.xz" | ||
checksum=b3fcf20996e57b1f4df3941caac10f143bb29890a42f7a65407cd19271fc89f7 | ||
checksum=406d97f51dd4ca61e91f84666a00c3e976d3e667cd248b76d92fdb35ce876499 | ||
|
||
build_options="gir" | ||
build_options_default="gir" | ||
|
||
post_install() { | ||
vlicense LICENSE | ||
vlicense LICENSE.txt | ||
} | ||
|
||
graphene-devel_package() { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we were supposed to make sobumps each time we update libraries, sorry if thats not the case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well if thats the case I was working on a
mutter
update that needs the new symbols provided (at leastmeson
enforces such version), but I didn't know that back then.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Package version shouldn't need to be changed in common/shlibs unless the soname/symbols change.