[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#945256: marked as done (Do not make `gcc` depend on one paticular version.)

Your message dated Fri, 22 Nov 2019 05:28:44 +0100
with message-id <[🔎] 44a0107a-ecf6-3b64-5a52-4c6704cef2e2@debian.org>
and subject line Re: Bug#945256: Do not make `gcc` depend on one paticular version.
has caused the Debian Bug report #945256,
regarding Do not make `gcc` depend on one paticular version.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
945256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945256
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Package: gcc
Version: 4:9.2.1-3.1
Severity: wishlist

It seems that the GCC-related packages (`cpp`, `g++`, etc.) have hard dependencies to one particular version of said programs, so when a new version of GCC is released and a package depends on `gcc` or `cpp`, I have to install multiple versions of GCC or CPP.

I think that a better idea is to:
1. Make GCC-related packages virtual packages, and make various versions of `gcc` like `gcc-8` and `gcc-9` provide the `gcc` package name.
2. Use the debian-alternatives system for the GCC-related binaries, so if a program only needs to use a compiler, it would use the latest version (or user-specifies version with `update-alternatives`), and if a program needs a particular version, it would directly use `gcc-8` or `gcc-9`.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBcBAEBCAAGBQJd11OtAAoJENi1YDlFXXQfk6IIAJQpYVtuOm0WaRGKRytF
r6C1+L+bU3FwIFs1PWxeZTlyeP5Z64CChl6EscU4j+JQgKZKE84tWCysnGgB
5986TmDHh6aD3Z3x8l4XiL/Ukz3kWhnvATvIBKAbQGHSDKhhNvs+7cUtQbrc
42W0JsQeSlMfgITPkMFV8VHZ17FA45+U4YA/hexzMk3TPGLgXVGcvRb1JYqX
O1UlV9h/OPce17v+YdOXSNPXY8Ob0DSrc7R7Sus/9YuMnE3rlouVowAy0G09
z8JfldBAHqp2CZKYvBkQQ+tAg3Otj0sgpQNlLgMlrWeI1oDqjKGWPc+qjbE8
dfYkWXrQAr2xIKCPVqSxcLA=
=vGb5
-----END PGP SIGNATURE-----

Attachment: publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys

Attachment: publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 22.11.19 04:19, Gong S. wrote:
> Package: gcc
> Version: 4:9.2.1-3.1
> Severity: wishlist
> 
> It seems that the GCC-related packages (`cpp`, `g++`, etc.) have hard dependencies to one particular version of said programs, so when a new version of GCC is released and a package depends on `gcc` or `cpp`, I have to install multiple versions of GCC or CPP.
> 
> I think that a better idea is to:
> 1. Make GCC-related packages virtual packages, and make various versions of `gcc` like `gcc-8` and `gcc-9` provide the `gcc` package name.
> 2. Use the debian-alternatives system for the GCC-related binaries, so if a program only needs to use a compiler, it would use the latest version (or user-specifies version with `update-alternatives`), and if a program needs a particular version, it would directly use `gcc-8` or `gcc-9`.

No. GCC versions usually come with different ABIs and APIs in some cases, like
having different soversions.  Handling different ABIs using alternatives is
simply wrong.

> Please limit your reply to 7-bit ASCII.
> I refuse to see your idiotic emoji in a TTY.

Please stop making idiotic requests.

--- End Message ---
Reply to: