Bug 1768455 - TeX shouldn't depend on Chromium
Summary: TeX shouldn't depend on Chromium
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-04 13:49 UTC by Augusto Stoffel
Modified: 2019-11-13 11:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-13 09:56:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Augusto Stoffel 2019-11-04 13:49:06 UTC
As of recently, installing texlive-scheme-medium also installs Chromium as a dependency.

When I install the medium texlive scheme, I expect to get a functioning TeX system without too much bloat.  A web browser is certainly not needed to compile a typical (La)TeX document.  (The dependency on Chromium is via Asymptote, which also seems to be quite far from being an essential TeX component.)

On the other hand, let me also point out some packages which are pretty standard and so should probably be part of the medium scheme, but aren't:

 - biber
 - texlive-urlbst
 - 'tex(amsrefs.sty)'
 - 'tex(xy.sty)'

Comment 1 Tom "spot" Callaway 2019-11-04 16:55:36 UTC
Point taken. It grew that dependency when asymptote hardcoded google-chrome as its web browser callout command. I originally switched it to chromium (since google-chrome is not in Fedora), but I will switch it to xdg-open, which should open the default web browser, whatever that is, and have a much smaller dependency footprint.

As far as the packages in texlive-scheme-medium, those are set by texlive, we just reflect those. I would encourage you to reach out to the texlive upstream with your suggested changes.

Comment 2 Fedora Update System 2019-11-04 18:26:24 UTC
FEDORA-2019-dc54a9e6f0 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-dc54a9e6f0

Comment 3 Fedora Update System 2019-11-04 18:26:30 UTC
FEDORA-2019-a63c123818 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a63c123818

Comment 4 Fedora Update System 2019-11-05 00:47:39 UTC
asymptote-2.59-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-22ee82abc4

Comment 5 Fedora Update System 2019-11-05 01:26:10 UTC
asymptote-2.59-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-dc54a9e6f0

Comment 6 Fedora Update System 2019-11-05 01:29:12 UTC
asymptote-2.59-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a63c123818

Comment 7 Fedora Update System 2019-11-13 09:56:51 UTC
asymptote-2.59-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2019-11-13 10:06:31 UTC
asymptote-2.59-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2019-11-13 11:29:39 UTC
asymptote-2.59-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.