jcgruenhage/void-packages
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Manual.md: remove mentions of noarch, note it should not be used.

Browse source
This commit is contained in:
fosslinux 2020-08-27 17:17:50 +10:00 committed by Daniel Kolesa
parent 7654598016
commit 96cd808ab0
1 changed files with 5 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
Manual.md
View file

@ -711,8 +711,7 @@ used.
- `fetch_cmd` Executable to be used to fetch URLs in `distfiles` during the `do_fetch` phase. - `fetch_cmd` Executable to be used to fetch URLs in `distfiles` during the `do_fetch` phase.
- `archs` Whitespace separated list of architectures that a package can be - `archs` Whitespace separated list of architectures that a package can be
built for, available architectures can be found under `common/cross-profiles` built for, available architectures can be found under `common/cross-profiles`.
alongside the `noarch` value for packages that do not contain any machine code.
In general, `archs` should only be set if the upstream software explicitly targets In general, `archs` should only be set if the upstream software explicitly targets
certain architectures or there is a compelling reason why the software should not be certain architectures or there is a compelling reason why the software should not be
available on some supported architectures. available on some supported architectures.
@ -725,9 +724,8 @@ Examples:
archs="x86_64-musl ~*-musl" archs="x86_64-musl ~*-musl"
# Default value (all arches) # Default value (all arches)
archs="*" archs="*"
# Packages that do not depend on architecture-specific objects
archs=noarch
``` ```
Do not use noarch. It is deprecated and being removed.
<a id="explain_depends"></a> <a id="explain_depends"></a>
#### About the many types of `depends` variable. #### About the many types of `depends` variable.
@ -914,8 +912,8 @@ can be used to pass arguments during compilation. If your package does not make
extensions consider using the `gem` build style instead. extensions consider using the `gem` build style instead.
- `gem` For packages that are installed using gems from [RubyGems](https://rubygems.org/). - `gem` For packages that are installed using gems from [RubyGems](https://rubygems.org/).
The gem command can be overridden by `gem_cmd`. `archs` is set to `noarch` unconditionally The gem command can be overridden by `gem_cmd`.
and `distfiles` is set by the build style if the template does not do so. If your gem `distfiles` is set by the build style if the template does not do so. If your gem
provides extensions which must be compiled consider using the `gemspec` build style instead. provides extensions which must be compiled consider using the `gemspec` build style instead.
- `ruby-module` For packages that are ruby modules and are installable via `ruby install.rb`. - `ruby-module` For packages that are ruby modules and are installable via `ruby install.rb`.
@ -1451,7 +1449,7 @@ type used to split architecture independent, big(ger) or huge amounts
of data from a package's main and architecture dependent part. It is up of data from a package's main and architecture dependent part. It is up
to you to decide, if a `-data` subpackage makes sense for your package. to you to decide, if a `-data` subpackage makes sense for your package.
This type is common for games (graphics, sound and music), part libraries (CAD) This type is common for games (graphics, sound and music), part libraries (CAD)
or card material (maps). Data subpackages are almost always `archs=noarch`. or card material (maps).
The main package must then have `depends="${pkgname}-data-${version}_${revision}"`, The main package must then have `depends="${pkgname}-data-${version}_${revision}"`,
possibly in addition to other, non-automatic depends. possibly in addition to other, non-automatic depends.
@ -1589,7 +1587,6 @@ The following variables influence how Haskell packages are built:
Font packages are very straightforward to write, they are always set with the Font packages are very straightforward to write, they are always set with the
following variables: following variables:
- `archs=noarch`: Font packages don't install arch specific files.
- `depends="font-util"`: because they are required for regenerating the font - `depends="font-util"`: because they are required for regenerating the font
cache during the install/removal of the package cache during the install/removal of the package
- `font_dirs`: which should be set to the directory where the package - `font_dirs`: which should be set to the directory where the package