Go to file
Daniel Martí 6ca3189006 Merge branch 're-enable-lexica-after-buid-fix' into 'master'
Re-enable v0.9.2 of Lexica after fixing build and retagging.

Apologies for pointing the v0.9.2 metadata to a broken build. Don't think I used `-f` during my test `fdroid build`. I'm not sure how semantic versioning usually deals with fixing broken builds, but I left it at v0.9.2, fixed the linter problem during the build, and moved the v0.9.2 tag to the new (hopefully working) commit.

Do you guys have a suggestion about what the usual way for dealing with this is? Do others tend to bump the version number again to, e.g. `v0.9.3`, or perhaps do a `v0.9.2-1`?

See merge request !1151
2016-01-17 18:20:35 +00:00
build
hooks
metadata Merge branch 're-enable-lexica-after-buid-fix' into 'master' 2016-01-17 18:20:35 +00:00
srclibs
stats Update known apks 2016-01-17 10:05:08 +00:00
templates
tools
.gitignore
.gitlab-ci.yml
CONTRIBUTING.md
fdroid-icon.png
LICENSE
README.md

F-Droid Data

build status

This repository holds general and build information for all the apps on our main repo on f-droid.org.

Quickstart

Clone fdroidserver:

git clone https://gitlab.com/fdroid/fdroidserver.git

Add the cloned dir to your PATH:

export PATH="$PATH:$PWD/fdroidserver"

Enter it:

cd fdroiddata

An empty configuration file should work as a start:

touch config.py

Make sure fdroid works and reads the metadata files properly:

fdroid readmeta

Contributing

See the Contributing doc.

More information

You can find more details on the manual.