diff options
author | wm4 <wm4@nowhere> | 2016-06-02 11:48:01 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2016-06-02 11:48:01 +0200 |
commit | 0c3a7914da9a7567f08c60a3fc315a1e4980487d (patch) | |
tree | 3cbef35fdc5c1150066ed8b7a29af9f3ad533d42 /README.rst | |
parent | 11d69fc6ced02c4682945598c34eb4cd07a50c25 (diff) | |
download | mpv-build-0c3a7914da9a7567f08c60a3fc315a1e4980487d.tar.bz2 mpv-build-0c3a7914da9a7567f08c60a3fc315a1e4980487d.tar.xz |
Default to git master branches for almost everything
Diffstat (limited to 'README.rst')
-rw-r--r-- | README.rst | 19 |
1 files changed, 13 insertions, 6 deletions
@@ -162,17 +162,24 @@ In general, changes to the mpv-build repository itself are relatively safe, keeping branches in sub-repositories might be ok, and making local, uncommitted changes in sub-repositories will break. -Forcing master versions for some parts -====================================== +Selecting release vs. master versions +===================================== + +By default, mpv, ffmpeg and libass use the git master versions. These are +bleeding edge, but should usually work fine. To get a stable (slightly stale) +version, you can use release versions. Note that at least for mpv, releases +are not actually maintained - releases are for Linux distributions, which are +expected to maintain them and to backport bug fixes (which they usually fail +to do). The following command can be used to delete all local changes, and to checkout -the current master version for mpv: +the latest release version of mpv: - ./use-mpv-master + ./use-mpv-release -And run ``./rebuild`` or similar. Use this to switch back to the latest release: +And run ``./rebuild`` or similar. Use this to switch back to git master: - ./use-mpv-release + ./use-mpv-master Likewise, you can use ``./use-ffmpeg-master`` and ``./use-ffmpeg-release`` to switch between git master and the latest FFmpeg release. |