we need to be careful here, some components have build dependencies to other native components. Casing point, Zeppelin, Tez, and Amabri have dependencies to frontend-maven-plugin that pulls in native NodeJS binary based on the build system.
On Sat, Mar 25, 2017 at 2:04 PM, Roman Shaposhnik <[email protected]> wrote: > Those workaround only matter during build time. Once the package is > built it is truly > arch independent. IOW, we can build on x86 and use it anywhere. > > This is a bit confusing since node itself is NOT arch independent. > However, none of > these packages actually need node -- they all use it to > preprocess/bundle JS during > compile time. > > Makes sense? > > Thanks, > Roman. > > On Sat, Mar 25, 2017 at 6:26 AM, Olaf Flebbe <[email protected]> wrote: > > Hi Roman, > > > > BTW: There are _arch dependent_ package workarounds in _arch independent_ > > packages ! I think we should mark the package as arch dependent in order > to > > make sure. > > > > The one which comes to mind is tez: > > > > See src/common/tez/do-component-build ;-( > > > > Will file a JIRA. > > > > Olaf > > > > > > Am 25.03.2017 um 13:57 schrieb Olaf Flebbe <[email protected]>: > > > > Hi, > > > > On the debian side I was assuming that reprepro will handle this for you. > > Simply add different arch specific packages (which can be found by name). > > > > I am not sure about the yum side of things. > > > > > > Olaf > > > > > > Am 24.03.2017 um 01:42 schrieb Roman Shaposhnik <[email protected]>: > > > > Hi! > > > > recent issues surrounding builds on two of > > our two non-x86 platforms got me thinking > > that while it is fun to build on them (to iron out > > kinds in JDK and what not) we don't actually > > have to release the packages for most of the > > projects since all those are arch independent. > > The only ones that ARE arch dependent would be: > > bigtop-jsvc > > gpdb > > hadoop > > hue > > qfs > > tajo > > zookeeper > > > > The question then becomes how do you structure > > the repos. Do you have on repo for arch independent > > stuff and one for each arch? Can you have all the > > packages in a single repo? > > > > What are the good practices around this? > > > > I'm especially looking for advice from Canonical guys > > and Linaro folks. > > > > Thanks, > > Roman. > > > > > > >
