summaryrefslogtreecommitdiff
path: root/wm/bbconf
AgeCommit message (Collapse)AuthorFilesLines
2006-07-19Drop support for LTCONFIG_OVERRIDE. For quite a long time, pkgsrcjlam1-2/+1
had actually been ignoring LTCONFIG_OVERRIDE anyway and just using the default LIBTOOL_OVERRIDE to replace libtool scripts in packages. This just formalizes the fact that LTCONFIG_OVERRIDE is not used meaningfully by pkgsrc.
2006-05-19Uses C++.joerg1-2/+2
2006-04-17Bump BUILDLINK_ABI_DEPENDS.png and PKGREVISION for png-1.2.9nb2 update.wiz1-2/+2
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-2/+2
2006-01-24Bump BUILDLINK_RECOMMENDED of textproc/expat to 2.0.0 becausewiz1-2/+2
of the shlib major bump. PKGREVISION++ for the dependencies.
2005-11-11reverting unconsidered changestonio5-25/+31
2005-11-11Rename LATEX_ACCEPTED and LATEX_DEFAULT to TEX_ACCEPTED and TEX_DEFAULTtonio5-31/+25
It is more consistent with the tex.buildlink3.mk name. Also, if a package really needs latex, it just has to set TEX_ACCEPTED to latex distributions altough today, all TEX_ACCEPTED possibilities are latex distributions
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-2/+1
Several changes are involved since they are all interrelated. These changes affect about 1000 files. The first major change is rewriting bsd.builtin.mk as well as all of the builtin.mk files to follow the new example in bsd.builtin.mk. The loop to include all of the builtin.mk files needed by the package is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk is now included by each of the individual builtin.mk files and provides some common logic for all of the builtin.mk files. Currently, this includes the computation for whether the native or pkgsrc version of the package is preferred. This causes USE_BUILTIN.* to be correctly set when one builtin.mk file includes another. The second major change is teach the builtin.mk files to consider files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most of the builtin.mk files test for the presence of built-in software by checking for the existence of certain files, e.g. <pthread.h>, and we now assume that if that file is under ${LOCALBASE}, then it must be from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The exceptions to this new check are the X11 distribution packages, which are handled specially as noted below. The third major change is providing builtin.mk and version.mk files for each of the X11 distribution packages in pkgsrc. The builtin.mk file can detect whether the native X11 distribution is the same as the one provided by pkgsrc, and the version.mk file computes the version of the X11 distribution package, whether it's built-in or not. The fourth major change is that the buildlink3.mk files for X11 packages that install parts which are part of X11 distribution packages, e.g. Xpm, Xcursor, etc., now use imake to query the X11 distribution for whether the software is already provided by the X11 distribution. This is more accurate than grepping for a symbol name in the imake config files. Using imake required sprinkling various builtin-imake.mk helper files into pkgsrc directories. These files are used as input to imake since imake can't use stdin for that purpose. The fifth major change is in how packages note that they use X11. Instead of setting USE_X11, package Makefiles should now include x11.buildlink3.mk instead. This causes the X11 package buildlink3 and builtin logic to be executed at the correct place for buildlink3.mk and builtin.mk files that previously set USE_X11, and fixes packages that relied on buildlink3.mk files to implicitly note that X11 is needed. Package buildlink3.mk should also include x11.buildlink3.mk when linking against the package libraries requires also linking against the X11 libraries. Where it was obvious, redundant inclusions of x11.buildlink3.mk have been removed.
2005-04-16nclude converters/libiconv/buildlink3.mk to make this pkg buildkristerw1-1/+2
on NetBSD 1.6.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 checksums to the SHA1 ones.wiz1-1/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-9/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-04-11Convert to buildlink3.snj1-3/+3
2003-07-21COMMENT should start with a capital letter.martti1-2/+2
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2002-09-20buildlink1 -> buildlink2jlam3-7/+9
2002-03-18Initial import of bbconf-1.4:wiz10-0/+144
Welcome to bbconf, the all-in-one blackbox configuration tool. Never heard of blackbox before? Well, let's just say that it's the best Window Manager for X that's out "there" in our humble opinion. Simply put, this little utility here has such lofty goals as being the one place where you can configure anything and everything you need to that has to do with blackbox. bbconf aims to do that through the use of plugins--plugins which allow you to configure anything you wish about blackbox or its helper applications such as bbkeys, bbpager, bbapm, bbmail, bbpal, etc. bbconf is distributed with 4 plugins that allow you to configure blackbox's keybindings, blackbox's styles/themes, and your blackbox menus and submenus. The architecture of the plugins themselves are very simple and elegant -- making it easy for anyone else to add onto the distributed plugins to make it easy to configure whatever else you want to for your blackbox/X sessions.