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

Update the docs to better explain RM/branch

Browse source
This commit is contained in:
Daniel Martí 2013-06-24 20:23:35 +02:00
parent c46abf6b14
commit 684b8509e8
1 changed files with 9 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/fdroid.texi
View file

@ -938,18 +938,20 @@ available and the upstream developer keeps us posted on new versions.
in the source repository is checked. The appropriateness of this method depends in the source repository is checked. The appropriateness of this method depends
on the development process used by the application's developers. You should not on the development process used by the application's developers. You should not
specify this method unless you're sure it's appropriate. specify this method unless you're sure it's appropriate.
It currently works for every repository type excepting bzr. For git repos, the It currently works for every repository type to different extents. For git,
branch used defaults to master. You may specify your own by using git-svn and hg repo types, you may use "RepoManifest/yourbranch" as UCM so
"RepoManifest/yourbranch" as UCM. The same applies to hg, in which case the that "yourbranch" would be the branch used in place of the default one. The
default value is the "default" branch. default values are "master" for git, "default" for hg and none for git-svn (it
stays in the same branch). On the other hand, branch support hasn't been
implemented yet in bzr and svn, but RepoManifest may still be used without it.
@item @item
@code{Tags} - The AndroidManifest.xml file in all tagged revisions in the @code{Tags} - The AndroidManifest.xml file in all tagged revisions in the
source repository is checked, looking for the highest version code. The source repository is checked, looking for the highest version code. The
appropriateness of this method depends on the development process used by the appropriateness of this method depends on the development process used by the
application's developers. You should not specify this method unless you're sure application's developers. You should not specify this method unless you're sure
it's appropriate. It currently only works for git and git-svn repositories. In it's appropriate.
the case of the latter, the repo URL must encode the path to the trunk and It currently only works for git and git-svn repositories. In the case of the
tags. latter, the repo URL must encode the path to the trunk and tags.
@item @item
@code{Market} - This is being phased out and should only be used when the other @code{Market} - This is being phased out and should only be used when the other
automatic modes don't work. automatic modes don't work.