Re: mechanism to retain system library versions

2013-12-18 Thread Miloslav Trmač
On Wed, Dec 18, 2013 at 2:55 PM, Stanislav Ochotnicky wrote: > Quoting Neal Becker (2013-12-18 14:06:23) >> During the past few months, I've switched from building my software against a >> bundled version of boost libraries, to building against the system boost >> libs. >> >> On updating to f20,

Re: mechanism to retain system library versions

2013-12-18 Thread Martin Langhoff
Ah! http://dev.laptop.org/git/packages/ cheers, m On Wed, Dec 18, 2013 at 9:48 AM, Neal Becker wrote: > Hey thanks! But did you forget to include a link to the git repos? > > Martin Langhoff wrote: > >> Neal, >> >> look like you've found the one thing fedora devel has consensus on ;-) >> >>

Re: mechanism to retain system library versions

2013-12-18 Thread Neal Becker
Hey thanks! But did you forget to include a link to the git repos? Martin Langhoff wrote: > Neal, > > look like you've found the one thing fedora devel has consensus on ;-) > > Here is a series of git repos that show how I was maintaining some > rpms outside of the fedora infra, but using fedp

Re: mechanism to retain system library versions

2013-12-18 Thread Martin Langhoff
Neal, look like you've found the one thing fedora devel has consensus on ;-) Here is a series of git repos that show how I was maintaining some rpms outside of the fedora infra, but using fedpkg (which I recommend) -- more specifically mockbuild. These repos are public, but you can do the same i

Re: mechanism to retain system library versions

2013-12-18 Thread Rex Dieter
Neal Becker wrote: > How do others solve this problem package your software as rpms too, so such dependencies get tracked. -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-

Re: mechanism to retain system library versions

2013-12-18 Thread Stanislav Ochotnicky
Quoting Neal Becker (2013-12-18 14:06:23) > During the past few months, I've switched from building my software against a > bundled version of boost libraries, to building against the system boost libs. > > On updating to f20, all of my software became broken, because the library > versions it w

Re: mechanism to retain system library versions

2013-12-18 Thread Martin Langhoff
On Wed, Dec 18, 2013 at 8:19 AM, Neal Becker wrote: > 2) somehow build against f20 libs on an f19 system? this is trivially done using mock. Actually, what I do, even for non-public builds, is to have a spec file in a git repository and build/rebuild the rpm using fedpkg. fedpkg makes things inc

Re: mechanism to retain system library versions

2013-12-18 Thread Paul Howarth
On 18/12/13 13:19, Neal Becker wrote: Florian Weimer wrote: On 12/18/2013 02:06 PM, Neal Becker wrote: During the past few months, I've switched from building my software against a bundled version of boost libraries, to building against the system boost libs. Is your software packaged in Fed

Re: mechanism to retain system library versions

2013-12-18 Thread Neal Becker
Florian Weimer wrote: > On 12/18/2013 02:06 PM, Neal Becker wrote: >> During the past few months, I've switched from building my software against a >> bundled version of boost libraries, to building against the system boost >> libs. > > Is your software packaged in Fedora? No, this is not intend

Re: mechanism to retain system library versions

2013-12-18 Thread Florian Weimer
On 12/18/2013 02:06 PM, Neal Becker wrote: During the past few months, I've switched from building my software against a bundled version of boost libraries, to building against the system boost libs. Is your software packaged in Fedora? How do others solve this problem, or can anyone think of

mechanism to retain system library versions

2013-12-18 Thread Neal Becker
During the past few months, I've switched from building my software against a bundled version of boost libraries, to building against the system boost libs. On updating to f20, all of my software became broken, because the library versions it was linked with were removed. So I had to race to re