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
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