Re: [Gearbox-devel] Packaging for Fedora

[Richard M. <jp...@gm...>]

Yes, those are the correct guidelines.  I've scoured them a few times, 
and I agree that they need clarification in this case.  I sent the 
fedora-packaging mailing list an email this morning asking for some 
clarification, but I've yet to get a response.

Rich


On 11/10/2009 10:48 PM, Geoffrey Biggs wrote:
> The packaging guidelines that I found here (I assume these are the
> correct guidelines):
>
> https://fedoraproject.org/wiki/Packaging/Guidelines
>
> Talk about adding an entry to ld.so.conf, so even if it's not
> commonplace, they should allow it, or update their packaging guidelines. :)
>
> Geoff
>
> Richard Mattes wrote:
>> Yes, Fedora has a folder at /etc/ld.so.conf.d/ where you can point ld to
>> other directories.  I offered that up as an option in the package review
>> request discussion, but they didn't seem to buy it.  I can only find
>> about 13 packages in F11 that use this technique, which leads me to
>> believe it's not commonplace.
>>
>> Rich
>>
>> On 11/10/2009 10:11 PM, Geoffrey Biggs wrote:
>>> Doesn't Fedora use /etc/ld.so.conf? A new package installed by the
>>> package manager should add something to that so other stuff can find its
>>> libraries. At least, that's how it's done on Gentoo and Debian and Vine.
>>>
>>> Geoff
>>>
>>> Richard Mattes wrote:
>>>> Alright I got a chance to try it out, it builds just fine on all
>>>> architectures [1] without all of the patches I needed the first time around.
>>>>
>>>> I'm still trying to wrangle a response out of the fedora-packaging
>>>> people, but I get the impression that they think all libraries should go
>>>> right in /usr/lib, without creating their own directory [2].  This is
>>>> probably to avoid having to mess with LD_LIBRARY_PATH in order to get
>>>> repo-provided libraries to work.  Creating subdirectories seems to be
>>>> protocol for plugin libraries that won't get accessed by anything but
>>>> your own program.  I checked, and there's a handful of packages that do
>>>> follow the same convention gearbox does: mainly Kitware programs and KDE
>>>> components.  Once I get a straight answer from someone, it shouldn't be
>>>> hard to shift the install directories around using
>>>> SetupDirectories.cmake.  I'd like to try to keep from disrupting build
>>>> processes elsewhere, so I'll keep coordinating with you guys as I find
>>>> out more.
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>> trial. Simplify your report design, integration and deployment - and focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> _______________________________________________
>>> Gearbox-devel mailing list
>>> Gea...@li...
>>> https://lists.sourceforge.net/lists/listinfo/gearbox-devel
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Gearbox-devel mailing list
>> Gea...@li...
>> https://lists.sourceforge.net/lists/listinfo/gearbox-devel
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gearbox-devel mailing list
> Gea...@li...
> https://lists.sourceforge.net/lists/listinfo/gearbox-devel