At 3:15 PM -0500 4/5/00, Gilles Detillieux wrote:
> > Sorry for the problems, but I'll make sure they're fixed for 3.2.0b2
Chalk this one up to a misunderstanding, a lack of documentation and
my head being in other things recently. I'm a bit worried about
merging in a couple largish patches to the same areas of code. So as
I said, I thought it could have been merging all those patches
together.
>I don't think Rajendra's example forms and config file made it into the
>CVS tree either.
No, I'm not quite sure what to do with them... They clearly need to
go in the documentation, and some parts of them need to go into the
default conf file. But what do we want to do with the rest: put them
in contrib? Well, they're not really contrib, they're actually part
of the code. Do we put them in installdir? If so, where should they
go?
One of the recommendations from Doug Barton <[EMAIL PROTECTED]>, who
did the FreeBSD "port" for 3.1.5 is for the installdir forms and
config files.
> We do that on a lot of ports. I would stay away from .orig since that's
>what 'patch' uses. We generally use .default for files that you can just
>copy over and they will work as is, and .sample for example files that
>provide a starting place like the htdig.conf file. It helps a lot,
>especially in cases where the user has to configure files that could be
>deleted by a new install or (in our case) removed when the user deletes
>the package.
I don't know--would users be confused if we installed a few example
config files?
> They'd probably help to figure out how to use this
>feature. If I recall from looking at his patch, the only purpose for
>collection_names was to generate template variables for use in follow-up
>search forms, to check all the check boxes for databases to search.
>Apart from that, it's all handled by multiple definitions of the config
>input parameter.
Right. To use the collections, you'd have one config file per
database as everyone recommends. :-) Then you can either have
multiple config fields, or connect them with '|' characters. So you
could have:
Pick a database:
<select name="config" multiple>
<option value="main">Main
<option value="foobar">Medical
<option value="docs">Documentation
<option value="foobar|docs">Medical & Documentation
</select>
(The example's a bit silly, Rajendra's examples are much better. My
point is that the config attributes can be joined by \001, \t or '|'
characters.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
