The foundation for your business
Fork me on GitHub
[ledgersmb-devel] Fwd: Porting to OpenBSD again
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ledgersmb-devel] Fwd: Porting to OpenBSD again

And Chris's answer.

---------- Forwarded message ---------
From: Chris Bennett <..hidden..>
Date: Sat, Nov 2, 2019 at 10:25 PM
Subject: Re: [ledgersmb-devel] Porting to OpenBSD again
To: Erik Huelsmann <..hidden..>

On Sat, Nov 02, 2019 at 09:20:57PM +0100, Erik Huelsmann wrote:
> 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.)

Sounds good.

> 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?

I am thinking that the most useful thing will turn out to be some
installation details for different web servers. That could be a longish
list since there are quite a few choices. Putting that into the final
package would be pretty cumbersome. And too much work to keep it always
up to date. The base httpd server in OpenBSD can be run in quite a few
different ways. But that's for much later.

You can close the issues on github. I did manage to miss the 1.7

Chris Bennett



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