From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Stale Samba in Portage
Date: Tue, 02 Aug 2005 09:27:49 +0800 [thread overview]
Message-ID: <1122946069.19160.71.camel@localhost> (raw)
In-Reply-To: <1122939902.8665.5.camel@localhost>
Its ok for a quick check - especially as I dont want ~x86 samba on that
system.
I regard /etc/portage and the way it has been done is a disaster waiting
to happen. You have files hidden away in there that unless you make the
effort, can (and do) keep insecure versions of software on your system -
make sure you regularly check what you put in there! It also did not
work properly on two of my systems (one has been decommissioned and the
other has been so much upgraded I think the problem has gone away - I
gave up after hours of trying to track down inconsistencies.
Sorry, but I hanker back to simpler times when -i made things so easy
and I didnt have to worry about someones idea of an "elegant" fix ...
BillK
On Mon, 2005-08-01 at 19:45 -0400, fire-eyes wrote:
> On Tue, 2005-08-02 at 07:14 +0800, William Kenworthy wrote:
> > ACCEPT_KEYWORDS='~x86' emerge samba -s
>
> ACCEPT_KEYWORDS done on the command line is a very poor idea,
> use /etc/portage/package.use instead.
>
> I forget the specifics, but I have seen a system run into serious
> problems and library screwups over that.
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-02 1:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 22:57 [gentoo-user] Stale Samba in Portage Raymond Lillard
2005-08-01 23:02 ` fire-eyes
2005-08-01 23:12 ` Zac Medico
2005-08-01 23:14 ` William Kenworthy
2005-08-01 23:45 ` fire-eyes
2005-08-01 23:58 ` Zac Medico
2005-08-02 7:38 ` Neil Bothwick
2005-08-02 1:27 ` W.Kenworthy [this message]
2005-08-02 1:32 ` Brett I. Holcomb
2005-08-02 1:49 ` [gentoo-user] Stale Samba in Portage (SOLVED) Raymond Lillard
2005-08-02 2:13 ` Nick Rout
2005-08-02 5:07 ` [gentoo-user] Stale Samba in Portage Richard Fish
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=1122946069.19160.71.camel@localhost \
--to=billk@iinet.net.au \
--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