A. Costa wrote:
> Package: bozohttpd
> Version: 20050410-2
> Severity: wishlist
> 
> I've been trying (and failing) to set up the 'apt-cacher' package** to
> work  under 'bozohttpd'.  It'd help if bozo's docs had something about
> whether it was possible or not***.  To avoid bloat I'd rather avoid
> 'apache'.

I'd say it's apt-cacher's responsibility to say with which web servers
it's compatible.

> (**some texts claim 'apt-cacher' needs 'apache', but it's not presently
> required in its .deb header -- maybe this bug should be moved or cloned
> to that package.)

>From what I've understood, apt-cacher *can* be used with Apache, but
that's not necessary.

> Background:
> 
>     "If everything goes well, the path /apt-cacher on the web server should
>     be accessible from any browser."
> 
>     - from 'Installing apt-cacher'
>     http://taprobane.org/apt-cacher.php
> 
> Whereas bozo's man page says:
> 
>     "...all CGI URL's must begin with /cgi-bin/."
> 
> The URL formats seem to be incompatible.  

According to the Debian Policy:

Cgi-bin executable files are installed in the directory
/usr/lib/cgi-bin/cgi-bin-name and should be referred to as
http://localhost/cgi-bin/cgi-bin-name

If apt-cacher wants to support all Debian cgi enabled web servers, it
should follow those rules. Now it explicitly supports Apache within its
package.

This is an apt-cacher wishlist bug, I will move it over to that project.

-- 
Mattias Nordstrom


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to