Hello, On Nov 28 22:54 Simon Lees wrote (excerpt):
Yes that is one of the main goals to start SLE 13 and openSUSE Leap 43.0 development with as close to a unified set of patterns as possible as this will make everyone's life easier. I guess given the feedback we have had about the printing pattern in openSUSE, if it is currently servicing multiple roles maybe we should consider taking this feedback in when creating the printing patterns for SLE 13, this is certainly the best time we will have to do so. It is my intention at this stage to make the openSUSE patterns match what the SLE patterns are doing but really for almost all cases I will be guided by the maintainers of the respective subsystems as they know there packages and hopefully there users better then I do. The main thing splitting some of the patterns out into separate packages and devel repositories should do is make it easier for the maintainers in those areas to update the patterns.
I think we (at least I) need a common understanding what it should actually mean in parctice when a user installs a pattern. I think different maintainers of different subsystems have different assumptions what users expect when installing a pattern. For example my personal assumption when installing a pattern that is broadly just called "Printing" would be that I get basically "all and everything that is needed for normal printing" installed. Or in other words: When I have a "Printing" pattern installed, I would not expect to get ever bothered again with installing "Printing" related software (except for very exotic use-cases). In contrast when there are specifically named patterns like "Printing:HP", "Printing:Epson",... and "Printing:Bluetooth", "Printing:AirPrint",... I would expect to get only installed what is specific for each one. But now things get complicated because e.g. "Printing:Epson" woud require to split each printer driver package that supports at least one 'Epson' printer model into sub-packages so that only the 'Epson' stuff could be installed. E.g. have fun with splitting the PPD files in /usr/share/cups/model/gutenprint/5.2/C/ Current 'gutenprint' supports 44 real printer manufacturers plus "Generic" - what the heck to do with the latter? And technically it does not make much sense for usual printer driver packages because usually a printer driver package provides one big driver binary (plus perhaps a library) for all its supported models so that sub-packages would only artificially cut away PPD files for other manufactures from one particular driver which would make basically only those users happy who count PPD files ;-)
Sorry if any of that doesn't make sense I probably should be sleeping.
At least for me everything you wrote makes perfect sense so you can relax and sleep well ;-) Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org