all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Question on the process of packge withdrawal
Date: Wed, 1 Mar 2023 10:40:41 +0100	[thread overview]
Message-ID: <20230301094041.GA14324@LionPure> (raw)
In-Reply-To: <CAJ3okZ2_dQZBmVQzPF=mVkdFv8BGE=NR4rAn-TwmZGnF0wgcLg@mail.gmail.com>

On +2023-02-28 18:16:18 +0100, Simon Tournier wrote:
> Hi,
> 
> On Tue, 28 Feb 2023 at 17:26, <bokr@bokr.com> wrote:
> 
> > IMO, it's a matter of storing the junk where it will not be a toxic liability
> > and nuisance, yet easily discovered by someone looking for "parts."
> 
> Well, I will not call that "junk". :-)
>

Me neither. That's what I meant to say with my
wrecked-cars-as-broken-packages anecdotal metaphor:
broken ≠ worthless :)

> IMHO, this is discoverable since it is part of the Git history of
> Guix.  The Git history of Guix also acts as an inventory.
>

I agree, the git history probably has everything in it, but for me
discovery is not so easy.

I think I need a map like openstreetmap, that on a high level could
show a map of software component boundaries instead of city plots,
and alternate views showing e.g. dependencies as roads between
warehouses/packages.

Obviously, related collections of things would cluster on map representations,
and interaction could pop up synopses and descriptions and urls etc -- like
what happens finding your way to the right bar in Brussels ;-)

How about a street-view drive along thread executions from power on
to login? Zoom in for detail data from dmesg or sytemctl -b or straces?

How about a drive into gnome-control-center?
With trip-planning how to get there and back from various contexts,
showing zoomable detail from high level widget thumbnails or
down to the lowest gdb run step.

Well QGIS is free/libre UIAM, but it is BIG.
And BIG means a LOT to trust, and that worries me.

Maybe good software maps could make reviewing and verifying easier,
until it's all automated. But how can we verify the automation?
(isn't there an old Latin saying about guarding guard dogs :)

I am not sure how the database of software maps would have to be
represented. What would be analogous to satellite photography and automatic
vectorization of roads and river boundaries etc.?

Actually, maybe a game engine would be better than GIS.
Super Bughunter Tomb Raider avatars ;-)
Yeah, that sounds like more fun. VRML?

Well, that's a big fantasy about "discovery" :)

Hm, how to get that running as native RISC-V code on open silicon? ;-)

> Cheers,
> simon
--
Regards,
Bengt Richter


  reply	other threads:[~2023-03-01  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26 20:11 Question on the process of packge withdrawal Sharlatan Hellseher
2023-02-27 17:12 ` Maxim Cournoyer
2023-02-27 19:55   ` Leo Famulari
2023-02-28 10:30 ` Simon Tournier
2023-02-28 16:26   ` bokr
2023-02-28 17:16     ` Simon Tournier
2023-03-01  9:40       ` Bengt Richter [this message]
2023-02-28 14:57 ` Andreas Enge
2023-02-28 17:10   ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230301094041.GA14324@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=sharlatanus@gmail.com \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.