Commit a732fc05 authored by Christoph Biedl's avatar Christoph Biedl Committed by Bernhard Link

Improve readability of FakeComponentPrefix documentation

while looking for something completely differen (is there a way to copy
packages between components?), I noticed the documentation for
FakeComponentPrefix is quite hard to read. Might a a result of how man
renders *roff, however I consider the presentation after applying the
attached patch an improvement.
parent 0874314a
......@@ -1241,24 +1241,32 @@ Also if a component starts with it, its directory in the dists dir
is shortened by this.
.br
So \fB
Codename: bla/updates
Suite: foo/updates
FakeComponentPrefix: updates
Components: main bad
\fP will create a Release file with \fB
Components: main bad\fP
will create a Release file with \fB
Codename: bla
Suite: foo
Components: updates/main updates/bad
\fP in it, but otherwise nothing is changed, while\fB
Components: updates/main updates/bad\fP
in it, but otherwise nothing is changed, while\fB
Codename: bla/updates
Suite: foo/updates
FakeComponentPrefix: updates
Components: updates/main updates/bad
\fP will also create a Release file with \fB
Components: updates/main updates/bad\fP
will also create a Release file with \fB
Codename: bla
Suite: foo
Components: updates/main updates/bad
\fP but the packages will actually be in the components
Components: updates/main updates/bad\fP
but the packages will actually be in the components
\fBupdates/main\fP and \fBupdates/bad\fP,
most likely causing the same file using duplicate storage space.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment