Well, our last snapshot was last summer, and I've spent, like, at
LEAST 20 minutes of dev time messing with stuff since then, so we're
obviously due for another.

https://www.ctwm.org/tmp/ctwm-3.8.2-post.20160418.tar.xz

SHA256 (ctwm-3.8.2-post.20160418.tar.xz) =
  d042072b89b8795d60f6bd31e0810b95e5905bd804eb4018a68cb4a9b42ef5c1

(see below for extra packaging info)


Why a snapshot?

  See mail about last summer's snap for details.  The short version is
  that, while it's easy to build the current VCS head any time, a
  gen'd tarball is sometimes easier, and I like making things easier.

  Any testing is appreciated.  It should be pretty safe; I've been
  running pretty much the VCS head steadily, and it hasn't invoked any
  nasal demons that I've noticed.  It works fine of my FreeBSD system,
  and is build tested on Fedora 23 and CentOS 6.7 VM's.


New since last snapshot

  The last snapshot was at r415, this one is r469, so you can poke at
  bzr or LP (or the github mirror, for that matter, though you'll have
  to go by date and not bzr revno for that) to see the details.
  Mostly there's a lot of continued internal cleanup and rearrangement
  that shouldn't have user visible effects.

  However, there are a few visible bits.  The GNOME bits have been
  removed since the last snap, as has the USE_SIGNALS code (invisible
  unless you were doing heroic contortions to enable it).  The pre-3.8
  title button specification style (without a '=' in it) will give an
  error now.  The RplaySounds{} specification can be done in the
  config file now.  Some improvements in a few places in the manual.
  And a few other sundry bits.


Package Building

  A further recent addition is setting some parameters in the build
  system which allows the `cpack` program (part of the cmake suite) to
  build packages of the types it knows about, which for our purposes
  mostly means RPM and DEB.  So it's presumably straightforward now to
  build packages of it.

  There's an example in the README of how to go about it; the cpack
  docs can show more detail and possibilities.  For an example, I've
  also put up the RPM I built from it (using just the command
  invocation in the README) on my Fedora 23 VM.

  https://www.ctwm.org/tmp/ctwm-3.8.2-post.20160418.f23.rpm

  SHA256 (ctwm-3.8.2-post.20160418.f23.rpm) =
    90da7c0295d6b78f44a0f081c451d83cbcbb0fcf0a9c7a92583d8c10e204e450


Wait, it's autumn, not spring

  's not my fault you're living upside-down...


What's next?

  (in next mail)


-- 
Matthew Fuller     (MF4839)   |  [email protected]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.

Reply via email to