a suggestion (or request) to whom it may concern for Wine package

maybe is only a personal point of view.
I dealt a lot to obtain a Wine-devel installation through ports collection, hours of waiting for mountains of make/compile terminal rows and not always successfully at first stage (some dependency packages not at the correct version to be reinstalled and startover again).
All this because the Wine standard pkg does not bring CUPS connection itself, the only possibility for having this "strange" function was selecting such item in the make config step on Wine-devel inside ports and then make install it, with all the timing loss above described.
Ask: is the printing possibility from a Windows app so alien to consider, as a sort of very uncommon need for a user?
Like to ask this to the devs who create/mantain app packages to install, and really wish to know the right way to address this question.
Someone here can tell how?
Thank you
 
Isn't CUPS pulling a mountain of dependencies?

In any case, you can compile wine without compiling the things it depends on. `make install-missing-packages`
 
Ask: is the printing possibility from a Window app so alien to consider, a sort of very uncommon need for a user?
I've only used Wine for games since 2016 and never imagined printing from it :p

But I wonder what might be exotic about it for support to be on a flag? I figured Wine would connect to CUPS via IP/socket without OS-intervention and not really need anything extra (libs/etc should be OS-side?)
 
Hmm, the only pig in CUPS' dependency list I can spot outright is docbook and friends.

But Wine pulls them in anyway. So on first estimation I'd say there isn't too much of a reason to leave cups out of the wine default.
 
Back
Top