summaryrefslogtreecommitdiff
path: root/x11/hsetroot
AgeCommit message (Collapse)AuthorFilesLines
2008-07-14Mark as destdir ready.joerg1-1/+3
2007-01-15Modular Xorg support.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-1/+2
2006-02-03Reset maintainer on his request. PR 32699.wiz1-2/+2
2005-07-25Fix C99 variable declarations to make this pkg compile with gcc 2.95.kristerw2-1/+21
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-2/+2
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-05-22Initial import of hsetroot, version 1.0.2:jmmv4-0/+36
hsetroot is a tool which allows you to compose wallpapers (root pixmaps) for X. It has a lot of options like rendering gradients, solids and images but it also allows you to perform manipulations on those things or chain them together. You could, for example, use one standard background image together with tint to make it fit your current theme. It is also compatible with semi-translucent applications like aterm and xchat. At the moment, hsetroot can render: gradients (multi-color with variable distance), solids (rectangles) and images (centered, tiled, fullscreen, or maximum aspect). It supports the following manipulations: tinting (overlaying a color mask), blurring, sharpening, flipping (horizontally, diagonally, vertically), and also allows you to adjust brightness, contrast and gamma-level. At last, it supports alpha-channels during renders. Package provided by Leonard Schmidt in PR pkg/30304.