|
Bugzilla – Full Text Bug Listing |
| Summary: | software manager: import installation sources | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | macias - <bluedzins> |
| Component: | YaST2 | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | dmacvicar, kkaempf, ma, mvidner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
macias -
2007-07-27 06:50:55 UTC
installation_sources is an alias for zypper First of all, the installation_sources script uses zypper to do its job and was provided as a compatibility replacement for a program that was in yast2-packagemanager.rpm. You can switch to zypper now (or after 10.3 is out). The new version of libzypp which, will be (hopefully) shipped with openSUSE 10.3 and therefore the applications using it (YaST, zypper, ...) use plain text .repo files located by default in /etc/zypp/repos.d to configure repositories (inst. sources). Exporting and importing them is a matter of copying the files. (Don't forget to refresh the repos after manipulating them). Should we provide a simple way to export/import these through zypper anyway? Jan, I am just a user so I know this question wasn't for me, but anyway my 2 cents: Pros: 1) black-box design, no matter what form is used to store repo list, from the user perspective it does not change, so it is great for backups for example (you just type xxxx --export and you have a guarantee all you have to do on system crash is xxxx --import and it works) 2) convenient for users, import, export, no fiddling with raw files 2.a) security -- if you want to send such file to somebody each time you have to check what the log, config, etc. really contains, this way, since you are about to send export you are sure it is nothing more than repo list 3) with a tiny extra option new functionality, you can import the list (i.e. replace the old one) or you can import & merge at the same time (even better) The export functionality is cp /etc/zypp/repod.d/* /backup The import functionality is cp /backup/* /etc/zypp/repod.d Duncan, thank you for help, I will sure use it because I don't have any other chance :-) However as the solution for users it does not have any advantages mentioned before. (In reply to comment #5 from Maciej Pilichowski) > However as the solution for users it does not have any advantages > mentioned before. huh ? what is more simple than file copy operation... ? I dont get your point... I explained them before (take a look). For example -- how can you merge anything using cp? How can you guarantee the design (it already changed!)? Etc. OK, i think i have a solution. For "importing" repos, you already can use zypper addrepo --repo repo_file_URL. It will add all the repos defined in the specified file (can be remote or local (although local needs fix, for now you have to specify it as file://absolute/path/to/the/file.repo). For exporting i will soon add a functionality to write all the repos into a single .repo file. (Probably zypper repos --export <file> or something like that). But, as mentioned before, you already can manipulate the files manually, they are just simple text files (ini format). zypper repos --export file done in svn, will be submitted in zypper 0.8.11 submitted in zypper 0.8.11 |