Bug 9641 - Need raptor package installed in staging
Summary: Need raptor package installed in staging
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: 2016.11
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-09 14:28 UTC by Erwan
Modified: 2017-02-26 14:16 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
add staging in raptor.mk (572 bytes, patch)
2017-02-10 14:00 UTC, Erwan 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Erwan 2017-02-09 14:28:13 UTC 
Hi
I've some build dependencies on raptor package, so I needed to have it installed on staging.
Is it possible to add RAPTOR_INSTALL_STAGING=YES in raptor.mk in a future release
Thk
Erwan
Comment 1 Yann E. MORIN 2017-02-09 17:13:43 UTC 
Erwan, All,

> Is it possible to add RAPTOR_INSTALL_STAGING=YES in raptor.mk in a future release

Yes, please submit a patch doing so! ;-)

Regards,
Yann E. MORIN.
Comment 2 Erwan 2017-02-10 14:00:58 UTC 
Created attachment 6886 [details]
add staging in raptor.mk

Hi
Here is the patch
BR
Erwan
Comment 3 Yann E. MORIN 2017-02-10 15:56:29 UTC 
Erwan,

Please submit the patch to the mailing list, as instructed in the manual:
    https://buildroot.org/downloads/manual/manual.html#submitting-patches

Regards,
Yann E. MORIN.
Comment 4 Thomas Petazzoni 2017-02-26 14:16:00 UTC 
This has been fixed in the next branch in commit https://git.buildroot.org/buildroot/commit/package/raptor?h=next&id=b4f54a98a38905fb4ca5413e174263913e20c9c3. The next branch will be merged in master right after 2017.02 is released, and therefore this change will be part of the 2017.05 release. Thanks!