Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 04 08:58
    MarkusGeigerITD opened #869
  • Aug 02 08:51
    umarabdullahmansoori commented #12
  • Jul 31 13:01
    umarabdullahmansoori commented #843
  • Jul 30 23:08
    ryanrichter94 closed #867
  • Jul 30 23:08
    ryanrichter94 commented #867
  • Jul 30 22:54
    ryanrichter94 closed #863
  • Jul 30 22:54
    ryanrichter94 locked #863
  • Jul 30 06:31
    Toadfield opened #867
  • Jul 24 23:44
    reelism opened #866
  • Jul 21 20:30
    blackghost1987 commented #765
  • Jul 21 20:29
    blackghost1987 commented #765
  • Jul 20 19:04
    Toadfield commented #863
  • Jul 20 18:51
    gep13 commented #863
  • Jul 19 09:00
    FSpfl opened #865
  • Jul 18 20:10
    Toadfield commented #863
  • Jul 13 02:45
    ezxpro opened #864
  • Jul 09 20:51
    robertheadley closed #848
  • Jul 09 20:51
    robertheadley commented #848
  • Jul 01 20:44
    FiftyFour7250 edited #863
  • Jul 01 01:09
    FiftyFour7250 opened #863
Tarmo Pikaro
@tarmopikaro_gitlab
My own codes are not yet in public, but I'll start to slowly integrate them into my own fork.
I'll start from this branch.
but there is no any commit inside.
I'll start slowly progressing.
I wanted to chat with you before I proceed, but none from choco team did reply.
I think I'll rename "choco" to "swupd" just to avoid confusion between tools.
Gary Ewan Park
@gep13
I have seen those two issues that you have raised. Some of the items that you mention in them are things that have been on the Chocolatey roadmap for a while, and we do plan on getting to them, it is just that other items are currently taking a priority, like Chocolatey Central Management, and recent changes to the Community Repository. There are plans this year to start making some much needed changes to Chocolatey, like support for NuGet V3. These sorts of changes are not easy though, and we need to make sure that we don’t break any existing functionality.
Just because you haven’t had a reply, doesn’t mean that we aren’t listening, just that we are not prioritising in that area currently.
Tarmo Pikaro
@tarmopikaro_gitlab
yes, you have some existing client base, I do not yet have any. I can break whatever I want basically.
Since not planning to create any pull request.
Gary Ewan Park
@gep13
And that is certainly your choice, but I would encourage you to make contributions back to Chocolatey itself, in the spirit of open source.
Tarmo Pikaro
@tarmopikaro_gitlab
I was thinking about maybe some sort of grey box reuse - so you check what I have done, I check your doings, and we cherry pick whateever we want from each other.
I think it's not always possible - see this ticket: chocolatey/choco#2139
But do you have internal choco team channel where you guys hang out ?
would it be possible for me to join that channel ?
Gary Ewan Park
@gep13
As mentioned in that issue, the commercial versions are what help pay for the free services that Chocolatey offers. There are real costs involved, for example the hosting of the site which currently serves 10’s millions of requests a day, so adding functionality that is provided in the commercial editions is not likely something that will be allowed.
In terms of getting added to our private chats, I honestly don’t know whether that would be possible, I would need to check.
Tarmo Pikaro
@tarmopikaro_gitlab
or maybe just mail exchange for begging
tapika-at-yahoo.com is my mail.
chocolatey cross compiled to .net core weights ~92 Mb.(TrimMode=CopyUsed) => btw, I've reduced that one to 61Mb.
If make simple ReadyToRun wpf app, then size starts from 80 Mb.
Tarmo Pikaro
@tarmopikaro_gitlab
but it's basically release ready, nothing extra needs to be done.
Gary Ewan Park
@gep13
While getting a .NET core version of Chocolatey is something that is on the long term road map, there are no immediate plans to move away from full .NET Framework. There are lots of moving parts in the Chocolatey eco-system, that would also need to be updated if we made this move.
Tarmo Pikaro
@tarmopikaro_gitlab
At the moment I need to support .net 4.7.2 and I have now two platforms supported - .net 4.7.2 and .net core 3.1
.net 5 is too immature from readytorun perspective.
Tarmo Pikaro
@tarmopikaro_gitlab
choco is quite well covered by testing, even thus I have 3 tests failing.
choco gui is not covered at all ?
Gary Ewan Park
@gep13
Correct, there are currently no tests for Chocolatey GUI.
Tarmo Pikaro
@tarmopikaro_gitlab
have you analyzed anything or prototyped on ui automation ?
I have made some sort of bootstrap testing, but it comes because need to identify that all assemblies are present.
Gary Ewan Park
@gep13
I have thought about adding some UI testing, but as yet, this hasn’t been implemented. It would be great to have some tests in Chocolatey GUI.
Tarmo Pikaro
@tarmopikaro_gitlab
choco has nunit tests, I'm thinking about switching to xunit.
UppercuT build framework seems to be outdated, will probably not support .net core.
Tarmo Pikaro
@tarmopikaro_gitlab
need to go. contact me over mail if necessary. I'll try to setup CI for swupd/chocolatey first, then merge chocolatey gui into swupd.
probably I would be interested to discuss build tools, ci, testing and so on.
most probably I'll remove uppercut, remove linux & mac platform support (will return it later via readytorun)
most probably will switch test framework from nunit to xunit.
but need to test it bit more.
Gary Ewan Park
@gep13
If anyone has any feedback/suggestions here, I would love to hear it, thanks! https://twitter.com/gep13/status/1381270241561436163
Gary Ewan Park
@gep13
@/all Downtime on the website and other Chocolatey services has been scheduled for Wednesday 21 April between 9am and 11am UTC. See the status page for more information on how this may impact you and your use of Chocolatey services.
Gary Ewan Park
@gep13
@/all We are performing scheduled updates to the Chocolatey website and Chocolatey services. See the status page for more information on how this may impact you and your use of Chocolatey services.
Paul Broadwith
@pauby
@/all We have completed the updates and the Chocolatey website and Chocolatey services are now available. See the status page for more information.
Paul Broadwith
@pauby
@/all Downtime on the website and other Chocolatey services has been scheduled for Tuesday 27 April between 9am and 11am UTC. See the status page for more information on how this may impact you and your use of Chocolatey services.
Paul Broadwith
@pauby
@/all We are performing scheduled updates to the Chocolatey website and Chocolatey services. See the status page https://status.chocolatey.org for more information on how this may impact you and your use of Chocolatey services.
Paul Broadwith
@pauby
@/all We have completed maintenance and the Chocolatey website and Chocolatey services are now available. See the status page https://status.chocolatey.org for more information.
Peter
@pkratten:matrix.org
[m]
Hey everybody! Anybody got an idea why my chocolateyGui looks like this?
1 reply
Kris Acker Bierma
@KrisBierma
@/all Hi. I found a couple dead links in the contributing.md that I'd like to update. Who can I ask about this?
2 replies
FSpfl
@FSpfl

Hey everybody

We have a problem with the ChocolateyGUI. We host our internal repository on a file share. We now have more than 50 packages in this repository. However, the ChocolateyGUI only shows 33 packages when we uncheck "All Versions". If we enable "All Versions", exactly 50 packages are displayed. We just have one page, we cannot switch to another page. With the search we can find the rest of the packages.

Is there a way to fix that or do we have to setup an other type of a package repository like a simple server?