[275] in athena10
Re: New OpenAFS build script
daemon@ATHENA.MIT.EDU (Evan Broder)
Wed Jun 25 21:35:53 2008
Message-ID: <4862F249.5050503@mit.edu>
Date: Wed, 25 Jun 2008 18:35:05 -0700
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: ghudson@mit.edu
CC: athena10@mit.edu
In-Reply-To: <200806251945.m5PJjEYS009359@outgoing.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
For the sake of the other Debathena developers (because I didn't notice
the first 2 or 3 times I ran this), you want to set the DEBATHENA_APT
environment variable before running the script. :)
- Evan
ghudson@MIT.EDU wrote:
> I've committed debathenify-openafs. I'm reasonably confident of its
> correctness at this time, and am using it to maintain the Athena 10
> apt repository.
>
> If SIPB Debathena maintainers would like to use it, instead of running
> the usual find-openafs-kernels/build-openafs/upload-openafs sequence,
> just run:
>
> da ./debathenify-openafs binary upload
>
> or for a single dist:
>
> ./debathenify-openafs hardy-amd64 binary upload
> ./debathenify-openafs hardy-i386 binary upload
>
> It won't repeat unnecessary work, and it should coexist happily with
> the directories created by build-openafs. In addition to modules
> packages, it will create and upload metapackages like
> "openafs-modules-generic" to keep linux-image metapackages in sync
> with OpenAFS modules. I have one of these metapackages installed on
> my work machine and it appears to do the right thing. I am currently
> puzzling out how the install script can decide which metapackage to
> install.
>
