Chris Rivera wrote:
> On Wed, 2007-03-28 at 18:17 +0200, Klaus Singvogel wrote:
> > Sorry to say, but we ship Foomatic too.
>
> The only foomatic package I see is foomatic-filters. All other ppds on
> my system are provided by cups-drivers or vendor specific packages.
Yes, true. You might not find it, if you're just looking at the names.
:-) "cups-drivers" contains the foomatic database, but some additional
drivers too.
I don't think that there are good reasons to rename it at the moment.
I think even more it helps the customer to classify the package as a
cups related package, whereas "foomatic-db" might not. :-)
> > > There are tools other than Yast that need a printer to ppd/driver
> > > mapping. The parsing and fuzzy mapping of ppd files on the system
> > > is painful. It would be nice to have one solution used by all of
> > > our tools.
> >
> > I think we shouldn't dig to deep into YaST here, and let YaST do
> > it's magic as it is.
>
> I'm not 100% convinced that Yast is the right tool for this. There are
> other tools, like gnome-cups-manager, that still need this same
> functionality. A simple mapping solution should be available to all
> system tools, not just Yast.
Correct. The maping needs to be done by a helper tool, which is called
by a HAL callout. And it should then call a further tool (with the
mapping information) which does the installation of the printer in
CUPS. Please keep in mind that there are specifications how much time
a tool can maximum run, when being a HAL callout.
Whereas the first tool needs still to be written, and could (in
theorie) call any printer installation tool in second step. So do I
think the later should become YaST, as it already contains a lot of
the needed code for PPD selection, etc. But even more: it's
independend of the used desktop system (politically clean and
therefore might get accepted by the KDE fraction and X11 purists too
:-), and even runs on headless server machines.
I might have given additional reasons in the past why we should use
YaST for the installation process. I will look them up, if you're
still in doubt.
I have this workflow in mind:
HAL --callout--> "helper tool" (tbd) --device mapping--> YaST
Regards,
Klaus.
--
Klaus Singvogel
SUSE LINUX Products GmbH
Maxfeldstr. 5 E-Mail: [EMAIL PROTECTED]
90409 Nuernberg Phone: +49 (0) 911 740530
Germany GnuPG-Key-ID: 1024R/5068792D 1994-06-27
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
