mirror of
https://github.com/YunoHost-Apps/ihatemoney_ynh.git
synced 2024-09-03 19:26:15 +02:00
[fix] sync README with reality
This commit is contained in:
parent
161ee92fb5
commit
c3b9424bcc
1 changed files with 3 additions and 20 deletions
23
README.md
23
README.md
|
@ -16,26 +16,9 @@ The behaviour is either :
|
|||
- per-project identifiers required
|
||||
- any visitor can create a new project.
|
||||
|
||||
I currently use
|
||||
[my fork](https://github.com/JocelynDelalande/ihatemoney/tree/ynh-patched)
|
||||
(copied as-is on branch *ynh_patched_upstream*) as
|
||||
|
||||
upstream, waiting for some pull request to enter
|
||||
[official code base](https://github.com/spiral-project/ihatemoney).
|
||||
|
||||
|
||||
Maintainer
|
||||
----------
|
||||
|
||||
I choose to embed the code in my repo, upstream policy is similar to
|
||||
[Debian's](https://wiki.debian.org/PackagingWithGit#Using_the_upstream_repo).
|
||||
|
||||
- the *upstream* branch points to a vanilla (tested) upstream commit
|
||||
- the *master* branch includes yunohost specific files and the right files
|
||||
layout (eg: source is in a *sources* subdir).
|
||||
|
||||
Upgrading source code to a further version is a matter of:
|
||||
|
||||
1. pulling the right commit from upstream git in the upstream branch
|
||||
2. merging upstream into master
|
||||
3. adapting the upgrade script if required
|
||||
I rely on
|
||||
[ihatemoney official releases](https://github.com/spiral-project/ihatemoney/releases)
|
||||
(tarballs). Don't hesitate to pull-request this repo if I missed one :-).
|
||||
|
|
Loading…
Reference in a new issue