David C. Rankin composed on 2017-07-25 15:16 (UTC-0400): ...
When you 'zypper lr' (list repos), zypper just scans the /etc/zypp/repos.d directory and includes what it finds. The `'enabled` flag in each file tells zypper whether the repo is enabled or not.
While undeniably true, your response describes nothing like what I was trying to convey to John that you found in John's onlist reply to my private email to him. I create on my LAN server one set of .repo files and timestamp all with the date of a distribution release. All installations here at some early point get their /etc/zypp/repos.d/ content from the LAN server. Those copied (except for TW's) are never, unless in the rare case that I desire a temporary change in priority, subsequently changed before support for that release expires. Repos here are enabled or disabled by changing which files end in .repo or not, either by copying a file that does not end in .repo to one that does in order to enable /or/ to change an applicable baseurl, or by deleting a .repo file to disable. WRT libzypp, all files in /etc/zypp/repos.d/ that do not end in .repo are inert, ignored, irrelevant, etc., just as if their content was in any relevant way invalid. Repo caching for me, and locking/unlocking particularly, in openSUSE works fabulously, as does the vast majority of the zypp-based system. Other package management systems by comparison I find hopelessly deficient. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org