On Dec 09, 2018, at 10:32 AM, Ken Moffat via blfs-support
<[email protected]> wrote:
On Sun, Dec 09, 2018 at 08:53:18AM +0100, Pierre Labastie via blfs-support
wrote:
On 09/12/2018 05:21, Hans Malissa via blfs-support wrote:
Great, thanks a lot for the explanation!
The 'SVN version', is that's what's listed under 'current development'?
Almost: SVN version can be one day ahead ;)
Pierre
I meant the rendered version which is available online ;)
And to expand on that: for new versions of packages we create
tickets, and the changelog entry 'Fixes #1234' will be a link to the
ticket.
Usually the ticket lists what upstream think they changed/fixed.
Sometimes there are security issues - if we know about these we
might raise the severity of the ticket.
For a lot of packages, upgrading from what is in 8.3 is not
important - unless a fix addresses an issue important to you.
And mostly, upgrading versions of dependencies is not critical (so,
for example, llvm-6 is still good-enough if you have already built
it). For firefox, the version of rust in the development book only
gets upgraded when necessary.
Okay, thanks a lot for the explanation. I'm comparing the 'rustc' sections in
the stable (8.3-systemd) and development version (2018-12-11 systemd) versions
of the book. They seem to be fairly similar; the only differences I see are the
version numbers of rustc (1.25.0 vs. 1.29.2), the version numbers of the
dependencies, the 'quiet-tests = true' statement, and the actual install
command ('export LIBSSH2_SYS_USE_PKG_CONFIG=1'). Given that the version numbers
of the dependencies may not be critical (as explained above), what makes the
8.3-systemd version of rustc unsuitable for firefox? Is it just the version
number of rustc?
Thanks a lot,
Hans--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
