[GH-ISSUE #431] Improve chocolatey package #356

Open
opened 2026-02-26 09:31:07 +03:00 by kerem · 12 comments
Owner

Originally created by @majkinetor on GitHub (Jan 14, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/431

ffmpeg and gifski could be added as choco dependencies. Gifski doesn't exist as choco package yet but I am willing to make it.

That way

  • doing cinst screentogif would install all of them and configure correctly.
  • doing choco update ... would update only dependencies that actually have a new version
  • it is also possible to install only main package without dependencies using --ignore-dependencies cmd line argument.

What do you think ?

If you accept, I can do relevant work. I also think package should be embedded (i.e. contain binary inside, not just link)

Originally created by @majkinetor on GitHub (Jan 14, 2019). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/431 **ffmpeg** and **gifski** could be added as choco dependencies. Gifski doesn't exist as choco package yet but I am willing to make it. That way * doing `cinst screentogif` would install all of them and configure correctly. * doing `choco update ...` would update only dependencies that actually have a new version * it is also possible to install only main package without dependencies using ` --ignore-dependencies` cmd line argument. What do you think ? If you accept, I can do relevant work. I also think package should be embedded (i.e. contain binary inside, not just link)
Author
Owner

@Kristinita commented on GitHub (Jan 30, 2019):

@majkinetor , It would be nice, if you add lossygif to Chocolatey too. See my table — it a best GIF compression tool.

Thanks.

<!-- gh-comment-id:458983210 --> @Kristinita commented on GitHub (Jan 30, 2019): @majkinetor , It would be nice, if you add [**lossygif**](https://kornel.ski/lossygif) to Chocolatey too. See [**my table**](https://github.com/NickeManarin/ScreenToGif/issues/445) — it a best GIF compression tool. Thanks.
Author
Owner

@majkinetor commented on GitHub (Jan 30, 2019):

@Kristinita

They don't provide binaries so its a bit complicated as I need to build them myself which I generally do not do.

<!-- gh-comment-id:458999168 --> @majkinetor commented on GitHub (Jan 30, 2019): @Kristinita They don't provide binaries so its a bit complicated as I need to build them myself which I generally do not do.
Author
Owner

@NickeManarin commented on GitHub (Feb 28, 2020):

@majkinetor Hi, sorry for taking so long.

I would like to push this forward, at least with FFmpeg.

With Gifski and SharpDX, it's a little bit different. I think that it's best to bundle together.

<!-- gh-comment-id:592686454 --> @NickeManarin commented on GitHub (Feb 28, 2020): @majkinetor Hi, sorry for taking so long. I would like to push this forward, at least with FFmpeg. With Gifski and SharpDX, it's a little bit different. I think that it's best to bundle together.
Author
Owner

@majkinetor commented on GitHub (Feb 28, 2020):

Sure, just add 1 line to nuspec file, that it depends on ffmpeg. I am personally involved in keeping this package up to date all the time as you can see in the version history.

If you need any help let me know.

<!-- gh-comment-id:592708092 --> @majkinetor commented on GitHub (Feb 28, 2020): Sure, just add 1 line to nuspec file, that it depends on [ffmpeg](https://chocolatey.org/packages/ffmpeg). I am personally involved in keeping this package up to date all the time as you can see in the version history. If you need any help let me know.
Author
Owner

@NickeManarin commented on GitHub (Mar 3, 2020):

Strange, it's not working on my tests in here:

I added these lines to the nuspec:

<metadata>
  <package>
    [...]
    <dependencies>
      <dependency id="ffmpeg" version="4.2.2"/>
    </dependencies>
  </metadata>
</package>

And I'm trying to test with this command:
choco install -fdv .\screentogif.nuspec

I end up with this error:

screentogif not installed. An error occurred during installation:
 Unable to resolve dependency 'ffmpeg (≥ 4.2.2)'.
<!-- gh-comment-id:594203386 --> @NickeManarin commented on GitHub (Mar 3, 2020): Strange, it's not working on my tests in here: I added these lines to the nuspec: ``` <metadata> <package> [...] <dependencies> <dependency id="ffmpeg" version="4.2.2"/> </dependencies> </metadata> </package> ``` And I'm trying to test with this command: `choco install -fdv .\screentogif.nuspec` I end up with this error: ``` screentogif not installed. An error occurred during installation: Unable to resolve dependency 'ffmpeg (≥ 4.2.2)'. ```
Author
Owner

@NickeManarin commented on GitHub (Mar 3, 2020):

Forget it, it's working now with this command, running the same folder as the package:

choco install -s "'.;https://chocolatey.org/api/v2/'" -fdv screentogif

<!-- gh-comment-id:594205192 --> @NickeManarin commented on GitHub (Mar 3, 2020): Forget it, it's working now with this command, running the same folder as the package: `choco install -s "'.;https://chocolatey.org/api/v2/'" -fdv screentogif`
Author
Owner

@NickeManarin commented on GitHub (Mar 3, 2020):

Now for the Gifski and SharpDX, I think that I could simply ship my own MSI file.
But I'm not sure how existent "choco" installations of ScreenToGif would work.

Because the current package is installed via the portable version.

<!-- gh-comment-id:594208995 --> @NickeManarin commented on GitHub (Mar 3, 2020): Now for the Gifski and SharpDX, I think that I could simply ship my own MSI file. But I'm not sure how existent "choco" installations of ScreenToGif would work. Because the current package is installed via the portable version.
Author
Owner

@majkinetor commented on GitHub (Mar 5, 2020):

Now for the Gifski and SharpDX, I think that I could simply ship my own MSI file.

Why not just add them to portable installation directly. Why MSI for 1 simple exe and a library ?

Like suggested I can create gifsky package. If you add it to deps, the exe will then be available on the PATH. If you don't want to depend on choco, you should embedd it.

<!-- gh-comment-id:595064160 --> @majkinetor commented on GitHub (Mar 5, 2020): > Now for the Gifski and SharpDX, I think that I could simply ship my own MSI file. Why not just add them to portable installation directly. Why MSI for 1 simple exe and a library ? Like suggested I can create gifsky package. If you add it to deps, the exe will then be available on the PATH. If you don't want to depend on choco, you should embedd it.
Author
Owner

@NickeManarin commented on GitHub (Mar 5, 2020):

I'll try to embedd both Gifski.dll and SharpDX.dll.

<!-- gh-comment-id:595336124 --> @NickeManarin commented on GitHub (Mar 5, 2020): I'll try to embedd both Gifski.dll and SharpDX.dll.
Author
Owner

@lucastheisen commented on GitHub (Mar 23, 2020):

I just got a message saying Netframework 4.8 is required as well... Could be added as another dep: https://chocolatey.org/packages/netfx-4.8

<!-- gh-comment-id:602815593 --> @lucastheisen commented on GitHub (Mar 23, 2020): I just got a message saying Netframework 4.8 is required as well... Could be added as another dep: https://chocolatey.org/packages/netfx-4.8
Author
Owner

@NickeManarin commented on GitHub (Mar 31, 2020):

@lucastheisen Yes, it can be. Thanks.

<!-- gh-comment-id:606668080 --> @NickeManarin commented on GitHub (Mar 31, 2020): @lucastheisen Yes, it can be. Thanks.
Author
Owner

@brian6932 commented on GitHub (Jul 16, 2021):

Is it possible to get an installer in addition to the current portable version, or at least an install argument? Cause the current package is potable only

<!-- gh-comment-id:881204552 --> @brian6932 commented on GitHub (Jul 16, 2021): Is it possible to get an installer in addition to the current portable version, or at least an install argument? Cause the current package is potable only
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ScreenToGif#356
No description provided.