Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Dec 2005 16:36:44 -0800
From:      Doug Barton <dougb@FreeBSD.org>
To:        Florent Thoumie <flz@xbsd.org>
Cc:        freebsd-rc@freebsd.org
Subject:   Re: rc.d/ldconfig change
Message-ID:  <43B32F9C.9080809@FreeBSD.org>
In-Reply-To: <200512280310.25988.flz@xbsd.org>
References:  <1134927080.744.14.camel@cream.xbsd.org> <43B1F218.2080408@FreeBSD.org> <200512280310.25988.flz@xbsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Florent Thoumie wrote:

> I don't much care about where it's stored, I figured out that etc/ was a
> good candidate because /etc/ had already ld.so.conf but libdata is fine
> with me.

Ok, let's go with that unless someone else has a better idea.

> Note that I modified BSD.local.dist in latest version of the patch.

I did after I finished reading the thread. :) Good catch.

>>> Here's what I was thinking about (see attached patch).
>>> 
>>> This way, I can imagine a USE_LDCONFIG variable containing 
>>> directories and bsd.port.mk would just :
>>> 
>>> .if defined(USE_LDCONFIG) echo ${USE_LDCONFIG} >
>>> ${PREFIX}/etc/ld.so.conf.d/${UNIQUENAME} .endif
>> I would use touch here, but I won't quibble.
> 
> Not sure how you could do the same thing with only touch.

Ok, I think I'm confused about one part of the patch or another then. It 
seems from your rc.d/ldconfig patch that all you are looking at are the 
names of the files in the ldconfig_local_d directories, but it occurs to me 
now that just the names won't really help, you actually need to store the 
paths to feed to ldconfig somewhere, which I presume is what you were going 
to include in the USE_LDCONFIG variable. Am I right so far? If so, then I 
don't understand how your patch to rc.d/ldconfig is going to work, but I may 
be missing something. :)


Doug

-- 

     This .signature sanitized for your protection




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B32F9C.9080809>