| Summary: | Do we upgrade drakconf as if it were an ordinary application? | ||
|---|---|---|---|
| Product: | [ROSA-based products] ROSA Fresh | Reporter: | Zombie Ryushu <zombie.ryushu> |
| Component: | -Enter Bugs Here- | Assignee: | Desktop Triage Team <triage-desktop> |
| Status: | RESOLVED WONTFIX | QA Contact: | Desktop Triage Team <triage-desktop> |
| Severity: | normal | ||
| Priority: | Normal | CC: | denis.silakov |
| Version: | Fresh | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | drakconf-legacy | ISO-related: | |
| Bad POT generating: | Upstream: | ||
|
Description
Zombie Ryushu
2015-01-28 00:19:40 MSK
ROSA's direction for the last several years was to get rid of old drakxtools wherever possible. In KDE, users are encouraged to use KDE Control Center, and some necessary drak tools (whose functionality is not implemented in KDE itself - e.g., rpmdrake) are integrated in it. In LXDE, lxde-control-center is considered to be drakconf replacement. drakconf-legacy package still exists, but it was moved to contrib repository and now it is not much supported, at least not by ROSA maintainers. |