Import statements sorted with isort and fixed MockBuilder.py (#266)

* Fixed missing closing bracket in the MockBuilder.py

* Import statements sorted with isort

[CLEANUP] Remove unused import statements (#264)

python3: Finish python3 change. python2 breaking

* Based on mmlr's 2017 work to use Python3 with
changes and adjustments for the current codebase

Introduce TEST_REQUIRES for test-only requires.

This lets recipes specify dependencies that are only needed for the test
phase. Separating them out from BUILD_[PRE]REQUIRES allows for
situations that could otherwise result in cyclic dependencies.

Note that this bumps the repository format version, causing a repository
rebuild (re-parsing of all recipes, flushing of all caches). This is
required because the dependency info files and various caches need to be
regenerated to cope with the added test requires keys.

Fixes #151.

read VENDOR from settings file (issue #61)

Rename SRC_FILENAME to SOURCE_FILENAME for consistency's sake.

Rename SRC_URI to SOURCE_URI for consistency's sake.

Allow specifying VENDOR in a recipe.

This will allow using HaikuPorter to build recipes with
repositories not maintained by the Haiku Project.

Cleanup imports.

Fix propagation of some recipe attritbutes.

* BUILD_REQUIRES and BUILD_PREREQUIRES must be inherited from the main
package to all sub packages, as these apply to all of them.

Revert to tab spacing for Pe's sake.

Try again with whitespace.

Second attempt to fix whitespace. Options are different on OS X.

Convert tabs to spaces.

Implement support for freestanding package names in recipes.

* Package names used to be linked to port names (they could only extend
it). Now, independent package names and versions can be set by means of
PACKAGE_NAME and PACKAGE_VERSION recipe attributes.

Introduce explicit recipe format version.

* Added support for reading the recipe format version used by a ports
tree from the file 'FormatVersions'.
* Added check that ensures that the recipe format version of a given
ports tree matches the one supported by haikuporter.

Reduce supported checksums to SHA-256 only.

Remove dead code

Add more cryptographic hashes to check

* File size, MD5, RIPEMD-160, SHA-1, SHA-256 and SHA-512 are now
supported
* A warning about every missing hash is emitted
* Only present hashes are checked
* Creating a modified tarball which still creates the same hash for all
those hashes should be impossible
* That means if the haikuports checkout is trusted, you can also trust all
tarballs which it downloads
* The bc recipe has been updated as an example

Support putting additional files into source package.

* add new recipe variable ADDITIONAL_FILES, which is a list of files
and directories underneath the 'additional-files' folder that should
be copied into the source package
* implement copying of additional files into source package

Better protect against easy mistakes in recipes:

* explicitly check for dashes in names of provides and requires
declarations and complain if one is found

Support building secondary arch packages from regular recipes

* Add settings SECONDARY_CROSS_DEVEL_PACKAGES, SECONDARY_CROSS_TOOLS,
and SECONDARY_TARGET_ARCHITECTURES to config file and command line
option --secondary-cross-devel-packages, overriding the first.
SECONDARY_TARGET_ARCHITECTURES is the list of secondary target
architectures that ports may be built for (for a hybrid target).
SECONDARY_CROSS_TOOLS is the respectively matching list of cross
tools directories and SECONDARY_CROSS_DEVEL_PACKAGES the list of
Haiku cross development sysroot packages.
* Repository: For all configured secondary architectures add derived
ports.
* BuildPlatformUnix:
- setupNonChrootBuildEnvironment()/cleanNonChrootBuildEnvironment() do
now support an optional secondaryArchitecture parameter which is set
when building a port for a secondary architecture. The build
environment is set up using the respective cross tools and Haiku
cross devel package.
- Fix setting up the system include and library search paths for
gcc 4. It has other paths built in.
* Recipes can now set a SECONDARY_ARCHITECTURES (similar to
ARCHITECTURES) to indicate for which secondary architectures the port
can be built.
* Add new shell variables effectiveTargetArchitecture,
effectiveTargetMachineTriple, and effectiveTargetMachineTripleAsName
which are set to the values for the target architecture we are
actually building for (i.e. the primary or secondary architecture).
When cross-compiling the pre-existing target* variables continue to
correspond to the primary architecture.
* The variables binDir, sbinDir, libDir, includeDir, oldIncludeDir,
developLibDir are set to a respective subdirectory when building for
a secondary architecture.

Add support for meta-ports, specifically 'meta_portsfile'

* a meta-port is a port that just builds other (non-meta) ports, but it
doesn't provide any sources or build actions of its own
* when building a list of ports specified via --portsfile, the meta-
port 'meta_portsfile' is now being used to group all the required
ports (pulling in any runtime requirements, too)
* when building only source packages, consider all packages stable, as
otherwise sources for not-yet-stable packages could not be collected
(one would have to mark them as stable manually)
* add more missing implicit build provides to Unix build platform

Clean up trailing whitespace

PackageType.DEBUG -> DEBUG_INFO

"debuginfo" seems more appropriate, since the package contains the
debug info files, not a debug version of the respective software (e.g.
library).

Get rid of the SOURCE_EXPORT_SUBDIR recipe attribute

Instead just allow SOURCE_DIR to be an arbitrary relative path. That
already seemed to work in some cases, but not for all.
Due to the directory folding the semantics is a bit weird (well it
already was before).

Add missing POST_INSTALL_SCRIPTS recipe attribute

Add license header (MIT)

* additionally: uppercase copyright notices and separate them from the
top by a single line

RecipeAttributes: make 'extendable' tri-state

There are now two states for attributes that are extendable, which
specify what to do when the attribute has not been set for a package:
INHERITED to inherit the main package attribute's value and DEFAULT to
set the default value.

Add support for exporting only a subdirectory from the source

* added new recipe attribute SOURCE_EXPORT_SUBDIR which can be set to
a subdir within the source directory that shall be exported

Change HOMEPAGE attribute type to list

Build a source package by default.

* building of the source package can be avoided by setting
DISABLE_SOURCE_PACKAGE=yes in the recipe

Drop recipe attribute NAME_EXTENSION, as it doesn't make sense.

Minor cleanup: fix sorting of recipe attributes.

Follow renaming of global-settings-files attribute

Add recipe attributes for the new package attributes

Implement support for more than one source per port.

* pull new class Source out of Port, which encapsulates download,
checksum-validation, checkout, unpacking and patching of a source
* adjust (and simplify) handling of source

Evaluate PATCHES variable set in recipes

Allows recipes to explicitly specify the patches to apply.

If a patch file with the name of the port exists, PATCHES is set to
that by default. This feature should rather be removed eventually, so
that all patches have to be specified explicitly. I was just too lazy
to adjust all concerned recipes.

* pulled 'Package' out of 'Port' and adjusted everything to support creating multiple
packages from a single recipe file
Not many new features have been implemented yet, but building packages seems to work again.

Refactoring: rip haikuporter apart into separate modules

Allow specifying VENDOR in a recipe.

This will allow using HaikuPorter to build recipes with
repositories not maintained by the Haiku Project.

Cleanup imports.

Fix propagation of some recipe attritbutes.

* BUILD_REQUIRES and BUILD_PREREQUIRES must be inherited from the main
package to all sub packages, as these apply to all of them.

Revert to tab spacing for Pe's sake.

Try again with whitespace.

Second attempt to fix whitespace. Options are different on OS X.

Convert tabs to spaces.

Implement support for freestanding package names in recipes.

* Package names used to be linked to port names (they could only extend
it). Now, independent package names and versions can be set by means of
PACKAGE_NAME and PACKAGE_VERSION recipe attributes.

Introduce explicit recipe format version.

* Added support for reading the recipe format version used by a ports
tree from the file 'FormatVersions'.
* Added check that ensures that the recipe format version of a given
ports tree matches the one supported by haikuporter.

Reduce supported checksums to SHA-256 only.

Remove dead code

Add more cryptographic hashes to check

* File size, MD5, RIPEMD-160, SHA-1, SHA-256 and SHA-512 are now
supported
* A warning about every missing hash is emitted
* Only present hashes are checked
* Creating a modified tarball which still creates the same hash for all
those hashes should be impossible
* That means if the haikuports checkout is trusted, you can also trust all
tarballs which it downloads
* The bc recipe has been updated as an example

Support putting additional files into source package.

* add new recipe variable ADDITIONAL_FILES, which is a list of files
and directories underneath the 'additional-files' folder that should
be copied into the source package
* implement copying of additional files into source package

Better protect against easy mistakes in recipes:

* explicitly check for dashes in names of provides and requires
declarations and complain if one is found

Support building secondary arch packages from regular recipes

* Add settings SECONDARY_CROSS_DEVEL_PACKAGES, SECONDARY_CROSS_TOOLS,
and SECONDARY_TARGET_ARCHITECTURES to config file and command line
option --secondary-cross-devel-packages, overriding the first.
SECONDARY_TARGET_ARCHITECTURES is the list of secondary target
architectures that ports may be built for (for a hybrid target).
SECONDARY_CROSS_TOOLS is the respectively matching list of cross
tools directories and SECONDARY_CROSS_DEVEL_PACKAGES the list of
Haiku cross development sysroot packages.
* Repository: For all configured secondary architectures add derived
ports.
* BuildPlatformUnix:
- setupNonChrootBuildEnvironment()/cleanNonChrootBuildEnvironment() do
now support an optional secondaryArchitecture parameter which is set
when building a port for a secondary architecture. The build
environment is set up using the respective cross tools and Haiku
cross devel package.
- Fix setting up the system include and library search paths for
gcc 4. It has other paths built in.
* Recipes can now set a SECONDARY_ARCHITECTURES (similar to
ARCHITECTURES) to indicate for which secondary architectures the port
can be built.
* Add new shell variables effectiveTargetArchitecture,
effectiveTargetMachineTriple, and effectiveTargetMachineTripleAsName
which are set to the values for the target architecture we are
actually building for (i.e. the primary or secondary architecture).
When cross-compiling the pre-existing target* variables continue to
correspond to the primary architecture.
* The variables binDir, sbinDir, libDir, includeDir, oldIncludeDir,
developLibDir are set to a respective subdirectory when building for
a secondary architecture.

Add support for meta-ports, specifically 'meta_portsfile'

* a meta-port is a port that just builds other (non-meta) ports, but it
doesn't provide any sources or build actions of its own
* when building a list of ports specified via --portsfile, the meta-
port 'meta_portsfile' is now being used to group all the required
ports (pulling in any runtime requirements, too)
* when building only source packages, consider all packages stable, as
otherwise sources for not-yet-stable packages could not be collected
(one would have to mark them as stable manually)
* add more missing implicit build provides to Unix build platform

Clean up trailing whitespace

PackageType.DEBUG -> DEBUG_INFO

"debuginfo" seems more appropriate, since the package contains the
debug info files, not a debug version of the respective software (e.g.
library).

Get rid of the SOURCE_EXPORT_SUBDIR recipe attribute

Instead just allow SOURCE_DIR to be an arbitrary relative path. That
already seemed to work in some cases, but not for all.
Due to the directory folding the semantics is a bit weird (well it
already was before).

Add missing POST_INSTALL_SCRIPTS recipe attribute

Add license header (MIT)

* additionally: uppercase copyright notices and separate them from the
top by a single line

RecipeAttributes: make 'extendable' tri-state

There are now two states for attributes that are extendable, which
specify what to do when the attribute has not been set for a package:
INHERITED to inherit the main package attribute's value and DEFAULT to
set the default value.

Add support for exporting only a subdirectory from the source

* added new recipe attribute SOURCE_EXPORT_SUBDIR which can be set to
a subdir within the source directory that shall be exported

Change HOMEPAGE attribute type to list

Build a source package by default.

* building of the source package can be avoided by setting
DISABLE_SOURCE_PACKAGE=yes in the recipe

Drop recipe attribute NAME_EXTENSION, as it doesn't make sense.

Minor cleanup: fix sorting of recipe attributes.

Follow renaming of global-settings-files attribute

Add recipe attributes for the new package attributes

Implement support for more than one source per port.

* pull new class Source out of Port, which encapsulates download,
checksum-validation, checkout, unpacking and patching of a source
* adjust (and simplify) handling of source

Evaluate PATCHES variable set in recipes

Allows recipes to explicitly specify the patches to apply.

If a patch file with the name of the port exists, PATCHES is set to
that by default. This feature should rather be removed eventually, so
that all patches have to be specified explicitly. I was just too lazy
to adjust all concerned recipes.

* pulled 'Package' out of 'Port' and adjusted everything to support creating multiple
packages from a single recipe file
Not many new features have been implemented yet, but building packages seems to work again.

Refactoring: rip haikuporter apart into separate modules