PROCESS::<%ENV> := Rakudo::Internals.createENV(0);
my constant %?ENV = Rakudo::Internals.createENV(1);

Rakudo::Internals.REGISTER-DYNAMIC: '$*CWD', {
#    PROCESS::<$CWD> = nqp::p6box_s(nqp::cwd());
    my $CWD := nqp::p6box_s(nqp::cwd());
    PROCESS::<$CWD> = IO::Path.new($CWD, :$CWD); # need :CWD to prevent looping
}

# vim: ft=perl6 expandtab sw=4

PROCESS::<%ENV> := Rakudo::Internals.createENV(0);

Rakudo::Internals.REGISTER-DYNAMIC: '$*CWD', {
#    PROCESS::<$CWD> = nqp::p6box_s(nqp::cwd());
    my $CWD := nqp::p6box_s(nqp::cwd());
    PROCESS::<$CWD> = IO::Path.new($CWD, :$CWD); # need :CWD to prevent looping
}

# vim: ft=perl6 expandtab sw=4

Revert "Implement %?ENV for the core setting"
Revert "Implement %?ENV for the core setting"

This reverts commit d3e8c82dc2f14b2bf1e41a39982644d33c8c47b2.

Baking ENV into CORE.setting.moarvm at compile time prevents packaging rakudo
for openSUSE as the rpm linter rightfully complains about the BUILDROOT path
being included in the compiled file. This would also include much more
information about the build server than the user should be able to get.

As we don't know any use case for this unspecced and untested feature anyway,
it's better to remove it.
