>>>>> Jonathan Nieder <jrnie...@gmail.com> writes: >>>>> Ivan Shmakov wrote:
>> Although rarely used, Lynx implementation of CGI is actually enough
>> for Gitweb to work (e. g., for testing purposes.) Like:
[…]
> Very interesting. In the next upload[1] the plan is for the main git
> package to provide gitweb (to support "git instaweb" better) and the
> gitweb package to only provide configuration and documentation:
> $ dpkg -L gitweb
> /.
> /etc
> /etc/apache2
> /etc/apache2/conf.d
> /etc/apache2/conf.d/gitweb
> /etc/gitweb.conf
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/gitweb
> /usr/share/doc/gitweb/examples
> /usr/share/doc/gitweb/examples/index.aux-generation
> /usr/share/doc/gitweb/NEWS.Debian.gz
> /usr/share/doc/gitweb/README.Debian
> /usr/share/doc/gitweb/README
> /usr/share/doc/gitweb/changelog.Debian.gz
> /usr/share/doc/gitweb/changelog.gz
> /usr/share/doc/gitweb/copyright
> /usr/lib
> /usr/lib/cgi-bin
> /usr/lib/cgi-bin/gitweb.cgi -> ../../share/gitweb/gitweb.cgi
> $
> Based on your request, I am tempted to put gitweb.conf and some gitweb
> documentation in the main git package, too,
It's my opinion that the documentation accompanying the software
packaged should always go either into the package itself, or
into the corresponding “-doc” package.
Thus, if gitweb is to be moved to the git package, the
documentation should either go into git, or git-doc.
> and make the role of the gitweb package backward compatibility
I'd second on this.
> and autoconfiguration with those webservers (apache) that support it.
I see nothing wrong with the main git package providing
autoconfiguration for Web servers.
In particular, while configuring an unsupported Web server to
work with gitweb, the administrator may choose to consult the
Apache configuration files. Having to install Apache to do just
that may be too inconvenient.
It's not uncommon to have seemingly “useless” files of such a
kind. As an example, I could vaguely recall that there're
(were?) a dozen or so packages that provide a /etc/logrotate.d/
file without actually mentioning logrotate in the dependencies.
Consider, e. g.:
$ dpkg -s dpkg | grep logrotate
/etc/logrotate.d/dpkg 782ea5ae536f67ff51dc8c3e2eeb4cf9
$ dpkg -L dpkg | grep logrotate
/etc/logrotate.d
/etc/logrotate.d/dpkg
$
>> Therefore, I deem the current Depends: on apache2 | httpd as
>> somewhat too tight. Could it please be loosened?
> Yes, it could be loosened to a Recommends, though see above for an
> alternative solution.
No objections on moving all the contents of the gitweb package
to the main git package (provided that it will never negatively
affect the dependencies of the latter), and, if necessary,
git-doc, and retaining the gitweb package for compatibility /
transition.
> Side note: have you thought about adding lynx support to git instaweb
> (git-instaweb.sh in the source)? It sounds to me like this could be
> fairly simple. If interested, g...@vger.kernel.org (no subscription
> required) with cc to Jakub Narebski <jna...@gmail.com> would
> presumably be the one to contact.
I've never used git instaweb, but I may check it out. Thanks
for the pointer.
> Thanks for a pointer.
[…]
> [1]
> - git://repo.or.cz/debian-git/jrn.git proposed-updates
> - http://repo.or.cz/w/debian-git/jrn.git
> - http://mentors.debian.net/debian/pool/main/g/git/git_1.7.4~rc3-0.0.1.dsc
--
FSF associate member #7257
pgpNUAPIM3FIy.pgp
Description: PGP signature
