Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

some package scripts are in the wrong packages #333

Open
ThinkOpenly opened this issue Jan 26, 2018 · 0 comments
Open

some package scripts are in the wrong packages #333

ThinkOpenly opened this issue Jan 26, 2018 · 0 comments
Labels

Comments

@ThinkOpenly
Copy link
Contributor

The deb package builds produce two related packages, one with the at version in the package name, and one version-agnostic, for example:

$ apt-cache search advance-toolchain | grep ppc64le | grep -v at10
advance-toolchain-cross-ppc64le - Advance Toolchain cross compiler
advance-toolchain-cross-ppc64le-mcore-libs - Advance Toolchain
advance-toolchain-cross-ppc64le-runtime-extras - Advance Toolchain cross compiler runtime extras files
advance-toolchain-at11.0-cross-ppc64le - Advance Toolchain cross compiler
advance-toolchain-at11.0-cross-ppc64le-mcore-libs - Advance Toolchain
advance-toolchain-at11.0-cross-ppc64le-runtime-extras - Advance Toolchain cross compiler runtime extras files

The versioned packages should be "stand-alone", but some important scripts are built into the version-agnostic packages instead, for example:

$ dpkg-query --control-list advance-toolchain-at11.0-cross-ppc64le
triggers
shlibs
md5sums
$ dpkg-query --control-list advance-toolchain-cross-ppc64le
md5sums
postinst
prerm
@tuliom tuliom added the bug label Jan 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants