| 1 |
On Sunday 20 June 2004 10:04, Chris W wrote: |
| 2 |
> ht://dig is also listed as requiring webapp-ification in bug |
| 3 |
> http://bugs.gentoo.org/show_bug.cgi?id=53855 |
| 4 |
|
| 5 |
That'll be because it relies on the deprecated webapp-apache eclass. |
| 6 |
|
| 7 |
> After having a quick look at it on Friday I thought that htdig |
| 8 |
> doesn't fit well with the webapps mindset. The bulk of the |
| 9 |
> package is executables for index creation/maintenance that are |
| 10 |
> currently installed into /usr/bin et al. Only htsearch and |
| 11 |
> support HTML/images go into the website directories. While I |
| 12 |
> could maintain that separation under webapps, with a single set |
| 13 |
> of binaries, it would disallow the multiple version support in |
| 14 |
> the webapps concept. Should the binaries be put somewhere else? |
| 15 |
|
| 16 |
In this case, it might make sense to break ht://dig into two packages. Put |
| 17 |
the stuff that goes in /usr/bin et al into one package, and put the stuff |
| 18 |
that goes into /var/www into a separate package. |
| 19 |
|
| 20 |
> I also could not see a clean way for a post-install script to |
| 21 |
> create a separate index databases, configuration files, and |
| 22 |
> search page HTML (per VHOST) given the limited information |
| 23 |
> available to the script. Perhaps I have missed an available |
| 24 |
> environment variable identifying the VHOST name or some such. |
| 25 |
|
| 26 |
man 5 webapp.eclass should have the info you're looking for. |
| 27 |
|
| 28 |
Best regards, |
| 29 |
Stu |
| 30 |
-- |
| 31 |
Stuart Herbert stuart@g.o |
| 32 |
Gentoo Developer http://www.gentoo.org/ |
| 33 |
http://stu.gnqs.org/diary/ |
| 34 |
|
| 35 |
GnuPG key id# F9AFC57C available from http://pgp.mit.edu |
| 36 |
Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C |
| 37 |
-- |
Archives