From: "Andrey Falko" <ma3oxuct@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Safety/wiseness of moving stray files from /etc/env.d
Date: Thu, 20 Nov 2008 17:56:38 -0800 [thread overview]
Message-ID: <350fc7cf0811201756g228eac08n3065b51b4c291c2a@mail.gmail.com> (raw)
In-Reply-To: <20081120235106.7e892217@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
On 11/20/08, Jorge Peixoto de Morais Neto <please.no.spam.here@gmail.com>
wrote:
>
>
> Is it safe/wise to move 20java and 05gcc-i686-pc-linux-gnu to a backup
> directory? How about binutils/config-i386-pc-linux-gnu? How about the blas,
> cblas and lapack directories (I have long ago unmerged the corresponding
> packages)? They contain only this:
>
>
Well, since you are backing them up, I don't see much harm since you can
move them back once you see that something broke. When is the last time you
did an etc-update? What running env-update?
[-- Attachment #2: Type: text/html, Size: 838 bytes --]
next prev parent reply other threads:[~2008-11-21 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 1:51 [gentoo-user] Safety/wiseness of moving stray files from /etc/env.d Jorge Peixoto de Morais Neto
2008-11-21 1:56 ` Andrey Falko [this message]
2008-11-21 8:57 ` Jorge Peixoto de Morais Neto
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=350fc7cf0811201756g228eac08n3065b51b4c291c2a@mail.gmail.com \
--to=ma3oxuct@gmail.com \
--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