Neil Williams wrote:
> On Sat, 18 Aug 2007 15:24:32 -0500 (CDT)
> Carlo Segre <[EMAIL PROTECTED]> wrote:
>
>> This is the thing aobut boost, it is not a library but basically a set of
>> functions taht gets included in your program.
>>
> Those functions have to live somewhere. Headers are
On Sat, 18 Aug 2007 15:24:32 -0500 (CDT)
Carlo Segre <[EMAIL PROTECTED]> wrote:
> > Potential problems:
> > 1. file collisions. Make sure the internal versions are installed as
> > package-specific libraries, NOT into /usr/lib/ directly.
>
> The boost libraries are simply includes, no binary libr
I appreciate your comments
On Sat, 18 Aug 2007, Neil Williams wrote:
On Sat, 18 Aug 2007 14:10:39 -0500 (CDT)
Carlo Segre <[EMAIL PROTECTED]> wrote:
One of my packages uses the boost headers and distributes them in the
original tarball. I have been modifying the configuration scripts to
ign
On Sat, 18 Aug 2007, Felipe Sateler wrote:
Carlo Segre wrote:
Upstream prefers to
continue distribution in the tarball and it would avoid having to
continually patch the configuration scripts.
Maybe you could convince upstream of providing a --with-system-boost option
to use either the provi
Carlo Segre wrote:
> Upstream prefers to
> continue distribution in the tarball and it would avoid having to
> continually patch the configuration scripts.
Maybe you could convince upstream of providing a --with-system-boost option
to use either the provided copy or the external ones.
--
Fel
On Sat, 18 Aug 2007 14:10:39 -0500 (CDT)
Carlo Segre <[EMAIL PROTECTED]> wrote:
> One of my packages uses the boost headers and distributes them in the
> original tarball. I have been modifying the configuration scripts to
> ignore the local copy and use the libboost-dev dependency instead. Si
On Sat, 18 Aug 2007, Carlo Segre wrote:
One of my packages uses the boost headers and distributes them in the
original tarball. I have been modifying the configuration scripts to ignore
the local copy and use the libboost-dev dependency instead. Since these are
headers and not real libraries
Hi All:
One of my packages uses the boost headers and distributes them in the
original tarball. I have been modifying the configuration scripts to
ignore the local copy and use the libboost-dev dependency instead. Since
these are headers and not real libraries, would it violate policy for m
8 matches
Mail list logo