|
Bugzilla – Full Text Bug Listing |
| Summary: | YUM service chaining | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Naresh Wignarajah <naresh> |
| Component: | libzypp | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | adrian.schroeter, aj, dmacvicar, hmuelle |
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Naresh Wignarajah
2006-03-08 18:08:28 UTC
AFAICT YUM server meta data does not support this, i.e. providing additional YUM service metadata, which would be required to autoadd additional services. Unclear who can clarify this, NEEDINFO to aj for clarification. Either way my recommendation is we do this in a SP if required. Adrian, can you drive this? Adrian and myself will be looking into this, as we need this feature for the openSUSE build service as well. However, I'd suggest we discuss this upstream with the rpm-metadata folks. Moving to enhancement. It's not really ZENworks but related so leave it as such. Can we get this for libzypp? Yes, we should. Michael, Duncan, didn't you already think about a 'meta-respository' server, not returning package metadata but (links to) multiple repositories instead ? Determining which repository does a repository need is the point that needs to be defined. Naresh, can you please specify usecases to see if this is covered with latest features added? We will not fix this for 10.3, and for 11 we will look into something similar, but a more concrete usecase and specification. |