-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Joey,

After I got this bug report I spent quite a bit of time trying to
convert the various backupninja bashisms to POSIX so that it would work
with dash/ash. I learned a few things about POSIX shell scripting that
showed me how I depend on some of the higher-level data structures and
aids that shells like Bash have. Its frustrating not having arrays
available.

I thought this would be easy originally, as the first few issues were
relatively trivial to fix, but as I went deeper and deeper I realized
that backupninja depends on a lot of bashisms. This is especially true
because we use easydialog, which is repelete with arrays and other
bashisms. Worse is that the code in each of the handlers also has
bashisms and I did not write all of them so I would either need the
cooperation of the people who wrote them or I need to try and go through
and re-factor each one by first figuring out exactly what it does and
then how to make it do it in a less elegant way. Not a bad winter
project, but the contributors of the handlers would also need to be
convinced that fixes to their handlers will have to be done in a POSIX
manner...

Anyways, I'm curious of how deep this requirement is... The backupninja
main script has #!/bin/bash as its header, but my guess is that it needs
to be POSIX capable to be used in something like tasksel? If so, then
maybe not everything involved needs to be ported to POSIX...?

Micah

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDhh4L9n4qXRzy1ioRAp8uAJwIZEVnCE3/9ArFbV2Igx29E1SZXgCaAksm
dMD0+UCe1kj+806a/imzrfA=
=56Vl
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to