I'm not objecting this, but I'd love to have more discussion to figure out whether this is the right thing to do. What I get from your proposal is users want to do things which RPM/DEB don't do well while tar.gz is good at it. However is it able to do it in another way which is far more beneficial in more scenarios? In general, it's like when users are asking for a faster horses, can we come up with cars?
How about we start with the first step which is to elaborate why users choose to go for tar.gz? Guodong Xu <[email protected]> 於 2019年7月16日 週二 下午12:24寫道: > Hi, all > > This is a request for comments for a potential new feature. Please have a > look and let me know whether this adds value to the community. Appreciate > your opinions on this. > > As most of you know already, so far, Bigtop provides two packaging format: > deb and rpm. Users are recommended to install through apt and yum for their > respective linux distributions. > > Yet, there are still users coming to me and asking for the more traditional > .tar.gz packages. I know that shouldn't be a problem for x86 users, since > they can always download .tar.gz bin releases from each component's > official release website. But for users from other architectures, like > Arm64 and powerpc, story is different. .tar.gz are not readily available to > these architectures. > > In Bigtop, we are doing the job of building/packaging/testing big data > components in one single place. So, it makes sense that we step in, and > during our process of building each component, we keep a binary .tar.gz > copy for each component we supported. > > If you are supportive to the above idea, then next step will be how to > achieve that. I did some research actually. So, my method is to do two > things: > 0. this can be a subsequent task of either $target-deb or $target-rpm. It > depends on one of them two. > 1. add tar and cp into each component's 'do-component-build' file. > 2. add a new set of packaging tasks for each component. This means to add a > new task in genTasks() in packages.gradle. > Something like > Task t = task "${target}-bin-tar" ( > description: "Building .tar.gz binary for $target artifacts", > group: PACKAGES_GROUP) doLast { ... > > > > PS: > An example in 'do-component-build' for hadoop. Other components similar. > > diff --git a/bigtop-packages/src/common/hadoop/do-component-build > b/bigtop-packages/src/common/hadoop/do-component-build > index 2a1a6345..cb8ddd9d 100644 > --- a/bigtop-packages/src/common/hadoop/do-component-build > +++ b/bigtop-packages/src/common/hadoop/do-component-build > @@ -146,3 +146,6 @@ cp -r target/staging/hadoop-project build/share/doc > > # Copy fuse output to the build directory > cp > > hadoop-hdfs-project/hadoop-hdfs-native-client/target/main/native/fuse-dfs/fuse_dfs > build/bin > + > +# Copy binary build result > +cp hadoop-dist/target/hadoop-${HADOOP_VERSION}.tar.gz .. > > > Best regards, > -Guodong >
