The basic idea is to copy the packages that are build by gitbuilders or by the buildpackage teuthology task in a central place. Because these packages are built, for development versions as well as stable versions[2]. And they are tested via teuthology. The packages that are published on http://ceph.com/ are rebuilt from scratch, using the process that Alfredo described. This is fine for the supported platforms and for the stable releases. But for the development releases and the platforms that are no longer supported but still built by gibuilders, we could just copy the packages over.
Does that sound sensible ?
Hi Loic:
Community packages for "deprecated" platforms ("deprecated" in the sense
that the Ceph developers are no longer testing on them) would be
welcomed by many, I imagine. And the additional workload for the Stable
Releases team is not large. The question is, where will the packages be
copied *to*?
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
