On Thu, Oct 30, 2003 at 10:12:45AM -0500, Michael K. Johnson wrote:
As I said, I haven't been responsible for config tools at Red Hat
years. Yes, Crutcher and I had arguments about redhat-config-printer.
However, there's one issue we had there that really overrides my
arguments: until FC1, we were trying to support two very different
print systems from one tool, including migrating configurations.
So it's not necessarily the wrong decision in this particular case.
At least it doesn't regen the config files every time you sneeze,
and you *can* choose to configure by hand if you like and not have
your files overridden at all; that's a huge difference from SMIT.
IMHO, redhat-config-printer should be replaced by a tool that just
changes the CUPS configuration files when you want it to. The whole
'editing a look-aside configuration file and periodically writing out
the real configuration files from it' thing was useful for LPRng->CUPS
migration by chance alone: I still needed to write code to import
queues from the configuration files because of the CUPS web interface.
The current situation just stifles its functionality. The new tool
should look roughly the same of course, and be at least as scriptable
as the current one (so that kudzu can add print queues).
With CUPS of course there really is the possibility of providing a
list of command lines to run (lpadmin).