summaryrefslogtreecommitdiff
path: root/help
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2020-03-09 03:01:39 +0000
committerNorbert Preining <norbert@preining.info>2020-03-09 03:01:39 +0000
commit0561778af6f8fde0a3a1c334e2aab9a4f1142d6e (patch)
treec19fe45e4101aed56e7fb3602174c6a5e335d7d1 /help
parenta8880a5ee484845d9a526c5ca8d21d31214af22b (diff)
CTAN sync 202003090301
Diffstat (limited to 'help')
-rw-r--r--help/ctan/CTAN-upload-addendum.html63
1 files changed, 34 insertions, 29 deletions
diff --git a/help/ctan/CTAN-upload-addendum.html b/help/ctan/CTAN-upload-addendum.html
index 8a00079d27..7c9f240172 100644
--- a/help/ctan/CTAN-upload-addendum.html
+++ b/help/ctan/CTAN-upload-addendum.html
@@ -10,7 +10,7 @@
-->
<link rel="stylesheet" type="text/css" href="https://www.tug.org/tugstyle.css" />
<meta name="author" content="Petra R&uuml;be-Pugliese" />
- <meta name="date" content="2020-03-07" />
+ <meta name="date" content="2020-03-08" />
<meta http-equiv="content-type" content="text/html; charset=us-ascii" />
<style type="text/css">
.highlight { color:navy;}
@@ -729,33 +729,38 @@
example: <tt>jsclasses</tt>,
which needs a specially customized TeX system.
-->
- <br />
- <a id="keeppdffiles"></a>
- The <em>exception</em> to this rule are
- the <tt>.pdf</tt> files of the documentation:
- We do indeed wish to keep these,
- ready for immediate access by visitors,
- alongside with their sources.
- <br />
- <a id="readmeunpacked"></a>
- The same holds for
- <a href="#readme">README files</a>
- in cases where these, too,
- can be generated from other sources:
- We always want the
- <span class="highlight">README unpacked</span>,
- as a convenient starting point
- for inspecting the package.
- <br />
- <a id="generatedinsfiles"></a>
- A recent development are
- <span class="highlight">generated <tt>.ins</tt>
- files</span>.
- Having immediate acces to them may be helpful to users.
- We therefore agree that they may be kept unpacked, too.
- Indeed, one may be of the opinion that
- keeping them unpacked
- should be <em>recommended</em>.
+ There are however some <i>exceptions</i> to this rule:
+ <ul>
+ <li>
+ <a id="keeppdffiles"></a>
+ The
+ <span class="highlight">
+ PDF files of the documentation</span>:
+ We do indeed wish to keep these,
+ ready for immediate access by visitors,
+ alongside with their sources.
+ </li>
+ <li>
+ <a id="readmeunpacked"></a>
+ <a href="#readme">README files</a>:
+ Even in cases where they
+ can be generated from other sources,
+ we want to keep them unpacked,
+ as a convenient starting point
+ for inspecting the package.
+ </li>
+ <li>
+ <a id="generatedinsfiles"></a>
+ Generated <span class="highlight"><tt>.ins</tt>
+ files</span>:
+ These are a recent development.
+ Having immediate access to them may be helpful to some users.
+ We therefore agree that they may be kept unpacked, too.
+ Indeed, one may be of the opinion that
+ keeping <tt>.ins</tt> files unpacked
+ should be generally <em>recommended</em>.
+ </li>
+ </ul>
</li>
</ol>
</li>
@@ -1522,6 +1527,6 @@
$LastChangedDate$
</p>
Until then: -->
- Last updated: 2020-03-07
+ Last updated: 2020-03-08
</body>
</html>