On Fri, 22 Mar 2019 at 22:15:17 +0100, William Gathoye wrote:
> 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).
No idea, that's a question for releng (cloph). In the meantime you can
read the source:
https://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update
(Note that I never claimed that using the update check system would
solve your use-case :-P)
--
Guilhem.
--
To unsubscribe e-mail to: [email protected]
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/website/
Privacy Policy: https://www.documentfoundation.org/privacy
