[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Re: [Monotone-debian] Boost Transitions; deprecating 1.
From: |
Zack Weinberg |
Subject: |
[Monotone-devel] Re: [Monotone-debian] Boost Transitions; deprecating 1.34.1 |
Date: |
Mon, 16 Feb 2009 13:20:30 -0800 |
On Mon, Feb 16, 2009 at 11:59 AM, Steve M. Robbins <address@hidden> wrote:
> Hello,
>
> Now that Lenny is finally released, I want to give everyone
> build-depending on Boost a heads-up on what's coming. This message is
> being sent to all package addresses that build-depend on the 1.34.1
> release of Boost, i.e. libboost-dev, libboost-regex-dev, etc.
>
> In a nutshell: libboost-dev is deprecated and will be removed in the
> coming weeks. In its place please build-depend on libboost1.38-dev
> (and siblings), which will be uploaded very shortly.
Thank you for the heads-up. I have two questions.
1) My package is known to work correctly with a wide range of boost
releases (1.33.1-1.35 at least; I haven't tried .37 or .38 but I don't
anticipate problems). To make life easier for backporters, I am thus
inclined to use a build-depends entry of the form
boost1.38-dev | boost1.37-dev | boost1.35-dev | boost-dev
As long as the current preferred package is first in the list of
or-deps, does this cause problems anywhere?
2) I was planning to upload a new upstream version of the package in
the next few days. Should I do this upload before boost1.38-dev shows
up, or wait until it does? If I do it before, would it be acceptable
to leave boost1.38-dev out of the dependency list, as I would then not
have actually tried it?
zw
- [Monotone-devel] Re: [Monotone-debian] Boost Transitions; deprecating 1.34.1,
Zack Weinberg <=