summaryrefslogtreecommitdiff
path: root/emulators/xtrs
AgeCommit message (Collapse)AuthorFilesLines
2013-04-06"Each sed command should appear in an assignment of its own."rodent1-9/+9
2013-01-13Update to xtrs-4.9dnb1: enable sound support through OSS.is4-10/+28
2013-01-12slipped through the cracks. neeed for 4.9nb5 and later.is1-1/+3
2013-01-12Update to xtrs-4.9d, with lots of bug fixes and improvements.is9-68/+84
2013-01-12Actually install the provided utility disk images with the emulator, sois2-4/+6
that we can swap files back and forth with TRS/80 disk operating systems.
2013-01-12Tim Mann allegedly suggested disabling HAVE_SIGIO for hanging xtrs onis3-3/+17
Linuxes 5 years ago. I see the same problem on NetbSD-6 (at least; didn't try older) and the same cure works.
2012-10-03Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-3/+1
2009-07-08user-destdir supportjoerg1-5/+8
2009-06-14Remove @dirrm entries from PLISTsjoerg1-3/+1
2009-05-20Recursive ABI depends update and PKGREVISION bump for readline-6.0 shlibwiz1-2/+2
major change. Reported by Robert Elz in PR 41345.
2007-07-27Don't use malloc.h.joerg4-1/+40
2007-02-06Modular Xorg support.joerg1-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-15Fix up last commit. Libraries are in ${X11BASE}/lib.joerg1-2/+2
2006-01-12Also replace hard-wired /usr/X11R6 with ${X11BASE}.joerg1-2/+2
2005-07-18The sources assume <malloc.h> exists. Create a fake one for platformskristerw1-1/+9
that don't have it.
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-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests to the SHA1 onesagc1-1/+2
2004-12-03Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.wiz1-2/+2
Suggested by Roland Illig, ok'd by various.
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-25Initial import of xtrs-4.9.uebayasi4-0/+64
xtrs is a Radio Shack TRS-80 Model I/III/4/4P emulator for Unix and the X Window System. It includes lower case, the real time clock, hi-res graphics, serial port, parallel printer, mouse, cassette, sound and music output (requires OSS), 5" and 8" floppy disk drives in single and double density, and even hard disk drives. The emulated floppy and hard disk file formats are compatible with the popular MSDOS-based emulators by Jeff Vavasour, Matthew Reed, and David Keil, and (if you choose a capable enough file format), all features of the original TRS-80 floppy disk controller are emulated. Under Linux, physical floppy disk drives are also supported. Physical cassettes can be read and written too. The user interface is a bit spartan, but it gets the job done.