public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Re: pkg_{pre,post}inst misusage
Date: Fri, 23 Dec 2005 14:19:38 -0700	[thread overview]
Message-ID: <pan.2005.12.23.21.19.38.46048@cox.net> (raw)
In-Reply-To: 200512240406.05350.jstubbs@gentoo.org

Jason Stubbs posted <200512240406.05350.jstubbs@gentoo.org>, excerpted
below,  on Sat, 24 Dec 2005 04:06:05 +0900:

>> You are /sure/ the new code won't screw anything of that sort up, right?
>> Maybe that's the reason nobody seems to have been around to know about.
>> It just sounds like it /could/ be dangerous to me.  For some reason, I
>> don't like the idea of something that could hose a system that badly!  =8^\
> 
> *Please* don't tell me you run ~arch.

Well, I do, plus some stuff from package.mask like gcc-4.x and the
associated binutils and glibc stuff.

OTOH, I have long run a working and a backup snapshot version of the
system portions of my system (everything that packages normally touch),
for this very reason -- I'm running unstable, so I should be prepared to
boot to the backup if the main system gets hosed, either by my
fat-fingering or that of someone else.

Still, the last glibc upgrade was more "exciting" than I had anticipated,
even if DO say if I wanted boring and reliable, I'd be doing household
appliances, not computers. <g>  (I'm proud to say I handled it without
having to resort to a reboot or the backups, tho... if only because I
happened to have an mc instance running  in another vt at the time, and I
was able to use it to restore enough symlinks manually, to read the
documentation, figure out what happened, and restore the others by copying
them out of the binpkg.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2005-12-23 21:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-23 10:10 [gentoo-dev] pkg_{pre,post}inst misusage Jason Stubbs
2005-12-23 11:19 ` Stefan Schweizer
2005-12-23 11:31   ` Jason Stubbs
2005-12-23 12:39     ` Harald van Dijk
2005-12-23 12:55       ` Jason Stubbs
2005-12-23 13:00       ` Jason Stubbs
2005-12-23 13:13         ` Harald van Dijk
2005-12-23 17:11           ` Zac Medico
2005-12-23 17:32             ` Jason Stubbs
2005-12-23 17:22           ` Jason Stubbs
2005-12-23 17:52             ` Harald van Dijk
2005-12-23 18:09               ` Jason Stubbs
2005-12-23 18:46                 ` Harald van Dijk
2005-12-23 18:42             ` Thomas de Grenier de Latour
2005-12-23 19:12               ` Jason Stubbs
2005-12-23 18:43             ` [gentoo-dev] " Duncan
2005-12-23 18:57               ` Simon Stelling
2005-12-23 19:06               ` Jason Stubbs
2005-12-23 21:19                 ` Duncan [this message]

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=pan.2005.12.23.21.19.38.46048@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@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