#9168: rustc - do not update automatically
-------------------------+------------------------
Reporter: ken@… | Owner: blfs-book
Type: enhancement | Status: new
Priority: normal | Milestone: hold
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+------------------------
Description changed by ken@…:
Old description:
> A statement of a new policy for BLFS.
>
> For the moment rustc and cargo are only in the book because firefox-53
> requires them, although librsvg will need then on its next non-
> development release.
>
> For firefox in particular, it is expected that newer versions of rust
> (that might actually mean cargo) will be required. But rust is a fairly
> heavy build and the release schedules for rust and cargo do not align
> with firefox releases.
>
> To avoid users (particularly those not using workstations) unnecessarily
> rebuilding these packages, do not automatically upgrade either rust or
> cargo in the book.
>
> For firefox, if time permits, I should be able to build a late beta to
> see if the version requirements have changed.
>
> Cargo in itself is not particularly heavy, at least at the moment, but a
> newer release might require a newer rustc.
>
> The downside of not automatically updating every (minor) version of cargo
> is that it may need to use a binary of the previous version, instead of
> bootstrapping from a (current or previous) self-compiled version. But my
> tests with current cargo suggest that bootstrapping afresh from a binary
> is quicker.
>
> If rustc is changed to allow it to build against our current LLVM (so
> that we can drop separate LLVM3), or if vulnerabilities are discovered in
> rust, then upgrade. Otherwise, only upgrade when one of the packages
> using rustc or cargo requires a newer version.
New description:
A statement of a new policy for BLFS.
For the moment rustc and cargo are only in the book because firefox-53
requires them, although librsvg will need then on its next non-development
release.
For firefox in particular, it is expected that newer versions of rust
(that might actually mean cargo) will be required. But rust is a fairly
heavy build and the release schedules for rust and cargo do not align with
firefox releases.
To avoid users (particularly those not using workstations) unnecessarily
rebuilding these packages, do not automatically upgrade either rust or
cargo in the book.
For firefox, if time permits, I should be able to build a late beta to see
if the version requirements have changed.
Cargo in itself is not particularly heavy, at least at the moment, but a
newer release might require a newer rustc.
The downside of not automatically updating every (minor) version of cargo
is that it may need to use a binary of the previous version, instead of
bootstrapping from a (current or previous) self-compiled version. But my
tests with current cargo suggest that bootstrapping afresh from a binary
is quicker.
If rustc is changed to allow it to build against our current LLVM (so that
we can drop separate LLVM3), or if vulnerabilities are discovered in rust,
then upgrade. Otherwise, only upgrade when one of the packages using
rustc or cargo requires a newer version.
Update: cargo has been shipped as part of rust for several releases, so
tidy up the title by removing it.
--
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/9168#comment:12>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
