DON looks for repo files to know which repositoreis to look for files in.<\/p>\n\n\n\n
Repo files should look familiar to most enterprise Linux users. It’s an INI format configuration file with some expected values:<\/p>\n\n\n\n
[repo_name]\nfriendly_name=Official DPM Repository\nbase_url=https:\/\/www.darkhorselinux.org\/dpm_repository\nenabled=1\nweight=0<\/code><\/pre>\n\n\n\nAt the top level section declaration is the name of the repository. These must be unique, and DON will throw an error if they are not.<\/p>\n\n\n\n
In each repo section is friendly_name<\/code>, base_url<\/code>, enabled<\/code>, which should all be quite familiar.<\/p>\n\n\n\nEach repo section also has a weight<\/code> value used to weight repos when finding packages or matching dependency rules. Weights with a higher value are searched first and weight defaults to 0. This allows the user to allow base system repositories or add-on repositories to take priority when matching dependencies for situations that require that. When looking for a package to meet a depenency, DPM will find the first package from the repository with the highest weight.<\/p>\n\n\n\nAny number of repositories can be configured in a .repo file. These files are intended to be located in \/etc\/don.repos.d\/<\/code>. If a repo filename does not end with .repo<\/code> it will be ignored by DON.<\/p>\n\n\n\nIt is highly recommended to have one repository per .repo file unless the repositories are specially related and meant to operate as one whole source, such as a collection of vendor repositories, or lumping together repositories from a common provider.<\/p>\n