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

Possible packaging in Chocolatey or WinGet #199

Closed
ptanmay143 opened this issue Nov 18, 2020 · 5 comments
Closed

Possible packaging in Chocolatey or WinGet #199

ptanmay143 opened this issue Nov 18, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@ptanmay143
Copy link

Is your feature request related to a problem? Please describe.
Having to manually install Lively on every system in a lab environment is tiresome process.

Describe the solution you'd like
Having lively packaged as a Chocolatey package.

Describe alternatives you've considered
Having lively packaged as a WinGet package.

@ptanmay143 ptanmay143 added the enhancement New feature or request label Nov 18, 2020
@rocksdanister
Copy link
Owner

rocksdanister commented Nov 18, 2020

I looked into WinGet in the past and it supports Inno installer.
I am not sure how the Visual C++ Redistributable and .Net core runtime(this require admin access.) will play nicely since its not currently automated and require user interaction to install.

Its possible to make a self contained lively binary so that .net core install can be avoided but currently I am having some issues with the selft contained build and xaml island.

@rocksdanister
Copy link
Owner

rocksdanister commented Nov 23, 2020

Update
So I managed to make a self contained version of Lively that require no additional dependency installation (.Net core and VC++)
I had to remove Xaml island(uwp) due to some publishing issues .

Cons:

  1. UI is not as smooth as the github version and lacks some visual features (animated gif, smooth scroll etc..)
  2. Maintaining two versions of Lively will be annoying.
  3. Not as efficient, bit higher memory usage.

Pros:

  1. Works on older version of Windows.
  2. Should be more stable for people having issue with the xaml island version.

@ptanmay143
Copy link
Author

Maybe you could release this version as a pre-release on GitHub accompanied with a poll and a notice regarding the pros and cons of the new approach.

@rocksdanister
Copy link
Owner

rocksdanister commented Nov 26, 2020

Currently testing Windows store version #9 (comment)
Will see how things turns out, I think WinGet supports MSIX package.

Note: I will publish it myself when ready, I request you do not publish to third party stores without my permission.

@rocksdanister
Copy link
Owner

Store release is up: #213

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants