Buildroot:PatchworkSessions

From eLinux.org
Revision as of 13:18, 8 March 2016 by Ymorin (talk | contribs) (taskd reviewd)
Jump to: navigation, search

Upcoming patchwork sessions: https://framadate.org/WEmxCql13oXFhbMs

March 8th: list of topics to discuss

  • [1/1] taskd: new package
    • Thomas: do we want such a package in Buildroot? A command line TODO-list application in an embedded system?
    • Yann: taskd is just the server part, so I'd say 'yes'. Review sent to ask for some changes; marked as changes-requested.
  • [RFC] DO NOT APPLY Remove usr/ component from HOST_DIR
    • Thomas: Do we want to go this way? Personally I'd say yes.
  • [1/2] toolchain: add support for the newlib library
    • Thomas: Final decision on this?
  • [1/1] toolchain-wrapper: prevent use of unsupported -fstack-protector*
    • Thomas: do we want this? I personally don't really like adding more and more crap to the wrapper. But others might disagreed.
  • "[1/2] help: add a way to document targets declared in local.mk/external.mk" and "[2/2] help: relocate help messages specific to one package"
    • Thomas: I'd say yes to patch 1/2, but no to patch 2/2 (I had already submitted a similar approach, and it was rejected in the past)
  • [v2,1/1] core: add option to force compiling C++ as C++11
    • Thomas: I don't like this.
  • [1/1] package/libgpg-error: bump to version 1.21
    • Thomas: libgpg-error now has some architecture specific bits. Shall we follow upstream? I'd say yes.
  • "package/gdb: avoid build issue with gdb sources from a git repository" or " [RFC] package/gdb: simplify the disable doc hook"
    • Thomas: we need to make a decision about this
  • "[1/1] overlay: Allow overlay to be a tar archive."
    • Thomas: In principle sounds like a good idea to me.