kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/p5-sybperl/Makefile

42 lines
1.1 KiB
Makefile
Raw Normal View History

Reset maintainer, developer lost his commit bit.
2010-03-21 17:29:38 +01:00
# $NetBSD: Makefile,v 1.16 2010/03/21 16:29:39 wiz Exp $
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
#
DISTNAME= sybperl-2.16
PKGNAME= p5-${DISTNAME}
Recursive PKGREVISION bump for jpeg update to 8.
2010-01-17 13:02:03 +01:00
PKGREVISION= 7
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
CATEGORIES= databases perl5
MASTER_SITES= http://www.peppler.org/downloads/
Reset maintainer, developer lost his commit bit.
2010-03-21 17:29:38 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev.
2006-10-04 22:46:42 +02:00
HOMEPAGE= http://www.peppler.org/freeware/sybperl.html
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
COMMENT= Perl modules for using Sybase/MS-SQL databases
Add DESTDIR support.
2008-06-12 04:14:13 +02:00
PKG_DESTDIR_SUPPORT= user-destdir
Turn PERL5_PACKLIST into a relative path instead of an absolute path. These paths are now relative to PERL5_PACKLIST_DIR, which currently defaults to ${PERL5_SITEARCH}. There is no change to the binary packages.
2005-07-13 20:01:18 +02:00
PERL5_PACKLIST= auto/Sybase/.packlist
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
BUILD_DEFS+= USE_SYBASE_OPENCLIENT
BUILD_DEFS+= SYBASE
.if defined(USE_SYBASE_OPENCLIENT) && empty(USE_SYBASE_OPENCLIENT:M[Nn][Oo])
. if defined(SYBASE) || exists(${SYBASE}/lib/libct.so)
BUILDLINK_PASSTHRU_DIRS=${SYBASE}
_SYBASE= ${SYBASE}
. else
PKG_FAIL_REASON+= "You must define SYBASE to the base directory of your Open Client."
. endif
.else
Bump PKGREVISION. (The freetds libraries used are in a new location due to freetds installation changes and may also depend on gettext-lib.) Include buildlink for gettext-lib, because CTlib.so uses libintl.so (noticed on build failure on DragonFly and then saw on NetBSD 2.1 too). Remove freetds subdirectory from the buildlink directory used during build. (This is because of recent installation changes for freetds.)
2006-01-04 20:39:33 +01:00
_SYBASE= ${BUILDLINK_PREFIX.freetds}
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
.endif
Replace RPATH_FLAG with LINKER_RPATH_FLAG and COMPILER_RPATH_FLAG, which are the full option names used to set rpath directives for the linker and the compiler, respectively. In places were we are invoking the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is inserted in case the flag is a word, e.g. -rpath. The default values of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the compiler that you use. They may be overridden on a ${OPSYS}-specific basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG, respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
2004-08-27 08:29:06 +02:00
PERL5_LDFLAGS+= ${COMPILER_RPATH_FLAG}${_SYBASE}/lib
Fixed pkglint warnings. The warnings are mostly quoting issues, for example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-12-05 21:49:47 +01:00
MAKE_ENV+= SYBASE=${_SYBASE:Q}
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
.if !defined(USE_SYBASE_OPENCLIENT)
Convert to buildlink3.
2004-05-08 06:50:50 +02:00
. include "../../databases/freetds/buildlink3.mk"
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
.endif
Bump PKGREVISION. (The freetds libraries used are in a new location due to freetds installation changes and may also depend on gettext-lib.) Include buildlink for gettext-lib, because CTlib.so uses libintl.so (noticed on build failure on DragonFly and then saw on NetBSD 2.1 too). Remove freetds subdirectory from the buildlink directory used during build. (This is because of recent installation changes for freetds.)
2006-01-04 20:39:33 +01:00
.include "../../devel/gettext-lib/buildlink3.mk"
Initial import of p5-sybperl-2.16 into the NetBSD packages collection. sybperl includes four modules: Sybase::DBlib, Sybase::CTlib, Sybase::BCP and Sybase::Sybperl. The first two implement a thin wrapper around the Sybase DB-Library and Client Library APIs, respectively. Sybase::BCP is a specialty module aimed at doing Bulk-Copy operations, and Sybase::Sybperl is a compatibility module with sybperl 1.xx (i.e. with the perl 4.x version). The sybperl modules are thin wrappers around the Sybase APIs. This is both good and bad. It's good because you have greater control, and because the API is (obviously) close to the way the server and the protocol work. It's bad in that it's a proprietary API, and that it is somewhat verbose.
2004-03-29 12:01:33 +02:00
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink