mirrors/fdroidserver
1
0
Fork 0
mirror of https://github.com/f-droid/fdroidserver.git synced 2025-09-13 14:32:28 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

New field: scandelete, like scanignore but deleting

Browse source 
Also, many improvements:

* scanning algorithm is much clearer
* Now paths start by '/', which means the repo dir root.
  - If they don't, '/' is added
  - If they start by './', the dot is removed
  - If "." is in the paths, it is replaced by "/"
* Handling/removing of problems is much easier
* Removed last initfun/funambol bits
This commit is contained in:
Daniel Martí 2013-11-01 13:46:19 +01:00
parent d507b2e894
commit e07d35f913
2 changed files with 58 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/fdroid.texi
View file

@ -346,7 +346,7 @@ Along similar lines (and only in conjunction with @code{--test}, you can use
@code{--force} to force a build of a Disabled application, where normally it
would be completely ignored. Similarly a version that was found to contain
ELFs or known non-free libraries can be forced to build. See also —
scanignore= in the Build Version section.
scanignore= and scandelete= in the Build Version section.
If the build was unsuccessful, you can find out why by looking at the output
in the logs/ directory. If that isn't illuminating, try building the app the
@ -908,17 +908,17 @@ You can use $$SDK$$, $$NDK$$ and $$MVN3$$ to substitute the paths to the
android SDK and NDK directories, and maven 3 executable respectively e.g.
for when you need to run @code{android update project} explicitly.
@item initfun=yes
Enables a selection of mad hacks to make com.funambol.android build.
Probably not useful for any other application.
@item scanignore=path1;path2;...
Enables one or more files/paths to be exlcuded from the scan process.
This should only be used where there is a very good reason, and
probably accompanied by a comment explaining why it is necessary.
When scanning, files whose relative paths start with any of the paths
given here are ignored.
When scanning the source tree for problems, matching files whose relative
paths start with any of the paths given here are ignored.
@item scandelete=path1;path2;...
Similar to scanignore=, but instead of ignoring files under the given paths,
it tells f-droid to delete the matching files directly.
@item build=xxxx
As for 'prebuild', but runs during the actual build phase (but before the