Re: Status of Debian Policy
> On Sun, 15 Jun 1997, Jim Pick wrote:
> > > > All packages that provide HTML documentation should register these
> > > > documents to the menu system, too. Check out section section 4.1, `Web
> > > > servers and applications' for details.
> > >
> > > Is that as well as registering with dwww?
> > I'm changing the way documents register themselves with dwww (again).
> > Hopefully, I'll get enough accomplished so that I can upload
> > something to experimental today. I wouldn't encourage anybody to
> > register their documents with dwww just yet, since it's all going
> > to change. Hopefully, I'll get past the prototype stage in the
> > next month or so, and there will be a standard supported way of
> > registering documents with dwww.
> I'm somehow confused now. Is registering to "dwww" any different from the
> "menu" system? Joost, perhaps you can give use some hints here (I think
> Jim is offline now).
It used to be the same, and that's why I also asked Jim about that.
But he seems to have something different in mind, I'm not quite sure
what he does have in mind though. Also I'm not sure it's better than
what we have currently, but anyway, here's an email he sent me:
(I hope Jim doesn't mind me reproducing it, but it seems he isn't
telling any secrets here)
Jim> > Is that via menu, or directly via dwww?
Jim> It's going to be very similar to the way menu works (I might steal some
Jim> code). I'm going to have a directory under /usr/lib/dwww/menudata
Jim> which will accept files similar to the way /usr/lib/menu works. I'll
Jim> probably have an /etc/dwww/menudata directory too, for local additions.
Jim> There will also be additional directories to accept "method" programs
Jim> for actually rendering the various parts of the dwww-menu heirarchy.
Jim> Also, there will be another directory for other "method" programs to
Jim> handle searching. The idea is that any package can easily extend
Jim> or modify the behaviour of dwww.
Jim> Instead of pre-rendering most of the pages, dwww will call
Jim> the dwww-menu "method" programs to render the pages on the fly.
Jim> Depending on the what the "method" program does, it might simply
Jim> build a page from dwww-menu items in /usr/lib/dwww/menudata - or
Jim> it might use other data sources (even other CGI scripts). I'll have
Jim> to redesign the cacheing mechanism a bit - it might make sense to
Jim> dump "dwww-cache", and use something like squid instead.
Jim> I've built a little program which reads all the /var/lib/dpkg/info/*.list
Jim> files, and pumps them though the "frcode" program that comes with
Jim> findutils. That way, I can use the "locate" program to provide similar
Jim> functionality to "dpkg -L" and "dpkg -S", except that most queries return
Jim> in less than 2 seconds. It works so well, I'm thinking of making a
Jim> separate "dlocate" program so that it can be used from the command line.
Jim> The dwww-menu entries will probably be in a pseudo-SGML type of format.
Jim> When I get enough time to actually learn how all the SGML tools work, I
Jim> might rework it to use a real SGML DTD. I figure that SGML will be a
Jim> good fit, since the output is going to always be HTML.
Jim> There are quite a few other things I want to add - when I'm done, it's
Jim> going to look nothing like the current dwww. The nice thing is, it will
Jim> be broken into separate pieces, so it will be easy for many people to
Jim> work on it and improve it simultaneously.
Jim> - Jim
joost witteveen, firstname.lastname@example.org
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .