Changeset a48a3d2 for pst/typesetting


Ignore:
Timestamp:
03/20/2024 07:12:31 PM (7 months ago)
Author:
Ken Moffat <zarniwhoop@…>
Branches:
12.2, gimp3, lazarus, trunk, xry111/for-12.3, xry111/spidermonkey128
Children:
73089ed3
Parents:
50745626
Message:

biber - clarify net space usage.

The only installed files are perl maodules and their manpages,
it appears those should still be present when updating from the
previous year.

Location:
pst/typesetting
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • pst/typesetting/biber.xml

    r50745626 ra48a3d2  
    1919    minimal. Copy full texmf to somewhere for working, measure with du -shm,
    2020    then install biblatex over the top of it and remeasure.
    21     For 3.16, texmf grows by 3MB -->
    22   <!ENTITY biber-buildsize     "16 MB"> <!-- only include biblatex size if texmf grows -->
     21    For 3.16, texmf grew by 3MB -->
     22  <!ENTITY biber-buildsize     "16 MB (installs 1.6MB of perl modules)"> <!-- only include biblatex size if texmf grows -->
    2323  <!ENTITY biber-time          "0.4 SBU including tests">
    2424
  • pst/typesetting/texlive.xml

    r50745626 ra48a3d2  
    248248        If you wish to upgrade to current <application>texlive</application>
    249249        on an older system where extra packages (<application>asymptote</application>,
    250         <application>biber</application>, <application>dvisvgm</application>, or
     250        <!-- Ken: comment biber - usually a new texyear has brought a new version
     251        but not so far for 2024. Looking at what it installs it is only perl
     252        modules and their man pages so those ought to still exist after the
     253        previous year's texlive has been removed.
     254        <application>biber</application>, -->
     255                                          <application>dvisvgm</application>, or
    251256        <application>xindy</application>) have been installed, you will need to
    252257        reinstall those as well as fixing up your <literal>PATH</literal> for
Note: See TracChangeset for help on using the changeset viewer.