I spoke with Christopher about this today. Here are the things we
discussed.
- mpdecimal is a leaf package, with no dependencies in noble using this package.
- Using system mpdecimal libraries was removed in 3.11.2-4, by removing the
library from debian/control and dropping the line --with-system-libmpdec from
debian/rules.
Looking at python3.12 in noble, if we did accept the package, it would not be
mistakenly pulled into build due to:
1) Not having the dependency in debian/control
2) Not having the --with-system-libmpdec set in debian/rules
3) configure.ac listing:
# Check for use of the system libmpdec library
AC_MSG_CHECKING([for --with-system-libmpdec])
AC_ARG_WITH(
[system_libmpdec],
[AS_HELP_STRING(
[--with-system-libmpdec],
[build _decimal module using an installed libmpdec library, see
Doc/library/decimal.rst (default is no)]
)],
[],
[with_system_libmpdec="no"])
AC_MSG_RESULT([$with_system_libmpdec])
which defaults to using vendored mpdecimal.
Note, that on python3.14 on stonking, we see:
# Check for use of the system libmpdec library
AC_MSG_CHECKING([for --with-system-libmpdec])
AC_ARG_WITH(
[system_libmpdec],
[AS_HELP_STRING(
[--with-system-libmpdec],
[build _decimal module using an installed mpdecimal library, see
Doc/library/decimal.rst (default is yes)]
)],
[],
[with_system_libmpdec="yes"])
AC_MSG_RESULT([$with_system_libmpdec])
which changes to defaulting to the system library, something to be aware
of.
From these points of view, it is likely safe to reintroduce mpdecimal from a
python prospective.
However, we must also consider that users may be building their own packages in
ppas, and that behaviour would change if we start shipping mpdecimal, for
example:
1) A user installs mpdecimal from jammy or lunar to their noble system or ppa
2) The user builds new python, or r, lua, elixir, or php on their own system or
ppa.
3) We ship mpdecimal from resolute into noble-updates.
4) The new resolute backport then breaks previously working builds if it has
some sort of regression or behaviour change, due to it now being used over the
existing ppa packages due to it having a higher version number.
There is always a risk to introduce packages from the stable release, and it
comes down to the benefits of consistency of libraries for those users who wish
to build newer versions of python on noble, versus theoretical regressions in
private package builds that we aren't quite sure even exist.
I will add this to the SRU Team agenda, and we will discuss it and see if we can
get consensus there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2167730
Title:
[SRU] Add libmpdec-dev to noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpdecimal/+bug/2167730/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
