Re: Re: status of Knoppix as build platform

Bill Immerman <[email protected]>
Newsgroups gmane.linux.bbc.devel
Message-ID <[email protected]>
Nate, thanks for lots of good info in your response. I've got one small 
clarification:

You replied:

 > Well, the default GARCHIVEROOT is /var/www/garchive.  If you build
 > your garchive in that directory, and you're running apache with
 > DocumentRoot set to /var/www (the default for Debian's apache
 > package), then your garchive is on the web. If it's a server on a
 > local network, then just add http://<your-server's-name>/garchive/ to
 > the end of FILE_SITES in gar.conf.mk so that it is preferred over
 > sites that are out on the Internet.  If your DocumentRoot is
 > different, adjust GARCHIVEROOT to suit.

(1) I needed $(DISTNAME)/ after garchive/; this was why it hadn't worked 
for me when I tried it 
earlier:  http://<your-server's-name>/garchive/$(DISTNAME)/

(2) Consider updating the description of FILE_SITES in garvariables.txt from:

This contains a space-separated list of file:// URLs to locations
where downloadable files (source archives and patches) on the local
system.

to:

This contains a space-separated list of URLs to locations
where files (source archives and patches) can be downloaded. When fetching 
files
with gar, these locations are tried, in turn, before trying the upstream 
location(s)
specified in the package Makefile. Order them according to the 
desirablility of
download sites (e.g., closest sites first).

(3) Consider adding to the comment in faq.txt regarding web service of a 
garchive::

[If you don't want your garchive to live in /var/www/garchive, then
you'll want to change GARCHIVEROOT to the directory where you want to
keep your tarballs.  If you have a Web server, you can point it at
that dir and share your garchive as a local cache to machines on your
network!] Add the URL of this Web server to FILE_SITES on another
gar build host to access this garchive.

Thanks again,
Bill
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.