Distributions we hope to support
- CentOS/RHEl/SciLinux
- Fedora
Repositories
- Rpmrepo-core : With most packages, as long as they dont overwrite a distro package
- Rpmrepo-plus : With packages that overwrite distro packages
Also, each repo would 3 sections :
- Stable : Which is the main repo and what users see by default
- Testing : Where developers and packagers can do test builds and ask for feedback etc
- Sandbox : Where developers and packagers can do their development work, this repo need not ultimately even be public, or even published to external mirrors.
There will need to be a repository package elevation process, so its clear to people how packages move from Testing to Stable.
Sample Layout on Disk
Web user interface
A single page per RPM ( or per Package, that way we can include all the sub-rpm as well, and reduce the number of pages we need) - split the page into 4 sections. eg:
- General info about the package, who is packaging it and a rpm -qi output perhaps
- links to the rpms / srpms / debuginfo / logs
- Place for people to leave comments about packages
- Status list in rpmrepo for that package
- Bugzilla satus - so list all issues reported against that package
- list update history of the package
The entire web interface to the packages needs to be, ofcourse, generated based on internal info, Its not humanely possible to maintain this info by hand for each package