ClearFoundation Tracker - ClearCenter | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0001053 | ClearCenter | clearos-release-professional | public | 2013-03-25 16:01 | 2013-04-01 12:27 |
Reporter | user2 | ||||
Assigned To | user2 | ||||
Priority | normal | Severity | tweak | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Platform | OS | OS Version | |||
Product Version | |||||
Target Version | 6.4.0 | Fixed in Version | 6.4.0 | ||
Summary | 0001053: Move clearos-core repo entry to separate file | ||||
Description | The clearos-core repo entry should be in a separate file. A lot of deployments will want to have clearos-core enabled all the time and moving the repo configuration to a separate configlet eases administration. One could make the case that the clearos-core repo configlet should be part of a separate RPM, but... Core is a bit of a special case. In addition, included it in the clearos-release package makes it possible to bootstrap a CentOS system as described in the developer docs: http://www.clearfoundation.com/docs/developer/architecture/core_system/start [^] The linked procedure is not a recommended way to install ClearOS, but simply a walkthrough for those coming from CentOS. | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2013-03-25 16:01 | user2 | New Issue | |||
2013-03-25 16:01 | user2 | Status | new => assigned | ||
2013-03-25 16:01 | user2 | Assigned To | => user2 | ||
2013-03-25 16:01 | user2 | Issue generated from: 0001005 | |||
2013-03-25 16:01 | user2 | Project | ClearOS => ClearCenter | ||
2013-03-25 16:01 | user2 | Category | clearos-release-community => General | ||
2013-03-25 16:03 | user2 | Category | General => clearos-release-professional | ||
2013-03-25 16:03 | user2 | Target Version | => 6.4.0 | ||
2013-04-01 12:27 | user2 | Status | assigned => resolved | ||
2013-04-01 12:27 | user2 | Fixed in Version | => 6.4.0 | ||
2013-04-01 12:27 | user2 | Resolution | open => fixed | ||
2013-04-01 12:27 | user2 | Status | resolved => closed |
There are no notes attached to this issue. |