I haven't found information about the. Improve this question. Add a comment. Active Oldest Votes. One argument is passed: new package version. Two arguments are passed in the following order: new package version, old package version.
One argument is passed: old package version. Improve this answer. You are recommending that people install unsupported software without bothering to see what it is going to do. That is, IMO, irresponsible. No, I didn't recommend this. With default yaourtrc and with my recommendation yaourt will ask if you want really build the package and really want to install, so you can choice answer "no" and check PKGBUILD. Then edit your answer to remove the recommendation to blindly install from the AUR Show 1 more comment.
Sign up or log in Sign up using Google. This variable should always start at 1, and then move up one at a time. When the pkgver itself moves up, this can and should be reset to 1, as the pkgver itself will notify users that upgrades are available. This variable sets the architecture the package is compatible with. Regardless, makepkg still needs it to be set so it knows the package is compatible with our system. This variable supports setting multiple values, so makepkg requires a different syntax as shown below.
This lists all of the packages that our package needs to function. Like arch , it can also contain multiple values, and thus must use the parenthesis syntax.
This defines the software license that your program is licensed under. The Arch Wiki has some info if you need help choosing a license. This is how makepkg knows what files to use to build our package. This can contain a variety of different kinds of sources, including local files and URLs. If you wanted to include file. Specifies a special install script that is to be included in the package.
It does not need to be included in the source array e. Specifies a changelog file that is to be included in the package. The changelog file should end in a single newline. An array of source files required to build the package. Compressed files will be extracted automatically unless found in the noextract array described below. Additional architecture-specific sources can be added by appending an underscore and the architecture name e. There must be a corresponding integrity array with checksums, e.
It is also possible to change the name of the downloaded file, which is helpful with weird URLs and for handling multiple source files with the same name. Files in the source array with extensions. An array of PGP fingerprints. If this array is non-empty, makepkg will only accept signatures from the keys listed here and will ignore the trust values from the keyring.
If the source file was signed with a subkey, makepkg will still use the primary key for comparison. Only full fingerprints are accepted. They must be uppercase and must not contain whitespace characters.
An array of file names corresponding to those from the source array. Files listed here will not be extracted with the rest of the source files.
This is useful for packages that use compressed data directly. This array contains CRC checksums for every source file specified in the source array in the same order.
If SKIP is put in the array in place of a normal hash, the integrity check for that source file will be skipped. If desired, move the cksums line to an appropriate location. Note that checksums generated by "makepkg -g" should be verified using checksum values provided by the software developer. Alternative integrity checks that makepkg supports; these all behave similar to the cksums option described above. An array of symbolic names that represent groups of packages, allowing you to install multiple packages by requesting a single target.
For example, one could install all KDE packages by installing the kde group. Defines on which architectures the given package is available e. An array of file names, without preceding slashes, that should be backed up if the package is removed or upgraded. See "Handling Config Files" in pacman 8 for more information. An array of packages this package depends on to run. Entries in this list should be surrounded with single quotes and contain at least the package name.
If the dependency name appears to be a library ends with. Appending the version yourself disables automatic detection. Additional architecture-specific depends can be added by appending an underscore and the architecture name e.
An array of packages this package depends on to build but are not needed at runtime. Packages in this list follow the same format as depends. Additional architecture-specific makedepends can be added by appending an underscore and the architecture name e.
An array of packages this package depends on to run its test suite but are not needed at runtime. These dependencies are only considered when the check function is present and is to be run by makepkg. Additional architecture-specific checkdepends can be added by appending an underscore and the architecture name e. An array of packages and accompanying reasons that are not essential for base functionality, but may be necessary to make full use of the contents of this package. Packages in this list follow the same format as depends, with an optional description appended.
The format for specifying optdepends descriptions is:. Additional architecture-specific optdepends can be added by appending an underscore and the architecture name e.
An array of packages that will conflict with this package i. This directive follows the same format as depends. Versioned conflicts are supported using the operators as described in depends.
0コメント