On 07/31/2018 03:31 AM, Michał Górny wrote:
> Use an explicit USE_ORDER entry to control mapping FEATURES=test into
> default-enabled USE=test, rather than forcing/masking it depending
> on the state of FEATURES.
>
> This makes it possible for users to enable (or disable) USE=test
> independently
On 07/27/2018 08:25 AM, Brian Dolbec wrote:
> On Fri, 27 Jul 2018 00:56:40 -0700
> Zac Medico wrote:
>
>> Add repos.conf settings that enable sync-openpgp-key-path support for
>> both emerge-webrsync and emerge-delta-webrsync:
>>
>> sync-webrsync-delta = true|false
>> Use
On 07/31/2018 08:42 AM, Brian Dolbec wrote:
> On Sun, 15 Jul 2018 16:02:03 -0700
> Zac Medico wrote:
>
>> For the empty profile that's used to check dependencies of
>> ebuilds that have empty KEYWORDS, populate implicit IUSE
>> from all of the make.defaults files found in the relevant
>>
On 07/31/2018 08:40 AM, Brian Dolbec wrote:
> On Sun, 15 Jul 2018 14:09:24 -0700
> Zac Medico wrote:
>
>> Pass the main-repo name from repos.conf as the repository name
>> for the PORTDIR RepoConfig constructor, so that it can override
>> the main repo location even if the profiles/repo_name
On Sun, 15 Jul 2018 16:02:03 -0700
Zac Medico wrote:
> For the empty profile that's used to check dependencies of
> ebuilds that have empty KEYWORDS, populate implicit IUSE
> from all of the make.defaults files found in the relevant
> repositories (this should take less than 1 second on most
>
On Sun, 15 Jul 2018 14:09:24 -0700
Zac Medico wrote:
> Pass the main-repo name from repos.conf as the repository name
> for the PORTDIR RepoConfig constructor, so that it can override
> the main repo location even if the profiles/repo_name file does
> not exist yet (like in a stage3 tarball).
>
Hello folks,
I apologize to everyone for sending this proposal before it was
finished. It was not voted on by the QA team hence it was not an
official proposal by the QA team. There was probably some
misunderstanding in communication.
After we finish the official draft and it is accepted by QA
On Tue, Jul 31, 2018 at 12:03 PM Luca Barbato wrote:
> > As far as I know, the Rust ecosystem is largely bimodal: stuff is either
> > compatible with stable and later, or it works only on nightly. It seems
> > very rare that code is actually tied to a particular Rust release and
> does
> > not
# Joonas Niilola (31 Jul 2018)
# Old and obsolete. Merged into one EFL package since 1.18 release.
# Removal in ~30 days. Bug #662510
=dev-libs/efl-1.17.0-r1
media-libs/elementary
media-plugins/emotion_generic_players
media-plugins/evas_generic_loaders
x11-themes/ethemes
Note: Upgrading to
> Your PR brokes tree:
> https://github.com/gentoo/gentoo/pull/9388#issuecomment-408914903
>
> Please fix these issues as well, for both QA and CI checks. (These
> problems may be a result of §1 (not yet submitted changes to the
> tree).
Thanks, done.
>
> It would be easier if your will split
Use an explicit USE_ORDER entry to control mapping FEATURES=test into
default-enabled USE=test, rather than forcing/masking it depending
on the state of FEATURES.
This makes it possible for users to enable (or disable) USE=test
independently of FEATURES. An example use case is installing test
On 31/07/2018 09:35, Dirkjan Ochtman wrote:
> On Mon, Jul 30, 2018 at 5:02 PM gibix wrote:
>
> As far as I know, the Rust ecosystem is largely bimodal: stuff is either
> compatible with stable and later, or it works only on nightly. It seems
> very rare that code is actually tied to a
On Mon, Jul 30, 2018 at 5:02 PM gibix wrote:
> This will allows projects like rustfmt, clippy, bindgen that need runtime
> linking with the proper rust version to work correctly. Beyond this while
> rust is getting older as project we will see more projects that will
> require a specific rust
13 matches
Mail list logo
