This fixes bugs FS#23259 and FS#23260.

Dan McGee authored Feb 27, 2011 and Rémy Oudompheng committed Mar 04, 2011

We regressed when splitting the package parser into two scripts; add a
variable to configure the path it is found on and add a 'namcap-devel'
script that allows running the whole deal from the current git checkout.

Signed-off-by: Dan McGee <dan@archlinux.org>

Dan McGee authored Feb 27, 2011 and Rémy Oudompheng committed Mar 04, 2011

A lot clearer and not magical.

Signed-off-by: Dan McGee <dan@archlinux.org>

Dan McGee authored Feb 27, 2011 and Rémy Oudompheng committed Mar 04, 2011

And additionally, don't swallow error output from parsepkgbuild calls-
this helped debug the next issue with a patch to come.

Signed-off-by: Dan McGee <dan@archlinux.org>

The kdeprograms and splitpkgbuild checks that certain dependencies are
correctly specified in the PKGBUILD. Sometimes these could be
actually available via a dependency chain and a naïve scan
would not notice it.

Using the getcovered function in Namcap.depends these indirect links are
spotted.

Two new rules are implemented:
- a check for the existence of all package() functions:
  the main work is actually done in parsepkgbuild
- a check for missing makedepends w.r.t. individual depends
  of children packages. For the moment no smart lookup of
  dependencies is done.

Requested by Pierre Schmitz.

Rules derived from PkgbuildRule receive the parent pkginfo
object and should treat the children is needed, whereas
PkgInfoRule's receive the children pkginfo individually.

Previously the rule list was obtained using an obscure
'-r list' option.

The PacmanPackage class old implementation used attributes
to store the values of pkginfo/pkgbuild variables. Since
this class will also be used as a storage space for namcap
rules, different access methods will be used for fields
and namcap internal variables:
- namcap-defines variables are attributes of instances
- PKGBUILD and PKGINFO fields are accessed through a container interface.

The two APIs will coexisst until the porting is complete.

The initializer of this class can also parse .PKGINFO file contents or
database entries, as output by parsepkgbuild. This gives better code
factorization for the pacman module.

The parsepkgbuild.sh script is supposed to turn PKGBUILDs into
PKGINFO-like output. For split packages the chosen syntax is the
following: a header containing SPLIT, BASE and NAMES fields is
output (they are set to 1, $pkgbase and $pkgname[@]).

Then traditional PKGINFO data is output for each sub-package,
separated by null bytes.

In order to support the parsing of split PKGBUILDs, the parsepkgbuild
script will be made more complex. For easier editing and maintenance,
it is advisable to put it in a separate file.

Desktop files with a MimeType entry should be added to the global
database by running update-desktop-database in the install
script.

Reported by Mathias Dienstbier.