On Wed, Jun 26, 2013 at 7:35 PM, Robin Sheat ro...@catalyst.net.nz wrote:
Tomas Cohen Arazi schreef op wo 26-06-2013 om 11:31 [-0300]:
My proposal is that koha-* commands shouldn't be Debian (.deb)
specific.
There are a number of assumptions that the scripts make about being in a
Debian-y
I've been thinking and sharing with some an idea I want to share with all
of you.
Since I stepped into Koha's world I've been focused (sometimes obsessively,
I should admit) on the user POV. Specifically on the ways to deploy,
maintain and finally use koha.
We are now encouraging people to use
Hi,
On Wed, Jun 26, 2013 at 7:31 AM, Tomas Cohen Arazi tomasco...@gmail.com wrote:
My proposal is that koha-* commands shouldn't be Debian (.deb) specific.
I agree, there is nothing that seems inherently Debian-specific to the
Koha instance and cluster management scripts. Making them available
On Wed, Jun 26, 2013 at 11:57 AM, Galen Charlton g...@esilibrary.com wrote:
Hi,
On Wed, Jun 26, 2013 at 7:31 AM, Tomas Cohen Arazi tomasco...@gmail.com
wrote:
My proposal is that koha-* commands shouldn't be Debian (.deb) specific.
I agree, there is nothing that seems inherently
Hi,
On Wed, Jun 26, 2013 at 8:17 AM, Tomas Cohen Arazi tomasco...@gmail.com wrote:
What I propose is fixing those standing divergences (things available in
tarball installs should seaminlessly be available on packages setups) and
then make Makefile.PL arrange stuff like packages do. Packages
Tomas Cohen Arazi schreef op wo 26-06-2013 om 11:31 [-0300]:
My proposal is that koha-* commands shouldn't be Debian (.deb)
specific.
There are a number of assumptions that the scripts make about being in a
Debian-y environment, particularly how the init scripts work, location
of lock files,
