defineDebugInfoPackage: change first argument to basePackageSuffix

[jmairboeck]

This allows defining multiple debuginfo packages by not hard-coding the used packageSuffix for the debuginfo package any more but deriving it from the basePackageSuffix instead.

Note: This is a breaking change! All invocations of defineDebugInfoPackage in haikuports must be changed. The default case to define the main debuginfo package is to use an empty string (i.e. "") as the first argument now. To define a debuginfo package for a subpackage, use its package suffix instead (similar to packageEntries and getPackagePrefix).

Also adds support for PACKAGE_NAME and PACKAGE_VERSION overrides, both for the referenced base package and the debuginfo package itself. In both cases, they must be declared before defineDebugInfoPackage is called.

Fixes #348.

---

Question: should the debugInfoSuffix also be changed for subpackages? (i.e. the base package name and version that is added to debug info file names)

[jmairboeck]

I changed the debugInfoSuffix as well in a separate commit. I think it makes the most sense this way.

[jmairboeck]

Another question: should this handle inherited attributes (like SUMMARY, DESCRIPTION etc.) to automatically "inherit" them from the (non-default) base package, if they have been overridden for that?

(I guess this can get pretty complex if we really want to go that far ...)

[Begasus]

Another question: should this handle inherited attributes (like SUMMARY, DESCRIPTION etc.) to automatically "inherit" them from the (non-default) base package, if they have been overridden for that?

(I guess this can get pretty complex if we really want to go that far ...)

I was fighting with this the other day, thinking about adding a SUMMARY for a doc package, haikuporter automatically adds a "documentation" suffix to the package just like it's done for the "development" suffix, so I guess it should follow that order (should check how this is done for tools packages?).

[jmairboeck]

Another question: should this handle inherited attributes (like SUMMARY, DESCRIPTION etc.) to automatically "inherit" them from the (non-default) base package, if they have been overridden for that?

(I guess this can get pretty complex if we really want to go that far ...)

I think this is easier to be handled in the recipes. Let's say: if you override these variables for the debuginfo base package, you also have to do it for the debuginfo package manually for consistency.

I'll add that to the glib recipe in the example PR.

[jmairboeck]

I now also fixed the missing line continuation in the usage error message.

[jmairboeck]

For reference: this should apply the necessary transformation for all current usages of defineDebugInfoPackage in haikuports:

git grep -Fl "defineDebugInfoPackage " | xargs sed -i -E 's/(defineDebugInfoPackage\s+)\S+/\1""/'

if/when this is applied and deployed.