From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Re: Re: Re: libungif and giflib conflict.
Date: Wed, 02 Nov 2005 16:07:32 -0700 [thread overview]
Message-ID: <pan.2005.11.02.23.07.32.324733@cox.net> (raw)
In-Reply-To: 200511022259.51970.harmgeerts@home.nl
Harm Geerts posted <200511022259.51970.harmgeerts@home.nl>, excerpted
below, on Wed, 02 Nov 2005 22:59:51 +0100:
> On Wednesday 02 November 2005 21:54, Duncan wrote:
>> Hmm... That --noreplace is a new one on me. I normally simply
>>
>> echo <category/pkg> >> /var/lib/portage/world
>>
>> Newer versions of portage (don't believe it's in stable portage yet) even
>> have an emaint command that removes the bad lines for you.
>
> So did I, but now the warning `emerge depclean` produces tells me I can use
> this. I find this rather nice as it is a lot safer and keeps the world file
> free from user errors. For example replacing >> with > would be the most
> destructive user error :P
> I have portage 2.0.53_rc7 installed and I'm not sure which version introduced
> --noreplace so it might not be available for everyone yet.
I'm still on rc6, so I guess I need to sync and emerge -uD world.
However, it's probably in rc6 too, only I didn't notice it in the warning
(<sheepish> as I don't read it as I know what the warning is about... only
they added something! </sheepish>).
Not here, forgetting the second > in >> wouldn't be destructive! I think
this hint was featured in GWN a while back (yes, it was, comments are good
things! =8^):
-- snip --
# Based on a tips & tricks GWN feature.
# Makes redirection to an existing file an error.
# Use >> instead of > to append, or >| if overwriting is desired.
set -o noclobber
-- snip --
Put that in your .bashrc or whatever (my /etc/profile and .bashrc and all
that are rather seriously customized, here, it's a file called
noclobber.sh in /etc/profile.d/, but my bashrcs and profiles source
everything in /etc/profile.d/ so it's added to them).
That way, using > to redirect to an existing file produces an error saying
it already exists. The comment gives the solution, use >> to append, or
use >| to force-overwrite the file.
So... "echo whatever > /var/lib/portage/world" would NOT "be the end of my
world" here! (double entendre/entente)
--
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-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-02 23:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 5:36 [gentoo-amd64] libungif and giflib conflict Nick Currier
2005-11-01 5:52 ` Barry.SCHWARTZ
2005-11-01 6:00 ` Brian Litzinger
2005-11-01 8:36 ` [gentoo-amd64] " Duncan
2005-11-01 15:07 ` Nick Currier
2005-11-01 17:39 ` Brian Litzinger
2005-11-01 18:19 ` [gentoo-amd64] " Duncan
2005-11-02 4:30 ` Nick Currier
2005-11-02 13:09 ` Harm Geerts
2005-11-02 19:42 ` Nick Currier
2005-11-02 20:54 ` [gentoo-amd64] " Duncan
2005-11-02 21:59 ` Harm Geerts
2005-11-02 23:07 ` Duncan [this message]
2005-11-03 0:52 ` Sebastian Redl
2005-11-03 2:32 ` Harm Geerts
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.11.02.23.07.32.324733@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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