- Chase libftdi update - Bump PORTREVISION - Remove MD5 checksumf5b86c8ebe
Port details
comms/lirc0.9.0_14,1
Linux Infrared Remote Control
- Maintainer
- ports@FreeBSD.org
- Packages
- lirc 0.9.0_14,1
- Upstream
- Higher version available: 0.10.2
- CPE
- none, CVEs only via VuXML
- WWW
- https://www.lirc.org/
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (94)
And this was missed too, doh!8de4beafc1
Also commit this that was just missed.b7cc32da9b
- Add an example lircd.conf that's preconfigured for use with webcamd, either with USB DVB tuner remotes supported by the Linux drivers by default that webcamd uses, or for remotes supplied with MCE USB IR receivers. - Bump PORTREVISION.6c6ae31690
- Adjust pkg-message after remote support has been committed to the webcamd port. - Bump PORTREVISION.b3b20f5e8a
- Update comms/lirc to 0.9.0p1_4 in order to be able to use the lirc support in webcamd svn (for mceusb-based receivers/transmitters and USB DVB tuner remotes supported by the Linux code), and enable support for a few more USB devices while we're at it tho of those only an FTDI-based one was tested:
http://www.huitsing.nl/irftdi/ [1]
- Fix plist for audio/rhythmbox and multimedia/totem and
add missing LIRC_{CFLAGS,LIBS} variables to CONFIGURE_ENV for
multimedia/xine when building them with (optional) lirc support. [2]
- Chase liblirc_client shlib version bump for ports depdending on it
and bump PORTREVISIONs for ports depending on it by default.
Approved by: portmgr (miwi) [2]
Thanks to: Warren Block <wblock@wonkity.com> for testing [1]0edca97428Sync to new bsd.autotools.mk4a8684e352
Begin the process of deprecating sysutils/rc_subr by s#. %%RC_SUBR%%#. /etc/rc.subr#1d6b4b3f91
- Switch SourceForge ports to the new File Release System: categories starting with B,Cc926af277e
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22. -Update libtool and libltdl to 2.2.6a. -Remove devel/libtool15 and devel/libltdl15. -Fix ports build with libtool22/libltdl22. -Bump ports that depend on libltdl22 due to shared library version change. -Explain what to do update in the UPDATING. It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop and applications in the runtime. With help: marcus and kwm Pointyhat-exp: a few times by pav Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and a few MarcusCom CVS users. Also, I might have missed a few. Repocopy by: marcus Approved by: portmgr789d75c728
Fix a few "bad example" problems in the rc.d scripts that have been propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.0175383f0a- Remove conditional checks relevant only on FreeBSD 5.x and olderc4d4cacd63
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script. Specifically, newer autoconf (> 2.13) has different semantic of the configure target. In short, one should use --build=CONFIGURE_TARGET instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)741aa71483- Remove USE_XLIB/USE_X_PREFIX/USE_XPM in favor of USE_XORG - Bump PORTREVISION Approved by: portmgr (xorg cleanup)5afc678aac
- Remove USE_GETOPT_LONG which is a no-op since March 2007dad0d0873a
- Welcome X.org 7.2 \o/. - Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}. - Bump PORTREVISION for ports intalling files in ${X11BASE}.d4f0d0048aDon't install the config file. Requested by: kris Submitted by: Daniel O'Connor (maintainer)5aad167b56
Add support for DVICO USB remote control. Submitted by: grog Approved by: Daniel O'Connor (maintainer)db4012df9a
Use libtool port instead of included version to avoid objformat a.out botchae994c8ea8
- Update to 0.8.0 - Hack configure so produced daemon binary is ready to use with third party kernel drivers. - Make libirman support optional. - Move daemon communication sockets under /var/run/lirc. - Add startup script. - Use bzip2. - Minor cleanups. Approved by: maintaner4d529a51ea
Don't offer irman as an option. It's required to build the port. Submitted by: Daniel O'Connor (maintainer)38db3f95fd
- portlint(1) PR: 95766 Submitted by: Alexander Botero-Lowry <alex___foxybanana.com> Approved by: maintainer timeout (14 days)2d214c77cd
Conversion to a single libtool environment. Approved by: portmgr (kris)8503536d38
SHA256ify Approved by: krion@acd87b4ad8
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present in bsd.autotools.mk essentially makes this a no-op given that all the old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in exactly the same way as USE_AUTOTOOLS itself. Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME team -- all GNOME 2.12.x ports use it. Preliminary documentation can be found at: http://people.FreeBSD.org/~ade/autotools.txt which is in the process of being SGMLized before introduction into the Porters Handbook. Light blue touch-paper. Run.54a0b86543
Back out previous commit, the pkg-plist may have been fixed already.eb4ad1a3db
BROKEN: Incorrect pkg-plist782ca95093
Fix INDEX build, and correct broken dependency. Reported by: kris' make index script Approved by: portmgr hat8596b2cc79
* Daniel O'Connor <doconnor@gsoft.com.au> has agreed to take over maintainership as I don't actively use this port anymore.12f1ea4b19
* Patch for vga on i386. PR: ports/878326add713f17
* Update to 0.7.2. PR: ports/86528 Submitted by: Daniel J. O'Connor <darius@dons.net.au>3ef2cf17d7
At Kris's request, back out the MACHINE_ARCH spelling correction until after 5.4-RELEASE.c3d8037aeb
Assist getting more ports working on AMD64 by obeying the Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.f2fc2d60ae
Set the device directory to /var/lirc and check for libirman in the correct location. Submitted by: Lewis Thompson <purple@lewiz.net> PR: ports/7519097609abfad
Add capability to build with libirman support. Suggested and tested by: dennis@rootxs.nl92b6b2ba88
Apply a big libtool patch to allow porters to use the libtool installed by the libtoolX ports instead of the one included with each port. Ports that set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of the included version. To restore previous behavior, use the new macro, USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version. For example, to use the ports version of libtool-1.5, add the following to your Makefile: USE_LIBTOOL_VER= 15 To use the included version of libtool with extra hacks provided by libtool-1.5, add the following to your Makefile: USE_INC_LIBTOOL_VER= 15 With this change, ports that had to add additional libtool hacks to prevent .la files from being installed or to fix certain threading issues can now delete those hacks (after appropriate testing, of course). PR: 63944 Based on work by:eik and marcus Approved by: ade (autotools maintainer) Tested by: kris on pointyhat Bound to be hidden problems: You bet9e5632dd66
Add size data, approved by maintainers.3bca696b10
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.3f651573adFix plist & unmark broken.1cca8a633c
BROKEN: Broken pkg-plist1b2114b544
Respect CFLAGS; utilize USE_GETOPT_LONG; utilize USE_LIBTOOL. PR: ports/59842 Submitted by: Ports Fury Approved by: maintainer timeout (6 weeks)d00fb69ce5
Bump PORTREVISION on all ports that depend on gettext to aid with upgrading. (Part 2)053fdb6a6b
Add USE_XLIB to the ports Makefile Noticed by: bento835ea5d077
New port: comms/lirc: Linux Infared Remote Control This is a port of the LIRC, Linux Infrared Remote Control, package (www.lirc.org). This port installs the daemons and tools for interacting with device drivers that support the LIRC device interface. The port does not install any FreeBSD infrared device drivers yet; the user must obtain these from third parties or port the existing Linux drivers. PR: ports/46774 Submitted by: Mike Heffner <mikeh@FreeBSD.org> <mheffner@acm.vt.edu>627aa4a08e