On Sat, Jan 19, 2013 at 3:07 PM, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
On Sat, 2013-01-19 at 14:55 +0100, Alex Naumov wrote:
Yes, but it should work exactly like this.
Imagine such situation: you have 100 (or more) machines and they have the same printers. You just install this package and it configure the system (via CUPS) to use these printers. Yes, for "home-desktop-users" it will be redundant (they can configure it manually), but for industrial use that's exactly what we need.
I doubt that what you want in an 'industrial' setup is to have your machines all hang in an rpm task trying to find a printer which vanished...
Printers are there. If printers are not connected that's not a my problem. My task as a packager is just to create a package that will make all stuff (sources+configurations) and put it to the repo.
you want a setup that installs the logic and the executes the logic decoupled from the package installation (maybe a cron job firing up).
Yes, packaging is just a packaging, but what I do is the full automatically printer-system configuration (without some extra setup).
Just imagine you rollout this package to a large park, configuring 'your printer', the cleaning lady passed the printer, pulls the plug: your entire industrial park is in a hanging rpm transaction... surely this is not what you want.
I understand what you mean, but such situations will never happen :) And again: I'm not going to use such logic for desktop-users packages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org