From Fedora Project Wiki
Denisarnaud (talk | contribs) mNo edit summary |
Denisarnaud (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
[[Features]] > [[Features/F14Boost144]] > | [[Features]] > [[Features/F14Boost144]] > | ||
== FESCo Submission/Process == | |||
Following is the discussion extracted from the [https://fedorahosted.org/fesco/ticket/406 FedoraHosted's ticket following up the FESCo submission and process] | |||
# Changed by [[User:Kevin|kevin]] 20:58, 28 June 2010 (UTC) | |||
#* Keywords set to meeting. | |||
# Changed by [[User:Mclasen|mclasen]] 16:35, 29 June 2010 (UTC) | |||
#* Leaving my comments here, since I am likely going to miss FESCo today: | |||
#* Shipping upstream boost instead of a forked build system seems to be the right thing to do. Working with upstream on moving to more standard build tools is also a good idea, but shipping a fork is probably not the best way to do that... | |||
#* I'm not that familiar with boost. Will this update require a rebuild of all dependencies? If so, can we plan to do this in a separate tag ? | |||
#* +1 | |||
# Changed by [[User:Kevin|kevin]] 22:24, 29 June 2010 (UTC) | |||
#* Status changed from new to closed. | |||
#* Resolution set to fixed. | |||
#* This feature was approved at the 2010-06-29 meeting. | |||
== Reference == | |||
See also [[Talk:Features/F13Boost141 |Talk:Features for Fedora 13 Boost 1.41]] | See also [[Talk:Features/F13Boost141 |Talk:Features for Fedora 13 Boost 1.41]] | ||
Revision as of 06:22, 30 June 2010
Features > Features/F14Boost144 >
FESCo Submission/Process
Following is the discussion extracted from the FedoraHosted's ticket following up the FESCo submission and process
- Changed by kevin 20:58, 28 June 2010 (UTC)
- Keywords set to meeting.
- Changed by mclasen 16:35, 29 June 2010 (UTC)
- Leaving my comments here, since I am likely going to miss FESCo today:
- Shipping upstream boost instead of a forked build system seems to be the right thing to do. Working with upstream on moving to more standard build tools is also a good idea, but shipping a fork is probably not the best way to do that...
- I'm not that familiar with boost. Will this update require a rebuild of all dependencies? If so, can we plan to do this in a separate tag ?
- +1
- Changed by kevin 22:24, 29 June 2010 (UTC)
- Status changed from new to closed.
- Resolution set to fixed.
- This feature was approved at the 2010-06-29 meeting.