I'd be interested in having a command to get the manifest of a check-in.
The artifact command comes up short when the check-in happens to have
a delta manifest. I wrote a Tcl script to combine a delta manifest with
its baseline, but I think it would be preferable to expose this
capability already available inside Fossil.
The trouble is the obvious choice of name for this command would be
"fossil manifest", yet "manifest" is already the name of a setting.
[f74f7014] combined the settings with the commands and web pages in the
aCommand table. Should we add a manifest command, there would be two
entries with the same name.
I recently modified dispatch_name_search() to tolerate prefixes being
shared between entries of different types. I can modify it further to
tolerate different-type entries having the same names outright.
However, there's still trouble when eType is CMDFLAG_ANY, i.e. when
dispatch_name_search() is called by help_page() or help_cmd().
What to do? I could give up and continue to use my Tcl script, I could
contribute my Tcl script for others to use, we could call the command
that prints a manifest something other than "manifest", or we could add
an alternative to dispatch_name_search() that can return more than one
result. In that last case, "fossil help manifest" would print help for
both the command and the setting.
Thoughts?
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
