[313] in athena10
alpine integration status
daemon@ATHENA.MIT.EDU (ghudson@MIT.EDU)
Fri Jul 11 14:34:43 2008
Date: Fri, 11 Jul 2008 14:33:58 -0400 (EDT)
From: ghudson@MIT.EDU
Message-Id: <200807111833.m6BIXwgd024692@outgoing.mit.edu>
To: athena10@mit.edu
I've committed stuff to integrate alpine for hardy and lenny. For the
remaining dists:
* etch only has an alpine package in backports. It would probably
be easy to integrate if we modify debathenificator to pull stuff
from backports when desired.
* dapper has no alpine package. We'd have to do our own backport
and then modify debathenificator to be able to find it, or
something.
* feisty has an alpine package based on 0.82. It would require
additional build system work to integrate since it has no concept
of alpine_c_client_cflags.
* gutsy has an alpine package based on 0.99, and a package in
backports based on 1.0. The latter would work if we modify
debathenificator to pull stuff from backports when desired; the
former would require additional build system work to integrate
because it has broken processing of multi-word
alpine_c_client_cflags values.
Since my focus is on hardy, I'm going to beg out of the above work.
If someone else wants to do it, I have krb5-configure.patch versions
for 0.82 and 0.99. (They're not hard to make, though.)
Since we do not have alpine integrated on every dist supported by
Debathena, there are two complications:
1. The pine package can't be fully deprecated from SIPB Debathena.
2. The debathena-alpine-config packages should not be built for all
dists. This is the first regular Debian package we have with
that constraint. I am going to make changes to sbuildhack and
daupload-release to support a "nobuild" file which can specify
dists not to build a package for. Then I and Evan can drop a
nobuild file into the package build directory after running
dasource for the first time.
