Difference between revisions of "Translations:Manjaro Packaging Standards/38/en"

Latest revision as of 18:09, 7 September 2021

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (Manjaro Packaging Standards)

Remember {{ic|namcap}} can be used to check both pkg.tar.gz files and PKGBUILDs
</li>
<li> '''Dependencies'''
are the most common packaging error. Namcap can help detect them, but
it is not always correct. Verify dependencies by looking at source
documentation and the program website. </li>
<li>'''Do not use {{Ic|replaces}}''' in a PKGBUILD unless the package is to be renamed, for example when ''Ethereal'' became ''Wireshark''. If the package is an alternate version of an already existing package, use {{Ic|conflicts}} (and {{Ic|provides}} if that package is required by others). The main difference is: after syncing (-Sy) pacman immediately wants to replace an installed, 'offending' package upon encountering a package with the matching {{Ic|replaces}} anywhere in its repositories; {{Ic|conflicts}} on the other hand is only evaluated when actually installing the package, which is usually the desired behavior because it is less invasive.</li>
<li>
All files uploaded to the AUR should be contained in a '''compressed tar
file''' containing a directory with the '''{{ic|PKGBUILD}}''' and '''additional build files''' (patches, install, ...) in it.
{{bc|foo/PKGBUILD
foo/foo.install
foo/foo_bar.diff
foo/foo.rc.conf}}
The archive name should contain the name of the package
e.g. foo.tar.gz.

Remember {{ic|namcap}} can be used to check both pkg.tar.gz files and PKGBUILDs
	</li>
<li> '''Dependencies'''
are the most common packaging error. Namcap can help detect them, but
it is not always correct. Verify dependencies by looking at source
documentation and the program website. </li>
<li>'''Do not use {{Ic|replaces}}''' in a PKGBUILD unless the package is to be renamed, for example when ''Ethereal'' became ''Wireshark''. If the package is an alternate version of an already existing package, use {{Ic|conflicts}} (and {{Ic|provides}} if that package is required by others). The main difference is: after syncing (-Sy) pacman immediately wants to replace an installed, 'offending' package upon encountering a package with the matching {{Ic|replaces}} anywhere in its repositories; {{Ic|conflicts}} on the other hand is only evaluated when actually installing the package, which is usually the desired behavior because it is less invasive.</li>
	<li>
		All files uploaded to the AUR should be contained in a '''compressed tar
			file''' containing a directory with the '''{{ic|PKGBUILD}}''' and '''additional build files''' (patches, install, ...) in it.
{{bc|foo/PKGBUILD
foo/foo.install
foo/foo_bar.diff
foo/foo.rc.conf}}
		The archive name should contain the name of the package
		e.g. foo.tar.gz.

Remember namcap can be used to check both pkg.tar.gz files and PKGBUILDs

Dependencies are the most common packaging error. Namcap can help detect them, but it is not always correct. Verify dependencies by looking at source documentation and the program website.

Do not use replaces in a PKGBUILD unless the package is to be renamed, for example when Ethereal became Wireshark. If the package is an alternate version of an already existing package, use conflicts (and provides if that package is required by others). The main difference is: after syncing (-Sy) pacman immediately wants to replace an installed, 'offending' package upon encountering a package with the matching replaces anywhere in its repositories; conflicts on the other hand is only evaluated when actually installing the package, which is usually the desired behavior because it is less invasive.

All files uploaded to the AUR should be contained in a compressed tar file containing a directory with the PKGBUILD and additional build files (patches, install, ...) in it.

foo/PKGBUILD
foo/foo.install
foo/foo_bar.diff
foo/foo.rc.conf

The archive name should contain the name of the package e.g. foo.tar.gz.