[Package Request]: All KDE Packages - Nightly, Stable, Release

Trenly commented 2 years ago

This issue is to combine all the requests for KDE packages into a single place and reduce clutter

Nightly

Stable

Release

ItzLevvie commented 2 years ago

https://github.com/microsoft/winget-pkgs/issues/39240 needs to be added to this list.
https://github.com/microsoft/winget-pkgs/issues/39241 needs to be added to this list.
https://github.com/microsoft/winget-pkgs/issues/39242 needs to be added to this list.
https://github.com/microsoft/winget-pkgs/issues/39243 needs to be added to this list.

RokeJulianLockhart commented 2 years ago

I am able to assist compilation of this list, so that such frequent modification of it by @ItzLevvie and @Trenly shall not be necessary. Please see this .txt file.

Approximately 37 remain.

Trenly commented 2 years ago

This comment is response to "http://github.com/microsoft/winget-pkgs/issues/39190#issue-1090227311" and "http://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1002592593".

I am able to assist compilation of this list so that frequent modification of it by @ItzLevvie and @Trenly shall not be necessary:

Addition of "http://github.com/microsoft/winget-pkgs/issues/39245" is necessary. Addition of "http://github.com/microsoft/winget-pkgs/issues/39247" is necessary. Addition of "http://github.com/microsoft/winget-pkgs/issues/39251" is necessary. Addition of "http://github.com/microsoft/winget-pkgs/issues/39252" is necessary.

Approximately 37 are remaining.

@BEEDELLROKEJULIANLOCKHART Please stop opening new issues for all of the package requests for KDE. You can just put the package ID's here. We are familiar with the KDE site and are already looking into the best way to add these packages. This issue was created to combine all of the other issues you opened into a single issue so that the issues tab isn't filled with KDE request spam

The problem with these packages is the retention of the packages and the fact that the Jenkins API's to fetch the latest URL's are not fast enough to catch all of the builds.

RokeJulianLockhart commented 2 years ago

https://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1002610719

Apologies – I'll do as you say.

I am able to add the identifiers manually, but that is not assistive, because the sole aspects which that effort is necessary for are:

verification of correctness of the URI that has been utilised for each description, and
ascertainment of the "Current Package Identifier" that is for each package.

However, I have not added them for any but https://github.com/microsoft/winget-pkgs/issues/30233#issue-1025347565.

Trenly commented 2 years ago

I shall adhere to your request. I am able to add the identifiers manually, but that is not assistive, because the sole aspects that effort is necessary for are verification of correctness the URI that has been utilised for each description, and ascertainment of the "Current Package Identifier" that is for each package, although I have not added that for any but "http://github.com/microsoft/winget-pkgs/issues/30233#issue-1025347565".

The URI's you have provided don't work after 3 days anyways. As long as we know which packages need to be added yet, we can find the correct URI's

vedantmgoyal9 commented 2 years ago

@BEEDELLROKEJULIANLOCKHART can you make manifests and open PRs to add an initial version of them in this repo, after that, it will be auto updated by the automation. Or, if anyone else would like to do so?

RokeJulianLockhart commented 2 years ago

https://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1038042858

@VEDANTMGOYAL2009, I would create the manifests that are necessary as recompense for your assistance if I were able to, but none of the software provided is available for the OS I'm using. I'll try to initialize a virtual machine, but that might necessitate some time.

RokeJulianLockhart commented 2 years ago

https://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1038279938

Has remediation of this problem progressed? I ask because many, many packages await this treatment.

If not, https://download.kde.org/stable and https://download.kde.org/unstable may be useful.

RokeJulianLockhart commented 1 year ago

https://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1222509294

Per https://github.com/vedantmgoyal2009/vedantmgoyal2009/issues/185#issuecomment-1002391298, I propose the undermentioned as the solution:

$BaseUrl = 'https://binary-factory.kde.org/view/Windows%2064-bit/job/kdeconnect-kde_Release_win64/'
((Invoke-WebRequest -Uri "$BaseUrl").Links | Where-Object {$_.outerText -like "Last successful build*"} | Select-Object -Property outerText) -match '[0-9]{3,}' | Out-Null; $build = $Matches.Values
$BaseUrl+$build+"/$(((Invoke-WebRequest -Uri "$BaseUrl$build/").Links | Where-Object {$_.href -like '*.exe'}).href)" 

$BaseUrl = 'https://binary-factory.kde.org/view/Windows%2064-bit/job/Cantor_Release_win64/'
((Invoke-WebRequest -Uri "$BaseUrl").Links | Where-Object {$_.outerText -like "Last successful build*"} | Select-Object -Property outerText) -match '[0-9]{3,}' | Out-Null; $build = $Matches.Values
$BaseUrl+$build+"/$(((Invoke-WebRequest -Uri "$BaseUrl$build/").Links | Where-Object {$_.href -like '*.exe'}).href)"

$BaseUrl = 'https://binary-factory.kde.org/view/Windows%2064-bit/job/KBibTeX_Nightly_win64/'
((Invoke-WebRequest -Uri "$BaseUrl").Links | Where-Object {$_.outerText -like "Last successful build*"} | Select-Object -Property outerText) -match '[0-9]{3,}' | Out-Null; $build = $Matches.Values
$BaseUrl+$build+"/$(((Invoke-WebRequest -Uri "$BaseUrl$build/").Links | Where-Object {$_.href -like '*.exe'}).href)"

It appears to operate for me!

RokeJulianLockhart commented 2 weeks ago

https://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1002610719

https://blogs.kde.org/2024/01/30/farewell-binary-factory-add-craft-jobs-your-apps-kdes-gitlab-now/ may invalidate some of the concerns expressed here. I presume that WinGet is well-tooled to support GitLab CI?

microsoft / winget-pkgs