Skip to content

Add start menu shortcut and launch upon install#2

Open
andrewdbond wants to merge 2 commits intoKeypirinha:masterfrom
andrewdbond:add-startmenu-shortcut-and-launch-on-install
Open

Add start menu shortcut and launch upon install#2
andrewdbond wants to merge 2 commits intoKeypirinha:masterfrom
andrewdbond:add-startmenu-shortcut-and-launch-on-install

Conversation

@andrewdbond
Copy link
Copy Markdown

Including because Chocolatey installs Keypirinha to a location
isn’t immediately obvious to most users, upon installation add a start
menu shortcut and launch Keypirinha. With this, Keypirinha's Chocolatey installation would also function more like other traditional (Chocolatey) installed software which starts needed background process(es).

Tweak PowerShell parameter names and capitalization to match PowerShell
documentation defaults.

The package version hasn't yet been bumped. If a new package version is released without a new version of the underlying software, https://chocolatey.org/courses/creating-chocolatey-packages/naming-description-and-versioning#package-versioning recommends adding a ".YYYYMMDD" suffix to the package version.

Including because Chocolatey installs Keypirinha to a location
isn’t immediately obvious to most users, upon installation add a start
menu shortcut and launch Keypirinha.

Tweak PowerShell parameter names and capitalization to match PowerShell
documentation defaults.
@polyvertex
Copy link
Copy Markdown
Member

Thanks for this! :)

Just a tiny thing before merging, as described in the README file, build/ in an output directory written by Keypirinha's own build tools, so only files under src/ should be committed.

Please revert changes to build/ so that I can merge.

I'm unaware of what internal build tools are used to generate the
/build/ directory from the /src/**.in files. However, to test my changes
I had to manually edit the /build/ files anyway. I understood that
/build/ files are overwritten during the release process. However, as I
was confident my files would match what the tool creates, I left them in
the previous commit. Per the software owner's request, I'm reverting the
/build/ changes. The /src/ changes remain.
@andrewdbond
Copy link
Copy Markdown
Author

Thanks. As I'm unaware of the tools used to create build/ from src/, to test my changes I had to manually edit the build/ files. I understood that build/ files are overwritten during the release process. However, as I was confident that my files would match what the tool creates, I left them in the previous commit. Per your request, I've now submitted a new commit with the build/ changes reverted. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants