From KDE 3.3 and on, the quanta package will be named kdewebdev. It is not just another name since the package contains also other programs now (kommander, kimagemapeditor, klinkstatus, kxsldbg, kfilereplace). However, in portage there is an unstable ebuild for "app-editors/quanta-3.3_pre20040506". I suggest this is renamed kdewebdev and placed in an own kde-base/kdewebdev folder.
? quanta-3.3_pre20040506 was released prior to the first kdewebdev alpha. kde-base/kdewebdev already exists. the quanta team plans to continue releasing bleading edge quanta versions, which will go into kdewebdev from now on.
Well, the kdewebdev folder does indeed exist, but it is basically a skeleton ebuild: it has no SRC_URI, for example, and still carries the name quanta in its description string; it does not download its file itself, nor does it enforce a dependency with quanta-3.3-b2 - so it's basically empty. Furthermore, the quanta-3.3-beta2 ebuild explicitly downloads the kdewebdev package. I don't mean to be irritating or anything, if you prefer keeping quanta ebuilds until KDE 3.3 comes out, it's of course no problem - I just wanted to make sure that the issue was known, since the migration to kdewebdev will have to be done at some point; looking at the filenames of the download section at the Quanta homepage, it seems the developers are shifting now. I just looked at the packages for kdewebdev-3.3-be2 and the previous quanta-3.2-be1, and there are indeed more programs in the kdewebdev package. Cheers, -Federico
Look at some the other kde ebuilds, like kdeutils. You'll see that the handling for all of the downloading, etc, is done by the eclass. I understand what you're saying, though. The quanta_pre package is just a hack to handle the change that the quanta developers have put in. Once we start getting a few iterations of kdewebdev in portage, the app-editors/quanta directory will most likely go away.
Ok then - I guess I understood the situation, bug marked as fixed.
