Bug#275171: konqueror: Please include "kecko" Gecko layout engine
On Tue, Oct 12, 2004 at 10:51:15PM +0200, Bellegarde C?dric wrote: > Le Mardi 12 Octobre 2004 11:10, [EMAIL PROTECTED] a ?crit?: > > The unreleased state of the product does not mean a wishlist bug is not > > appropriate. > > It make your bug invalid. > > Mozilla Qt is in mozilla CVS but it is totally unusable! > There is no kpart for now! No, the unreleased state of the product or unusability does not make the wishlist bug invalid. :) We've been through this already. My impression was that the kpart would be in KDE upstream, like the old one from the 2.x days. However, if the kpart really will live in Mozilla upstream rather than KDE upstream, the bug could certainly be retitled to an RFP and reassigned to wnpp, or reassigned to the appropriate Mozilla package. I believe I mentioned this previously. > And, it's a mozilla related package! > You will have mozilla-qt and mozilla-kpart , i think. -- _ivan
Bug#275171: konqueror: Please include "kecko" Gecko layout engine
On Mon, Oct 11, 2004 at 05:16:59PM +0200, Alejandro Exojo wrote: > El Mi?rcoles, 6 de Octubre de 2004 22:12, [EMAIL PROTECTED] escribi?: > > On Wed, Oct 06, 2004 at 09:31:49PM +0200, Alejandro Exojo wrote: > > Again, the unreleased status of the software does NOT mean the wishlist > > bug should be closed. It is a reasonable wishlist bug, and the current > > state or release status of the implementation is NOT RELEVANT and NOT > > justification to close the bug. > > The unreleased state of the project, means a lot if you can't put the > necessary information in the copyright file. The unreleased state of the product does not mean a wishlist bug is not appropriate. When there is code, there will be the necessary information to put in the copyright file. If there is a license problem, it will have to be resolved, but that does not invalidate a wishlist bug for the functionality. > > > and that doesn't have any relation with kdebase. > > > > My impression was that kecko was to be an alternate rendering engine for > > the konqueror browser that could be built alongside or as an alternative > > to the KTHML engine from KDE source. How does that have no relation to > > kdebase? > > Because the port is code related to mozilla, not tot KDE. Konqueror has the > feature of embedding plugins (java, flash, etc.) but asking its mantainers to > package those plugins, doesn't makes sense. As you note below, the port *is* code related to KDE, specifically a KPart that will eventually be available from the same source. This wishlist bug is for the inclusion of said code in the konqueror package, or another KDE package alongside it, enabling me to use the konqueror browser with the Gecko rendering engine in addition to KHTML. > > My impression is that it would be an option when compiling KDE, not a > > standalone package. Hence I filed the bug against the relevant KDE > > component (to me as a user, anyway) rather than as an RFP. > > > > If kecko will be _separate_ source package that isn't built from KDE > > source, then reassigning to wnpp and retitling as RFP would be > > appropriate - but as I said my impression was that it would be a part of > > the KDE source (albeit one that depended on Gecko). > > It needs two components: a KPart, and the Qt port, as the new you posted > explained. [snip] > Anyway, latest news: > > http://www.kdedevelopers.org/node/view/666 > > So _today_ (not Wed, 6 Oct 2004 05:21:47 -0700, when you first reported the > bug), it seems that there is the first code available. I checked it out, and > at least now we can say that there is a license and copyright holder(s), but > it is a combination of MPL/GPL/LGPL, so it can be complex. But again, as I > said, it's code unrelated to KDE. > > Still there is no code for the KPart needed. It's very probable, that it will > be commited to the kdenonbeta module, and, when it fits the KDE release > schedule, will be moved to kdebase. > > Then, at that moment, but not before, if the packages of that version of > konqueror in Debian, doesn't include support for embedding gecko, a wishlist > will make sense. No. At that moment may make sense to think about *implementing* the feature in Debian. The wishlist bug is appropriate at any time. > This is my point, and I hope you understood it. I can sympathize, but you should not impose your opinion on Debian in conflict with our practices. > Anyway, I'm not the mantainer > of this package, neither a Debian developer, so if have more information to > add, don't reply to me, do it to the bugreport only, please. I am a Debian developer, and I have never heard nor seen documented the conditions you state are necessary for a wishlist bug. On the contrary, wishlist bugs are commonly used to request features in _any_ state of completion, even those for which there is no code or even an idea before the wishlist bug itself. The BTS developer documentation at http://www.debian.org/Bugs/Developer#severities states that wishlist bugs are appropriate "for any feature request", not "requests for features already released upstream". -- _ivan
Bug#275171: konqueror: Please include "kecko" Gecko layout engine
On Wed, Oct 06, 2004 at 09:31:49PM +0200, Alejandro Exojo wrote: > El Mi?rcoles, 6 de Octubre de 2004 16:30, [EMAIL PROTECTED] escribi?: > > On Wed, Oct 06, 2004 at 04:07:27PM +0200, Alejandro Exojo wrote: > > > El Mi?rcoles, 6 de Octubre de 2004 14:21, [EMAIL PROTECTED] escribi?: > > > > http://dot.kde.org/1094924433 > > > > > > If you read the story, you will see that this code relies on Mozilla's > > > repository, and that is yet unreleased. > > > > Yes, I know. > > Then why you fill a bugreport against konqueror? (Source: kdebase) Because to me as a user, this is where I'd see the feature - as an alternate rendering engine available in Konqueror, built along with konqueror and other items from kdebase source. I have no opinion on whether it would be more appropriate to move the bug to kdebase - feel free to move it if so. > > > I'm closing this bug because it's invalid. > > > > This statement does not follow from the previous ones. > > > > This is certainly a valid wishlist bug. Please do not close it until > > the feature is implemented, presumably after upstreams have made > > releases with the necessary code. > > I closed it because the wishlist is "package kecko", but "kecko" is an > unreleased software, that maybe never sees the light (like the other gecko > port that existed), Again, the unreleased status of the software does NOT mean the wishlist bug should be closed. It is a reasonable wishlist bug, and the current state or release status of the implementation is NOT RELEVANT and NOT justification to close the bug. (IIRC, the previous gecko port did see the light of day - I seem to recall a debian package of it for KDE 2.x) Feel free to retitle this bug to "Please include a Gecko layout engine" or something along those lines if the specific mention of "kecko" is what you find inappropriate here. > and that doesn't have any relation with kdebase. My impression was that kecko was to be an alternate rendering engine for the konqueror browser that could be built alongside or as an alternative to the KTHML engine from KDE source. How does that have no relation to kdebase? > > If you don't plan to implement the feature even when it is available > > upstream, leave it open and tag it wontfix. > > Maybe the best solution is reassign it to wnpp and retitle it as a RFP bug. > Then, if someone wants to package it, it's his/her decision. My impression is that it would be an option when compiling KDE, not a standalone package. Hence I filed the bug against the relevant KDE component (to me as a user, anyway) rather than as an RFP. If kecko will be _separate_ source package that isn't built from KDE source, then reassigning to wnpp and retitling as RFP would be appropriate - but as I said my impression was that it would be a part of the KDE source (albeit one that depended on Gecko). > I _think_ is invalid because this software is unreleased, The unreleased status of the kecko software in no way makes the bug invalid. Consider the situation where the kecko software didn't exist at all; a wishlist bug for gecko renderer support in konqueror would certainly be appropriate. The fact that some work has actually been done toward this end but is not yet released does not invalidate the wishlist bug during the time it takes upstream to implement and release. > but I'm 99% sure that this isn't a valid wishlist bug I believe you are incorrect for the reasons stated above. > _agaisnt konqueror_. Feel free to reassign to the appropriate KDE package, of course. -- _ivan
Bug#275171: konqueror: Please include "kecko" Gecko layout engine
On Wed, Oct 06, 2004 at 04:07:27PM +0200, Alejandro Exojo wrote: > El Mi?rcoles, 6 de Octubre de 2004 14:21, [EMAIL PROTECTED] escribi?: > > Package: konqueror > > Version: 4:3.3.0a-1 > > Severity: wishlist > > > > Please include the "kecko" Gecko layout engine in addition to KHTML > > > > http://dot.kde.org/1094924433 > > If you read the story, you will see that this code relies on Mozilla's > repository, and that is yet unreleased. Yes, I know. > I'm closing this bug because it's invalid. This statement does not follow from the previous ones. This is certainly a valid wishlist bug. Please do not close it until the feature is implemented, presumably after upstreams have made releases with the necessary code. If you don't plan to implement the feature even when it is available upstream, leave it open and tag it wontfix. Thank you. -- _ivan
Bug#275171: konqueror: Please include "kecko" Gecko layout engine
Package: konqueror Version: 4:3.3.0a-1 Severity: wishlist Please include the "kecko" Gecko layout engine in addition to KHTML http://dot.kde.org/1094924433 -- _ivan
Bug#239297: kcontrol: should Depend: on kdebase-data
Package: kcontrol Version: 4:3.2.1-1 Severity: normal If kcontrol is run without kdebase-data installed, no entries appear under the "Index" or "Search" tabs, and nothing can be configured. Please consider adding a dependancy on kdebase-data, as the program appears to be unusable without it. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.24-1-k7 Locale: LANG=C, LC_CTYPE=C Versions of packages kcontrol depends on: ii kdelibs44:3.2.1-1KDE core libraries ii libart-2.0-22.3.16-3 Library of functions for 2D graphi ii libasound2 1.0.3b-1 Advanced Linux Sound Architecture ii libaudio2 1.6c-3 The Network Audio System (NAS). (s ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-5 client library to control the FAM ii libfontconfig1 2.2.2-1 generic font configuration library ii libfreetype62.1.7-2 FreeType 2 font engine, shared lib ii libgcc1 1:3.3.3-4GCC support library ii libice6 4.3.0-7 Inter-Client Exchange library ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libpcre34.5-1.1 Perl 5 Compatible Regular Expressi ii libpng12-0 1.2.5.0-5PNG library - runtime ii libqt3c102-mt 3:3.2.3-2Qt GUI Library (Threaded runtime v ii libraw1394-50.10.1-1 library for direct access to IEEE ii libsm6 4.3.0-7 X Window System Session Management ii libssl0.9.7 0.9.7c-5 SSL shared libraries ii libstdc++5 1:3.3.3-4The GNU Standard C++ Library v3 ii libx11-64.3.0-7 X Window System protocol client li ii libxcursor1 1.0.2-5 X Cursor management library ii libxext64.3.0-7 X Window System miscellaneous exte ii libxft2 2.1.2-6 FreeType-based font drawing librar ii libxmu6 4.3.0-7 X Window System miscellaneous util ii libxrandr2 4.3.0-7 X Window System Resize, Rotate and ii libxrender1 0.8.3-7 X Rendering Extension client libra ii libxt6 4.3.0-7 X Toolkit Intrinsics ii libxtst64.3.0-7 X Window System event recording an ii xlibmesa-gl [libgl1]4.3.0-7 Mesa 3D graphics library [XFree86] ii xlibs 4.3.0-7 X Window System client libraries m ii zlib1g 1:1.2.1-5compression library - runtime -- no debconf information -- _ivan