From: Christian Neukirchen <chneuk...@gmail.com>
To: Donald Allen <donald...@gmail.com>
Cc: voidlinux <void...@googlegroups.com>
Subject: Re: xbps-install of texlive very slow
Date: Thu, 01 Oct 2015 16:20:04 +0200 [thread overview]
Message-ID: <87wpv6pt63.fsf@gmail.com> (raw)
In-Reply-To: <6fa0ab6d-60b3-4f03-88aa-2d7f27e1e13c@googlegroups.com> (Donald Allen's message of "Thu, 1 Oct 2015 07:15:01 -0700 (PDT)")
Donald Allen <donald...@gmail.com> writes:
>> Donald Allen <dona...@gmail.com <javascript:>> writes:
>>
>> > Installation (not downloading) of texlive-bin-2015_1 is very, very slow.
>> > It's a big package, but I've done this on this same machine (2.5 Ghz AMD
>> > dual-core processor, 4GB, 7200 rpm disk, / on an ext4 file-system) with
>> > Arch (configured similarly) in far less time.
>>
>> Yes, this is because TeXLive's tlmgr is slow.
>>
>> Arch actually repacked TeXLive, but we chose not to do that due to
>> lack of manpower and immediate outdatedness.
>>
>
> Thank you for the explanation. It's good to know that this is not something
> inherent in the package manager, which is what I was concerned about. If
> it's specific to texlive, then that's not a problem for me.
Yes, the package only contains the real TeXLive installer, which is slow.
However since you only update it once a year, this was not a reason to
spend much time speeding it up.
XBPS itself is amongst the fastest package managers I've used.
--
Christian Neukirchen <chneuk...@gmail.com> http://chneukirchen.org
prev parent reply other threads:[~2015-10-01 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:22 Donald Allen
2015-10-01 12:28 ` Christian Neukirchen
2015-10-01 14:15 ` Donald Allen
2015-10-01 14:20 ` Christian Neukirchen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpv6pt63.fsf@gmail.com \
--to="chneuk..."@gmail.com \
--cc="donald..."@gmail.com \
--cc="void..."@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).