Bug#810301: merged /usr support for debootstrap

[Ansgar Burchardt <ansgar@debian.org>]

On Thu, 7 Jul 2016 14:46:36 +0200 Marco d'Itri <md@linux.it> wrote:
> On Jul 05, Cyril Brulebois <kibi@debian.org> wrote:
> 
> > For those wondering (and AFAICT) it seems the only issue here is
how to
> > handle multilib, since multiarch is “hidden” below usr/lib (in
> > usr/lib/<triplet> subdirectories).
> Indeed.
> 
> > Actually, this means an architecture which isn't listed doesn't get
> > extra paths, and /lib might be enough for some ports, e.g. arm64.
> I do not expect that we will get any other multilib ports.
> 
> > It would seem a better idea to list all ports explicitly though.
> Why? See above.
> 
> > > >  first_stage_install () {
> > > > +	case $SUITE in
> > > > +		etch|etch-m68k|jessie|lenny|squeeze|wheezy) ;;
> > > > +		oldstable|stable) ;;
> > > > +		*) setup_merged_usr ;;
> > > 
> > > This means “debootstrap stable” on stretch once it's released
is going
> > > to lead to different results compared to “debootstrap
stretch”.
> > That part remains to be fixed.
> Yes, but how? The current stable cannot work with a merged /usr, so 
> I expected that this would be changed just before stretch is
released.

Could you use the "Codename" field from Release to normalize the suite
name?  That should work even when the meaning of "stable" changes.

(Which makes me wonder: does debootstrap check that the suite it is
asked to install is either in the Release file's Suite or Codename
field?)

Ansgar