kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/finance/libofx/buildlink3.mk

17 lines
441 B
Makefile
Raw Normal View History

Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these.
2012-05-07 03:53:12 +02:00
# $NetBSD: buildlink3.mk,v 1.10 2012/05/07 01:53:29 dholland Exp $
Initial import of libofx-0.8.0, based on the package provided by Gary Duzan in PR 32439: This is the LibOFX library. It is a parser and an API designed to allow applications to very easily support OFX command responses, usually provided by financial institutions for statement downloads. To my knowledge, it is the first working OpenSource implementation of the OFX (Open Financial eXchange) specification on the client side.
2006-02-05 23:25:01 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= libofx
Initial import of libofx-0.8.0, based on the package provided by Gary Duzan in PR 32439: This is the LibOFX library. It is a parser and an API designed to allow applications to very easily support OFX command responses, usually provided by financial institutions for statement downloads. To my knowledge, it is the first working OpenSource implementation of the OFX (Open Financial eXchange) specification on the client side.
2006-02-05 23:25:01 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
.if !defined(LIBOFX_BUILDLINK3_MK)
LIBOFX_BUILDLINK3_MK:=
Initial import of libofx-0.8.0, based on the package provided by Gary Duzan in PR 32439: This is the LibOFX library. It is a parser and an API designed to allow applications to very easily support OFX command responses, usually provided by financial institutions for statement downloads. To my knowledge, it is the first working OpenSource implementation of the OFX (Open Financial eXchange) specification on the client side.
2006-02-05 23:25:01 +01:00
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILDLINK_API_DEPENDS.libofx+= libofx>=0.8.0
Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these.
2012-05-07 03:53:12 +02:00
BUILDLINK_ABI_DEPENDS.libofx+= libofx>=0.9.1nb1
Initial import of libofx-0.8.0, based on the package provided by Gary Duzan in PR 32439: This is the LibOFX library. It is a parser and an API designed to allow applications to very easily support OFX command responses, usually provided by financial institutions for statement downloads. To my knowledge, it is the first working OpenSource implementation of the OFX (Open Financial eXchange) specification on the client side.
2006-02-05 23:25:01 +01:00
BUILDLINK_PKGSRCDIR.libofx?= ../../finance/libofx
Fixed pkglint warnings.
2006-06-14 12:26:42 +02:00
BUILDLINK_INCDIRS.libofx+= include/libofx
Initial import of libofx-0.8.0, based on the package provided by Gary Duzan in PR 32439: This is the LibOFX library. It is a parser and an API designed to allow applications to very easily support OFX command responses, usually provided by financial institutions for statement downloads. To my knowledge, it is the first working OpenSource implementation of the OFX (Open Financial eXchange) specification on the client side.
2006-02-05 23:25:01 +01:00
.include "../../textproc/opensp/buildlink3.mk"
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
.endif # LIBOFX_BUILDLINK3_MK
Initial import of libofx-0.8.0, based on the package provided by Gary Duzan in PR 32439: This is the LibOFX library. It is a parser and an API designed to allow applications to very easily support OFX command responses, usually provided by financial institutions for statement downloads. To my knowledge, it is the first working OpenSource implementation of the OFX (Open Financial eXchange) specification on the client side.
2006-02-05 23:25:01 +01:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= -libofx
Reference in a new issue Copy permalink