- 22 Nov, 2018 4 commits
-
-
intrigeri authored
The developer may need to pass environment variables such as @$ARTIFACTS@, @http_proxy@, and @TAILS_BUILD_OPTIONS@. If they faced the issue this workaround is about, they know how to start a build already, so we don't need to tell them again and risk them copy'n'pasting a command that may lead to undesirable behavior.
-
intrigeri authored
-
- 16 Jan, 2018 1 commit
-
-
Loic Dachary authored
-
- 22 Dec, 2017 1 commit
-
-
intrigeri authored
-
- 12 Dec, 2017 1 commit
-
-
anonym authored
This has caused several issues throughout the years, the lastest instance being the reopening of #14933, so let's just remove this feature. The optimization this allows for when rebuilding the same branch frequently (together with the keeprunning option) was probably only used by me, and rarely at that, so I'd argue it is not worth the maintenance cost. Will-fix: #14933
-
- 08 Dec, 2017 1 commit
-
-
Fix veing/being, and fix extraneous newline inside a `code` fragment.
-
- 13 Sep, 2017 30 commits
-
-
intrigeri authored
This way, we can make it clear that there are two methods to verify an ISO, while previously we had three methods (2 for ISO images and 1 for IUKs) following each other ⇒ better semantics. While I'm at it, point to the doc for building IUKs as one can't verify something they have not built in the first place.
-
intrigeri authored
The user's goal is to get an ISO in the end, not to "start the build".
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
We did that move 15 months ago, by now everyone should have followed.
-
intrigeri authored
-
intrigeri authored
First, this problem has been fixed in 0.3, not 0.0.3. Second, Stretch has 0.3 and we don't support building on older Debian anymore.
-
intrigeri authored
I've just learned about this command while working on this doc. If *I* have never needed it, presumably we should not expose this information to everyone who tries to build Tails for the first time.
-
intrigeri authored
Use structure and phrasing closer to what we do everywhere else in our doc.
-
intrigeri authored
This has not been the case since ~5 months.
-
intrigeri authored
-
intrigeri authored
Most users should just try the simplest thing that can possibly work, and troubleshoot _if needed_ afterwards.
-
intrigeri authored
At dev time, one generally wants to save time and build the ISO faster more than anything else.
-
intrigeri authored
Guess what? These figures have been outdated for years.
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
I think the use case for changing these settings for other reasons is basically non-existent in the real world.
-
intrigeri authored
Make the extproxy option less prominent: since we switched to our own APT snapshots, using an extproxy does not save any download bandwidth unless configured in a very special and undocumented way. Give an example early, so that one has an idea of how to set a build option without reading the entire section. Merge all the previous three (!) build settings sections into a single one.
-
intrigeri authored
-
intrigeri authored
I.e. apply a structure and style closer to what we do everywhere else in our doc, be less verbose, avoid leaving the choice when not needed (e.g. those who know how to apply new group membership don't need to be told about this option, and those who don't know how to do it must not be given information they cannot act upon).
-
intrigeri authored
Pretty self-explaining, uh? :)
-
intrigeri authored
The text was hard to notice, stuck between a somewhat impressive TOC div and a level 1 heading.
-
intrigeri authored
… and don't start pointing to the Wikipedia rabbit hole on the second line of the doc.
-
intrigeri authored
Let's not make the reader think they need to read the design doc in order to follow these instructions. And it felt like we had two "misc." buckets; one is enough :)
-
intrigeri authored
Now that the manual build instructions are out of the way, let's make the TOC less scary.
-
intrigeri authored
Rationale: make the doc about the currently maintained and supported build method less daunting by removing one choice and making the page shorter. It'll still be listed in "Related pages" at the bottom of contribute/build.
-
intrigeri authored
Telling people that something is easy has two major problems: it makes them feel bad/inadequate if they fail or find it hard, which is not nice; it tells them what their feelings should be, which generally works poorly with humans except in strongly imbalanced power relationships where all kinds of creepy psychology can happen.
-
intrigeri authored
Since #14459 is solved, mistakenly building from the master branch is less of a problem: at least the ISO should build successfully. So let's stick to the basics, document how to build the devel branch, and point to the detailed doc only in passing rather than as a compulsory stopover.
-
intrigeri authored
-
- 11 Sep, 2017 1 commit
-
-
intrigeri authored
-
- 28 Jul, 2017 1 commit
-