Messy WIP for LedgerSMB importing into OpenBSD on git
Hi, I finally put up copies of the work I started to import the Perl modules needed to make LedgerSMB work with OpenBSD. Yes, this is a mess. 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 OpenBSD. 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@openbsd.org if you have any questions. https://github.com/CPBen/LSMB-for-OBSD-WIP I've never worked as a group on git, so I'm not sure if I need to do anything to allow pushing, etc. Thanks, Chris Bennett
Hi Chris, On Tue, May 4, 2021 at 9:29 PM Chris Bennett <chris@bennettconstruction.us> wrote:
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 OpenBSD.
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@openbsd.org if you have any questions.
https://github.com/CPBen/LSMB-for-OBSD-WIP
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): https://docs.github.com/en/github/collaborating-with-issues-and-pull-request... Hope that helps and thanks for all the work you did so far! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
On Wed, May 05, 2021 at 11:21:11PM +0200, Erik Huelsmann wrote:
Hi Chris,
On Tue, May 4, 2021 at 9:29 PM Chris Bennett <chris@bennettconstruction.us> wrote:
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.
Yes, I just got a proper method of submitting these in one email for each particular chain of dependencies. I will make up a chart of each group that needs to be done together. Since there is always one or more first ones at the bottom, I can ask for those first and work upwards from there. The cpanfile looks very simple, but then comes out a ton of dependencies for each one. I'll try to come up with something easy to follow. I was also thinking that a page showing what had been submitted and another showing what was committed to the tree would be helpful. Submitted but still needing changes will also help show where more work needs to be done to get the rest of a section finished out. I should have started out more organized like this from the start. Some of the PGObject ones have been a bit of a challenge to get them to pass the database testing. I also made a stupid mistake that I need to go back and fix in some of those. Oh well 8-/ live and learn!
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): https://docs.github.com/en/github/collaborating-with-issues-and-pull-request...
Hope that helps and thanks for all the work you did so far!
Regards,
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
participants (2)
-
Chris Bennett -
Erik Huelsmann