[
https://issues.apache.org/jira/browse/BIGTOP-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051698#comment-14051698
]
Sean Mackrory commented on BIGTOP-1363:
---------------------------------------
We've very occasionally bundled patches that fix build-related stuff, but yes
to support this generally would very much, IMO, be a departure from existing
policy.
I'd like to suggest an alternate solution to the problem that we've wanted to
do for a long time anyway - make it easy to build from a branch of a source
repository, rather than just published tarballs. Bigtop releases would still be
entirely Apache releases, but developers could routinely build from trunk or
curate their own branches.
> (Discussion) Bigtop may manage apache patches
> ---------------------------------------------
>
> Key: BIGTOP-1363
> URL: https://issues.apache.org/jira/browse/BIGTOP-1363
> Project: Bigtop
> Issue Type: Improvement
> Components: Build
> Reporter: Guo Ruijing
>
> Bigtop may manage apache patches.
> Motivation 1: component build fails due to some apache patches. bigtop don't
> need to wait for component rebase to workaround component build failure.
> Example 1) Hadoop build fails in bigtop-0.6.0/bigtop-0.7.0 build fails due to
> HADOOP-10110.patch missing.
> Example 2) flume 1.4.0 build fails due to Flume-2172
> Motivation 2: third party can use bigtop to manage apache or vendor patches
> (Not bigtop goal, but if more people use bigtop to do distribution, bigtop is
> more stable)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
