public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Deprecating AMD64 17.0 profiles?
Date: Tue, 10 Nov 2020 10:13:59 +0100	[thread overview]
Message-ID: <afaf392cc36c93600c66f5cd3729c6f89e60c73a.camel@gentoo.org> (raw)
In-Reply-To: <X6pVGKjj4n+VAMNf@gentoo.org>

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

On Tue, 2020-11-10 at 09:53 +0100, Fabian Groffen wrote:
> On 10-11-2020 09:49:27 +0100, Michał Górny wrote:
> > > > So what you're saying is that you've had the wrong value of SYMLINK_LIB
> > > > for ages, and now you've created a meaningless 17.1 profile that chnages
> > > > it but isn't actually supposed to change anything, correct?
> > > 
> > > I guess, because the amd64 17.0 profile is deprecated with force, and I
> > > had to do something ...
> > 
> > Now that's a lie.  Only the regular amd64 profiles are deprecated.
> > There are no deprecation notices e.g. in the x32 profile or prefix
> > profiles.
> 
> Our profiles either directly depend on the amd64/17.0 profile, or we use
> a sub-profile from amd64/17.0 profile, so if it's going to get removed,
> we are having a problem, don't we?

It isn't going to be removed as long as other profiles depend on it.
 It'll probably be re-parented.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2020-11-10  9:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 15:17 [gentoo-dev] [PATCH] profiles: Reorder AMD64 profile list to place 17.1 on top Brian Evans
2020-10-22 15:44 ` Michał Górny
2020-10-22 19:16   ` [gentoo-dev] Deprecating AMD64 17.0 profiles? Andreas K. Hüttel
2020-11-07 11:42     ` Alexey Sokolov
2020-11-07 11:56       ` Fabian Groffen
2020-11-09 19:38         ` Alexey Sokolov
2020-11-10  7:55           ` Fabian Groffen
2020-11-10  8:34             ` Michał Górny
2020-11-10  8:41               ` Fabian Groffen
2020-11-10  8:49                 ` Michał Górny
2020-11-10  8:53                   ` Fabian Groffen
2020-11-10  9:13                     ` Michał Górny [this message]
2020-11-10  9:21             ` Alexey Sokolov
2020-11-10  9:27               ` Fabian Groffen
2020-11-07 13:39       ` Andreas K. Huettel
2020-11-07 14:01         ` Alexey Sokolov
2020-11-09 10:30     ` Jaco Kroon
2020-11-09 10:59       ` Ulrich Mueller
2020-11-09 11:09         ` Jaco Kroon
2020-11-09 11:45           ` Marek Szuba
2020-11-09 11:54     ` Peter Stuge
2020-11-09 12:48       ` Aaron Bauman
2020-11-09 12:57       ` Andreas K. Huettel

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