released tarball has a bad name
radosroka opened this issue · comments
Radovan Sroka commented
Please rename released tarball:
usbgard-notifier-0.0.1 -> usbguard-notifier-0.0.1
Radovan Sroka commented
Why there is such a fail?
/tmp/tmp.h52BZ4cpqs/usbgard-notifier-0.0.1 » ./configure --prefix /home/$(id -nu) rsroka@Axis
checking whether make supports nested variables... yes
....
checking for protobuf... yes
checking for qb... yes
checking for rsvg... yes
./configure: line 12444: librsvg-2.0_summary=-I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -pthread -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo : No such file or directory
....
Attila Lakatos commented
Please rename released tarball:
usbgard-notifier-0.0.1 -> usbguard-notifier-0.0.1
Nice observation, thank you.
Attila Lakatos commented
Why there is such a fail?
/tmp/tmp.h52BZ4cpqs/usbgard-notifier-0.0.1 » ./configure --prefix /home/$(id -nu) rsroka@Axis checking whether make supports nested variables... yes .... checking for protobuf... yes checking for qb... yes checking for rsvg... yes ./configure: line 12444: librsvg-2.0_summary=-I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -pthread -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo : No such file or directory ....
The above mentioned variable contains a prohibited character, specifically "-", which is unallowed in configure.ac. Thanks!