On Thu, Aug 30, 2018 at 12:31:35AM +0300, Ruslan Kabatsayev wrote:
> On Wed, 29 Aug 2018 at 21:13, Ken Moffat <[email protected]> wrote:
> >
> > > 2. Cargo package registry must be fetched into appropriate location.
> > > This can be done with the following commands (requires git):
> > >
> >
> > <sarcasm>Oh goody, adding another git command.</sarcasm> And the
> > hash will need to be updated for a newer version of rust.
>
> Of course, the actual git command may be replaced in the BLFS
> instructions by a snapshot of the registry at the time of updating to
> newer rustc version. BLFS has a similar thing done with e.g.
> gimp-help-2018-08-21.tar.xz (see the Gimp-2.10.6 page).
>
"A snapshot" is easy - we usually take the latest. But rust has at
least one version which is intended to be the *next* release, so
someboy needs to work out which hash.
Also, "space, the final frontier" - big distros have lots of space
to store downloads, we don't.
> >
> > Unmaintainable.
>
> Do you mean the list of crates is unmaintainable? How come? I suppose,
> when updating to a new version, BLFS maintainer does build the package
> at least once (at least to update estimated build time) and does this
> in the "usual"—online—way. If so, then after build the
> ~/.cargo/registry/cache/*/ directory will contain the necessary
> crates, so the list can easily be updated from this. And the hash
> following "github.com-" can be found too.
>
Until now, I've been the one maintaining this. Sometimes I have
downloaded multiple versions of rust - looking at one of my machines
where user lfs has done the builds - yes, one hash. But within
that, multiple versions of several crates.
> > >
> > > 5. After all these steps you no longer need Internet connection, so
> > > you can simply continue as you would following current BLFS
> > > instructions. I've actually built rustc on an offline machine using
> > > these preparations before going offline, and it worked nicely.
> > >
> > But - you still had to be online to get them.
>
> Of course I do have to be online to download anything, including the
> saner packages like Xorg, which don't try to go online when actually
> building themselves. But once I download everything I need, it should
> be possible to go on a vacation offline with a USB stick, and play
> with (B)LFS without surprises.
>
> >
> > This just seems to add pain.
>
> Well, if all the maintainers here feel the same, I won't pursue this
> further. I just wanted the book to be useful for a bit wider range of
> users.
>
We've got enough trouble maintaining the book as it is, without
expanding how people can build it. To be honest, I'm surprised at
anybody building rust on i686 - it, and the browsers which use it,
are long and large builds on modern x86_64, building on i686
machines will be painful.
ĸen
--
Also Spuke Zerothruster
(Finnegans Wake)
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
