Re: using boost headers
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: Re: using boost headers
- From: Asheesh Laroia <email@example.com>
- Date: Sat, 18 Aug 2007 12:34:43 -0700 (PDT)
- Message-id: <alpine.DEB.firstname.lastname@example.org>
- In-reply-to: <Pine.LNX.email@example.com>
- References: <Pine.LNX.firstname.lastname@example.org>
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, would it violate policy for me to revert to
the version included in the tarball? Upstream prefers to continue
distribution in the tarball and it would avoid having to continually patch
the configuration scripts.
I haven't checked Policy, but if there's a chance that the headers will be
for version X whereas the system libboost is version Y, and they're not
API-compatible, then that would be Bad.
Q: How many Harvard MBA's does it take to screw in a light bulb?
A: Just one. He grasps it firmly and the universe revolves around him.