-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
Choco package #221
Comments
We did consider adding a chocolatey package but we have no expertise in it. Do you think you could take care of it @pointcache ? |
Also no expertise, but i will. Just cant promise i will maintain it long term, but ill do the initial setup. |
There is a scoop package now, closing. FYI @Meakk . |
That being said, if you still want to create a Chocolatey package, you are very welcome to do so @pointcache :) |
Hey there, here are some thoughts I posted on evsar3/sshfs-win-manager#19 to build a chocolatey package.
Hope this helps, and thanks for this great software! |
Hey again. Just submitted a PR so f3d gets listed on winget-pkgs, see PR microsoft/winget-pkgs#172695 - not yet merged! Once it gets officially listed, it should be better to setup a Github Action workflow which would push on github release the new f3d package to winget-pkgs - see this example post for two recommended ways to setup that action - usually advised to use Winget-Releaser Github Action, simpler but relies on external github action. Also another example github action workflow based on winget-releaser |
Following issue f3d-app#221 Uses [winget-releaser](https://github.com/vedantmgoyal9/winget-releaser) I suggest a `Classic Github Token` with `public_repo` scope is created by f3d-app org or another maintainer, following [this link](https://github.com/settings/tokens/new), then the Token can be added to the triplex repo as a secret named `WINGET_ACC_TOKEN`. See below, that user also will have to fork the winget-pkgs repository. Notes: > You will need to create a *classic* Personal Access Token (PAT) with `public_repo` scope. New fine-grained PATs aren't supported by the action. Review f3d-app#172 for information. > Fork [microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present.
* Create Github Action to release winget package Following issue #221 Uses [winget-releaser](https://github.com/vedantmgoyal9/winget-releaser) I suggest a `Classic Github Token` with `public_repo` scope is created by f3d-app org or another maintainer, following [this link](https://github.com/settings/tokens/new), then the Token can be added to the triplex repo as a secret named `WINGET_ACC_TOKEN`. See below, that user also will have to fork the winget-pkgs repository. Notes: > You will need to create a *classic* Personal Access Token (PAT) with `public_repo` scope. New fine-grained PATs aren't supported by the action. Review #172 for information. > Fork [microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present. * Fix typo .exe in regex * Update tag required and identifier * Edit package identifier to f3d-app.f3d
I know most devs don't want / have time to maintain chocolatey packages, but if you can, please.
I would love to have some high quality standard 3d viewer in my pm.
The text was updated successfully, but these errors were encountered: