Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 392663 - no ebuild exists for current versions of kde-base/smoke
Summary: no ebuild exists for current versions of kde-base/smoke
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 18:32 UTC by Andreas Arens
Modified: 2011-12-01 22:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Arens 2011-11-30 18:32:56 UTC
system: ~amd64

latest version in tree: 4.6.5

dilfridge, with kde 4.7.3 stabilization targeted, was this just just forgotten?
Comment 1 Johannes Huber (RETIRED) gentoo-dev 2011-11-30 18:54:51 UTC
kde-base/smoke was splitted with kde 4.7, see:

kde-base/smokegen
kde-base/smokekde
kde-base/smokeqt
Comment 2 Andreas Arens 2011-11-30 19:34:22 UTC
Well, it seems this is a kde-meta flaw, not reflecting the transition from the monolithic kde-base/smoke package to the new smokegen, smokekde, and smokeqt packages.
Also no word on the KDE upgrade guide.. A hint would be nice.
Comment 3 Johannes Huber (RETIRED) gentoo-dev 2011-11-30 19:45:25 UTC
There is no kde 4.7 upgrade guide yet. The smoke tranisition is documented by a  blocker in ebuilds which is handled by portage on world update.

More info can be found in handbook:
Working with Gentoo
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2
Comment 4 Andreas K. Hüttel archtester gentoo-dev 2011-12-01 22:11:56 UTC
(In reply to comment #2)
> Well, it seems this is a kde-meta flaw, not reflecting the transition from the
> monolithic kde-base/smoke package to the new smokegen, smokekde, and smokeqt
> packages.
> Also no word on the KDE upgrade guide.. A hint would be nice.

a) there is no 4.7 upgrade guide yet
b) it's perfectly fine in kde-meta

We'll keep it in mind, but it's not a bug per se.