kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/net/gnome-online-accounts/Makefile

36 lines
1.3 KiB
Makefile
Raw Normal View History

revbump for libsoup's ABI issue
2016-05-03 13:40:00 +02:00
# $NetBSD: Makefile,v 1.6 2016/05/03 11:40:06 prlw1 Exp $
Import gnome-online-accounts-3.16.3 as net/gnome-online-accounts. Gnome Online Accounts (GOA) provides a centralized service that allows a set of online accounts to be configured for use with core GNOME applications. In UX terms, GOA provides a static list of online accounts that can be setup by users (through the Online Accounts panel in System Settings). These accounts can then be used by core GNOME applications. While third party applications can access the accounts setup through GOA, this is not its explicit goal, nor does GOA set out to enable third party applications to add online accounts of their own. There are several reasons for this: * Third-party applications should be able to identify themselves to online services for the purposes of branding and tracking. * Third-party applications shouldn't be able to identify themselves under a generic OS or distributor key - this would be misleading as to what is actually accessing the account, and would prevent there from being specific contracts of trust between users and applications who access their data. * It would prevent users from blocking specific applications from accessing their account (should an application sandboxing framework come into effect).
2015-07-12 02:46:43 +02:00
DISTNAME= gnome-online-accounts-3.16.3
revbump for libsoup's ABI issue
2016-05-03 13:40:00 +02:00
PKGREVISION= 4
Import gnome-online-accounts-3.16.3 as net/gnome-online-accounts. Gnome Online Accounts (GOA) provides a centralized service that allows a set of online accounts to be configured for use with core GNOME applications. In UX terms, GOA provides a static list of online accounts that can be setup by users (through the Online Accounts panel in System Settings). These accounts can then be used by core GNOME applications. While third party applications can access the accounts setup through GOA, this is not its explicit goal, nor does GOA set out to enable third party applications to add online accounts of their own. There are several reasons for this: * Third-party applications should be able to identify themselves to online services for the purposes of branding and tracking. * Third-party applications shouldn't be able to identify themselves under a generic OS or distributor key - this would be misleading as to what is actually accessing the account, and would prevent there from being specific contracts of trust between users and applications who access their data. * It would prevent users from blocking specific applications from accessing their account (should an application sandboxing framework come into effect).
2015-07-12 02:46:43 +02:00
CATEGORIES= net devel
MASTER_SITES= ${MASTER_SITE_GNOME:=sources/gnome-online-accounts/3.16/}
EXTRACT_SUFX= .tar.xz
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= https://wiki.gnome.org/Projects/GnomeOnlineAccounts
COMMENT= Service that allows online accounts to be used with GNOME
LICENSE= gnu-gpl-v2
BUILD_DEPENDS+= gtk-doc>=1.3:../../textproc/gtk-doc
BUILD_DEPENDS+= gdbus-codegen-[0-9]*:../../devel/gdbus-codegen
GNU_CONFIGURE= yes
USE_LIBTOOL= yes
USE_PKGLOCALEDIR= yes
Needs msgfmt.
2015-09-17 19:12:38 +02:00
USE_TOOLS+= gmake intltool pkg-config msgfmt
Import gnome-online-accounts-3.16.3 as net/gnome-online-accounts. Gnome Online Accounts (GOA) provides a centralized service that allows a set of online accounts to be configured for use with core GNOME applications. In UX terms, GOA provides a static list of online accounts that can be setup by users (through the Online Accounts panel in System Settings). These accounts can then be used by core GNOME applications. While third party applications can access the accounts setup through GOA, this is not its explicit goal, nor does GOA set out to enable third party applications to add online accounts of their own. There are several reasons for this: * Third-party applications should be able to identify themselves to online services for the purposes of branding and tracking. * Third-party applications shouldn't be able to identify themselves under a generic OS or distributor key - this would be misleading as to what is actually accessing the account, and would prevent there from being specific contracts of trust between users and applications who access their data. * It would prevent users from blocking specific applications from accessing their account (should an application sandboxing framework come into effect).
2015-07-12 02:46:43 +02:00
.include "../../chat/telepathy-glib/buildlink3.mk"
.include "../../devel/glib2/buildlink3.mk"
.include "../../devel/glib2/schemas.mk"
.include "../../devel/gobject-introspection/buildlink3.mk"
.include "../../graphics/hicolor-icon-theme/buildlink3.mk"
.include "../../net/libsoup/buildlink3.mk"
.include "../../security/libsecret/buildlink3.mk"
.include "../../sysutils/dbus-glib/buildlink3.mk"
.include "../../textproc/json-glib/buildlink3.mk"
.include "../../textproc/libxml2/buildlink3.mk"
.include "../../www/librest07/buildlink3.mk"
.include "../../www/webkit-gtk/buildlink3.mk"
.include "../../x11/gtk3/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink