|
Bugzilla – Full Text Bug Listing |
| Summary: | build cycle between yast2-users and yast2-mail | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Andreas Jaeger <aj> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | ro, varkoly |
| Version: | Alpha 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Jaeger
2007-04-29 11:35:08 UTC
yast2-users doesn't require yast2-mail but yast2-mail-aliases. Peter, does yast2-mail-aliases require yast2-mail? Maybe the best way would be to move MailAliases.ycp to some other module (probably yast2), which is required by both yast2-users and yast2-mail. yast2-mail-aliases do not require yast2-mail. But the problem is that yast2-mail-aliases will be build from the same tarball as yast2-mail. i.e. if you want to build yast2-mail-aliases, you have to build yast2-mail to :-( We can put MailAliases.ycp in yast2-users or in yast2 i.o.s I think it is fine to move MailAliases.ycp to yast2.rpm I've moved MailAliases.ycp to yast2. |