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

Groups > linux.debian.user > #246317

Re: packages built with golang

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Mar 14, 2022 at 05:23:02PM -0700, Cousin Stanley wrote:
> Dan Ritter wrote:
> 
> > ....
> > Not having Built-Using is just like not having dependencies.
> 
>   Thanks for the explanation.
> 
>   I can understand the need for the Built-Using list
>   for the developers that need it. 

No, it seems you haven't understood.

Assume some security issue becomes known for, say, libssl.

The developers fix it. The Debian developer integrates the fix into
the package (if necessary, by backporting. You, the user, do an
apt-get upgrade. The fixed version gets installed in your system,
every program using that library is now fine.

With go, you have, say, some crypto library linked STATICALLY to
15 programs from as many packages. The bug gets fixed and...
nothing happens. Unless... your system knows that those 15 packages
were "Built-Using:".

That's why you need that metadata.

As for why they are shown to you, the system administrator --
well, the installer's decision to install those 15 packages
has to be transparent to you. It is, after all, the dark
sister of "Depends:" in the statical linking world.

Cheers
-- 
t

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

Thread

packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-14 21:20 +0100
  Re: packages built with golang Andy Smith <andy@strugglers.net> - 2022-03-14 22:10 +0100
    Re: packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-15 01:00 +0100
      Re: packages built with golang David Wright <deblis@lionunicorn.co.uk> - 2022-03-15 01:20 +0100
        Re: packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-15 02:00 +0100
          Re: packages built with golang Greg Wooledge <greg@wooledge.org> - 2022-03-15 02:40 +0100
  Re: packages built with golang Dan Ritter <dsr@randomstring.org> - 2022-03-14 22:30 +0100
    Re: packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-15 01:50 +0100
      Re: packages built with golang <tomas@tuxteam.de> - 2022-03-15 07:30 +0100
        Re: packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-15 15:00 +0100
          Re: packages built with golang Dan Ritter <dsr@randomstring.org> - 2022-03-15 15:20 +0100
            Re: packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-15 16:50 +0100
              Re: packages built with golang Greg Wooledge <greg@wooledge.org> - 2022-03-15 17:00 +0100
              Re: packages built with golang Kushal Kumaran <kushal@locationd.net> - 2022-03-15 17:00 +0100
              Re: packages built with golang Curt <curty@free.fr> - 2022-03-15 19:00 +0100
              Re: packages built with golang Dan Ritter <dsr@randomstring.org> - 2022-03-15 19:00 +0100
                Re: packages built with golang Cindy Sue Causey <butterflybytes@gmail.com> - 2022-03-16 03:20 +0100
                Re: packages built with golang Cousin Stanley <cousinstanley@gmail.com> - 2022-03-17 00:50 +0100
          Re: packages built with golang <tomas@tuxteam.de> - 2022-03-15 16:40 +0100
  Re: packages built with golang songbird <songbird@anthive.com> - 2022-03-15 03:30 +0100

csiph-web