public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] base-system needs developers who care
Date: Wed, 24 Aug 2016 16:08:28 +0200	[thread overview]
Message-ID: <1472047708.31785.156.camel@gentoo.org> (raw)
In-Reply-To: <20160824160505.3d07b9d6@abudhabi.paradoxon.rec>

El mié, 24-08-2016 a las 16:05 +0200, Lars Wendler escribió:
> 
[...]
> Oh, and to all new team members:
> Please keep in mind to *not* use EAPI-6 for base-system packages yet,
> so
> we can retain a somewhat stable upgrade path even for very old
> systems.
> 
> 
> Kind regards
> Lars

This reminds me a question I have for some time: is it documented in
some place what are the steps to follow for updating old systems? I
remember posts like:
http://blog.siphos.be/2013/12/upgrading-old-gentoo-installations/

but I don't know if that is "official" or a workaround or... :/

Thanks a lot for the info!


  reply	other threads:[~2016-08-24 14:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 23:17 [gentoo-dev] base-system needs developers who care Robin H. Johnson
2016-08-23 23:36 ` Anthony G. Basile
2016-08-24  0:03 ` Lars Wendler
2016-08-24  0:08   ` Anthony G. Basile
2016-08-24  1:06     ` Benda Xu
2016-08-24 14:05     ` Lars Wendler
2016-08-24 14:08       ` Pacho Ramos [this message]
2016-08-24 14:42         ` Upgrading Old Gentoo - Was " M. J. Everitt
2016-08-29 17:18         ` Joshua Kinard
2016-08-24 15:32       ` Mike Gilbert
2016-08-24 15:49         ` Michael Orlitzky
2016-08-25  8:00         ` Alexis Ballier
2016-08-24 17:17       ` William Hubbs
2016-08-24 20:33       ` Andreas K. Huettel
2016-08-24  1:11 ` William Hubbs
2016-08-24 17:24   ` Robin H. Johnson
2016-08-24  1:25 ` Patrick McLean
2016-08-24 12:04 ` Jason Zaman
2016-08-24 15:37 ` Mike Gilbert
2016-08-25  8:01 ` Alexis Ballier
2016-08-28  6:34   ` Daniel Campbell

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=1472047708.31785.156.camel@gentoo.org \
    --to=pacho@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