xpachanges(7)

xpachanges7

Changes for users from xpa 1.0 and 2.0

Usage

This document describes changes that will affect users who migrate from XPA 1.0 to XPA 2.0.

Overview

There have been a few changes that affect users who upgrade XPA from version 1.0 to version 2.0. These changes are detailed below.

•

XPA commands no longer have a resolver routine (this is open to negotiations, but we decided the idea was dumb). For the SAOtng program, this means that you must explicitly specify the access point, i.e.,:

  cat foo.fits | xpaset SAOtng fits

instead of:

  cat foo.fits | xpaset SAOtng
•

By default, xpaset, xpaget, etc. now wait for the server callback to complete; i.e., the old -W is implied (and the switch is ignored). This allows support for better error handling. If you want xpaset, etc. to return before the callback is complete, use -n switch:

  echo "file foo.fits" | xpaset -n SAOtng
•

The old -w switch in xpaset and xpaget is no longer necessary (and is ignored), since you can have more than one process communicating with an xpa access point at one time.

•

The new -p switch on xpaset means you need not read from stdout:

  xpaset -p SAOtng colormap I8

will send the paramlist to the SAOtng callback without reading from stdin.

Releases

9 releases since Debian 4.0 (Etch); the text changed 4 times.

  1. 4.0–5.0
  2. 7
  3. 8
  4. 9–10
  5. 11–13

From libxpa-dev 2.1.20-3 in Debian 13 (Trixie). Parsed by carta from the page's man source.