Closed gtaforever00 closed 3 years ago
I'll keep each instance inside the main repo. Building the latest tag (most recent release) and master branch (bleeding edge changes) is probably best.
Where the actual program files are placed doesn't matter much to me. The other packages place the directory inside /usr/share, so that might be best for consistency. If possible, I'd like to add an X shortcut to the executable, as well.
As for naming, alttpr-opentracker seems appropriate to me.
I very much appreciate the work you're putting in on this! Please let me know if there is anything I can do to help!
Thank you for your suggestions. I have been able to use gendesk
to auto generate a .desktop
file.
On the install directory, I was just going off of this Arch Package Guidelines. It states for large self-contained packages to use /opt
.
I will create a merge request with the PKGBUILD files. Do you want them in a directory called PKGBUILD in the root of the repo?
Also, I couldn't find a hard set of dependencies for the Avalonia framework. We should consider these BETA for that reason.
If you have a few minutes sometime, I'd like to get you on a voice call in Discord or something to make sure that I'm understanding you correctly and can get you what you need.
I ended up reversing course on this one. I created an empty repo called OpenTracker-pacman and invited you as a contributor. Go ahead and place all of the PKGBUILD files there in the correct folder structure.
Hey trippsc2,
Can you resend the invite? I missed the 7 day deadline. I have the files working pretty well. I will upload them to the repository once I can commit them.
The invitation has been resent. Let me know if there's anything I can help with.
Thanks again. I have the initial commit made on the new repo. Please let me know your thoughts or improvements.
Thank you very much for doing the work on this! I don't think there are any Avalonia requirements, as Avalonia is just a set of .NET libraries. Since the .NET runtime is bundled with the compiled app, the build dependencies (.NET SDK and gendesk) should be the only dependencies. I think it is AUR ready.
I agree on the AUR ready. The Avalonia blog stated they moved to OpenGL to reduce dependencies on X11 and Wayland desktop environments in v0.8. There is also some issues regarding fonts in the issue tracker in the Avalonia repo for Linux. I think those might be machine specific enough not to care too much about.Just thoughts as to what issues may arise when the general public start using it. On Feb 3, 2021 8:36 AM, trippsc2 notifications@github.com wrote: Thank you very much for doing the work on this! I don't think there are any Avalonia requirements, as Avalonia is just a set of .NET libraries. Since the .NET runtime is bundled with the compiled app, the build dependencies (.NET SDK and gendesk) should be the only dependencies. I think it is AUR ready.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
I submitted both packages to the AUR. Provide me your AUR username and I'll add you as a co-maintainer.
Thanks again for all of your help with this!
AUR packages are up and working. Closing this.
I have developed PKGBUILD files to install on Arch Linux based distros. I had a few questions on how you wanted to proceed. I have one to compile latest tag, one to compile latest commit, and I am working on one for downloading the binary files that is released with the tags.