[
https://issues.apache.org/jira/browse/BIGTOP-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138994#comment-14138994
]
Konstantin Boudnik commented on BIGTOP-1373:
--------------------------------------------
I think the argument is about a non-issue. There's no limitations on how many
stacks one can produce using some variance of the definition files (aka
bigtop.mk). All one needs to do to produce a stack then is to create a tailored
definitions and run build with that particular file, instead of the standard
bigtop.mk. Will the custom file override bits and pieces of the base one, or
will be a separate full stack definition - is up to the particular
implementation. It doesn't matter for this discussion IMO. The only
functionality we need to support, as [~rvs] pointed out, is to be able to
download bits from more protocol URLs than just http and ftp, supported right
now.
Are we all talking about the same thing, btw? ;)
> Add a mechanism of obtaining source for components from SCM
> -----------------------------------------------------------
>
> Key: BIGTOP-1373
> URL: https://issues.apache.org/jira/browse/BIGTOP-1373
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.8.0
> Reporter: Julien Eid
> Attachments: BIGTOP-1373-extrafile.patch,
> BIGTOP-1373-noextrafile.patch, BIGTOP-1373.patch
>
>
> This was brought up here (https://issues.apache.org/jira/browse/BIGTOP-1363)
> as a much wanted feature for our build system so we can build against
> branches. I have two approaches to doing this that I'll be posting up Patch
> files for and seeing which approach everyone likes better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
