[OpenAFS-devel] 1.6 and post-1.6 OpenAFS branch management and schedule

[Russ Allbery]

Jason Edgecombe <jason@rampaginggeek.com> writes:

> Impressive and ambitious. I like it. I also like the time-based releases.

> Is there a plan to keep the OS packaging up-to-date? Possibly have weekly
> or daily rpm, deb, and msi files generated?

I can't speak for the RPM and MSI work, but I'll address the Debian
packages.

It's a bit of work to do the builds, and would be a lot more work if we
needed to build for multiple platforms, so I prefer to upload Debian
packages to Debian and let the Debian build network do that work.  I'm
maintaining packages for master in Debian experimental and plan to
continue to do so going forward.  However, given the amount of time that I
have to spend on this, I would prefer to do new packages at the same time
as we do new development releases and not more frequently than that.

> I would be fine with being able to manually building packages from git.

You should already be able to build Debian packages from Git.  I try to
keep the packaging files in the tree up-to-date with the most recent
Debian package.  Run make dpkg from the top level of the tree to get
Debian packages.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>