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

Pull requests / updates? #24

Open
hansmbakker opened this issue Nov 13, 2022 · 5 comments
Open

Pull requests / updates? #24

hansmbakker opened this issue Nov 13, 2022 · 5 comments

Comments

@hansmbakker
Copy link

hansmbakker commented Nov 13, 2022

Hi @hashtagchris, I was wondering whether you'd be willing to review the work that @gvheertum and @vestervang have been doing, and merge it?

I mean the caching PR (#15) and the commits in @vestervang's fork (main...vestervang:DotNet-BlueZ:main)

I'd like to look into a dotnet 7 upgrade, and am wondering whether a PR would be accepted?

@vestervang
Copy link

Hi @hansmbakker i'm currently maintaining this fork as I use it at work. If you want to improve the library you can make a PR there and i'll have a look at it and push the changes to nuget.

@hansmbakker
Copy link
Author

hansmbakker commented Nov 14, 2022

@vestervang great that you continued the work!

Please see some updates in ProrepubliQ#7

Could your repo somehow take over the "lead role" in the sense that the issue reporting is here but the most recent updates are in your repo?

@aolszowka
Copy link

aolszowka commented Mar 24, 2023

So I've just cloned the repository that @vestervang holds, it looks like this was updated to .NET 7, not a huge deal but is there a reason we want to target that as opposed to netstandard like this upstream project does?

FWIW out of the box the current Ubuntu LTS (Jammy) does not have dotnet-sdk-7 in its default apt repos which is what I'm currently targeting.

I also noticed that the branch doesn't have the ability to open issues; do we want to still try an coordinate with this upstream project or do we want to attempt a hard fork?

EDIT: I went ahead and took the initiative to retarget the library itself back to netstandard2.0, upgraded the Tdms.DBus to the latest, and converted to dotnet-tool.json and opened vestervang#1 I ran a test with the scan app, but as I cannot see a way to validate my changes completely I'll have to assume they're OK. I'll continue making changes on that branch and targeting and coordinating here until I hear otherwise?

@vestervang
Copy link

Hi @aolszowka,

I have enabled issues on the repo now and there is no reason as far as i can see that we should target dotnet7 specifically.

@aolszowka
Copy link

Ok I am going to start coordinating work over there on that repository, please let me know if it becomes too much. I've got some free time today to grind this!

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

No branches or pull requests

3 participants