Forgot to send to the mailing list...

---------- Forwarded message ---------
From: Erik Huelsmann <ehuels@gmail.com>
Date: Sat, Nov 2, 2019 at 9:20 PM
Subject: Re: [ledgersmb-devel] Porting to OpenBSD again
To: Chris Bennett <chris@bennettconstruction.us>


Hi Chris,

On Sat, Nov 2, 2019 at 1:35 PM Chris Bennett <chris@bennettconstruction.us> wrote:
I was CPBen on github.
Yes here is better.

Thanks for taking this to the list. (And thanks for picking up the effort.)

I am updating to latest -current right now.
If anyone wants to help, that would be great.
OpenBSD has become a breeze to update now. A flash stick or drive works
fine. Development has to be done on -current only.

It seems that it might help me to be running a Linux version too.
Which one would be recommended as easy and workable on a flash stick?
I'm a total noob on Linux, now.

If you want to be running linux from a usb stick, I think a distribution with a Live version will help. (I'd suggest DebianLive, because we have regularly updated Debian packages.)
 
I posted two issues on github, one with the very minimum dependencies
that I have to add. Is anyone still using OpenOffice versus Libreoffice.
OpenOffice just isn't supported on OpenBSD for a long time.

Well, LedgerSMB I don't think things will make a big difference: it doesn't depend on either, but simply generates a document format which either will consume.
 
Docker is also not an option.

No problem. Nothing requires Docker; it's just a very convenient way of producing a standardized distribution which works "always" (well, most of the time).
 
PostgreSQL 12+ will be the version coming out.

From what I can tell, we were compatible with 9.x, 10 and 11; I'm expecting us to be compatible with 12.
 
[snip]

And thanks to Mr. Ransbottom for his $100 donation to me. That allowed
me to purchase an external hard drive which I really needed to get this
work done.

Very nice to hear that this effort comes from that sponsoring!
 
Is there any reason for me to work on any version before 1.7+ also?

I don't think so. We've seen very few regressions on 1.7 even though it's been a major change under the hood. Over the coming months some issues will be ironed out as they are found, but there's really little reason not to use it at all.

 
I and intended to work on a Mexican Spanish translation, but my passport
is expired and I need to get a Mexican accounting textbook. The
different Spanish speaking countries vary wildly in their accounting
methods, so my Spain dictionary on accounting might not be appropriate.

I use git, but not in a group. Would opening an OpenBSD branch be a good
idea?

I really don't expect you will need to change much on the project's source code -- which would be a primary reason to create a branch. I *can* imagine though that you'll need to store a lot of code/changes required to do the porting of the Perl packages you listed in one of the tickets into OpenBSD. Because development of packages is usually tangent on the development of the project itself, we've created package repositories within the GitHub 'ledgersmb' organisation: https://github.com/ledgersmb/ledgersmb-docker for the Docker packages/images, https://github.com/ledgersmb/pkg-ledgersmb for the Debian package and https://github.com/ledgersmb/lsmb-overlay for a Gentoo Overlay (package).
 
We could create another repository for the OpenBSD package(s), if that helps?


Glad to be back again,
Chris Bennett


Nice to see activity on this front again!

--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.


--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.