x11/brisk-menu: fix dependencies, remove duplicate plist entry
====> Running Q/A tests (stage-qa) Error: /usr/local/libexec/brisk-menu is linked to /usr/local/lib/libX11.so.6 from x11/libX11 but it is not declared as a dependency Warning: you need USE_XORG+=x11 ====> Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist ===> Checking for items in pkg-plist which are not in STAGEDIR Error: Missing: share/glib-2.0/schemas/com.solus-project.brisk-menu.gschema.xml ===> Error: Plist issues found. The schema is already packaged via GLIB_SCHEMAS. http://package21.nyi.freebsd.org/data/113amd64-default-qat/532906/logs/brisk-menu-0.6.0.log
This commit is contained in:
parent
170908f826
commit
007934ce64
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=533660
@ -4,6 +4,7 @@
|
||||
PORTNAME= brisk-menu
|
||||
DISTVERSIONPREFIX= v
|
||||
DISTVERSION= 0.6.0
|
||||
PORTREVISION= 1
|
||||
CATEGORIES= x11
|
||||
|
||||
MAINTAINER= ericbsd@FreeBSD.org
|
||||
@ -16,7 +17,7 @@ LICENSE_FILE_CC-BY-SA-4.0= ${WRKSRC}/LICENSE.CC-BY-SA-4.0
|
||||
|
||||
LIB_DEPENDS= libnotify.so:devel/libnotify
|
||||
|
||||
USES= compiler:c11 gnome mate meson ninja pkgconfig gettext
|
||||
USES= compiler:c11 gettext gnome mate meson ninja pkgconfig xorg
|
||||
MESON_ARGS= --sysconfdir=${PREFIX}/etc
|
||||
|
||||
USE_GITHUB= yes
|
||||
@ -25,6 +26,7 @@ GH_ACCOUNT= getsolus
|
||||
USE_GNOME= gtk30
|
||||
USE_MATE= menus panel
|
||||
GLIB_SCHEMAS= com.solus-project.brisk-menu.gschema.xml
|
||||
USE_XORG= x11
|
||||
|
||||
.if exists(/usr/bin/ld.lld)
|
||||
LDFLAGS+= -fuse-ld=lld
|
||||
|
@ -1,6 +1,5 @@
|
||||
libexec/brisk-menu
|
||||
share/dbus-1/services/org.mate.panel.applet.BriskMenuFactory.service
|
||||
share/glib-2.0/schemas/com.solus-project.brisk-menu.gschema.xml
|
||||
share/icons/hicolor/scalable/actions/brisk_system-log-out-symbolic.svg
|
||||
share/locale/ar/LC_MESSAGES/brisk-menu.mo
|
||||
share/locale/ca/LC_MESSAGES/brisk-menu.mo
|
||||
|
Loading…
Reference in New Issue
Block a user