On Monday, 10 May 2004, at 21:31:38 (-0400), seth vidal wrote: > B/c then I have to follow each rpm release and multiple rpm releases > with any change in the syntax or formatting there so my command line > parsing can: > 1. tell you when something doesn't exist > 2. make any sense at all > 3. be reasonably documented You wouldn't have to mimic the rpm command line parameters as I did. You could choose your own scheme and support any subset of the actual transaction flags. To a certain extent, you're already driven by the capabilities of rpmlib, so supporting a well-established set of flags seems a reasonable course of action to me. Of course, the more closely you mimic the rpm command line parameters, the more existing documentation you can leverage for the meanings of individual keywords. :-) Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <mej@xxxxxxxxx> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "The problem with the gene pool is there's no lifeguard." -- Steven Wright
