Bootstrap Sprint

Location, Date

• when: August 16-19. (Sat-Tue)

• where: Irill, Paris

  • Venue info: http://www.irill.org/about/information-for-guests

• The full sprint will run for 4 days from 10am Sat 16th to 6pm Tue 19th. But if you prefer to arrive during Sat or leave Tue afternoon, due tue time or travel constraints, that's fine. Saturday is kind of optional

Participants

• Helmut Grohne (rebootstrap) (Arrive Sat lunchtime, leave Wed morn)
• Wookey (cross toolchains/bootstrapping) (Arrive friday night, leave Tuesday night)
• Adam Conrad (glibc maintainer)
• Johannes Schauer (botch and bootstrap.d.o maintainer)
• Aron Xu (mips64el porter)
• Guillem Jover (dpkg maintainer) (Monday and Tuesday (TBC)
• Mathias Klose (gcc maintainer) (Arrive Sat lunchtimeish, leave Tuesday afternoon)

Agenda

In general work out how bootstraping should operate, particularly in terms of toolchains/cross toolchains

• Make glibc stages work. With multilib
• Decide on how apt-get-able cross toolchains *should* look like:
  • Package naming patterns (there are multiple ones atm)?
  • Interference with native compilers? Co-installable toolchains?
  • One-package-per-arch or combined?
  • Cross-arch dependencies or not?
  • Guillem's 'fake' cross-toolchains idea

• Discuss toolchain dependency translation (e.g. gcc-${host}), see CrossTranslatableBuildDeps

• How to ensure that build profiles work in Jessie? See bug#744246
  • Push into archive? (trying atm)
  • Set up copy of archive for testing? (painful)
• Discuss how we add missing metadata about early bootstrap into package lists. One aspect is dependency translation. Another is that dependencies on build-essential are not spelled out. In bootstrap, We need an order to cross build build-essential though, so we need to know these dependencies.
• Other cross-build pieces
  • What should be in cross-build-essential (or finer-grained mechanism?)
  • autofoo cache data, cmake toolchain files etc. Move out of dpkg-cross?

• discuss need for Cross-Builds: yes/no field (or how to otherwise store that information)

• discuss the extend to which initial bootstraps can be automated (because initially no binary package dependencies are known), also known as chicken and egg problem of automated bootstrapping
• discuss whether arch:all should imply m-a:foreign for build dependencies bug#666772 but vorlon is not present so probably no need to raise this point
• discuss the requirement that binary packages built with a build profile must be equal in functionality to those normally built (or be split or renamed) and how to enforce this (reproducible builds?)

• discuss how intersecting build profiles should be applied. Either doc-generator <!profile.nodoc>, testsuite-runner <!profile.notest> or doc-generator <!profile.nodoc !profile.stage1>, testsuite-runner <!profile.notest !profile.stage1>

• discuss whether more build profiles should be introduced, how about mapping some DEB_BUILD_OPTIONS to build profiles? (nodoc, nocheck, ...)
• Document the outcome of the discussions for future reference!

Useful Links

• Rebootstrap: https://wiki.debian.org/HelmutGrohne/rebootstrap

• Reboostrap Jenkins CI: https://jenkins.debian.net/view/rebootstrap/

• Crosstoolchain alioth project: https://alioth.debian.org/projects/crosstoolchain/

• https://wiki.debian.org/MultiarchCrossToolchainBuild

• Build Profiles Spec and patches: https://wiki.debian.org/BuildProfileSpec

• Bootstrapability analysis: http://bootstrap.debian.net/

• Bootstrap Wiki page: https://wiki.debian.org/DebianBootstrap

Reports

...

Acknowledgements

the sprint has been possible thanks to:

• donations to the Debian project

• Irill, Paris for the Venue, and Roberto Di Cosmo for arranging it.

CategorySprint