From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] do subslots improve user-experience?
Date: Sat, 2 Nov 2013 21:26:57 +0000 [thread overview]
Message-ID: <20131102212657.28fd47e3@digimed.co.uk> (raw)
In-Reply-To: <5274EA64.6000404@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
On Sat, 02 Nov 2013 13:04:52 +0100, hasufell wrote:
> * how often do you experience useless rebuilds?
That's an unreasonable question. How do we know whether a rebuild was
useless or not unless we skip it and then find that a single feature of a
complex program no longer works properly, and to do that we have to block
the update from emerge world.
Yes, there are a lot more updates and rebuilds, but are these useless? I
have no facts to device either way.
> * do you really have a problem with running
> revdep-rebuild/haskell-updater/perl-cleaner etc after every emerge?
No. The only problem with those approaches is knowing when they need to be
run. That's what I like about the preserved-rebuild approach, it tells
you that rebuilds need to be done but lets the user device when to do
them.
> * do you think it's worth the effort to add more stuff
> to the PM, so that you don't have to run revdep-rebuild that often?
If it's done in a way that is understandable to users. Gentoo users like,
even need, to understand what is going on. Sub-slots don't achieve that.
> * do you trust the other methods like subslots or preserved-rebuild to
> work reliably? (as in: do you still use revdep-rebuild?)
I trust preserved-rebuild. I have a weekly cron script that checks
various aspects of my system, including a revdep-rebuild -p. That part
almost never finds anything these days.
Sub-slots appear to work, but they are opaque and intrusive.
@preserved-rebuild requires a tiny amount more effort from the user, but
gives more control and seems more Gentoo-ish to me.
--
Neil Bothwick
Q: Why is top-posting evil?
A: backwards read don't humans because
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-02 21:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 12:04 [gentoo-user] do subslots improve user-experience? hasufell
2013-11-02 12:31 ` Philip Webb
2013-11-02 13:16 ` Alan McKinnon
2013-11-03 19:07 ` [gentoo-user] " Martin Vaeth
2013-11-03 19:23 ` hasufell
2013-11-04 7:46 ` Martin Vaeth
2013-11-03 19:55 ` Alan McKinnon
2013-11-05 9:52 ` Martin Vaeth
2013-11-05 10:04 ` Peter Humphrey
2013-11-05 10:14 ` Alan McKinnon
2013-11-05 12:11 ` Marc Joliet
2013-11-05 14:44 ` Alan McKinnon
2013-11-05 15:21 ` Bruce Hill
2013-11-05 19:47 ` Alan McKinnon
2013-11-06 11:50 ` Marc Joliet
2013-11-06 12:54 ` Martin Vaeth
2013-11-06 18:15 ` Alan McKinnon
2013-11-07 6:26 ` Martin Vaeth
2013-11-05 18:06 ` Martin Vaeth
2013-11-05 19:59 ` Alan McKinnon
2013-11-06 7:46 ` Martin Vaeth
2013-11-06 13:11 ` Alan McKinnon
2013-11-07 6:16 ` Martin Vaeth
2013-11-02 15:32 ` [gentoo-user] " Daniel Campbell
2013-11-02 16:14 ` Dustin C. Hatch
2013-11-02 17:07 ` Daniel Frey
2013-11-02 19:56 ` Volker Armin Hemmann
2013-11-02 20:33 ` thegeezer
2013-11-02 21:26 ` Neil Bothwick [this message]
2013-11-03 0:38 ` [gentoo-user] " walt
2013-11-03 10:16 ` Neil Bothwick
2013-11-05 13:29 ` [gentoo-user] " Bruce Hill
2013-11-05 14:29 ` Bruce Hill
2013-11-05 21:28 ` Neil Bothwick
2013-11-05 21:38 ` Bruce Hill
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=20131102212657.28fd47e3@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox