On Mon, Apr 19, 2021 at 4:14 PM Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> > The only reason the file is there is that it gets built inside the
> > source directory, which gets copied entirely to location-python package
> > as-is. Considering the situation, this commit ensures the .la files is
> > not packaged by deleting it from the package files subdirectory.
> >
> > location-importer package pulls in two Python (.py) files from the
> > source directory. These files should not be included in the
> > location-python package as a result.
>
> And how do they go there when they are just being deleted here?

dh_install copies files to separate subdirectories, from which
packages are constructed.

d/location-python.install specifies:
usr/lib/python3*/site-packages

d/location-importer.install specifies:
usr/lib/python3*/site-packages/location/database.py
usr/lib/python3*/site-packages/location/importer.py

As a result, those two particular .py files end up in both the
location-python and location-importer package subtrees. After
dh_install, before the next stage of packaging, we can get rid of the
two files from the location-python directory.

--Valters