Difference between revisions of "VCS PKGBUILD Guidelines/ru"

VCS PKGBUILD Guidelines/ru (view source)

173 bytes added , 1 year ago

Created page with "=== Функция pkgver() === Автопереход {{ic|pkgver}} теперь осуществляется с помощью специальной функции {{ic|pk..."

translator

10,756

edits

@@ Line 35: / Line 35: @@
   source=('project_name::git+http://project_url#branch=project_branch')
-=== The pkgver() function ===
+=== Функция pkgver()  ===
-The {{ic|pkgver}} autobump is now achieved via a dedicated {{ic|pkgver()}} function. This allows for better control over the {{ic|pkgver}}, and maintainers should favor a {{ic|pkgver}} that makes sense.
+Автопереход {{ic|pkgver}} теперь осуществляется с помощью специальной функции {{ic|pkgver()}}. Это позволяет лучше контролировать {{ic|pkgver}}, и сопровождающие должны отдавать предпочтение {{ic|pkgver}}, которая имеет смысл.
 It is recommended to have following version format: ''RELEASE.rREVISION'' where ''REVISION'' is a monotonically increasing number that uniquely identifies the source tree (VCS revisions do this). The last VCS tag can be used for ''RELEASE''. If there are no public releases and no repository tags then zero could be used as a release number or you can drop ''RELEASE'' completely and use version number that looks like ''rREVISION''. If there are public releases but repo has no tags then developer should get the release version somehow e.g. by parsing the project files.