| Summary: | Reasons for profile version numbering should be documented | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Einstok Fair <einfair> |
| Component: | Devmanual | Assignee: | Gentoo Devmanual Team <devmanual> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | gentoo, sam |
| Priority: | Normal | Keywords: | NeedPatch |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | notes from #gentoo channel | ||
Created attachment 762388 [details] notes from #gentoo channel Profile names contain a version number, such as 17.0 or 17.1. It would be nice to have list of reasons when one need to increase the version. Such as: - changes in File Hierarchy Standard (FHS) - splitting system packages into parts - something else? It is also nice to explain why rules are added and what wrong will happen if they will not be followed. The last thought is applicable to all other rules in developers guide. Right now there are no such explanations in many places. Also it will be nice to have the documentation for specific use case of profile usage - for synchronization of settings between binary server and it's clients. It's common enough, i think.