mirror of
https://github.com/f-droid/fdroidserver.git
synced 2025-09-13 22:42:29 +03:00
manual: Don't reuse scanignore doc in scandelete
This commit is contained in:
parent
a782a615c6
commit
664f6e4adb
1 changed files with 6 additions and 4 deletions
|
@ -980,11 +980,13 @@ When scanning the source tree for problems, matching files whose relative
|
||||||
paths start with any of the paths given here are ignored.
|
paths start with any of the paths given here are ignored.
|
||||||
|
|
||||||
@item scandelete=<path1>[,<path2>,...]
|
@item scandelete=<path1>[,<path2>,...]
|
||||||
Similar to scanignore=, but instead of ignoring files under the given paths,
|
When running the scan process, any files that trigger errors - like binaries -
|
||||||
it tells f-droid to delete the matching files directly.
|
will be removed. It acts just like scanignore=, but instead of ignoring the
|
||||||
|
files, it removes them.
|
||||||
|
|
||||||
When scanning the source tree for problems, matching files whose relative
|
Useful when a source code repository includes binaries or other unwanted files
|
||||||
paths start with any of the paths given here are removed.
|
which are not needed for the build. Instead of removing them manually via rm=,
|
||||||
|
using scandelete= is easier.
|
||||||
|
|
||||||
@item build=xxxx
|
@item build=xxxx
|
||||||
As for 'prebuild', but runs during the actual build phase (but before the
|
As for 'prebuild', but runs during the actual build phase (but before the
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue