Received: from [68.230.241.43] (helo=fed1rmmtao103.cox.net) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1LNXrq-0004ZD-Kk for openembedded-devel@openembedded.org; Thu, 15 Jan 2009 20:27:03 +0100 Received: from fed1rmimpo03.cox.net ([70.169.32.75]) by fed1rmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090115192019.NREL12838.fed1rmmtao103.cox.net@fed1rmimpo03.cox.net> for ; Thu, 15 Jan 2009 14:20:19 -0500 Received: from localhost ([68.230.61.57]) by fed1rmimpo03.cox.net with bizsmtp id 3vLH1b00B1E665w04vLH9H; Thu, 15 Jan 2009 14:20:19 -0500 X-Authority-Analysis: v=1.0 c=1 a=SXV9vV5SJNIA:10 a=e6x8O5mGaEsA:10 a=Kdko7-liitwbtSjYBPUA:9 a=j2D6ZA7kWbhB28zVfo4A:7 a=vVbbdM_eOO_rCakNDTyfUJqmiusA:4 a=LY0hPdMaydYA:10 X-CM-Score: 0.00 Date: Thu, 15 Jan 2009 12:20:17 -0700 From: Tom Rini To: openembedded-devel@openembedded.org Message-ID: <20090115192017.GJ6710@smtp.west.cox.net> References: <20090115061418.GA13352@denix.org> <20090115074118.GC7020@gmail.com> <19c1b8a90901151053n5402dcbdle52c090fe5c94c71@mail.gmail.com> MIME-Version: 1.0 In-Reply-To: <19c1b8a90901151053n5402dcbdle52c090fe5c94c71@mail.gmail.com> Organization: Embedded Alley Solutions, Inc User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: [RFC] Fix udev pulling in libvolume-id-dev X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 19:27:03 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 15, 2009 at 10:53:50AM -0800, Khem Raj wrote: > On Thu, Jan 15, 2009 at 3:10 AM, Koen Kooi wrote: > > On 15-01-09 08:41, Khem Raj wrote: > >> > >> On (15/01/09 07:56), Koen Kooi wrote: > >>> > >>> On 15-01-09 07:14, Denys Dmytriyenko wrote: > >>> > >>>> libvolume-id-dev does not provide the actual .so library, but it > >>>> contains a > >>>> symlink in /usr/lib, which points to /lib/libvolume.so.0 (the host one!) > >>>> instead of ../../lib/ one... > >>> > >>> That's the intended behaviours, since installing the packages will have > >>> it point to ${libdir}/libvolume.so.0 on your device. I'm not sure if we > >>> want to patch every package to use relative symlinks. > >> > >> We would use -dev packages on staged area normally to compile other apps > >> depending on a given packge if we do not fix the symlink I think it will > >> try to link to wrong library. > > > > We don't use the -dev packages to populate staging :) I keep trying to > > convince Richard that we should use them, but he keeps coming up with good > > reasons not to do so :) > > Hmm then why do we generate them ?. We do not need these packages on > target unless we switch to > native development on target. SDKs, which oddly DO let you do development vs them, so any problem stopping us from using them for staging is a problem here. But that's all part of another thread RP and I need to start. Or one of us does, at least. -- Tom Rini