On Sat, May 5, 2012 at 2:13 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote:
> Now (again IIUC) the interesting bit is whether it's better for BigTop > to be repackaging and -distributing upstream components by itself, or > if it would in fact be better for BigTop to simply provide something > like "bigtop-x.y.rpm" and "bigtop-x.y.deb" packages that just declare > dependencies to specific, integration-tested versions of upstream > packages. It would be much better for Bigtop to work with the Apache dev communities that already exist for each of the projects rather than releasing incompatible artifacts. It creates a lot of confusion that the Bigtop Hadoop rpms are labelled as "hadoop-*.rpm" and yet are significantly different from the Hadoop rpms that are produced by the Hadoop project. Even more troubling is that the Bigtop distro is starting to change the interaction with the user to the projects. > To do this, BigTop would need to work with the upstream projects to > help them produce the appropriate deployment packages as a part of > their normal release processes. And BigTop could also team up with > Infrastructure to maintain the kind of repository structure and > download service expected by deployment tools like yum and apt, a bit > like what Maven projects have in https://repository.apache.org/. I asked Roman to do this and he decided not to. Certainly Hadoop is interested in having the improvements made in their rpms and debs. -- Owen --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
