Comment 11 for bug 728426

Yes and no. LGPL license permits linking (calling library) from the main program code, but it does not permit to merge the code into one code that is no way to know which code is LGPLed and which is MIT. If you can't separate the code into library (external file) and you would still like to have one merged version of program, then LGPL requires relicensing all of the product to LGPL license. So the main question is: can you separate the LGPL code into library. If yes then printing can be written as main part of the code and just calling library from main program. If this library separation is not possible, then write an extension and put whole extension code under LGPL.

"... users without printers may just want to switch the functionality off." Yes sure, but I don't think this should be the only argument. For example I never use Effects, so it would be nice to exclude this functionality into extension. Don't think this should be done. There are just core functionalities (printing is one of them, and effects is the second in image editing program) that should just be included in main program. I have never seen a printing support in extension, this is core function. So this should not be the only argument of decision.

I suggest to look into the code and find out if LGPL code can be stored into library and if it can, then write printing into main program, if not then write an extension.