The easiest option usually involves engaging a Koha consultant or consulting company. There is a list on the website - Paid Support. Sent from Samsung Mobile -------- Original message -------- From: Vijaya Kumar <kumarjammala@gmail.com> Date:20/09/2014 11:36 (GMT+05:30) To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Koha-devel Digest, Vol 106, Issue 27 GOOD MORNING KOHA USERS,    KINDLY ARRANGE TO SEND EASY METHOD  RELATAED TO HOW TO INSTALL KOHA SOFTWARE ON LINUX  PLATFORM. THANKING YOU YOU, YOURS SINCERELY DR.J.VIJAYA KUMAR On Fri, Sep 19, 2014 at 3:30 PM, <koha-devel-request@lists.koha-community.org> wrote: Send Koha-devel mailing list submissions to         koha-devel@lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit         http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to         koha-devel-request@lists.koha-community.org You can reach the person managing the list at         koha-devel-owner@lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics:    1. Re: Conventions for CLI scripts (Mark Tompsett)    2. Re: Conventions for CLI scripts (Owen Leonard)    3. Koha Developer IRC meeting 23 September 2014 at 15:00     and       22:00 UTC (Tomas Cohen Arazi)    4. Re: Conventions for CLI scripts (Robin Sheat) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Sep 2014 09:29:42 -0400 From: "Mark Tompsett" <mtompset@hotmail.com> To: "Koha Devel" <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Conventions for CLI scripts Message-ID: <BLU172-DS12DBBBF2EE72A0544E626FC6B70@phx.gbl> Content-Type: text/plain; format=flowed; charset="utf-8";         reply-type=original Greetings,

     1. There are two directions for this:              I. By default the action will be performed, unless you add                 an argument (--dry-run for example.)             II. By default the action will not be performed, unless you                 add an argument (--commit for example.)

If you run a script called DestroyTheDatabase, you would expect the default action to be complete and utter deletion. I think a dry-run flag would make sense for this type of script. The problem is those scripts whose name is not indicative of DB modifications. I suspect you are thinking about checkNonIndexedBiblios.pl which only runs if you include -c, much like point 1 subsection II. The name doesn't suggest default modifications. In this case, you have to add the -z which will then insert the non-indexed Biblios into the zebra queue. This is like the second method. Can we have a mix? Does a mix make any sense? This kind of reminds me of the help for scripts issues I was wondering about. I see a script name, other than reading the code, how do I get a sample use page? Do we force help on users if no parameters are passed? Do we expect a particular letter or phrase? --help -h --usage --examples --something-else? checkNonIndexedBiblios.pl does it both ways.

     2. What do we want to call the options, whichever way is picked?              I. Keeping in mind that some things (-c for example) can                 conflict with other conventions.

Are there different conventions to choose from? How does Debian (Ubuntu, etc.) do it?

     3. Are there any other conventions we should deal with at the same         time?

None of which I am aware. [SNIP] +1 on the turning off  auto-commit, so dry runs do the same as actual runs. +1 on the explicit rollback or commit.

        $dbi->begin_work;

Actually, I guess that is a nicer way of doing this? # Start transaction $dbh->{AutoCommit} = 0; $dbh->{RaiseError} = 1; GPML, Mark Tompsett ------------------------------ Message: 2 Date: Thu, 18 Sep 2014 09:37:33 -0400 From: Owen Leonard <oleonard@myacpl.org> To: Koha Devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Conventions for CLI scripts Message-ID:         <CAO4qe2PLYna57wQqeFX56KXK=rS_235Bdf2YSVnd03wO063h9g@mail.gmail.com> Content-Type: text/plain; charset=UTF-8

Do we force help on users if no parameters are passed?

As a non-expert in command line things, this is what I would expect. At the very least a brief help, with the suggestion that passing --help would give more.  -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org ------------------------------ Message: 3 Date: Thu, 18 Sep 2014 12:05:23 -0300 From: Tomas Cohen Arazi <tomascohen@gmail.com> To: koha-devel <koha-devel@lists.koha-community.org> Subject: [Koha-devel] Koha Developer IRC meeting 23 September 2014 at         15:00   and 22:00 UTC Message-ID:         <CABZfb=X94ca854xgq0enhSj+4iemD1ez1zm3S_99nrU2B8S96A@mail.gmail.com> Content-Type: text/plain; charset="utf-8" I'm calling for a dev meeting next week, dedicated to DBIC discussions. We'll have DBIC's Peter Rabbitson on the IRC channel to hear his POV too. He can attend 15:00 UTC only though. I'll be happy to have all positions explicitly stated, and discussed. If we can make a decision, that's bonus points. Please send me your POV so I can put that on the wiki to sumarize what we already discussed. Otherwise, i'll do my best to be impartial. -- Tom?s Cohen Arazi Prosecretar?a de Inform?tica Universidad Nacional de C?rdoba ? +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765  E225 0A27 2EA1 B2F3 C15F