Attempt to split into multiple packages

[hobu]

For the upcoming PDAL 2.6.0, we have added the ability to conveniently build -DSTANDALONE=ON plugins that have external library dependencies. This should allow us to split the conda package into something like this:

• libpdal (base library and command line utilities, same as libgdal)
• pdal-trajectory
• pdal-tiledb
• pdal-draco
• pdal-hdf
• pdal-nitf
• pdal-pgpointcloud
• pdal <-- installs python-pdal stuff and everything else :point_up:

It's not quite working and of course points to the unreleased PDAL 2.6.0 branch but I want to make sure it can work before releasing 2.6.0.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[hobu]

@ocefpaf For the not-yet-released PDAL 2.6.0, we am planning on splitting pdal package into a number of subpackages including libpdal. This is to reduce our sensitivity to various plugins requiring rerendering and to cut out some conflicts that seem to be arising on windows.

What considerations should we take before we merge this PR (after PDAL 2.6.0 is released, of course)?

[ocefpaf]

Multiple outputs can be complex but at a first glance everything looks good here. I'm not the best person to say b/c we need to know how the downstream packages and users are using pdal. for example, someone that expects to just conda install pdal seems to be covered. The ones that may want pdal-* will need docs/warnings.

The most complex one are packaging that are building using pdal but from now on would be OK with libpdal only. Those will require a pin to ensure they'll get the right combo of pdal/libpdal. (Image building with one version of libpdal but, if we forget to pin things correctly, install it with an older pdal.)

[hobu]

A couple more points to add.

• Unlike GDAL, what is currently python-pdal is released on a different schedule than the base libpdal library
• For PDAL 2.6.0 we will implement the package splitting in this PR
• We will wait for the next PDAL Python release to rename the python-pdal conda forge package to pdal
• How should we update pins to protect this from falling apart 😄 ?

[ocefpaf]

• How should we update pins to protect this from falling apart 😄 ?

Let's say that from now on you only want folks building against pdal 2.6.0, unless they explicitly require an older version, you should mimic gdal/libgdal pins in: https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml

PS: Hey @isuruf I know you are super busy lately with the Windows arm stuff but if you find some spare time do you mind taking a look at this PR?

[isuruf]

Add

conda_build:
  error_overlinking: true

to conda-forge.yml and this build would error. You should fix the dependencies so that the build passes again.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• pin_compatible should be used instead of pin_subpackage for pdal because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-split'].

For recipe:

• The arrow-cpp output has been superseded by libarrow.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe:

• The arrow-cpp output has been superseded by libarrow.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.