I've kinda disappeared for awhile because OpenBSD does not support Docker.
Just as I was ready to get started, I ran into that problem right away.
I have meant to send an email about that, but I was rather frustrated with
I also intended to help with the Spanish translations. And didn't.
The good news on that, I did find a Spanish/English dictionary specifically
for business terms only.
That's not a book I expected to find, much less expect to exist.
As far as OpenBSD, I need to do lot of work on that.
Could someone recommend a Linux distribution that works well that I can
install and look at as an example as I work?
What is the situation with browsers? I use mostly Firefox, but I'm
finding more and more sites that really run off of only Chromium
Where are the right repositories located for development at?
OpenBSD is running PostgreSQL 10.5 (or later when -current is released
soon). Any issues with that or later versions of PostgreSQL?
I discovered that some work was started on Docker by someone else quite a
while back, but has not been worked on any further.
I'm a little bit unclear on exactly what Docker is doing and not doing.
I will spend some time looking into that.
What is it doing in particular for LedgerSMB and just for this project
only, can some kind of temporary workaround be used?
Can I go ahead and port all of the missing modules and pass/fail the
existing tests until something can be done about the Docker problem?
OpenBSD has recently done a lot of work to make porting much easier to do.
I do see that a lot of projects are using Docker, so it may be worth the
effort to get it working in OpenBSD. People are using it with an Alpine
Linux vmm from OpenBSD, but I have no experience in that.
Note that due to illness; although I updated our 'ledgersmb-1.6' pkg
for v1.6.10 I haven't yet updated the 'ledgersmb' pkg for that version
so what's in Debian Testing is still only v1.6.9. And since the hard
freeze in preparation for the Debian release of Buster as the new
stable has gone active, there is no more auto migration to Testing for
updated packages in Debian unstable until after the new version has
Besides still waiting for the last 3 debconf translations so that the
pkg can be updated with them, I've also been thinking about a major
change in the package; that being changing it so that it uses the dojo
distributed in the LedgerSMB archive instead of that in Debian like is
already being done with our 'ledgersmb-1.6' package, on the basis that
the version in Debian is not the same as that actually being used by
the app itself.
There's not that much of a dojo related version difference with what
LedgerSMB 1.6 uses (Debian testing has v1.14.2) but that's not the
case for LSMB 1.7 so it's something I need to look at in any case.
A ledgersmb package with major changes could always be uploaded to
Debian Experimental (& our package repos, of course), so that's what
I'll be looking at doing if necessary.
Related to that is still getting the autopkgtest functionality done
for the package. That (which does 'as installed' testing) is useful I
think in any case but in particular having to do related to the
different dojo versions. But that is based on my thinking that the JS
code is actually being at least somewhat exercised in the 't/' and or
'xt/' testing, which I was wondering about due to something one the
other devs said/ but which I've been assured that the JS code is being
exercised in the bdd tests in xt/. So I figure to work on getting the
t/ tests working for the autopkgtest to start off with and continue
from there to the xt/ tests.
Any comments/questions/etc, please let know.
Robert J. Clay