veyepar: Multiarch/Crossbuild/Bootstrap/Toolchain minisprint

Author(s):	Wookey
Location	Stockholm
Date	aug Tue 18	Days Raw Files
Start	11:00	First Raw Start	error-in-template
Duration	05:00:00	Offset	None
End	16:00	Last Raw End
Chapters
Total cuts_time	None min.

https://summit.debconf.org/debconf15/meeting/239/multiarch-bootstrap-crossbuilding/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

assets release.pdf MultiarchBootstrap.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Discussion of the state of Multiarch, Crossbuilding, Bootstrapping, and Cross-toolchains in Debian. There has been good progress in these areas recently, but numerous issues remain, such as Multiarch dpkg/apt/aptitude inconsistencies, cross-dependencies, and how Cross-toolchains in the archive should look.

Not everyone is interested in all of this so the session will be spit into chunks:
11:00 Multiarch
13:00 Crossbuilding and bootstraping
15:00 Cross-toolchain packaging

Agenda:
 
Multiarch things:

* Multiarch (not!) in Policy
 * dpkg/apt/aptitude inconsistencies
 * cross-dependencies
 * bootstrapping-related issues
 * embedded interpreter problem

Agreement on the correct interpretations of some things is needed:

1) if a package foo with arch:A depends on bar:any where bar is m-a:no and arch:A, is that dependency satisfied?

2) Do we accept https://wiki.debian.org/Multiarch/InterpreterProposal? If not what should we do instead?

3) Should we declare 666772 (apt cross-build-dep handling should be liberal with Arch: all packages) wontfix officially (and document corollary) ?

Crossbuilding:

General roadmap - what still needs doing?

Feedback from users on what we have so far is very welcome.

* Cross-dependencies
 * Multiarching more packages
 * toolchain support packages
 * Cmake crossing - state?
 * Using build profiles
 * sbuild issues
 * Documentation

Bootstrapping

Followup from Helmut's talk on Monday.

Cross-Toolchains

gcc-5 uses -cross standalone packages
gcc-4.9 uses wdotap multiarch packages

* Everyone happy with standalone packages?

* Should cross-toolchains be multibbed?

* What set of toolchains should be pre-built in the archive?

* What about toolchains not provided as binaries? Cross-gcc source-generator OK?

* What ancilliary packages are needed?

Full details in gobby document on gobby.debian.org in the path                          
debconf15/bof/Multiarch-Crossbuilding-Bootstrap-Toolchains

Comment:

production notes