Bug #54638 for Getopt-Long-Descriptive: Generate pod from the options spec

Hi In my fork, I generate pod in the ::Usage object http://github.com/goraxe/Getopt-Long-Descriptive I spoke to you on IRC and suggested G:L:D was not the home for this, and Pod::Weaver may be a better fit. Example of the pod I'm generating is attached Cheers Goraxe

going to print usage as pod =head1 NAME dbicadmin =head1 SYNOPSIS dbicadmin: [-CcDdfhIiinpqrSstuuv] [long options...] =head1 OPTIONS =over =back =head2 Actions =cut =over =item B<--create> or B<-c> Create version diffs needs preversion =cut =item B<--upgrade> or B<-u> Upgrade the database to the current schema =cut =item B<--install> or B<-i> Install the schema to the database =cut =item B<--deploy> or B<-d> Deploy the schema to the database =cut =item B<--select> or B<-s> Select data from the schema =cut =item B<--insert> or B<-i> Insert data into the schema =cut =item B<--update> or B<-u> Update data in the schema =cut =item B<--delete> or B<-D> Delete data from the schema =cut =item B<--op> compatiblity option all of the above can be suppied as --op=<action> =cut =item B<--help> or B<-h> display this help =cut =item B<--pod> Output this usage as pod =cut =back =head2 Options =cut =over =item B<--schema-class> or B<--schema> or B<-C> The class of the schema to load =cut =item B<--resultset> or B<--resultset_class> or B<--class> or B<-r> The resultset to operate on for data manipulation =cut =item B<--config-stanza> or B<-S> Where in the config to find the connection_info, supply in form MyApp::Model::DB =cut =item B<--config> or B<-f> Supply the config file for parsing by Config::Any =cut =item B<--connect-info> or B<-n> Supply the connect info as additonal options ie -I dsn=<dsn> user=<user> password=<pass> =cut =item B<--connect> Supply the connect info as a json string =cut =item B<--sql-dir> or B<-q> The directory where sql diffs will be created =cut =item B<--sql-type> or B<-t> The RDBMs flavour you wish to use =cut =item B<--version> or B<-v> Supply a version install =cut =item B<--preversion> or B<-p> The previous version to diff against =cut =item B<--set> JSON data used to perform data operations =cut =item B<--lib> or B<-I> Additonal library path to search in =cut =item B<--attrs> JSON string to be used for the second argument for search =cut =item B<--where> JSON string to be used for the where clause of search =cut =item B<--force> Be forceful with some operations =cut =item B<--trace> Turn on DBIx::Class trace output =cut =item B<--quiet> Be less verbose =cut =back