Open an issue qualified as you see listed there, adding @maintainer in the description might help get the right attention, depends if it is still actively maintained. Going to the project website might be more direct.
Adding a PR means pick up the SW where things were left off, get it working and submit for inclusion in the codebase. This might be the only viable option in getting it active depending on interest level.
What is the project website (do you mean where the code is stored)?
If what is actively maintained...the software??? I just need it in binary form...why does it have to be "maintained." It's the only software that works worldwide to connect an Amateur Radio to a networked computer...so I'm sure there's interest.
If I understand a PR...that just means place the code into OpenWRT's build bot, correct? (this is what I seem to need, the code already exists)
The code exists, it just need to be compiled and packaged.
(This is a software suite where they're really can't be interest until the software works...this is included in every distro of Linux..THEY'RE THE BASIC TOOLS NEEDED FOR CONFIGURATION OF AX.25 INTERFACES...so I'm just a little confused here...)
I would simply copy the files from another distro, but OpenWRT is one of the few full distros built for my target.
It matters if it is maintained,because if something changes and package breaks we would be stuck with a broken package forever.
PR is short for a Pull Request,that is a way to request your code to be merged into OpenWRT on OpenWRT github.
So you basically need to either get maintainers of the software to wrike makefiles and if needed patches specific to OpenWRT for each package and get that merged.
I've sent an email to every author listed in the TAR files, I simply provided them your quote stating that something is needed (other than the source code).
I've always been told this software "is available in all Linux distributions," so this seems backwards - going back to the people that provided the software already...I'm also lost about the "broken package forever" issue...perhaps what the software does is not known...these people are university professors, Internet fixtures, etc...I don't understand what they may have left out of the software that's needed...it works on every computer...
Or...perhaps it's only confusing because I'm a N00b to this...or I'm actually becoming @maintainer???
You make an issue on https://bugs.openwrt.org/
PR is made when you have working code that you want to merge.
No, it is not available in all just by itself, it needs to have a maintainer and working makefile which will enable successful compilation.
What is there not to understand that OpenWRT changes all the time and stuff(Including packages can break).
So not having a person who is responsible for keeping that package working is not smart.
I really think the nature of the software stack is not understood. I mentioned:
This is extremely difficult and I assumed that this would be "added" to OpenWRT over 6 years ago...now I have people emailing me in different languages...I want to attmept to write the makefile myself...
So, I see a makefile in the TAR...will this file work, or do I have to create a new one???
If I make a new one, how does it become a package I can tell other Amateur Radio Operators to type opkg install foo from anywhere in the world (is that the PR)???
First of all, those packages look like they are not overly complicated to compile as they don't have some weird dependencies.
So, first take a look at simpler packages like nano in openwrt/packages so you can figure out the logic.
Simplest package is pretty much just a folder and a Makefile inside.
In Makefile you define stuff like name,version and location where to pull source code from.
Off course and all options and dependencies needed for building.
# Copyright (C) 2007-2014 OpenWrt.org
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
TITLE:=ax25 library for hamradio applications
This library is for ham radio applications that use the ax25
protocol. Included are routines to do ax25 address parsing, common
ax25 application config file parsing, etc.
I wanted to confirm one thing:
This means that if I install libax25, it will install kmod-ax25 - if it is not yet installed?