Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
In general they're in /var/lib/ and I think by default Suse's Yast uses libzypp so in some sub-directory of /var/lib/zypp
I think by default rpms are not kept and there doesn't seem to be a way to enable keeping them in Yast's repository manager but using the zypper command line there is a "-k" option when adding repositories (see the man page - "man zypper")
From "man zypper" see "-k, --keep-packages
Enable RPM files caching for the repository. "
zypper is able to work with YaST, YUM, and aptrpm repositories, ZENworks 7 Linux Management, ZENworks 6.6.x Linux Management servers, as well as local files.
addrepo (ar) [options] <URI> <alias>
addrepo (ar) [options] <FILE.repo>
Add a new repository specified by URI and assign specified alias to it or specify URI to repo file.
Newly added repositories have auto-refresh disabled by default (except for repositories imported from a .repo, having the auto-refresh enabled). To enable auto-refresh, use the --refresh option of the modifyrepo command.
Also, this command does not automatically refresh the newly added repositories. The repositories will get refreshed when used for the first time, or you can use the refresh command after finishing your modifications with *repo commands. See also METADATA REFRESH POLICY section for more details.
-r, --repo <FILE.repo>
Read URI and alias from specified .repo file
-t, --type <TYPE>
Type of repository (yast2, rpm-md, or plaindir). There are several aliases defined for these types: yast2 - susetags, yast, YaST, YaST2, YAST; rpm-md - repomd, rpmmd, yum, YUM; plaindir - Plaindir.
Add the repository as disabled.
Probe given URI.
Don't probe URI, probe later during refresh.
Specify descriptive name for the repository.
Enable RPM files caching for the repository.
Disable RPM files caching.