[
https://issues.apache.org/jira/browse/BIGTOP-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279281#comment-14279281
]
Olaf Flebbe commented on BIGTOP-1579:
-------------------------------------
The ultimate test case I can think of is to recompile the whole bigtop project.
I did this on debian and Centos. Debian recompiled, but I happen to have an
issue on crunch with RPM builds. Looking at the SPEC file I am wondering how it
ever worked in the past. I may have broken this package. (Issue is filenames
and directories within the SOURCE tar.gz and the directories the SPEC file
%setup is using). Either way: it can be fixed
> Improve Bigtop Toolchain : Create diff files
> --------------------------------------------
>
> Key: BIGTOP-1579
> URL: https://issues.apache.org/jira/browse/BIGTOP-1579
> Project: Bigtop
> Issue Type: Bug
> Components: build
> Reporter: Olaf Flebbe
> Assignee: Olaf Flebbe
> Fix For: 0.9.0
>
> Attachments: 0001-BIGTOP-1579-Implement-patching-for-Bigtop.patch,
> 0001-BIGTOP-1588-BIGTOP-1579-Implement-patching-for-Bigto.patch,
> 0001-BIGTOP-1588-BIGTOP-1579-Implement-patching-for-Bigto.patch,
> 0002-BIGTOP-1588-BIGTOP-1579-Implement-patching-for-Bigto.patch
>
>
> Right now, we apply changes/patches in the do-build-component script in the
> bigtop-packages/common/<package> part of the build process .
> Would be cleaner and easier to use the RPM / Deb functionality of RPMbuild /
> debuild to apply patches. But right now the gradle script is not flexible
> enough. Since make is now obsolete we can improve this situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
