From: Jared Lindsay <cinder.sub@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] 2005.1
Date: Fri, 12 Aug 2005 17:16:29 -0700 [thread overview]
Message-ID: <e16d914c050812171654479d7@mail.gmail.com> (raw)
In-Reply-To: <42FD002C.4030809@albrookdata.com>
Thanks for the responses...I realized after I sent that that I should
RTFM, indeed, which I did. Sorry for the trouble!
On 8/12/05, Francisco Perez <fperez@albrookdata.com> wrote:
> I guess it goes without saying that you could easily google for it or
> find this in gentoo.org, but never the less, here it is:
>
> The main 'Update Your Profile Page' (Definitely read this first, it
> explains everything you need to know.)
> http://www.gentoo.org/doc/en/gentoo-upgrading.xml
>
> Instructions for AMD64 with multilib enabled.
> http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=1#doc_chap1
>
> Instructions for AMD64 with multilib disabled.
> http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=1#doc_chap5
>
> Frank
>
> Jared Lindsay wrote:
>
> >How do you update your profile?
> >
> >On 8/11/05, Francisco Perez <fperez@albrookdata.com> wrote:
> >
> >
> >>Some releases have new profiles, in which case you need to update your
> >>/etc/make.profile directory link, in other cases you don't. If you are
> >>using 2004.3 then you should switch your profile to 2005.0, because if
> >>not, you'll only get the updates upto, but not including those on
> >>2005.0. From what I can see on this thread there has been a profile
> >>change for 2005.1 from 2005.0 for AMD64, but I don't think there was a
> >>profile change for 2005.1 for x86.
> >>
> >>Frank
> >>
> >>Jared Lindsay wrote:
> >>
> >>
> >>
> >>>I was always under the impression that as long as you keep doing
> >>>emerge -uD world, you are as up-to-date as possible. If we ARE using
> >>>2004.3 (which I am), what changes are there when you migrate from a
> >>>(fully updated) 2004.3 to 2005.1?
> >>>
> >>>On 8/11/05, Simon Stelling <blubb@gentoo.org> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>Gregory Symons wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>The 2005.1 and 2005.0 profiles are nearly identical, but that might
> >>>>>>change in a while, especially if you're using a sub-profile. Switching
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>would that be a long while or a short while?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>No idea.
> >>>>
> >>>>--
> >>>>Simon Stelling
> >>>>Gentoo/AMD64 Operational Co-Lead
> >>>>blubb@gentoo.org
> >>>>--
> >>>>gentoo-amd64@gentoo.org mailing list
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>--
> >>gentoo-amd64@gentoo.org mailing list
> >>
> >>
> >>
> >>
> >
> >
> >
> --
> gentoo-amd64@gentoo.org mailing list
>
>
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2005-08-13 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 23:36 [gentoo-amd64] 2005.1 Gregory Symons
2005-08-10 23:54 ` Simon Stelling
2005-08-11 1:31 ` John C. Shimek
2005-08-11 1:40 ` Simon Stelling
2005-08-11 2:17 ` Gregory Symons
2005-08-11 9:48 ` Simon Stelling
2005-08-11 17:39 ` Jared Lindsay
2005-08-11 17:45 ` Karol Krizka
2005-08-11 17:52 ` Francisco Perez
2005-08-12 0:01 ` Jared Lindsay
2005-08-12 7:02 ` Andreas Vinsander
2005-08-12 20:01 ` Francisco Perez
2005-08-13 0:16 ` Jared Lindsay [this message]
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=e16d914c050812171654479d7@mail.gmail.com \
--to=cinder.sub@gmail.com \
--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