public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ~amd64 - my experience so far...
Date: Mon, 12 Apr 2010 20:42:47 +0800	[thread overview]
Message-ID: <1271076167.8658.44.camel@rattus> (raw)
In-Reply-To: <t2p5bdc1c8b1004120529g2aaf103qd55d9f24164d281e@mail.gmail.com>


> I am however documenting my experiences for others than come after me
> to this question of "to ~amd64 or not ~amd64". Nothing more. It worked
> for Alan who is a __very__ experienced and capable person. It didn't
> work for Mark (at this point) who is a 10 year Gentoo user but
> __nothing__ more than a user type Those people can decide who they are
> closer to in capabilities and make their choice a bit more informed.
> 
> I didn't wake up this morning thinking I could do what you and Neil
> and others on this list can with this distro. I'm not that silly! I
> just wanted to try ~amd64 to see what happened. It will take me less
> than 90 minutes to get to a new clean install if I blow everything
> away and start over. It's not a big deal.
> 
> - Mark
> 

Is there a reason why you want to run all @system as ~amd64, and the
rest stable.  To me it makes more sense (especially for production
systems) to run @system as stable and only ~amd64 those apps and
dependencies you want/need to be bleeding edge.

Anyhow, what I really wanted to say is for more sensible unmasking,
check out autounmask:

moriah home # esearch autounmask
[ Results for search key : autounmask ]
[ Applications found : 1 ]

*  app-portage/autounmask
      Latest version available: 0.27
      Latest version installed: [ Not Installed ]
      Size of downloaded files: 3 kB
      Homepage:    http://download.mpsna.de/opensource/autounmask/
      Description: autounmask - Unmasking packages the easy way
      License:     GPL-2


moriah home #





  reply	other threads:[~2010-04-12 12:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 11:57 [gentoo-user] ~amd64 - my experience so far Mark Knecht
2010-04-12 12:00 ` Alan McKinnon
2010-04-12 12:29   ` Mark Knecht
2010-04-12 12:42     ` William Kenworthy [this message]
2010-04-12 12:56       ` Mark Knecht
2010-04-12 13:10       ` [gentoo-user] " Kerin Millar
2010-04-12 12:57     ` [gentoo-user] " Alan McKinnon
2010-04-12 16:33       ` KH
2010-04-13  7:09         ` Alan McKinnon
2010-04-13  7:30           ` William Kenworthy
2010-04-13 12:40             ` Mark Knecht
2010-04-13 15:12               ` Paul Hartman
2010-04-13 16:11                 ` Mark Knecht
2010-04-13 17:34                   ` Alex Schuster
2010-04-13 18:30                     ` Mark Knecht
2010-04-13 15:37               ` Paul Hartman
2010-04-12 14:01     ` Neil Bothwick
2010-04-12 12:14 ` Zeerak Mustafa Waseem
2010-04-12 12:35   ` Mark Knecht
2010-04-12 13:07     ` [gentoo-user] " walt
2010-04-12 18:44       ` Mark Knecht
2010-04-12 18:57         ` Paul Hartman
2010-04-12 19:02           ` Paul Hartman
2010-04-12 21:03           ` Mark Knecht
2010-04-12 21:14             ` Paul Hartman
2010-04-12 22:18               ` Mark Knecht
2010-04-12 19:02         ` Alex Schuster
2010-04-12 13:06 ` Kerin Millar
2010-04-12 15:45 ` [gentoo-user] " Paul Hartman
2010-04-12 18:30   ` Paul Hartman

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=1271076167.8658.44.camel@rattus \
    --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