| Summary: | kde should require mtools | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Priyadi Iman Nurcahyo <priyadi> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mehlng |
| Priority: | High | ||
| Version: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Priyadi Iman Nurcahyo
2002-07-12 23:06:12 UTC
I'm no KDE guy, but that doesn't seem like a strict dependency. Especially if emerging mtools after KDE gets you that support anyway. It doesn't, it's a compile-time thing. Hm.... Posted on gentoo-core for policy clarification. Status update: since this is a rarely requested functionality, and kdebae is
such an important package, we've decided not to make this a dep for now. Once
we have support for package-specific ("minor") use flags/parameters, we'll
implement this and other similar things that way. (It will happen _some_ day,
just not very soon.)
I've got a comment about it in the ebuild, so I won't forget.
OK Seemant, let's keep this open so as to not forget about it... I intended to add a local use flag to kdebase, but now I see that in kde 3.1x, the dep is a rutime one. I.e. the floppy ioslave is always built, and you can emerge mtools at any point in the future to make it work. I'll drop a note to alpha@gentoo.org that they may want to add a keyword to the mtools ebuild (it already has ppc and sparc), add an informational notice to the kdebase ebuild and close this bugreport in a fw days if you don't object. (I wouldn't blame you for not responding after all this time. But, that's what low priority does to a bugreport.) Psst, Dan... do you want to close this bug now? :) For now this can be considered fixed. When persistent local useflags get around we might have a conditional dependency on mtools. |
