Re: Don't implement config functionality (hardcoding Config Tools)

On Thu, Jan 15, 2004 at 08:59:25PM +0000, Simon Edwards wrote:

> I also have a daemon/system service util that works 
> well on Mandrake and needs to be ported to Debian. (It looks easy enough 
> judging from Knoppix).

It's almost the same (SysV init), the only thing that you have to
consider (from the screenshots in your page) is than in Debian there is
not "5=graphical boot, 2=non-graphical boot"  and the default runlevel
(graphical or not) is 2. To see if you are in Debian within your code
you can check for the file /etc/debian_version.

I'll try to help you porting it to Debian as soon as I have a working
PyKDE installation (for some library problems it doesn't work on Sid
now).


> I also have a mount util that is half done (/etc/fstab 
> is no problem, most of the work in GUI based). Those are the kinds of 
> problems that I'm facing.

Same here.

I'll start shortly (read: next week) to write a Python/Qt/KDE network
device configuration tool using ifupdown (the Debian standart) and
/etc/network/interfaces. I plan it to be in the line of the GUI tools
found in other distributions (RH, Mandrake, SuSE...) which Debian
currently lacks (there are lots of unrelated text-mode tools and scripts
but nothing graphical, automatic, and easy) and I'm sure the parsing of
/etc/network/interfaces is not going to be a problem at all. 

Same with kalternatives, parsing the format of /var/lib/dpkg/alternatives/*
files was the easy part (that's done by the AltManager object), the GUI
got 90% of the work (and is still not finished).

Cheers, 
        Juanjo

PS: Somebody has a working PyKDE + Debian Sid? How? Ricardo packages are
still missing, it fails to compile on my system and I need to do some
real work ;)