From: 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: Tue, 28 Feb 2023 17:26:31 +0100 [thread overview]
Message-ID: <20230228161432.GA12679@LionPure> (raw)
In-Reply-To: <87r0uajd4y.fsf@gmail.com>
Hi,
On +2023-02-28 11:30:21 +0100, Simon Tournier wrote:
>
> I proposed to remove the package because it was broken and no one was
> willing to fix it. What is the point to keep broken packages?
>
What is the purpose of a junk-yard for broken cars?
I think there is some use :) I kept an old VW going many decades
by more than once in my youth going with tools to a junk yard
where the deal was:
Find what you need in some wreck, detach it with your own tools,
bring it to the office, and negotiate a price.
(the office guy could usually point you to the likely wrecks
if you described what you needed, and would even offer to rent you
some tools and help, all negotiable :)
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."
Software "parts" are a little different, but the R&R (remove & replace)
aspect seems similar ;-)
And it should be easy to keep an inventory of junk-yard contents by bug numbers.
Maybe somone would enjoy curating "junk" :)
Disclaimer: I am a terrible pack-rat ;/
(with no time to be junk curator, though I appreciate their work, along with
any{one,thing} helping me find what I want (rather than the other way around) :)
[...]
> Cheers,
> simon
>
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2023-02-28 16:27 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 [this message]
2023-02-28 17:16 ` Simon Tournier
2023-03-01 9:40 ` Bengt Richter
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230228161432.GA12679@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).