Talk:Arch package guidelines

From ArchWiki
Revision as of 21:00, 25 May 2015 by Jristz (talk | contribs) (/selinux: new section)
Jump to: navigation, search

.install files

Something more should be said about .install files. Mention that there are also examples in /usr/share/pacman but it also needs some explanation on how they work. --Mauro2 (talk) 05:30, 15 October 2012 (UTC)

Fields order

Arch_Packaging_Standards#Package_etiquette states: "It is common practice to preserve the order of the PKGBUILD fields as shown above." But this is not true. Common practice is to use /usr/share/pacman/PKGBUILD.proto as a template, and the order of fields in that prototype has a far greater influence on packages in the wild than this page. This page should edited to reflect the current state of PKGBUILD.proto. Perhaps this page should state: "It is common practice to order PKGBUILD fields so they match the order of fields in PKGBUILD.proto. Ichimonji10 (talk) 14:32, 19 October 2013 (UTC)

Punctuation in PKGBUILD

What is the official guidance regarding ending a pkgdesc in a period or using commas and English prose punctuation in general?

[Link] to discussion thread.

Graysky (talk) 15:17, 14 June 2013 (UTC)

Package naming

  • Package names should consist of alphanumeric characters only; all letters should be lowercase.
--unsigned
This is a guideline, but I see some packages with hypens and underscores (tesseract-data-chi_sim), dots (gstreamer0.10), plus (libxml++) and even at-signs (kde-l10n-ca@valencia). A package with uppercase name is libreoffice-bn-IN. According to the makepkg source, the allowed chars are: [:alnum:]+_.@-. Lekensteyn (talk) 22:38, 1 February 2014 (UTC)
"alphanumeric characters only" rule is ridiculous, 85% of official packages break this rule. I think it should be changed to allow hypens. It makes package names more readable. In regards to other characters, the + sign breaks AUR search (example, should be escaped). axper (talk) 11:19, 11 May 2014 (UTC)
  • Package names should NOT be suffixed with the upstream major release version number (e.g. we don't want libfoo2 if upstream calls it libfoo v2.3.4) in case the library and its dependencies are expected to be able to keep using the most recent library version with each respective upstream release. However, for some software or dependencies, this can not be assumed. In the past this has been especially true for widget toolkits such as GTK and Qt. Software that depends on such toolkits can usually not be trivially ported to a new major version. As such, in cases where software can not trivially keep rolling alongside its dependencies, package names should carry the major version suffix (e.g. gtk2, gtk3, qt4, qt5). For cases where most dependencies can keep rolling along the newest release but some can't (for instance closed source that needs libpng12 or similar), a deprecated version of that package might be called libfoo1 while the current version is just libfoo.
--unsigned
  • Package versions should be the same as the version released by the author. Versions can include letters if need be (eg, nmap's version is 2.54BETA32). Version tags may not include hyphens! Letters, numbers, and periods only.
--unsigned
This rule needs to get more stricter. Having a slash in the version breaks filenames. For craziness, I tried setting up a pkgver containing all characters from 0x01 to 0xff which makes makepkg throw a Bash syntax error. The current packages have versions matching {{ic}[[alnum:]._+~]+} (and a colon for epoch, a hypen for pkgrel). What about limiting to those characters? Debian has a similar set, see their policy docs Lekensteyn (talk) 22:38, 1 February 2014 (UTC)
  • Package releases are specific to Arch Linux packages. These allow users to differentiate between newer and older package builds. When a new package version is first released, the release count starts at 1. Then as fixes and optimizations are made, the package will be re-released to the Arch Linux public and the release number will increment. When a new version comes out, the release count resets to 1. Package release tags follow the same naming restrictions as version tags.
--unsigned

Is it acceptable for build() to start by removing directories?

I just downloaded a PKGBUILD whose build() function begins with the following:

find ./ -maxdepth 1 -mindepth 1 -type d  -exec rm -r {} \;

It seems to me that a PKGBUILD has no business doing this and that it is potentially dangerous. I admit that its danger will typically require people to do non-standard things and, arguably, things they would be better advised not to do anyway. But it still seems to me to invite trouble.

I don't remember seeing this in a PKGBUILD before but I can't find anything definitely ruling it out.

Is it acceptable for a build function to start by removing directories in this way? Is it safe?

--cfr (talk) 03:03, 27 February 2014 (UTC)

I'd argue that this is an acceptable thing to do, at least in some cases. As an example, consider Talend Open Studio DI: a single source file provides files for Windows, Linux, Mac OS, PowerPC (?) and Solaris. In response, the talend-open-studio-diAUR PKGBUILD simply removes them. Does removing those files invite trouble? Yes. But removing files seems like an integral tool in the package maintainer's toolkit, and plenty of other weird stuff happens in PKGBUILDs too. Ichimonji10 (talk) 02:20, 3 March 2014 (UTC)

Update "Submitting packages to the AUR" section

The line

> One can easily build a tarball containing all the required files by using makepkg --source. This makes a tarball named $pkgname-$pkgver-$pkgrel.src.tar.gz, which can then be uploaded to the AUR.

in the "Submitting packages to the AUR" section on this page should be updated to refer to mkaurball, which is now apparently required to build valid AUR source packages automatically.

(Sorry, I am new to the ABS, so I won't change this page myself. I would probably miss something.)

--Drawm (talk) 14:57, 27 August 2014 (UTC)

I would argue that the section should not even be here - there is already Arch User Repository#Submitting packages, and "submitting packages to AUR" has little to do with the official packaging standards. -- Lahwaacz (talk) 15:14, 27 August 2014 (UTC)
You would argue correctly, although I haven't checked if there's something worth being merged. -- Kynikos (talk) 03:39, 28 August 2014 (UTC)
I agree that this section needs to be edited or deleted, and I was going to do it myself, but don't see any "edit" buttons anywhere on the main page. Maybe this section should just provide the link to the correct information in Arch User Repository#Submitting packages. Whoever can edit this, it needs to be done because it gives incorrect information, which I and others have tried to follow only to be told by the AUR that it won't work. Colinkeenan (talk) 23:25, 28 September 2014 (UTC)
You're right, I've just fixed it. However the two sections should really be merged, maybe keep the AUR rules here and the instructions in the AUR article? -- Kynikos (talk) 01:46, 29 September 2014 (UTC)

Custom variables are now substituted

[[1]] says: "The AUR cannot detect the use of custom variables and so cannot use them in substitutions." This is no longer true, as the PKGBUILD is parsed by bash on the client in order to generate an .AURINFO file. Someone with edit privileges can safely remove this paragraph. -- Marcel-

/selinux

Someone with privileges could edit the page and point that selinux itself and they needed packages could install in /selinux as an exception in the directory section.

AUR4

Someone with editing power could add info on what is need to upload packages to aur4.archlinux.org and aur 4.0.0 since the proposal is switch to aur 4.0 for july I don't want a over crowded of overreacted users screamming horrorified asking about that they can't find info on how upload packages to aur 4.0. and deleted accounts and packages.