Public bug reported:
We currently produce binary Debian packages whose names are prefixed
with the source package name. For example:
Package: linux-aws-headers-6.8.0-1001
Package: linux-aws-tools-6.8.0-1001
Package: linux-aws-cloud-tools-6.8.0-1001
The main reason for this is that these packages provide 'common' files
for the flavored packages so that we don't ship the same files with
different packages. To reduce the installed package size.
For example:
linux-<foo>-tools-<version> provides a single set of scripts and binaries.
linux-tools-<version>-<flavor-a> depends on the above and provides symlinks to
the scripts and binaries.
linux-tools-<version>-<flavor-b> depends on the above and provides symlinks to
the scripts and binaries.
...
This is all nice but presents multiple issues:
1) It results in a lot of packaging complexity.
2) It's confusing as the binary prefixes are different between the main linux
source and the derivatives.
3) It increases the number of packages to build.
4) It is only beneficial if multiple flavored packages are installed in
parallel. The only kernels that provide multiple flavors are some arm64 kernels
with generic and generic-64k flavors. Out of all the supported kernels and
architectures, this is a very small subset (6 out of 48 on Noble).
For all of the above reasons, we should get rid of these common packages
and just let the flavored packages provide the files.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2089819
Title:
Don't produce linux-<foo>-... binary packages
Status in linux package in Ubuntu:
New
Bug description:
We currently produce binary Debian packages whose names are prefixed
with the source package name. For example:
Package: linux-aws-headers-6.8.0-1001
Package: linux-aws-tools-6.8.0-1001
Package: linux-aws-cloud-tools-6.8.0-1001
The main reason for this is that these packages provide 'common' files
for the flavored packages so that we don't ship the same files with
different packages. To reduce the installed package size.
For example:
linux-<foo>-tools-<version> provides a single set of scripts and binaries.
linux-tools-<version>-<flavor-a> depends on the above and provides symlinks
to the scripts and binaries.
linux-tools-<version>-<flavor-b> depends on the above and provides symlinks
to the scripts and binaries.
...
This is all nice but presents multiple issues:
1) It results in a lot of packaging complexity.
2) It's confusing as the binary prefixes are different between the main linux
source and the derivatives.
3) It increases the number of packages to build.
4) It is only beneficial if multiple flavored packages are installed in
parallel. The only kernels that provide multiple flavors are some arm64 kernels
with generic and generic-64k flavors. Out of all the supported kernels and
architectures, this is a very small subset (6 out of 48 on Noble).
For all of the above reasons, we should get rid of these common
packages and just let the flavored packages provide the files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089819/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
