[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1009797: apt: support "nodoc" build profile



Quoting David Kalnischkies (2022-04-18 23:16:40)
> On Sun, Apr 17, 2022 at 06:50:19PM -0700, Vagrant Cascadian wrote:
> > I thought docbook* and xsltproc could also be excluded from the
> > Build-Depends, but that triggered some other build failures.
> 
> They (alongside po4a) are used to build the manpages which we ship in
> our arch:any packages (we could go with apt-common, but while that
> saves mirror space, it could waste system space as you now have manpages
> installed for things you haven't installed… or we go with multiple
> apt-common packages which increases complexity and overhead… so far we
> haven't gone down this road as it seems not very beneficial in the end).
> 
> We certainly could improve support for nodoc (upon your patch) by not
> building the manpages in this profile which could indeed help boot-
> strapping (although they never asked so far, which I am somewhat
> surprised now to be honest)

if apt is a problem for bootstrapping, you'd probably hear from Helmut
immediately. :)

Right now, to rebootstrap a new architecture, apt is cross compiled. This means
that build dependencies like xsltproc, docbook-xml and docbook-xsl can come
from an existing architecture because both packages are Multi-Arch:foreign.
This is why those build dependencies do not present a problem for
bootstrapping. Other big dependencies like doxygen, graphviz and w3m are in
Build-Depends-Indep so they are also not interesting for bootstrapping as they
are only used to create Architecture:all packages.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature


Reply to: