pystac upstream split

[Antonio Valentino]

Dear Bas,
I'm working on the update of pystac.
With w 1.15.x the package has been split into:
* pystac-core
* pytest-pytsac
* 22 extensions (each with a single python module)

Everything is in a single repository and we currently get the the source 
tarball directly from github.

The original idea was (the one currently implemented in salsa and still 
not fully working) was to generate multiple python packages from a 
single source but I realized that pystac(-core) and the extensions are 
versioned (and also released) independently.

This is an issue for the current implementation because all the debian 
packages now have the same version.
Do you know if it is possible to control the version of the individual 
packages generated form the same source tarball?

In any case the single source approach would have limitations because I 
would not be able to update the extensions independently.

Unless you have a different advice, I think that the cleanest solution 
would be to have 25 independent packages and to get the source tarballs 
from PyPI.

If you agree with the approach I would kindly ask you to create new 
salsa repositories for

pystac-core

pystac-ext-classification
pystac-ext-datacube
pystac-ext-eo
pystac-ext-file
pystac-ext-grid
pystac-ext-item_assets
pystac-ext-label
pystac-ext-mgrs
pystac-ext-mlm
pystac-ext-pointcloud
pystac-ext-projection
pystac-ext-raster
pystac-ext-render
pystac-ext-sar
pystac-ext-sat
pystac-ext-scientific
pystac-ext-storage
pystac-ext-table
pystac-ext-timestamps
pystac-ext-version
pystac-ext-view
pystac-ext-xarray_assets

pytest-pystac


Of course I will need again your help for the review of the new packages 
and the first upload.


kind regards
-- 
Antonio Valentino