All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Manoj Srivastava <srivasta@golden-gryphon.com>,
	selinux@tycho.nsa.gov, Joshua Brindle <jbrindle@tresys.com>
Subject: Re: /lib/libsemanage.so.1 links to  /usr/lib/libustr-1.0.so.1
Date: Mon, 19 Oct 2009 11:35:09 -0400	[thread overview]
Message-ID: <4ADC872D.5050205@redhat.com> (raw)
In-Reply-To: <1255965103.3099.51.camel@moss-pluto.epoch.ncsc.mil>

On 10/19/2009 11:11 AM, Stephen Smalley wrote:
> On Mon, 2009-10-19 at 11:07 -0400, Daniel J Walsh wrote:
>> 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?
> 
> It's moving the other direction (presently in /lib, moving to /usr/lib).
> Manoj pointed out that because of the ustr dependency, it no longer
> makes sense to keep libsemanage in /lib, because libustr lives
> in /usr/lib.
> 
Oh, I misread. I think  like a symbolic link should handle this

Although the only entry I see for this is 

 ls -l /lib | grep '\.\.'
lrwxrwxrwx.  1 root root      14 2009-10-11 07:36 cpp -> ../usr/bin/cpp




--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2009-10-19 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13  7:20 /lib/libsemanage.so.1 links to /usr/lib/libustr-1.0.so.1 Manoj Srivastava
2009-10-13 14:07 ` Joshua Brindle
2009-10-14  5:49   ` Manoj Srivastava
2009-10-19 14:20     ` Stephen Smalley
2009-10-19 15:07       ` Daniel J Walsh
2009-10-19 15:11         ` Stephen Smalley
2009-10-19 15:35           ` Daniel J Walsh [this message]
2009-10-19 19:10             ` Joshua Brindle
2009-10-21 14:03       ` Manoj Srivastava
2009-10-21 14:29         ` Stephen Smalley
2009-11-27 18:03   ` Joshua Brindle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ADC872D.5050205@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=srivasta@golden-gryphon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.