Re: ITP: task-cups-printing
hi
Mariusz.Przygodzki@WAW1.siemens.pl schrieb:
> Thanks.I has just reviewed this discussion and I have headache.
I hope I didn't couase it, I didn't want to hurt anybody ... ;)
> What's wrong in following proposal (this is only theoretical game):
>
> 1. We have standard package task-printing.
> 2. task-printing depends on
> lpr | task-lprng-printing | task-cups-printing | task-...
> and above packages are optional (except of lpr)
> and conflicts between themselves.
The installer confronts the user (except in 'expert mode') with
a flat list of task packages, with the 'task-' prefix stripped off.
(tasksel does that, to be precise, you can run it on an already
installed system as well).
This was done in order for newbies or hurried ppl not having to
wade through dselect. Thus having too many task packages would
be contraproductive, since the list that tasksel shows would get
too bloated.
task-printing makes sense, though creating task packages for
each spooler seems silly (task-lprng-printing would only depend
on lprng (or lprng's dependencies are broken)).
BTW: A virtual package for the BSD printing commands
(lp{r,q,rm}) would be appropriate (eg 'bsd-print-clients).
Currently the package 'lpr' is used as if it was a virtual
package (Reverse Provides: cupsys-bsd, lprng; Reverse Depends:
xfce, magicfilter, psptools, trueprint, apsfilter, tetex-bin,
texdoctk, cupsys-bsd, lprng, af, dedit, tkman).
ciao, 2ri
--
No, I'm not going to explain it. If you can't figure it out, you didn't
want to know anyway... :-)
-- Larry Wall in <1991Aug7.180856.2854@netlabs.com>
Reply to: