On 10/19/2009 10:20 AM, Stephen Smalley wrote:
> On Wed, 2009-10-14 at 00:49 -0500, Manoj Srivastava wrote:
>> On Tue, Oct 13 2009, Joshua Brindle wrote:
>>
>>
>>> Yes, I'm not sure why you'd need libsemanage during early boot, we
>>> probably should apply this:
>>>
>>> diff --git a/libsemanage/src/Makefile b/libsemanage/src/Makefile
>>> index cfb9558..c531a2f 100644
>>> --- a/libsemanage/src/Makefile
>>> +++ b/libsemanage/src/Makefile
>>> @@ -1,7 +1,7 @@
>>> # Installation directories.
>>> PREFIX ?= $(DESTDIR)/usr
>>> LIBDIR ?= $(PREFIX)/lib
>>> -SHLIBDIR ?= $(DESTDIR)/lib
>>> +SHLIBDIR ?= $(PREFIX)/lib
>>> INCLUDEDIR ?= $(PREFIX)/include
>>> PYLIBVER ?= $(shell python -c 'import sys;print "python%d.%d" %
>>> sys.version_info[0:2]')
>>> PYINC ?= /usr/include/${PYLIBVER}
>>>
>>
>> I've applied this patch in Debian unstable.
>
> My only concern with relocating libsemanage is whether it will create
> any compatibility problems for existing binaries previously linked
> against /lib/libsemanage.so.1. Also it could get confusing if you build
> and install the newer version and existing binaries keep using the old
> library at the old location. You likely need/want to
> symlink /lib/libsemanage.so.1 to the new location.
>
Why does it need to be moved? Are you doing semanage functions during boot up?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
