From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Shirkey Subject: Re: ALSA docs Date: Fri, 26 Jul 2002 02:51:16 +0900 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <3D403A94.2070308@boosthardware.com> References: <3D402F7D.3010405@boosthardware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org 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