Time to move kmyfirewall?

[Unai Garro Arrazola]

On Thursday 10 April 2003 23:08, George Staikos wrote:

> > The current state in the CVS is that it doesn't build but it's pretty
> > simple to be fixed (KMyFirewallConfigDialog seems to have been renamed,
> > when kmyfirewall.cpp  still looks for KMFirewallConfigDialog). I just got
> > it built and it seems to work (tm).
>    Sorry, this is the wrong approach.  You need to show that it's maintained 
> in order to move it to a release module.  The last thing we want is to have 
> more code for the regular maintainers to fix bugs for.
> 

The point is not to have it maintained by the regular maintainers. As you can 
see in the project page (http://prdownloads.sourceforge.net/kmyfirewall) 
there have been quite regular updates so far. It works wonders with KDE 
3.1... but just doesn't work straight with CVS, since nobody tests it against 
CVS.

At least from my point of view, it's just not so easy to maintain a package in 
kdenonbeta, when nobody pays attention and nobody tests regularly. I'm sure 
that there're several packages in the kde-cvs that are much less maintained 
right now: see krita, aktion, ksim,kworldclock,kmoon,... and the list can go 
forever. Most of their changes are as simple as fixing the e-mail address of 
the author.

This is not definetely a "nonbeta" soft, since it's been quite useable for a 
while already.

I've seen other tools disappearing for less than that (klyx 2) and then after 
a year someone else tries to do the same thing that doesn't work as good (lyx 
with QT frontend)



-- 
On a paper submitted by a physicist colleague:

"This isn't right.  This isn't even wrong."
		-- Wolfgang Pauli

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<