summaryrefslogtreecommitdiff
path: root/misc/xtide
AgeCommit message (Collapse)AuthorFilesLines
2010-02-04DESTDIR supportjoerg1-3/+7
2009-11-09Kill broken check for finding X11, just wire down our values.joerg3-20/+27
2009-10-28Simplify to not fall into ABI trapsjoerg1-3/+3
2009-10-28Ensure that rpath options have an argument for modular Xorg.joerg1-1/+8
2009-06-14Remove @dirrm entries from PLISTsjoerg1-3/+1
2009-02-08Add a patch to configure so that xtide can compile correctly with a X11cube3-3/+19
distribution in /usr/X11R7. Bump PKGREVISION.
2008-11-10Bump PKGREVISION for libXaw API depends bump due to libXaw8 removal.wiz1-1/+2
2006-12-27- fine grained X11 dependencies for packages which have either USE_IMAKEjoerg1-1/+3
or USE_X11BASE set, but don't include mk/x11.buildlink3.mk directly or via buildlink3.mks - introduce BUILDLINK_PREFIX.libXpm as alias for BUILDLINK_PREFIX.xpm in the !modular case - fix some cases where the check for libX11 couldn't work at all by using C++ for compilation without including the proper headers Verified using a full X11_TYPE=xorg bulk build without additional breakage. Discussed with salo@, wiz@ and send to packages@ for feedback.
2006-12-15Mechanically replace all includes of buildlink3.mk of the followingjoerg1-2/+2
packages with the modular Xorg equivalent. Those are falling back to the old location by default, so this commmit doesn't change dependencies. graphics/xpm ==> x11/libXpm fonts/Xft2 ==> x11/libXft x11/Xfixes ==> x11/libXfixes x11/xcursor ==> x11/libXcursor x11/Xrender ==> x11/libXrender x11/Xrandr ==> libXrandr
2006-11-05Updated xtide to 2.8.3.rillig6-65/+50
Too many changes to list here.
2006-07-22Added "c" to USE_LANGUAGES for packages that use GNU configure scripts,rillig1-2/+2
since they always need a C compiler, even when the source code is completely in C++. For some other packages, stated in the comment that a C compiler is really not needed.
2006-05-15Uses C++.joerg1-1/+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-03Inside of trying to fix a brain damaged configure script which ignoresjoerg2-5/+11
the --x-libraries parameter, just hack the Makefile to use X11BASE.
2005-12-29Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mkjlam1-2/+1
automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-2/+2
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-2/+1
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-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-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digestsagc1-1/+4
2004-11-27Remove maintainer on his request.wiz1-2/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+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-04-11Convert to buildlink3.snj1-4/+4
2003-07-22Honour PKG_SYSCONFDIR and install the configuration file by default (it isjmmv6-21/+20
needed, as pointed out in PR pkg/22187 by Greg Troxel).
2003-05-06Drop trailing whitespace. Ok'ed by wiz.jmmv1-1/+1
2002-10-21Convert to buildlink2.wiz1-4/+4
2002-07-02Add RCS Id.wiz1-0/+1
2002-03-13Give all packages which depend on "png" a version bump, and updatefredb1-2/+3
all dependencies on packages depending on "png" which contain shared libraries, all for the (imminent) update to the "png" package. [List courtesy of John Darrow, courtesy of "bulk-build".]
2002-01-21add missing USE_XPMdmcmahill1-1/+2
2001-11-11Adjust format a bit:hubertf1-0/+5
* 75 * '=' * RCS ID * blank line * message text * optional blank line * 75 * '='
2001-11-01Move pkg/ files into package's toplevel directoryzuntum3-1/+1
2001-08-25make this find shared libs at runtime (-Wl,-R)hubertf2-6/+8
2001-05-31Initial import of xtide-2.4 into the Packages Collection.agc9-0/+137
Provided in PR 13044 by Paul Goyette (paul@whooppee.com) XTide is a package that provides tide and current predictions in a wide variety of formats. Graphs, text listings, and calendars can be generated, or a tide clock can be provided on your desktop. XTide can work with X-windows, plain text terminals, or the web. This is accomplished with three separate programs: the interactive interface (xtide), the non-interactive or command line interface (tide), and the web interface (xttpd). The algorithm that XTide uses to predict tides is the one used by the National Ocean Service in the U.S. It is significantly more accurate than the simple tide clocks that can be bought in novelty stores. However, it takes more to predict tides accurately than just a spiffy algorithm -- you also need some special data for each and every location for which you want to predict tides. XTide reads this data from harmonics files. Ultimately, XTide's predictions can only be as good as the available harmonics data. Due to issues of data availability and of compatibility with non-U.S. tide systems, the predictions for U.S. locations tend to be a lot better on average than those for locations outside of the U.S. * Deviations of 1 minute from official predictions are typical for U.S. locations having the latest data. * Deviations of 20 minutes are typical for non-U.S. locations or U.S. locations that are using obsolete data. * Much longer deviations indicate a problem.