Difference between revisions of "Talk:Arch packaging standards"

From ArchWiki
Jump to: navigation, search
m (rem double redir)
Line 1: Line 1:
 
==Comments==
 
==Comments==
 +
This article needs to be updated to the new PKGBUILD.proto by those who have the power to do so!
 +
--[[User:Svenstaro|Svenstaro]] 05:05, 18 August 2010 (EDT)
 +
 +
----
 
In the Packaging Standard paragraph, it would be more useful in this sentence 'You should also see the PKGBUILD and makepkg manpages.' to send people to their repective wiki pages instead of the manpages. --[[User:Magikid|Magikid]] 12:26, 26 November 2009 (EST)
 
In the Packaging Standard paragraph, it would be more useful in this sentence 'You should also see the PKGBUILD and makepkg manpages.' to send people to their repective wiki pages instead of the manpages. --[[User:Magikid|Magikid]] 12:26, 26 November 2009 (EST)
  

Revision as of 09:05, 18 August 2010

Comments

This article needs to be updated to the new PKGBUILD.proto by those who have the power to do so! --Svenstaro 05:05, 18 August 2010 (EDT)


In the Packaging Standard paragraph, it would be more useful in this sentence 'You should also see the PKGBUILD and makepkg manpages.' to send people to their repective wiki pages instead of the manpages. --Magikid 12:26, 26 November 2009 (EST)

What encoding (ascii ? UTF-8 ?) should be used for text files in submitted packages ? --Airbag 13:43, 15 August 2006 (PDT)


I hope you didn't change my addition because you thought I was bullshitting the name of the document and section number I got that from, because it was quoted straight from a developer's documentation of that name, and from that section. Righto, carry on, just curious... --Neotuli 09:40, 15 Aug 2005 (EDT)


Added PKGBUILD prototype from CVS. Apparently many people don't even know there's a template hence the varying substandard pkgbuilds being submitted to the AUR. Also moved the etiquette subsection to the top since it contains more important information. tardo 22:32, 23 June 2007 (EDT)


The only section currently NOT included in the Creating Packages entry is everything below 2. Additional Guidelines. That can easily be merged in. Rcoyner 14:28, 26 Sept 2008 (EDT)

Suggestions

Shouldn't the License section be updated to reflect that the licensing system is in place and ready for users? Also, should the MIT license fall under the BSD exception? --WillySilly 14:52, 12 Apr 2006 (PST)


Arch_Packaging Standards#PKGBUILD Prototype Shouldn't the url be prepended to the package name? Does not work for me without.--Tantalum 17:17, 24 September 2009 (EDT)

Proposed revision

A couple of grammar problems/formality (and one occassion where a command shouldn't be used as root):

  • Changes in bold, subs. in strike.
  • Ignore the rest of the markup/heading changes.

Also, no abbrev. suggested (it's=it is), and less bold fonts.

Packaging Standards

The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances. Exception to this strict rule may only be packages having extra features enabled and/or patches in comparison with the official ones. In such an occasion, the pkgname array should be different to express that difference.

When building packages for the AUR, you should adhere to the package guidelines below, especially if you would like the intention is to contribute a your new package to Arch Linux.

...

PKGBUILD Prototype

Should really tell the user that prototypes are in /usr/share/pacman from the pacman and abs packages. Maybe also a newpkg (pkgtools) mention.


# Contributor: Your Name email at domain dot com> (disguise your email...

Package Etiquette

...
Do not introduce new variables into your PKGBUILD build scripts ...

The AUR cannot detect the use of custom variables and so canno ... This can most often be seen in the source array, e.g.:

...
file, or alternatively by exporting the PACKAGER environment variable before building packages with makepkg:

$ export PACKAGER="John Doe@email"

...
The above example is taken from the wine package in extra. The optdepends information will automatically be printed out on installation/upgrade. from pacman 3.2.1, so one should not keep this kind of information in .install files any longer.

...

Package Naming

...
Version tags may not include hyphens. Letters, numbers, and periods only.

...
the package will be re-released to the AL (???) public and

...

Directories

...
Use /etc/{pkgname}/ where {pkgname} is the name of the package

...

Makepkg Duties

...
When makepkg is used to build a package for you, it does the following automatically:

...

Architectures

...
depending on which architectures it can be built on. You can also use State 'any' for architecture independent packages.

...

Licenses

...
The license array is being implemented little by little in the official repos, and it should be used in AUR packages as well. You can Use it as follows:

  • If the source tarball does not contain the license details and the license is only displayed on a website for example, then you need to copy the licen...
  • Add 'custom' to the licenses array. Optionally, you can replace 'custom' with 'custom:"name of license"'.

...
When pacman gets the ability to filter on licenses (i.e., make pacman download only GPL and BSD licensed software") dual (or more) licenses will be treated by pacman using 'or', rather than 'and' logic, thus pacman will consider ...

Submitting Packages to the AUR

The submitted PKGBUILDs MUST NOT build applications already in any of the official binary repositories under any circumstances. Exception to this strict rule may only be packages having extra features enabled and/or patches in compare to the official ones. In such an occasion the pkgname array should be different to express that difference. This gets repeated word for word in #Packaging Standards

...
To ensure the security of pkgs submitted to the AUR please ensure that the md5sum values have been correctly filled. The md5sum's can b...

...
Please add a comment line to the top of the PKGBUILD file that follows this format. Remembe...

...

# Contributor: Your Name <address at domain dot com></pre>

recommend the use of the namcap package, written by Jason Chu (jason@archlinux.org), to analyze the sanity of your packages. namcap will tell you warn about bad permissions, missing dependencies, un-needed dependencies, and other common mistakes. You can install the namcap package by...

...
Don't 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.

...
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 you can then be uploaded to the AUR.

...

Additional Guidelines

Be sure to read the above guidelines first-- important points are listed on this page that will not be repeated in the following guideline pages...