I've just realised, this file is named .PKGINFO whereas all packages use PKGBUILD. PKGBUILD is the file that makepkg reads and builds the package according to it. .PKGINFO file is generated by makepkg command and it contains

pe, 2012-06-15 kello 23:14 +0100, Mateusz Loskot kirjoitti: list of files inside the package, it's size, name, version.... all that information. The .PKGINFO file is included inside the pkgname-pkgver-x86_64.pkg.tar.xz file and you should never modify it manually. .INSTALL is general name for the install file used in some packages. Basicly makepkg just copies the file specified in install= variable to the package along with the .PKGINFO file. Then about the .ChangeLog file. I am not 100% sure, but if I have not undestood everything incorrectly .ChangeLog file is the file specified in changelog= variable inside PKGBUILD and copied into the generated package by makepkg, just like .INSTALL file. This file should contain the changes made into the PKGBUILD and description on how they affect the application. ChangeLog without . in it is just the regular upstream Changelog file, that is then copyed into some dir in the package my make install or some cp/install command.

On Fri, Jun 15, 2012 at 11:14:29PM +0100, Mateusz Loskot wrote:

On 15 June 2012 21:17, Mateusz Loskot wrote:

...

Apart from the mandatory .PKGINFO file

I've just realised, this file is named .PKGINFO whereas all packages use PKGBUILD. Hmm, what am I missing here?

Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

.PKGINFO is "private API". It's generated by makepkg and lists all the metadata that will end up in pacman's DB once the package is installed. You do not need, and should not want, to try and create these manually. A minimal package might only be a PKGBUILD. The install scriptlet (which becomes .INSTALL), and the changelog (which becomes .CHANGELOG) are entirely optional files. Note that the changelog is for the package itself, and has no relation to the upstream source. Lots of details in PKGBUILD(5) and makepkg(8).

On 15 June 2012 23:32, Allan McRae wrote:

On 16/06/12 08:14, Mateusz Loskot wrote:

...

On 15 June 2012 21:17, Mateusz Loskot wrote:

...

Apart from the mandatory .PKGINFO file

I've just realised, this file is named .PKGINFO whereas all packages use PKGBUILD. Hmm, what am I missing here?

PKGBUILD is the file used by makepkg to build a package.  .PKGINFO is generated by makepkg and is used by pacman when installing the package.

Alan (and Dave too), Thanks too, I finally realised I misinterpreted the wiki article. My bad indeed.

If a file is specified in install= or changelog= they are copied into the package as .INTSALL and .CHANGELOG.   The source files for these can be named whatever the packager feels like.

It makes perfect sense to me now. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net