EDE (Equinox Desktop Environment) is simple and fast desktop
environment with familiar look and feel. EDE uses FLTK toolkit for
GUI presentation and UNIX philosophy for its design.
With UNIX philosophy, EDE splits each component in separate executable
entity to do one job and do it good. This makes EDE very easy to
alter for user needs and requirements.
EDE is light and fast. It uses C++ carefully yielding fast startup,
low memory usage and great portability. Also, we care not only about
how fast EDE runs, but how much time is needed to compile it.
These facts makes EDE a perfect desktop environment for older
computers and embedded devices. But, you can use it on your everyday
hardware too.
Comments landry@ jca@
ok landry@
tweak the plist to get a smooth removal of hs-monads-fd.
No objections dcoppa@
Update path tested on a sane set of installed hs-* packages
byo David Schaefer (thanks!).
when a man(7) input file contains two consecutive .TP lines.
This bugfix improves the formatting of unzip(1), for example.
While here, recognize 5.4 as an OpenBSD version in mdoc(7) files.
ok sthen@ dcoppa@ espie@
the current mess is that libtool allows things to link because of the .la,
but the configure script, as usual, fucks up, because it tries to link
directly, so both -lintl and -lX11 detections fail.
kind of sneaky with X11, as some values are cached, so X11 is detected,
BUT some other values are not, and they're not cached, so that ends up
with a paralytic X11 that misses half the useful functionalities it
actually has...
immediately fails at startup:
xmobar: user error (Text.Regex.Posix.String died: (ReturnCode 13,"repetition-operator operand invalid"))
when using the StdinReader plugin.
So do what's required with Text.Regex.PCRE instead of Text.Regex.Posix.
Code contributed by Alexander Polakov, thanks!
LLDP (Link Layer Discovery Protocol) is an industry standard protocol
designed to supplant proprietary Link-Layer protocols such as
Extreme's EDP (Extreme Discovery Protocol) and CDP (Cisco Discovery
Protocol). The goal of LLDP is to provide an inter-vendor compatible
mechanism to deliver Link-Layer notifications to adjacent network
devices.
lldpd implements both reception and sending. It also implements an
SNMP subagent for net-snmp to get local and remote LLDP
information. The LLDP MIB is partially implemented but the most useful
tables are here. lldpd also partially implements LLDP-MED.
lldpd supports bridge, vlan and bonding. bonding need to be done on
real physical devices, not on bridges, vlans, etc. However, vlans can
be mapped on the bonding device. You can bridge vlan but not add vlans
on bridges. More complex setups may give false results.
the "Video Output" preferences they should be passed along on the
mplayer command line (upstream svn revision r222)
Minor string cleanups (upstream svn revision r223)
