First, I'm a huge proponent of having a single place to look for command line scripts... honestly, I wasn't aware of scripts outside of ./debian/command_line/, and I'm someone who actively looks for command line scripts.
Would it be possible to make the scripts less dependent on being packaged? My impression is that a lot of the reasons for the dependency is hard coded paths, which probably aren't a good idea anyway... most of the scripts explicitly run under bash, which allows setting default values of shell variables, so it should be straightforward to set defaults which would allow the scripts to be extended to allow other paths while still being drop-in replacements for existing scripts.
2015-06-28 16:52 GMT-03:00 Mirko Tietgen <mirko@abunchofthings.net>:I have written two patches today which already existed. One, because
I misunderstood something, the other because I searched for a bug in
(and added my patch to) »packaging«, while the solution was in
»Command-line Utilities«.
Apart from having learned to take sunday off instead of writing
redundant code, I wonder why we have these two categories which seem
to be confusing to everyone. Take a look and you will see what I
mean, there is a lot of koha-* scripts in both.
Can we agree on having all command-line stuff used exclusively with
package installations in »packaging« in the future?I agree, those are command-line scripts, that happen to be shipped with the packages for now, but separation should be done to aid reporting.--Tomás Cohen AraziProsecretaría de InformáticaUniversidad Nacional de CórdobaGPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/