Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #12946

Bug#972213: boost1.71: Please indicate some way which python versions you support

From Alastair McKinstry <mckinstry@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.maint.python
Subject Bug#972213: boost1.71: Please indicate some way which python versions you support
Date 2020-10-16 11:20 +0200
Message-ID <B0u41-3Al-5@gated-at.bofh.it> (permalink)
References (1 earlier) <B0mg9-74v-3@gated-at.bofh.it> <B0rIR-24h-1@gated-at.bofh.it> <B0tB0-3ag-7@gated-at.bofh.it> <AZPtT-48k-3@gated-at.bofh.it> <B0tB0-3ag-7@gated-at.bofh.it>
Organization Debian

Cross-posted to 2 groups.

Show all headers | View raw


On 16/10/2020 09:19, Drew Parsons wrote:
> On 2020-10-16 14:43, Giovanni Mascellani wrote:
>> Hi,
>>
>> Il 16/10/20 02:53, Drew Parsons ha scritto:
>>>
>>> Would it make sense to use the Built-Using [1] header?
> ...
>>> [1]
>>> https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using 
>>>
>>
>> The precise web page you are linking hints that this use of Built-Using
>> would be improper:
>>
>> "This field should be used only when there are license or DFSG
>> requirements to retain the referenced source packages. It should not be
>> added solely as a way to locate packages that need to be rebuilt against
>> newer versions of their build dependencies".
>
> Ah yes, I had a feeling there were more reasons to not prefer this 
> method!
>
>
>> That said, I forgot to mention that the Python versions Boost is
>> compiled against is also tracked in the package names provided by
>> libboost-python1.71.0, which are currently libboost-python1.71.0-py38
>> and libboost-python1.71-py39.
>>
>> Is this better? More in general, there can be dozens of ways to
>> advertise which Python versions are used to build Boost.Python, but it
>> is not clear to me how this information should be consumed.
>
>
> That sounds like a useful approach.
>
> The ecflow build could access the provided versions via
>   dpkg -s libboost-python${BOOST_VERSION} | grep Provides

That works.

Code can be added that the package fails to rebuild if it can't get the 
necessary provides.

Thanks

Alastair

-- 
Alastair McKinstry, <alastair@sceal.ie>, <mckinstry@debian.org>, https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Bug#972213: boost1.71: Please indicate some way which python versions you support Drew Parsons <dparsons@debian.org> - 2020-10-16 03:00 +0200
  Bug#972213: boost1.71: Please indicate some way which python versions you support Giovanni Mascellani <gio@debian.org> - 2020-10-16 08:50 +0200
    Bug#972213: boost1.71: Please indicate some way which python versions you support Drew Parsons <dparsons@debian.org> - 2020-10-16 10:50 +0200
      Bug#972213: boost1.71: Please indicate some way which python versions you support Alastair McKinstry <mckinstry@debian.org> - 2020-10-16 11:20 +0200

csiph-web