Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Mon, 5 Dec 2011 19:30:40 +0000 (UTC)
From: "Andrew Bayer (Commented) (JIRA)" <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: 
 <1796150413.42072.1323113440399.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2027010129.42044.1323112961289.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (BIGTOP-292) BIgtop SRPMs can not be rebuilt
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/BIGTOP-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162972#comment-13162972 ] 

Andrew Bayer commented on BIGTOP-292:
-------------------------------------

I'd be fine with a tarball of everything but do-component-build and install_*.sh - those are the only ones that are truly consistent across all components, and are guaranteed to be there across all components (except for bigtop-utils, but that's a special case).
                
> BIgtop SRPMs can not be rebuilt
> -------------------------------
>
>                 Key: BIGTOP-292
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-292
>             Project: Bigtop
>          Issue Type: Bug
>          Components: RPM
>    Affects Versions: 0.2.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>            Priority: Blocker
>             Fix For: 0.3.0
>
>
> Quite a few packages (Hadoop being the most prominent examples) fail to mention all of the files from common they depdend upon during the build/install phase of SPRM -> RPM.
> The dump approach to fixing this is to list *all* of the missing files explicitly. However, perhaps we should really create a tarball with all the source dependencies and have that as a single extra Source1 tag
> Please chime in with your thoughts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira