On 03/10/16 15:35, Stephen Smalley wrote: > On 10/02/2016 12:15 AM, Jason Zaman wrote: >> instead of building the path manually which is more error prone > > Thanks, applied both. I guess the only question I have is whether a) > this same change ought to be applied to all other Makefiles (e.g. > libsemanage, policycoreutils), and b) could this break any existing > build recipes that relied on setting PYLIBDIR. Doesn't appear that > Fedora spec files do so, but not sure about other distribution packages. For the second question, ArchLinux packages will not break. I quickly looked at the Debian packages and it appears libselinux is using PYLIBDIR [1] but not libsemanage [2]. Also the Debian packages appear to install the Python module into /usr/lib/python.../dist-packages instead of the site-packages directory. I am wondering whether this may be important. Nicolas [1] https://anonscm.debian.org/cgit/selinux/libselinux.git/tree/debian/python.mk [2] https://anonscm.debian.org/cgit/selinux/libsemanage.git/ [3] https://packages.debian.org/sid/amd64/python3-selinux/filelist [4] https://packages.debian.org/sid/amd64/python3-semanage/filelist _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
