>> fossil server ?-P|--port TCPPORT? ?--service-install? >> ?--service-remove? ?REPOSITORY?
> I don't think that this a good idea because the "service" command > has several sub-commands. > > It is probably better to change the command-name from "service" > to e.g. "winsvc" Althouth "winsvc" could also be a good solution, what other sub commands, appart from "install" and "remove" do you really need? I understand that "start" and "stop" can be managed automatically, or for special cases, from the Windows GUI directly. RR 2011/7/19 Thomas Schnurrenberger <t...@gmx.net>: > On 19.07.2011 17:47, Ramon Ribó wrote: >> >> In my opinion, the name "service" is too generic and too windows >> specific. Fossil can give us a lot of services, apart from using the >> Windows services feature. >> >> I agree with another poster that a good solution could be to make it >> a subcommand of "server". How many times is people going to >> install/uninstall the service? >> >> Something like: >> >> fossil server ?-P|--port TCPPORT? ?--service-install? >> ?--service-remove? ?REPOSITORY? >> > I don't think that this a good idea because the "service" command > has several sub-commands. > > It is probably better to change the command-name from "service" > to e.g. "winsvc" > > -- > tsbg > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
