[
https://issues.apache.org/jira/browse/BIGTOP-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163005#comment-13163005
]
Bruno Mahé commented on BIGTOP-292:
-----------------------------------
I would rather avoid a separate tarball with extra files. It would make
rebuilding packages harder and error prone.
For instance, if I want to modify some of the init scripts, I would have to
expand that tarball, edit it, and rebuild that tarball every time.
Listing all the files maybe tedious initially, but that list will not change
that often, and it will enable us to take advantage of rpm/dpkg features, such
as checking all the files needed are there and no extra files will be included.
I can take care of this ticket by the end of this week.
> 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
