Summary: | sys-apps/file depends of python even when using -python due to unconditional inheritance of distutils | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexandru Toma <flash3001> |
Component: | [OLD] Unspecified | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexandru Toma
2005-08-19 05:39:16 UTC
You misunderstand how USE flags work. They're for controlling optional dependencies, and won't affect anything when a package always depends on another. Perhaps to clarify, python is an unconditional dep elsewhere in the dep tree. Unless I'm not thinking properly. Well, I think I know how USE flags are supposed to work. However, the only dependency of file is this one: DEPEND="!build? ( python? ( virtual/python ) )" So there is no other dependency tree. However, you are right. I thought this was a portage bug but its a bug in the file ebuild. It inherits distutils unconditionally and that makes it always depend on python, even when using -python. Reopening in order to assign to bug-wranglers Yeah, sorry if I was a bit trigger-happy on the 'assume the user is stupid' thing. It happens a bit too much these days. ;) No problem ;) I too should have investigated things a little more before posting. Sorry for all the mess in reassigning the bug. removed python from DEPEND You seem to have misunderstood this bug report. Please read it again. The problem is that the file ebuild depends on python even when using "-python" in the use flags which should disable this dependency. The change you have commited doesn't "fix" the bug in any way... The "actual results" as mentioned in the first comment are still the same. lemme rephrase we could: - remove all python support - add 'use python && inherit distutils' - ignore the issue since it doesnt seem to be a real important one i'm going with the last one Why don't you use the second option you have mentioned. It's just a line and it would fix the problem. I don't think you should ignore the problem especially when the fix is so simple. The problem might not be important but it's really annoying (at least to me). Every time I want to "emerge -u something" that has file somewhere in the dependency tree (and a lot of packages do), I end up having to upgrade python and a slew of other packages as well. So let me end by saying this: Please fix this bug if the fix is so simple ;) the 2nd one is wrong, it breaks portage caching mechanisms |