I have to agree with Manual who wrote:
>Why the hell would I install apache just to configure diald?
>.... I'd rather stick to a linuxconf plugin.
I don't like unrelated things being bundled together.
Unrelated things should not depend on each other, in my opinion.
Neither I think is reasonable for many to run an extra server (as apache)
just to change diald configuration once a year.
As well, I want to add support to an idea expressed few days ago by somebody:
Should we more think about automating configuration, rather than just
about GUI part ? Question is, who is the projected customer of
the application ? If, as I think, this is a fairly novice Linux user
(in a sense, not an exprienced network manager) with a couple of computers
at home - then most important for him is that any new program he
installs works (or almost works) 'out of the box'.
I myslef would be happy if there was a (debugged) library of
standard configurations (and filters) I could just copy (or choose in
GUI menu) in the first instance. And hopefully forget about
diald configuration forever.
Dmitri Pogosyan
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
