Consider not shipping the Installation Assistant in the ISO
Tails includes a local copy of the website, which currently includes the IA. From my perspective, it slows down the ISO build, while great parts or all of it are not useful from inside Tails. Also, regarding the development, QA and release process: I’m under the impression that this tool is managed as one we can update whenever we want by pushing to master, rather than as something that will be frozen and used as-is, from inside Tails, for the next 6 weeks.
So perhaps we should add
/install to excludes?
Granted, this also raises the question of building the website locally,
e.g. for doc writers and translators: these people do need to build
/install. I think we need to use different ikiwiki configuration for
these different use cases. One option would be to keep the default
ikiwiki*.setup suitable for doc and translation work, and to override
the settings we want, via command-line options, when building the
website for inclusion into an ISO.
I don’t know how broken internal links should be handled, if we exclude the IA from the ISO build. But IMO a broken link is better than a link to a page that has great chances not to work, so I don’t see it as a regression.
- Related to #6586