To port or not to port?
- Date: Sat, 19 Jan 2008 14:01:38 +0000
- From: Robert Hogan <lists@xxxxxxxxxxxxxxx>
- Subject: To port or not to port?
Hi, I maintain two minor KDE-3.5 based apps: KlamAV and TorK. KlamAV is firmly in bare maintenance mode. TorK is soon heading that way. (I want to spend my spare time coding new stuff.) Am I right in thinking I don't *need* to port either app to KDE4; that both will, all things being equal, continue to run just fine on most distros, even when they migrate to KDE4? This is based on the assumption that most or all distros are going to maintan a 3.5 compatibility layer, um, of some sort. So far as I can see most applications have used the porting process to completely renovate themselves or have been ported because they are a core part of KDE. The continued usability of the app doesn't appear to be a motivation. Am I right? Or do I need to gird my loins for a month or two of fiddle-compile cycles?
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
- Follow-Ups:
- Re: To port or not to port?
- From: Benoît Jacob
- Re: To port or not to port?
- From: Albert Astals Cid
- Re: To port or not to port?
- From: Andreas Pakulat
- Re: To port or not to port?
- Prev by Date: Konqueror Branch 3.5 JPEG thumbnail creation issue
- Next by Date: Re: To port or not to port?
- Previous by thread: Konqueror Branch 3.5 JPEG thumbnail creation issue
- Next by thread: Re: To port or not to port?
- Index(es):