public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: yac <yac@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Official way to do rolling update (Was: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec)
Date: Mon, 4 Nov 2013 05:15:18 +0100	[thread overview]
Message-ID: <20131104051518.51efd36c@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

On Sun, 03 Nov 2013 11:02:31 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

[snip]
> > 
> > Afaik there is no official way to update gentoo, is there?
> 
> It's always been "emerge -avuND world"
[snip]

Is this documented annywhere? I have a hard time finding it. I can see
it mentioned eg. in man emerge in -c option but that's not good enough.

Even if it is documented, I think it would be very helpfull to have
such a way implemented as "kind of option" to emerge like `emerge
--standard-ugrade` that would just alias to -uaNDv or possibly leverage
sets like `emerge @upgrade`

-- 
Jan Matějka        | Gentoo Developer
https://gentoo.org | Gentoo Linux
GPG: A33E F5BC A9F6 DAFD 2021  6FB6 3EBF D45B EEB6 CA8B

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2013-11-04  4:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  4:15 yac [this message]
2013-11-04  8:50 ` Official way to do rolling update (Was: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec) Daniel Campbell
2013-11-04  9:51   ` [gentoo-dev] Re: Official way to do rolling update (Was: " Duncan
2013-11-04 10:26     ` yac
2013-11-04 12:06       ` Dale
2013-11-04 12:28         ` Tom Wijsman
2013-11-04 15:50           ` Rich Freeman
2013-11-04 20:02           ` Dale
2013-11-04 20:27             ` Tom Wijsman
2013-11-04 21:47               ` Dale
2013-11-04 23:28           ` Alan McKinnon
2013-11-04 12:12       ` Tom Wijsman
2013-11-04 22:28       ` Duncan
2013-11-04 11:17     ` Martin Vaeth
2013-11-04 21:46       ` Duncan
2013-11-05  1:23         ` Michael Orlitzky
2013-11-05  7:51           ` Duncan
2013-11-05 16:21         ` Daniel Campbell
2013-11-04 21:53     ` Peter Stuge
2013-11-04 11:07 ` Official way to do rolling update (Was: Re: [gentoo-dev] " Tom Wijsman
  -- strict thread matches above, loose matches on Subject: below --
2013-11-02 13:16 [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec Anthony G. Basile
2013-11-02 13:51 ` Tom Wijsman
2013-11-02 15:03   ` Michał Górny
2013-11-02 19:20     ` Rick "Zero_Chaos" Farina
2013-11-02 20:35       ` yac
2013-11-02 20:57         ` Rick "Zero_Chaos" Farina
2013-11-02 22:09           ` yac
2013-11-02 23:19             ` Anthony G. Basile
2013-11-02 23:45               ` yac
2013-11-03  9:02                 ` Alan McKinnon
2013-11-04  0:59                   ` Official way to do rolling update (Was: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec) yac
2013-11-04  4:17                     ` yac

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=20131104051518.51efd36c@gentoo.org \
    --to=yac@gentoo.org \
    --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