On Friday 2016-12-16 00:05, Kristoffer Grönlund wrote:
Luke Jones <luke.nukem.jones@gmail.com> writes:
At present the build process is relying on the previous version of Rust being packaged with a naming scheme of 'rustc-1_11' for example, which is used for building the next version of Rust.
The issue I have with this is that we will end up with a large amount of previous versions at some point[...] [approaches:] 1. including the bootstrap tarball (for each arch) with the src rpm. 2. use the bootstrap tarballs to build the current compiler version 3. use spec file functionality to choose which tarball arch to use based on the cpu arch being built for.
4. Two concurrent versions Steps: When rust N=S+1 comes along: 1. have d:l:r/rustc-S use rustc-S 2. set d:l:r/rustc-N to <useforbuild>no</useforbuild> 3. have d:l:r/rustc-N use rustc-S 4. Create linked package for rustc-N 5. Eliminiate useforbuild in linked package 6. SR rustc S & N to Factory This is more or less the gcc approach, except that gcc has a lot bigger span than +1, because it's not as immature as rust. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org