Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 29 2015 13:57
    ferventcoder commented on 4af5e76
  • Jun 29 2015 13:48
    ferventcoder commented on 4af5e76
  • Jun 29 2015 13:34
    ferventcoder commented on f9ecefa
  • Apr 08 2015 05:36

    Jaykul on ListCommand

    (compare)

  • Apr 08 2015 05:36

    Jaykul on InstallCommand

    (GH-132) Make InstallCommand a… (maint) Line wrapping. (compare)

  • Apr 08 2015 05:10
    Jaykul commented on 5742f16
  • Apr 08 2015 05:09
    Jaykul commented on 5742f16
  • Apr 08 2015 05:07

    Jaykul on InstallCommand

    (maint) Line wrapping. (compare)

  • Apr 08 2015 04:36
    ferventcoder commented on 5742f16
  • Apr 08 2015 04:28
    Jaykul commented on 5742f16
  • Apr 08 2015 03:13
    ferventcoder commented on 5742f16
  • Apr 08 2015 03:13
    ferventcoder commented on 5742f16
  • Apr 07 2015 16:15
    ferventcoder commented on 83ef921
  • Apr 07 2015 15:06
    Jaykul commented on 83ef921
  • Apr 07 2015 14:46
    ferventcoder commented on 83ef921
  • Apr 07 2015 14:45
    ferventcoder commented on 83ef921
  • Apr 06 2015 16:32

    Jaykul on master

    Add Install and Uninstall Refac… (compare)

  • Apr 05 2015 06:33

    Jaykul on InstallCommand

    (GH-132) Make InstallCommand a… (compare)

  • Apr 05 2015 06:27

    Jaykul on 0.9.9.3

    (compare)

  • Apr 05 2015 06:27

    Jaykul on InstallCommand

    (GH-132) Make InstallCommand a… (compare)

George.IO
@Geogboe
Just wanted to document an interesing situation I had when building from source using Win10, VS17 Community, and Windows ADK pre-installed if anyone else has this. Line 222 seems to be an extra unnecessary #endregion which doesn't pair with anything. Commented it out. Also, the Path HKCU:\Software\PackageManagement\Tools\MT.EXE for my system was pointing towards arm64 not x64...and the build script looks at the reg key to find the path to the compiler...or library..or something. So that definitely didn't work. Possibly because I had done some Xamarine stuff before. So I had to change that and then the build succeeded.
Rob Reynolds
@ferventcoder
@Geogboe what we last decided on - look at https://github.com/OneGet/NuGetProvider and move most everything to that, then add the choco bits back on top of that
It has all the good nuget stuff, just needs the choco enhanced bits to it and then the additional choco functionality
George.IO
@Geogboe
@ferventcoder Awesome, thanks!
Kiran Hegde
@kirannhegde
@ferventcoder Are you still accepting contributions? If yes, where is the documented process to start contributing? I am sorry, i have never contributed on GitHub. So kindly excuse my ignorance.
Rob Reynolds
@ferventcoder
@kirannhegde yes, accepting contributions. There is not a documented process unfortunately.
You can take a look at https://github.com/chocolatey/choco/blob/master/CONTRIBUTING.md - the process would be similar (except there wouldn't need to be a CLA signature)
Kiran Hegde
@kirannhegde
@ferventcoder Thanks a ton for the link. I will go through it and hopefully be able to contribute. I am a newbie to open source. I have some prior development experience on C#, C++ and Powershell . For all practical reasons, you can consider that i a newbie to programming. ii strongly believe that more practice would make me a better programmer. I am looking to improvise on these skills. Hopefully contributing to open source will help me with my objectives thus also helping the open source community.
Kiran Hegde
@kirannhegde
@ferventcoder I am currently looking at the documentation on writing a provider: https://github.com/OneGet/oneget/blob/master/docs/writepowershellbasedprovider.md . Would this serve as a starting point to start contributing on the OneGet Provider for Chocolatey? Also, what are the pending tasks? Is there a list somewhere of the breakdown of tasks? I looked at chocolatey/chocolatey-oneget#5 and did not find any breakdown of tasks. I did love to start with something simple and then move on to bigger things since i am not an expert on C# yet. if you could or someone else could provide me some direction, i did love to get started with this.
Rob Reynolds
@ferventcoder
I'm not hugely familiar with oneget. The choco provider will likely need to be a c# provider - there is already a provider called Chocolatey-Get that I believe may be a good starting reference for you.
Kiran Hegde
@kirannhegde
@ferventcoder Thanks
Jens Bruggeman
@jensdotbruggeman
I have read the articles about the current state of the current Chocolatey OneGet integration (and should use ChocolatelyGet provider). I received issues with installation of newer packages f.e. nodejs-lts which tells me the package is installed but isn't really installed. Are these known issues with the current state of the provider? Is it possible to troubleshoot this issue?
Rob Reynolds
@ferventcoder
@jensdotbruggeman use the ChocolateyGet provider for now
JirkaPok
@jirkapok
If there is still somebody interesed in the oneget provider, contact me, i wellcome any cooperation.
Aurimas Navardauskas
@AurimasNav
Hi, very much interested
JirkaPok
@jirkapok
I am searching for volunteer who is able to review and test the package provider https://github.com/jirkapok/chocolatey-oneget/tree/NativeProvider
Let me know, if you want to help
Ethan Bergstrom
@ethanbergstrom

I've published a OneGet provider called Chocolatier (https://github.com/ethanbergstrom/Chocolatier) based on the ChocolateyGet provider with:

  • full support for registering/installing from both offline and online private repos
  • DSC compatibility
  • upgrading packages
  • optional Native API integration
  • PowerShell 7 support

It's out on PSGallery for testing if anyone wants to give a whirl.

JirkaPok
@jirkapok
i did similar stuff, lets ask chocolatey team, how they want to support it. Multiple providers are created. I want to see at least one of them as an official supported by the core team. But it looks like it is out of the scope of interest.
The question is, do we need one? I expected oneget becommes the windows standard for installing application, but it is now chocolatey it self.
Paul Broadwith
@pauby

@jirkapok

But it looks like it is out of the scope of interest.

That's not the case.

JirkaPok
@jirkapok
Yes, but it looks like this. The repo has no commits more than 3 years. Community is creating content like the Cocolatier.
chocolatey-community/chocolatey-oneget#5 is not commented by your team etc.
Simply it looks like nobody wants to publish the provider officially.
Paul Broadwith
@pauby

We have many priorities. The audience for a OneGet provider is small. We have to prioritise what we work on. When I get time I will be looking at the PR that has been submitted (it's not been forgotten)

As far as Chocolatier goes, we have a vibrant open source community that we encourage. It's awesome to see Chocolatier and other community content.

Ethan Bergstrom
@ethanbergstrom
As an FYI, I worked with Jianyun to merge my work back into her more widely known ChocolateyGet project and plan to help her with supporting it going forward.
Rob Reynolds
@ferventcoder
👍