public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] multilib amd64 news item for review
Date: Tue, 17 Mar 2015 16:32:10 +0100	[thread overview]
Message-ID: <20150317163210.0b647580@pomiot.lan> (raw)
In-Reply-To: <21765.39596.562571.312369@a1i15.kph.uni-mainz.de>

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

Dnia 2015-03-15, o godz. 15:43:56
Ulrich Mueller <ulm@gentoo.org> napisał(a):

> >>>>> On Sun, 15 Mar 2015, Michał Górny wrote:
> 
> > Hello, everyone. Here's the first draft of news item for
> > gx86-multilib. I tried to cover all the important aspects. Please
> > review and let me know what you think.
> 
> > Title: True multilib support on amd64
> > Author: Michał Górny <mgorny@gentoo.org>
> > Content-Type: text/plain
> > Posted: 2015-01-28
> > Revision: 1
> > News-Item-Format: 1.0
> > Display-If-Keyword: amd64
> > Display-If-Keyword: ~amd64
> 
> Users of no-multilib profiles won't be affected, so maybe
> Display-If-Profile should be used (in addition, or instead of
> Display-If-Keyword)?

Display-If-Profile does exact profile matching, so we'd have to keep
an up-to-date list of all profiles derived from multilib amd64...

> > Starting with 2015-03-29, we are enabling the true multilib support
> > on amd64 and masking the old emul-linux-x86 package sets for removal.
> > This change provides
> 
> I'm not a native speaker, but shouldn't a future tense be used here?
> 
> >                      our users with the opportunity to build 32-bit
> > libraries from source with all the flexibility given by ebuilds, rather
> > than relying on pre-packaged binary versions of them.
> 
> > The switch to the new system is likely to require a specific action from
> > the users of our multilib profiles. Since the new system collides with
> > the old one, the Package Manager must be able to clearly satisfy all
> > the dependencies using the new system in order to proceed. This may
> > require unmerging packages installed from third-party repositories that
> > have not been updated to support the new system.
> 
> > In order to enable building necessary 32-bit libraries, users will be
> > required to enable the abi_x86_32 USE flag on respective packages.
> 
> How? Maybe add a hint that this should be done in package.accept_keywords?

It can't :P. But added a hint for package.use.

> > In most of the cases, Portage will be able to deliver correct
> > suggestions for that when using the --autounmask feature. However, some
> > users may prefer setting ABI_X86 globally to enable 32-bit libraries
> > in all packages supporting building them.
> 
> Again, add a hint how to do this?

Likewise.

> > In case of issues, blockers especially, the users users
> 
> s/the users users/users/

Fixed.

> >                                                         are recommended
> > to manually uninstall any emul-linux-x86 packages that may have been
> > installed on their systems. This will aid the Package Manager
> > in choosing the correct dependency resolution path. If using Portage,
> > this can be done using the following command:
> 
> >     $ emerge -C 'app-emulation/emul-linux-x86*'
> 
> > Note that after performing this step, 32-bit applications on your system
> 
> So far you have used third person throughout, so avoid the "your"
> here.

Fixed.

> 
> > may become temporarily broken. Therefore, this step should be followed
> > by a @world upgrade immediately.
> 
> Maybe a pointer to the wiki could be added? How about this:
> https://wiki.gentoo.org/wiki/Multilib_System_without_emul-linux_Packages
> (with that page being updated if necessary).

If someone has time to uncruft that wiki page, I'd be happy to link it.

-- 
Best regards,
Michał Górny

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  parent reply	other threads:[~2015-03-17 15:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 14:11 [gentoo-dev] multilib amd64 news item for review Michał Górny
2015-03-15 14:14 ` Alex Xu
2015-03-15 14:43 ` Ulrich Mueller
2015-03-15 15:41   ` Rich Freeman
2015-03-15 16:25   ` Ben de Groot
2015-03-15 16:48     ` [gentoo-dev] " Duncan
2015-03-17 15:32   ` Michał Górny [this message]
2015-03-17 15:43     ` [gentoo-dev] " Ulrich Mueller
2015-03-17 15:33 ` Michał Górny
2015-03-17 15:55   ` René Neumann
2015-03-17 16:29     ` Michał Górny
2015-03-17 16:52       ` Andreas K. Huettel
2015-03-29 16:14       ` [gentoo-dev] " Nikos Chantziaras
2015-03-29 16:24         ` Michał Górny
2015-03-29 16:59           ` Nikos Chantziaras
2015-03-29 17:28             ` Michał Górny
2015-03-29 17:35               ` Andrew Savchenko
2015-03-29 17:41                 ` Ciaran McCreesh
2015-03-29 17:43                 ` Michał Górny
2015-03-29 18:00                   ` Andrew Savchenko
2015-03-29 18:31                     ` Nikos Chantziaras
2015-03-29 18:34                       ` Michał Górny
2015-03-29 17:51               ` Nikos Chantziaras
2015-03-18  7:40   ` [gentoo-dev] " Ben de Groot
2015-03-18 12:46     ` [gentoo-dev] " Duncan
2015-03-18 12:57       ` Ben de Groot

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=20150317163210.0b647580@pomiot.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@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