Page MenuHomePhabricator

webservice and webservice-runner have no man pages
Closed, DeclinedPublic

Event Timeline

scfc raised the priority of this task from to Low.
scfc updated the task description. (Show Details)
scfc added a project: Toolforge.
scfc moved this task to Ready to be worked on on the Toolforge board.
scfc subscribed.

We should / can kill webservice from the repo now, it isn't used anywhere (webservice2 is the default webservice now).

We can just put help files in --help there maybe?

I know, but I want to put webservice{,2} back in the repository. IIRC you pulled it out of there to hot-fix some issues, and now that these have been worked out and after you'll build in the bigbrother replacement, there's no longer a need to pass on tests & Co. (or need +2 from ops). When I review changes, I have a hard time figuring out the semantics of the different options and how they are affected, and I want my laziness back and let Jenkins do the work :-).

Debian's policy for man pages is AFAICS not that they should be there only for executables installed from a package, but that for each command, a user can find a manual by typing man command. So in theory, I would jot down a man page for executables installed by Puppet as well, but with no linter nagging in the past it was easier to just explain how portgrabber works when a user asked for the man page.

scfc renamed this task from webservice/webservice2 have no man pages to webservice and webservice-runner have no man pages.Feb 7 2017, 5:09 PM

Change 437054 had a related patch set uploaded (by Nehajha; owner: Nehajha):
[operations/software/tools-webservice@master] Man page for webservice

@scfc could you help reviewing the proposed change by @Nehajha ?

Change 437054 abandoned by BryanDavis:

[operations/software/tools-webservice@master] Man page for webservice


dcaro subscribed.

I think this is less relevant now, it will be replaced by an api + thin cli relatively soon.