On Tue, May 4, 2021 at 9:29 PM Chris Bennett <chris(a)bennettconstruction.us>
I finally put up copies of the work I started to import the Perl modules
needed to make LedgerSMB work with OpenBSD.
Thanks! Having it "out there" provides people with a basis to start
building on and contributing back to what you were already working on. If
that happens, it's great! If not, well, I guess you didn't loose much as
you were working on it anyway.
Yes, this is a mess.
Well, I guess that's only logical for anything that's heavily in progress.
My personal opinion is that it's not a problem when things are a bit messy;
maybe it's a good idea to describe in 4 or 5 bullets where you want to take
things? That way, when someone comes along and wants to join in, people
have a general sense of direction on what they could contribute to directly.
I had to drop a server out of the two I was using.
I was also editing files on my laptop, which can no longer run -current
I decided now that I had a chance to, just to push up what I had.
I'll clean things up as I have time.
Most of the modules are very straightforward to get committed.
Just prepare all the dependencies for what you want to submit.
But if you want to help, it's OK to just do one of the dependencies as a
good start. The work is pretty simple, but time consuming.
OpenBSD has it's own testing and installation structure, so don't run
the install process that works from CPAN.
Feel free to ask me or on ports(a)openbsd.org if you have any questions.
I've never worked as a group on git, so I'm not sure if I need to do
anything to allow pushing, etc.
Normally, people indeed need explicit authorization to be able to push to
your repository. There's documentation on GitHub Docs which explains how
collaboration is supposed to work when contributors don't have the
authorization to push directly (See Pull Requests):
Hope that helps and thanks for all the work you did so far!
-- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.