I have seen on the changelog. Ruby was required in the past to build the package.

CC: (none) => benoit.tuduri

dmorgan added the requires to fix this bug: 
https://bugs.mageia.org/show_bug.cgi?id=3827

CC: (none) => pierre-malo.denielou

Then maybe texexec should be in a subpackage, which can then require ruby.  We did something similar in another package for things that require perl, maybe groff?  Also texlive should not require that monster of a package texlive-texmf, especially now that texlive is a suggests of kdegraphics-thumbnailer (as of the KDE update for Mageia 3 Bug 10600 Bug 10388 and in Cauldron too I imagine).

Whiteboard: (none) => MGA3TOO

I agree with David: texlive-texmf is a monster, and KDE should not be made to depend on it if it isn't really needed.

CC: (none) => johnltw

Hi all,
Just to add my observations about this:
I had texlive and texlive-texmf installed with the last mageia 3 update (I had not texlive nor texlive-texmf before the update). 
The thing is, after the update finished, I was able to uninstall texlive and texlive-texmf with the software installer, I had no warning that some dependency would be broken, first that's sound strange to me because I thought this package was required since it was in the update, why was it in the update if it can it be deleted afterwards ?
second there was no orphans after texlive and texlive-texmf deletion.
That make me suggest that maybe there are several packages into the last kde update that have also texlive-texmf dependencies.

CC: (none) => apessoa

Coming back to the original bug report, I can create a subpackage with the ruby dependency.
For the texlive requires on texlive-texmf, it's a bit harder, but I will have a look ...

I think the suggests in kdegraphics-thumbnailer should not have been pushed (especially not as an update) as it creates more problems than it solves ...

Antonio, you can uninstall texlive and texlive-texmf because texinfo was only a suggests, not a requires.  That means it enables optional functionality, but you can uninstall it if you want.  The suggests was only added to the kdegraphics-thumbnailers package, due to the request in Bug 10388.  If there were no orphans after uninstalling the texlive packages, that would be because they didn't bring in any additional depedencies with them.

Ok, thanks David for the explanation. It's a bit weird to have optional packages installed during an update. I think it's the first time I see this.
Anyway, you were right about the dependencies: on another mageia installation I have, I removed texlive-texmf after the update and I had orphans that could also remove.

@Antonio

If you have more machines to update you can save yourself some time and bandwidth by running this command provided by doktor5000 on the forums:

urpmi --auto-update --no-suggests

This will exclude texlive and its friends from inclusion.

Original forum post at https://forums.mageia.org/en/viewtopic.php?f=7&t=5944&p=39515#p39506

Alright, thanks, that's a good tip. That's true I've another laptop to update as well (and it'll be finished).
I would say I'd rather not have to think about these kind of details every time I update my distrib and I guess a lot of people would agree with me.
Thanks for your time and let's hope there will be no more tricks like that.

Still valid.

It's not as easy as just splitting, as many texlive executable can end up calling those ruby scripts ...
Maybe for mageia 5 ...

Assignee: bugsquad => pierre-malo.denielou
Status: NEW => ASSIGNED

Why is it an issue in fact ?

For me it's normal that texlive requires ruby as some scripts in the package nrequire that language:
texlive-20160523-source/texk/texlive/linked_scripts/match_parens/match_parens
texlive-20160523-source/texk/texlive/linked_scripts/convbkmk/convbkmk.rb

at least directly and maybe some other indirectly. So except by providing an upstream patch to modify that, I'm not sure we should do something on our end.

CC: (none) => bruno

Just because there is some ruby scripts among the gazillion files constituting texlive doesn't make ruby mandatory to run latex AFAIK. I'm unable myself to identify such a script in my own usage.

The multiple automatic dependencies generators are unable to make a difference between something mandatory and something useless, they just find the presence of a script. That's a human job to review those dependencies, and sort out which are actually needed, and those that may be ignored or left to the final user to decide.

Report from fresh install yesterday: 

I installed mga6 freshly, network install (via urpmi-proxy), 64 bit, all default (plasma), and for some reason the texlive packages got installed, total install size 4 GB extra!!

(also reported on [dev] mailing list yesterday and today)

I guess texlive can not be blamed for getting installed (but maybe the lots of extra perl and rubu packages could be avoided)

-but:

* maybe someone here know what requires latex or wv when installing plasma *


It seems wv (MS Word to HTML and Latex) requires texlive. 

But why did it the installer install wv ?

I simply urpme texlive and it removed the other texlive packages, wv, jadetex, perl-LaTeX-Driver, and latex2html with it, and left me with lots of orphans of perl, ruby and some lib

CC: (none) => fri
Hardware: i586 => All

@all: if we include ruby since some scripts may need ruby, we also have to add python and perl as dependency.

Can't we just spilt up the scripts package into 4 packages:
- base
- perl
- python
- ruby

Not looking into detail, e.g. debian put these scripts into an extra package:
https://packages.debian.org/sid/tex/texlive-extra-utils

If I'm not wrong most of the scripts here are optional, so most of the users that install e.g. KDE will never need these scripts.

CC: (none) => mageia

I've looked into this issue:
ruby is only used for the context package. Since most users will never need context, I suggest to split this up into a new package, which can be installed, if needed.

Currently we install windows binaries. I patched the spec, but currently my vm has not enough disk space for download, build and package of this monster to test.

The most space for tex is used for fonts, especially type1 fonts. The original installer states collections for different languages (Korean, japanese,..). Maybe we can split the fonts based on these criterias into optional packages.

fixed in mga7

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED