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

Manual.md: fix instances of noarch=yes

Browse source
This commit is contained in:
maxice8 2019-02-16 03:58:32 -02:00 committed by maxice8
parent 0f76ad0f76
commit 0d03347c7b
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
Manual.md
View file

@ -567,7 +567,7 @@ Example: `conf_files="/etc/foo.conf /etc/foo2.conf /etc/foo/*.conf"`.
- `noarch` If set, the binary package is not architecture specific and can be shared
by all supported architectures.
> NOTE: `noarch` is deprecated and must be replaced by `archs=`
> NOTE: `noarch` is deprecated and must be replaced by `archs=noarch`
- `repository` Defines the repository in which the package will be placed. See
*Repositories* for a list of valid repositories.
@ -835,9 +835,9 @@ can be used to pass arguments during compilation. If your package does not make
extensions consider using the `gem` build style instead.
- `gem` For packages that are installed using gems from [RubyGems](https://rubygems.org/).
The gem command can be overridden by `gem_cmd`. `noarch` is set unconditionally and `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.
The gem command can be overridden by `gem_cmd`. `archs` is set to `noarch` unconditionally
and `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.
- `ruby-module` For packages that are ruby modules and are installable via `ruby install.rb`.
Additional install arguments can be specified via `make_install_args`.
@ -1284,7 +1284,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
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)
or card material (maps). Data subpackages are almost always `noarch=yes`.
or card material (maps). Data subpackages are almost always `archs=noarch`.
The main package must then have `depends="${pkgname}-data-${version}_${revision}"`,
possibly in addition to other, non-automatic depends.
@ -1411,7 +1411,7 @@ The following variables influence how Haskell packages are built:
Font packages are very straightforward to write, they are always set with the
following variables:
- `noarch=yes`: Font packages don't install arch specific files.
- `archs=noarch`: Font packages don't install arch specific files.
- `depends="font-util"`: because they are required for regenerating the font
cache during the install/removal of the package
- `font_dirs`: which should be set to the directory where the package
@ -1448,7 +1448,7 @@ the source of those patches/files.
pkgname=$pkgname
version=$version
revision=$((revision + 1))
noarch=yes
archs=noarch
build_style=meta
short_desc="${short_desc} (removed package)"
license="metapackage"