public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org, prefix@gentoo.org,
	hardened@gentoo.org, arm@gentoo.org, mips@gentoo.org,
	ppc@gentoo.org, ppc64@gentoo.org
Subject: Re: [gentoo-dev] Deprecation and removal of 13.0 profiles is imminent
Date: Tue, 19 Feb 2019 22:52:10 +0000	[thread overview]
Message-ID: <20190219225210.2f156b08@sf> (raw)
In-Reply-To: <20181216195638.146c625a@sf>

On Sun, 16 Dec 2018 19:56:38 +0000
Sergei Trofimovich <slyfox@gentoo.org> wrote:

> On Wed, 12 Dec 2018 00:25:04 +0000
> Sergei Trofimovich <slyfox@gentoo.org> wrote:
> 
> > Tl;DR: 13.0 profiles will be removed some time soon unless there are
> > enough reports broken on 13.0->17.0 switch.
> > 
> > 13.0 profiles been a while in Gentoo tree and are already deprecated
> > on some arches but not everywhere.
> > 
> > If you have problems using 17.0 profiles as a default please file a bug
> > and pile it against against the tracker bug (fresh one):
> >     https://bugs.gentoo.org/672960  
> 
> I filed a bunch of bugs to deprecate existing profile that rely on
> 'releases/13.0' profile snippet.
> 
> To deprecate a profile just drop a 'deprecated' file to profile dir
> that targets to target for users to switch to. Example:
>     https://bugs.gentoo.org/672960#c2
> Note: package.desc still remains
> 
> At removal time we will delete both deprecated profiles and package.desc entries.

A few months passed and we almost finished with a long tail.

To-be-deprecated profiles yet are:
  https://bugs.gentoo.org/673278
    prefix/linux-standalone/ppc64

+prefix@, what is our plan here? Can we drop at least empty
'deprecated' file to notify users?

  https://bugs.gentoo.org/673276
    hardened/linux/arm/armv6j
    hardened/linux/arm/armv7a

    hardened/linux/mips/mipsel/multilib/n32
    hardened/linux/mips/mipsel/multilib/n64
    hardened/linux/mips/mipsel/n32
    hardened/linux/mips/mipsel/n64
    hardened/linux/mips/multilib/n32
    hardened/linux/mips/multilib/n64
    hardened/linux/mips/n32
    hardened/linux/mips/n64

    hardened/linux/powerpc/ppc32
    hardened/linux/powerpc/ppc64/32bit-userland
    hardened/linux/powerpc/ppc64/64bit-userland

+hardened@ (and +arm@, +mips@, +ppc@, +ppc64) ,
is it fine to redirect these to vanilla 17.0 profiles?

-- 

  Sergei


  reply	other threads:[~2019-02-19 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  0:25 [gentoo-dev] Deprecation and removal of 13.0 profiles is imminent Sergei Trofimovich
2018-12-16 19:56 ` Sergei Trofimovich
2019-02-19 22:52   ` Sergei Trofimovich [this message]
2019-02-20  8:07     ` Fabian Groffen
2019-02-21  3:05     ` Joshua Kinard

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=20190219225210.2f156b08@sf \
    --to=slyfox@gentoo.org \
    --cc=arm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hardened@gentoo.org \
    --cc=mips@gentoo.org \
    --cc=ppc64@gentoo.org \
    --cc=ppc@gentoo.org \
    --cc=prefix@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