On 07/04/2018 09:30 AM, Xi Ruoyao wrote:
On 2018-07-04 05:49 -0500, DJ Lucas wrote:
On July 3, 2018 10:21:43 PM CDT, Bruce Dubbs <[email protected]> wrote:
I'm checking out meson-0.47.0 for lfs and the instructions in the bool
work nicely with the exception of the last two:
mv -v
/usr/lib/python3.6/site-packages/meson-0.47.0-py3.6.egg/share/man/man1/*.1
\
/usr/share/man/man1
rm -r /usr/lib/python3.6/site-packages/meson-0.47.0-py3.6.egg/share
Actually the mv command is OK, but there is more in the share
directory:
/usr/lib/python3.6/site-packages/meson-0.47.0-py3.6.egg/share/polkit-1/actions/com.mesonbuild.install.policy
What that appears to be for is installing packages via meson (we use
ninja, but I don't know if meson inserts things into the build files).
We do not install polkit in LFS, so I don't know what to do with this
file now or later in BLFS when we do install polkit.
I have three options that I can see:
1. Throw away the .policy file and leave the meson instructions as
they
are.
2. Just delete the man portion: rm ...egg/share/man
3. Create /usr/share/polkit-1/actions/ and move the .policy file
there.
Opinions?
Option 3.
Unfortunately the polkit action policy doesn't work with our configuration.
Meson seems "designed" to be installed with:
python3 setup.py install --root=dest
cp -rv dest/* /
I suggest to do this. If we still use "python3 setup.py install", the
polkit action file is useless (at least for now).
It would be interesting to see the differences between what you suggest
and what we have now.
And, "meson install" with polkit authentication is completely broken now.
I'll submit a PR tomorrow to fix it.
Nowhere in lfs or blfs do we do 'meson install'. We use it as a
substitute for configure and then use ninja instead of make.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
