aptate configuration manual
Previous   Next

Element opt

Name

opt

Synopsis

Element Content Model 
opt ::=
( topdir )
Attributes
Name Type Default
bad-rpm-mode Enumeration:
report-only
rename 		"report-only"
bloat Enumeration:
yes
no 		"yes"
flat Enumeration:
yes
no 		"yes"
follow Enumeration:
yes
no 		"no"
old-hashfile Enumeration:
yes
no 		"yes"
patch-rpm-component Enumeration:
yes
no 		"yes"
patch-rpm-string Enumeration:
prpm
patchrpm 		"prpm"
security-component Enumeration:
yes
no 		"yes"
signed-pkgs-only Enumeration:
yes
no 		"no"
sign-repository Enumeration:
yes
no 		"no"
update-rpms Enumeration:
yes
no 		"no"
verbose Enumeration:
0
1
2
3
4 		"3"
wget-tries NMTOKEN  
wget-wait NMTOKEN  

Description

root element "options".

An explanation of the attributes belonging to the element "opt".

variable explanation cla
bad-rpm-mode The action to be performed on a bad rpm. A bad rpm is an rpm that fails the command "rpm -q". There are 2 treatments; report-only and rename.
  • in report-only mode aptate, as it says, will inform you only. So manual action is required, to get the problem resolved to prevent the warning being reported over and over again.
  • in rename mode aptate will move the bad rpm away. This prevents that the problem is reported over and over again. However, if the problem persist, because the rpm is rsync-ed over and over again it may be that the rpm provided by your rpm source is corrupt. The only way to solve this problem is at the source: contact the rpm provider.

In both cases the rpm will be excluded from the apt repository.

yes
bloat Provide apt databases with extensive information. It's adviced to activate this on rpm systems. no
flat The location of source rpm components. In a flat repository (flat=yes) the source rpms are located at the same level as the binary rpms. In non flat (flat=no) repositories the source rpms are stored 1 directory higher than the binary rpms.

Aptate has been optimized for flat repositories. Aptate has no problems creating a non flat apt repository that holds only 1 archive. The result in case the non flat repository holds more than 1 archive depends on the way the source rpms are organized in the rpm (not apt) repository. The result may be good may be bad.

Anyway, a flat repository seems the right choice for most rpm based distributions. 		no
follow Follow symlinks when searching rpms in the rpm repository. This is a dangerous option as the links can lead outside the apt or rpm repository. The apt repository maintainer must ensure this will not happen and must ensure that no endless loops exist in the rpm repository if directories or files are symlinked. no
old-hashfile Provide the apt-rpm version 0.3.19 hashfile for backwards compatibility. no
patch-rpm-component If yes, aptate will look for patch rpms and if found will make a seperate apt component holding patch rpms only, next to the component being processed. Doing so gives the possibility to assign patch rpms a higher priority than regular binary rpms or to exclude them. The component gets the name of the component being processed suffixed with a "patch-rpm-string". The latter is explained as a seperate item. no
patch-rpm-string The suffix that will be added to the component name in case the component provides patch rpms. It is a matter of taste: patchrpms says more than prpm, but hopefully prpms will be as common as srpms... So, the component for patch rpms will be either called RPMS.<component name>-prpm, or RPMS.<component name>-patchrpm. no
security-component If yes, aptate makes an apt repository component providing rpms that have been released to solve security problems only. There are many reasons why it's good to have an apt component providing only security related rpms. This can be because the user is behind a slow connection, wants to maintain to stable system, etc.
This functionality works now only for SuSE, however it is possible to extend aptate's functionality to get other distributions supported. 		no
signed-pkgs-only If yes, aptate will only import rpms into the apt repository, that pass the rpm (gpg) signature check. no
sign-repository If yes, aptate will sign the aptate repository with the name specified in the authorization element. This is usefull in case the apt repository is mirrored and you want to prevent others to sneak in incorrect rpms into your mirrored repository. no
update-rpms If activated new rpm packages will be downloaded from the download server(s) as specified in the component parts of the configuration file. yes
verbose The verboseness of aptate.
  • 0: no output (but a few error messages)
  • 1: all error messages
  • 2: idem 1, plus progress messages
  • 3: idem 2, plus progress counters
  • 4: idem 3, plus which config file is being read
  • 5: display all messages (debug mode)
  • 6: idem 5, but temporarely directories and files are not being removed
yes
wget-tries This is a wget option. The wget man states:
Set number of retries to number. Specify 0 for infinite retrying. 		no
wget-wait This is a wget option. The wget man states:
Wait the specified number of seconds between the retrievals. Use of this option is recommended, as it lightens the server load by making the requests less frequent. More about the wget wait option in the wget manual. 		no

cla: command line argument

Children

The following elements occur in opt: authorization, distribution, repdir, sharedir, sources-list-file, sources-list-ftp, sources-list-http, topdir .

Previous Home Next
name Up reject
--- Generated by dtd2html ---