doc: Don't mention top-level {build, host, target}Platform
For technical reasons, we cannot easily add a warning to top-level definitions, so2a6e4ae49a
ande51f736076
reverted the deprecation. But we can still remove mention of the would-be deprecated definitions to steer people towards using the preferred alternatives.
This commit is contained in:
parent
359d00f8b0
commit
e39a73cc55
|
@ -47,13 +47,9 @@
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
In Nixpkgs, these three platforms are defined as attribute sets under the
|
In Nixpkgs, these three platforms are defined as attribute sets under the
|
||||||
names <literal>buildPlatform</literal>, <literal>hostPlatform</literal>,
|
names <literal>buildPlatform</literal>, <literal>hostPlatform</literal>, and
|
||||||
and <literal>targetPlatform</literal>. All three are always defined as
|
<literal>targetPlatform</literal>. They are always defined as attributes in
|
||||||
attributes in the standard environment, and at the top level. That means
|
the standard environment. That means one can access them like:
|
||||||
one can get at them just like a dependency in a function that is imported
|
|
||||||
with <literal>callPackage</literal>:
|
|
||||||
<programlisting>{ stdenv, buildPlatform, hostPlatform, fooDep, barDep, .. }: ...buildPlatform...</programlisting>
|
|
||||||
, or just off <varname>stdenv</varname>:
|
|
||||||
<programlisting>{ stdenv, fooDep, barDep, .. }: ...stdenv.buildPlatform...</programlisting>
|
<programlisting>{ stdenv, fooDep, barDep, .. }: ...stdenv.buildPlatform...</programlisting>
|
||||||
.
|
.
|
||||||
</para>
|
</para>
|
||||||
|
|
Loading…
Reference in a new issue