summaryrefslogtreecommitdiff
path: root/finance/gnucash/buildlink3.mk
AgeCommit message (Collapse)AuthorFilesLines
2012-09-15recursive bump from libffi shlib major bumpobache1-2/+2
(additionaly, reset PKGREVISION of qt4-* sub packages from base qt4 update)
2012-03-03Recursive bump for pcre-8.30* (shlib major change)wiz1-2/+2
2012-02-06Revbump forwiz1-2/+2
a) tiff update to 4.0 (shlib major change) b) glib2 update 2.30.2 (adds libffi dependency to buildlink3.mk) Enjoy.
2011-05-15pkglint cleanup:wiz1-2/+2
Shorten DESCR. Fix warning in buildlink3.mk. Install config files properly. Bump PKGREVISION for last.
2011-04-22recursive bump from gettext-lib shlib bump.obache1-2/+2
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
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.
2008-10-28Remove some commented lines.wiz1-18/+1
2008-03-07Update path in comment.wiz1-2/+2
2008-03-06Recursive PKGREVISION bump for gnutls-2.2.2 update with shlib major bump.wiz1-2/+2
2008-01-18Per the process outlined in revbump(1), perform a recursive revbumptnn1-2/+2
on packages that are affected by the switch from the openssl 0.9.7 branch to the 0.9.8 branch. ok jlam@
2008-01-12Fix path to package dir.wiz1-2/+2
2007-09-21Fix paths for GConf, libglade, libart, libsigc++, lablgtk moves.wiz1-2/+2
Bump PKGREVISION.
2007-07-19Update to 2.2.0, based on gnucash-current package.wiz1-4/+4
2.2.0 - 14 July 2007 o Welcome to the GnuCash 2.2.0 Release. o With this new release series, GnuCash is available on Microsoft Windows for the first time, and it also runs on GNU/Linux, *BSD, Solaris and Mac OSX. o This release has only a few user-visible new features, except for the completed port to the Microsoft Windows operating system. In summary, the following features are new, compared to the older 2.0.x series: o Port to Microsoft Windows completed. Note that Windows 2000, XP, or Vista is required; GnuCash does not run on Windows 98 or 95. o Data file notice: In version 2.1.2 the format for scheduled transactions in the data file was changed. Files using the old format will be read without problems by this new version, but the new version of GnuCash only writes the new format. The new file format cannot be loaded by older versions of GnuCash. (If you try, the file will fail to be loaded with an error message.) As a result, if you begin using the new Gnucash, and you have data files with scheduled transactions, then these files will not be readable by older versions. If you have to make a new data file readable by older versions of GnuCash, this can be achived by deleting all records of scheduled transactions in the scheduled transaction editor. o SWIG is now used instead of g-wrap for providing language bindings. o The Scheduled Transaction list view is now improved and summarized more compactly. The Since-Last-Run dialog has been simplified. o Check printing has been improved, with new formats and simpler format descriptions. o Automatic saving of the data file was added. o Bugfixes and improvements since the last version 2.1.5 include: o Updated translations. o Improved handling of Online Banking wizard on Windows.
2007-06-05opencdk shlib major changed; bump ABI depends and PKGREVISIONs ofwiz1-2/+2
affected packages.
2007-05-05Adapt for move of misc/goffice to misc/goffice0.2.wiz1-2/+2
2007-03-21Bump PKGREVISION for gnome-keyring ABI bump.wiz1-1/+2
2007-01-17Add buildlink3.mk file for dependencies.wiz1-0/+38
XXX: further bl3.mk files might need to be included, but the current state suffices for the one dependency I know of.