cc19266600
The way kiwi uses setup.py assumes that pip runs this script like a spec file in rpm is processed. However this is not the case given that pip implicitly creates a static zip file called wheel which looses all the code logic done in setup.py. Therefore setup.py should not contain code that needs to run at install time. Of course this change comes with an effect which is that the following files will not be available when installing kiwi from pip: * man pages: /usr/share/man/man8/... * command completion: /etc/bash_completion.d/kiwi-ng.sh * kiwi default config file: /etc/kiwi.yml * package docs: /usr/share/doc/packages/kiwi-ng/... (kiwi.pdf, LICENSE, README) kiwi stays fully functional without this information. It is expected that the installation of kiwi as a service will be done by a package and its package manager. When using kiwi from pip it is designed to provide a python module but not a complete user application. The way pip and wheels interact with each other seems to demonstrate that pip is not a package manager but more a python module manager. This Fixes #1415
19 lines
249 B
Makefile
19 lines
249 B
Makefile
buildroot = /
|
|
|
|
SRCS := $(wildcard *.c)
|
|
PRGS := $(patsubst %.c,%,$(SRCS))
|
|
|
|
CC = gcc
|
|
|
|
all: $(PRGS)
|
|
|
|
%.o: %.c
|
|
$(CC) $(CFLAGS) $< -o $@
|
|
|
|
clean:
|
|
$(RM) $(PRGS)
|
|
|
|
install:
|
|
install -d -m 755 ${buildroot}usr/bin
|
|
install -m 755 $(PRGS) ${buildroot}usr/bin
|