Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update/edit README.md and docs/CONFIGURE.md, 3 minor fixes #816

Merged
merged 4 commits into from
May 27, 2023

Conversation

rosecitytransit
Copy link
Contributor

@rosecitytransit rosecitytransit commented May 21, 2023

Includes adding a link to my decode rates logging plugin

3 minor fixes are:
-fix tbsk typo in p25_parser.cc
-remove duplicate include line in p25_frame_assembler_impl.cc
-remove duplicate add_file_log line in main.cc/have it capture log file config lines (fixes #754)

Can someone test the plugin? I'm using code that I added directly to Trunk Recorder, and I'm wondering if the override keyword should be used. Also, is there a desire to be able to specify the name/location of the rates file?

fix tbsk typo in p25_parser.cc

remove duplicate include line in p25_frame_assembler_impl.cc

remove duplicate add_file_log line in main.cc/have it capture log file config lines (fixes robotastic#754)
Copy link
Owner

@robotastic robotastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Just had 2 small questions

trunk-recorder/main.cc Show resolved Hide resolved
@taclane
Copy link
Contributor

taclane commented May 21, 2023

Instead of calling out a specific plugin in .gitignore like plugins/decode_rates, can't we just leave it as plugins/so it could be used as a staging area for other projects too?

@rosecitytransit
Copy link
Contributor Author

Instead of calling out a specific plugin in .gitignore like plugins/decode_rates, can't we just leave it as plugins/so it could be used as a staging area for other projects too?

No, because the plugins folder is really for internal plugins that are included in the Trunk Recorder code, and should be managed by git. The official way to use an external plugin is to put the code somewhere else and run sudo make install so it's available as a system object. My way avoids needing to do that. But there could be an "eternal_plugins" folder that is ignored.

@taclane
Copy link
Contributor

taclane commented May 21, 2023

Sorry, yeah. You are correct. All my plugins live in repos external to trunk-recorder and are manually installed.

Maybe we can recommend user_plugins\ directory as a staging area instead? It's just going to be cumbersome if every potential plugin requires representation in .gitignore.

@robotastic
Copy link
Owner

OK - I removed the plugin line from .gitignore. I would prefer not to have separate lines for each plugin there so I can minimize the number of PRs coming in. The best practice here would be to keep plugins outside of the Trunk Recorder repo. I should prob also clean out some of those weird directories from gitignore....

@robotastic robotastic merged commit 15bed14 into robotastic:master May 27, 2023
@rosecitytransit rosecitytransit deleted the v4master branch May 27, 2023 15:59
@rosecitytransit
Copy link
Contributor Author

I would prefer not to have separate lines for each plugin there so I can minimize the number of PRs coming in.

Totally understood. Can you provide your thoughts/guidance on issue 482 (just see the last 2 comments)? Would like to work on that next.

@rosecitytransit rosecitytransit restored the v4master branch May 28, 2023 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants