|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-nis-client has wrong information in "Requires" tag | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Lukas Ocilka <locilka> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Alpha 1plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Lukas Ocilka
2007-03-09 15:19:15 UTC
> because this dependency is not direct
What's the point? Why is the new way better? It isn't equivalent anyway.
Actually, this is the correct way how to express indirect dependency on some package which is not directly required. Don't beat me but packagers :) But the package is directly required (at least in what I do understand as requirement). Where is the source for your correct way definition? yast2-core is required by yast2.rpm I see. But I still don't see the benefit of the change. Well, the benefit is to make dependencies clearer ... Additionally, 'yast2-core < 2.8.0' doesn't make sense for 10.3 OK, I will use the Conflicts tag. |