|
Bugzilla – Full Text Bug Listing |
| Summary: | latex takes forever to install. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Neil Rickert <nwr10cst-oslnx> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | badshah400, coolo, ma, mls, werner |
| Version: | 13.1 Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Neil Rickert
2013-01-19 21:47:32 UTC
I can confirm that installing the recommended set of latex packages (for example, when installed as dependencies of texmaker or other latex front-ends) takes incredibly long (for me just the installation, not counting the downloading time, itself took a few hours; this used to be at most about half an hour including downloading and installing for texlive in 12.2). CC'ing texlive maintainer. The problem is zypper+rpm. Zypper is not able to perform the posttrans scripts only once as rpm does not provide an --noposttrans option. And zypper does not use the rpm only once for all packages but for every package it executes a single rpm command. The rpm allows to touch tag files in the %post scriptlests which will be used then in the final %posttrans scriptlets. That allows that you cann install e.g. 100 packages each touching the same tag file and then the the posttrans scriptlets will be called after all packages had been installed. With zyppers way this can not work. and upstream of rpm does not allow to skip the %posttrans scriptlets to enable zypper to do this on its own after installing all packages. I've reported this problem long time ago to both maintainers of (lib)zypp(er) and rpm. It looks like upstream rpm is not interested in providing an --noposttrans option. . *** This bug has been marked as a duplicate of bug 773575 *** |