I'm thus wondering:
* how the system performs the match between branches and how he keeps
track of the branches (see issue described just above ^)
* and (more interesting for my use case), how to have a build string
that will always work. i.e. a build string that will answer with the
latest version of the still branch and a build string that will
answer with the latest version of the fresh branch. Because at
chocolatey, the update script won't change (as the build id I'll fake).
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.