From: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA docs
Date: Fri, 26 Jul 2002 02:51:16 +0900 [thread overview]
Message-ID: <3D403A94.2070308@boosthardware.com> (raw)
In-Reply-To: 3D402F7D.3010405@boosthardware.com
I'm looking into ways to automate the modules options component file for
the docs.
At the moment I am considering using perl or mysql. Does anyone know
which is easier to setup to do the following.
Parse the INSTALL file for a module name.
Return the info for that module.
Then either
Write the module info to a temp file which is inserted into the template
or
insert the module info into the template.
The problem with mysql is that I would need access to the database. The
good thing is that it wouldn't have to get the info everytime a webpage
was accessed only when the info changed. (I think)
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
next prev parent reply other threads:[~2002-07-25 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 16:17 ALSA docs Patrick Shirkey
2002-07-19 17:39 ` Takashi Iwai
2002-07-21 6:40 ` Patrick Shirkey
2002-07-25 16:20 ` Patrick Shirkey
2002-07-25 16:32 ` Paul Davis
2002-07-25 17:03 ` Patrick Shirkey
2002-07-25 17:51 ` Patrick Shirkey [this message]
2002-07-27 0:15 ` Paul Davis
2002-07-29 4:38 ` Patrick Shirkey
2002-07-29 12:08 ` Paul Davis
2002-07-29 17:55 ` Patrick Shirkey
2002-07-29 18:12 ` Paul Davis
2002-07-29 19:12 ` Patrick Shirkey
2002-07-29 20:25 ` Patrick Shirkey
2002-07-27 0:20 ` Paul Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D403A94.2070308@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox