|
Bugzilla – Full Text Bug Listing |
| Summary: | pkg-bindings url classification is incomplete | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Michael Andres <ma> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P2 - High | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Fixed in SVN trunk, will be in yast2-pkg-bindings-2.19.0 (FACTORY, 11.3). |
Some of pkg-bindings url classification methods could be replaced by zypp::Url::schemeIs* methods. E.g: bool PkgFunctions::remoteRepo(const zypp::Url &url) { // is it a remote repository? ... return (scheme == "ftp" || scheme == "http" || scheme == "https" || scheme == "nfs" || scheme == "smb"); This is basically the same as url.schemeIsRemote(), except for unhandled remote schemes like 'nfs4' or 'cifs'. Anyway, it looks like any pkg-bindings url-scheme handling code neither handles 'nfs4' nor 'cifs'(modern form of 'smb'). At least those two should be covered.