Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4160 - Strengthen Arch Packaging Standards re new variables
|
DetailsThe current Packaging Standards include the following clause to address the use of new variables:
"Try to avoid introducing new variables into your PKGBUILD build scripts, as these could possibly conflict with variables used in makepkg itself. If you do find it necessary to include a new variable please prefix the variable name with an underscore" In the AUR at the moment, we have a growing number of examples of new and custom variables which are avoidable and unnecessary, but the wording above makes it difficult to present a convincing argument. I would like to suggest the following as a possible alternative: "Do not introduce new variables into your PKGBUILDs, unless the package cannot be built without doing so, as these could possibly conflict with variables used in makepkg itself. If a new variable is required, please prefix the variable name with an underscore" |
This task depends upon
Closed by Dennis Herbrich (gyroplast)
Tuesday, 14 March 2006, 19:32 GMT
Reason for closing: Fixed
Additional comments about closing: The english installation guide has been changed accordingly, and I'll take care of reviewing the whole thing once more and passing it on to the translators afterwards. See tasks 4169 and 4170.
Tuesday, 14 March 2006, 19:32 GMT
Reason for closing: Fixed
Additional comments about closing: The english installation guide has been changed accordingly, and I'll take care of reviewing the whole thing once more and passing it on to the translators afterwards. See tasks 4169 and 4170.
There are some PKGBUILDs that uses underscore to prefix local variables (for example in VMware player PKGBUILD on forum).