This way a proper separation between Python installs can be achieved. With no PYTHON_SITEDIR, installation paths are exactly the same as before this change. In practise, passing nonstandard path will break Entropy but so it is also with the currently available LIBDIR. This is a concern of a future improvement (at least the PYTHON_SITEDIR path, not necessarily LIBDIR as PYTHON_SITEDIR *will* be different if it's installed in Python specific directories).
40 lines
963 B
Makefile
40 lines
963 B
Makefile
SUBDIRS =
|
|
PREFIX = /usr
|
|
LIBDIR = $(PREFIX)/lib
|
|
PYTHON_SITEDIR = $(LIBDIR)
|
|
SBINDIR = $(PREFIX)/sbin
|
|
DESTDIR =
|
|
MATTER_PYDIR = $(DESTDIR)$(PYTHON_SITEDIR)/matter
|
|
|
|
all:
|
|
for d in $(SUBDIRS); do $(MAKE) -C $$d; done
|
|
|
|
install:
|
|
mkdir -p $(MATTER_PYDIR)/matter
|
|
mkdir -p $(MATTER_PYDIR)/matter/binpms
|
|
mkdir -p $(DESTDIR)$(SBINDIR)
|
|
|
|
install -m 644 matter/*.py $(MATTER_PYDIR)/matter/
|
|
install -m 644 matter/binpms/__init__.py \
|
|
$(MATTER_PYDIR)/matter/binpms/
|
|
|
|
install -m 755 matter_app.py $(DESTDIR)$(SBINDIR)/matter
|
|
install -m 755 antimatter.py $(DESTDIR)$(SBINDIR)/antimatter
|
|
|
|
for d in $(SUBDIRS); do $(MAKE) -C $$d install; done
|
|
|
|
base-install:
|
|
mkdir -p $(MATTER_PYDIR)/matter/binpms
|
|
|
|
install -m 644 matter/binpms/base.py \
|
|
$(MATTER_PYDIR)/matter/binpms/
|
|
|
|
entropysrv-install:
|
|
mkdir -p $(MATTER_PYDIR)/matter/binpms
|
|
|
|
install -m 644 matter/binpms/entropysrv.py \
|
|
$(MATTER_PYDIR)/matter/binpms/
|
|
|
|
clean:
|
|
for d in $(SUBDIRS); do $(MAKE) -C $$d clean; done
|