id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
22611	Move muparser to General Libraries	zeckma	blfs-book	"When updating a package in SLFS, I noticed it now required muparser. I didn't notice muparser was in BLFS since I would have expected it to be in genlib. Instead, it's in the LXQt section.

It was originally put in LXQt since no other packages need muparser in BLFS. But this sorta thing isn't treated the same way consistently. A lot of the time, packages are put in their proper category that they best belong to regardless what they are used by. For instance, let's say AppStream had its own chapter, and an update needed libfyaml but libfyaml is only used by AppStream, it shouldn't matter. libfyaml is still a general library and should be put in genlib. muparser falls in the same case, especially so since other packages outside of BLFS use it.

It's misleading to call muparser a LXQt component, it's a completely unrelated library. That's why I believe moving muparser to genlib is for the best. I was told that when muparser got added, there was an effort to put it in genlib but got denied because of the LXQt thing. We should do some future-proofing and move it to genlib, to be less misleading and more clear.

I can do this if approved."	enhancement	closed	normal	13.0	BOOK	git	medium	wontfix