Re: libcupsfilters: mupdf not "Required"

On 12/6/25 10:31 AM, Rainer Fiebig ([email protected] via blfs-dev Mailing List) wrote:
> Am 06.12.25 um 17:09 schrieb Rainer Fiebig ([email protected] via blfs-dev
> Mailing List):
>> Mupdf is labeled as "Required" for libcupsfilters.  However,
>> libcupsfilters-2.1.1 can be built without mupdf, using the config-option
>>
>> 	--disable-mutool
>>
>> I just did so and the build was fine, including the tests.
>>
>> So I suggest do downgrade mupdf to "Recommended" or perhaps even
>> "Optional" for libcupsfilters.
> 
> This seems to go even further as there is also
> 
> 	--disable-ghostscript
> 
> as a config-option.  So it seems to me that ghostscript can/should also
> be downgraded, like mupdf.
> 
> Here's part of the build-log, building without both, ghostscript and mupdf:
> [...]
> Build configuration:
>          libcups:         2.4.15
>          cups-config:     system
>          poppler:         yes
>          ghostscript:     no
>          gs-path:
>          mutool:          no
>          mutool-path:
>          ippfind-path:    system
>          imagefilters:    yes
>          jpeg:            yes
>          exif:            yes
>          png:             yes
>          tiff:            yes
>          dbus:            yes
>          werror:          no
>          test-font:       /usr/share/fonts/dejavu/DejaVuSans.ttf

I like that, but to decide whether to make them recommended or optional, I'm 
wondering what they do for libcupsfilters.

We do say ghostscript OR mupdf.  I'm guessing they convert to a pdf instead of the 
default ps format.

Perhaps one of them is needed to just output to a pdf file.

Thoughts?

   -- Bruce

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page