2001-01-24 00:31:17 +00:00
|
|
|
<sect1 id="ch02-download">
|
2002-05-30 00:15:53 +01:00
|
|
|
<title>Where to store the downloaded software</title>
|
2001-09-26 00:48:31 +01:00
|
|
|
<?dbhtml filename="download.html" dir="chapter02"?>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2001-08-29 17:56:32 +01:00
|
|
|
<para>Throughout this document, we will assume that all the
|
2001-07-22 20:45:10 +01:00
|
|
|
packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-04-29 16:06:46 +01:00
|
|
|
<para>While it doesn't matter at all where you save the downloaded
|
2002-09-22 04:01:40 +01:00
|
|
|
packages, we recommend storing it at least on the LFS partition. This
|
|
|
|
just makes sense because you need to have access to those those files
|
|
|
|
when you chroot to $LFS and when you boot into the LFS system, although
|
|
|
|
access when booted to $LFS could be handled other ways. $LFS/usr/src is
|
|
|
|
just a logical place to store source code, but by no means a requirement.
|
|
|
|
You may even want to create a subdirectory under $LFS/usr/src for tarball
|
|
|
|
storage. That way you can separate tarballs from temporary build
|
|
|
|
directories, but again that's up to you.</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-04-29 16:06:46 +01:00
|
|
|
<para>The next chapter contains a list of all the packages that need to be
|
|
|
|
downloaded. The LFS partition isn't created yet, so you can't store it
|
|
|
|
there yet. Just save it elsewhere for now, and when the LFS partition is
|
|
|
|
created, move them over.</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
</sect1>
|
|
|
|
|