|
Bugzilla – Full Text Bug Listing |
| Summary: | Source-type ZYPP should have a more obvious name | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Forgotten User --EoyBps8f <forgotten_--EoyBps8f> |
| Component: | YaST2 | Assignee: | Klaus Kämpf <kkaempf> |
| Status: | RESOLVED FIXED | QA Contact: | Mauro Parra Miranda <mauro> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | andreas.hanke, hmuelle, kkaempf, suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User --EoyBps8f
2006-05-28 11:22:51 UTC
-> Stano ? This is also true for the new zen-thingy and the "add service" dialogue! Stefan, we need to define the terms. Correct. Klaus, please help me with a short description of the different service types and I'll let marketing or PM find more descriptive names. Code10 currently supports two types of repositories 1. 'yast', line based ascii data used by SUSE since ages. Pros: Easy to generate, easy to read, easy to read-on-demand (no need to keep everything in memory), small in size, support for translations Cons: Used only by SUSE, spreads data across multiple files, extended over the years mostly on ad-hoc basis, no widespread support. 2. 'repomd' (also named 'yum'), XML based Pros: Standardized, Easy to extend, Accepted by community, Broad support by tools and libraries Cons: A bit harder to generate and parse, no read-on-demand, somewhat bloated (well, its XML), no translations support The zypp library currently supports auto-detection of both formats (but we will probably remove this capability since it makes error reporting harder). The current name zypp vs. yum in rug doesn't really denote the repository type but the 'owner'. Since ZMD and zypp both understand the repomd format, we use 'yum' to give ownership to ZMD (resp. rug, zen-*) and 'zypp' to give ownership to zypp (resp. YaST). Ideally, the source type names should be 'yast' and 'repomd' in the sense listed above (1. and 2.). But this needs some architectural changes in the way ZMD and YaST interact. Klaus, thanks for the clarification. What about NU and RCE? They are available, too... -> another needinfo for you :-) NU is 'Novell Update', which serves as kind of meta-repository. The main content isn't the metadata but a file containing URLs of other repositories. We should try to follow (make ?) a standard here. RCE is 'red carpet enterprise' (aka ZLM 6), an XML format now obsolete. Probably we should just write them out in the selection boxes. We definitively should eliminate the distinction YUM/ZYPP which makes no sense at all. Both are YUM types. So we have: - YUM - Novell Update - Red Carpet Enterprise Captured everything? cthiel pointed out that there is no "YUM" repository type. The correct name is "repomd", "yum" is a tool to access such a repo. Exactly. Smart calls the repomd "rpm-md", which is another "valid name" ;) So, if we have the chance to choose a new name instead of YUM --> let go for RepoMD. Please watch opensuse-factory. Rebecca Walter will take care for name unification. Forget comment #12. Rebecca will try to unify 'source', 'repository', 'channel', etc. together with the opensuse community. Naming of repository _types_ (yast, yum, repomd, ...) will be worked on later. . Revisit in preparation of Code11 Fixed in 10.3 |