Thanks Eric/Raul for the encouragement. I had a go at this and it was a pretty straightforward process. The next step is to submit a PR which will add the package to the directory and make it available to winget. Prior to that, it would be good to review the config files I've come up with and let me know if you have any suggested changes.
There are 3 Yaml files that describe the package. I've tested these locally & it will successfully install J on my Windows10 for either "user" (default) or "machine" scope. The default installation directory for the "user" scope is currently %UserProfile% whereas these days other similar software seems to install to %LOCALAPPDATA%\Programs\ . Maybe a potential change for J9.04 release? <Jsoftware.J.J.03.yaml> # Created using wingetcreate 1.1.2.0 # yaml-language-server: $schema= https://aka.ms/winget-manifest.version.1.2.0.schema.json PackageIdentifier: Jsoftware.J.9.03 PackageVersion: 9.03 DefaultLocale: en-US ManifestType: version ManifestVersion: 1.2.0 <Jsoftware.J.9.03.locale.en-US.yaml> # Created using wingetcreate 1.1.2.0 # yaml-language-server: $schema= https://aka.ms/winget-manifest.defaultLocale.1.2.0.schema.json PackageIdentifier: Jsoftware.J.9.03 PackageVersion: 9.03 PackageLocale: en-US Publisher: Jsoftware PackageName: J-language License: J Products are Copyright 1994-2021 by Jsoftware Inc. All rights reserved. ShortDescription: J is a high-level, general purpose programming language. ManifestType: defaultLocale ManifestVersion: 1.2.0 <Jsoftware.J.9.03.installer.yaml> # Created using wingetcreate 1.1.2.0 # yaml-language-server: $schema= https://aka.ms/winget-manifest.installer.1.2.0.schema.json PackageIdentifier: Jsoftware.J.9.03 PackageVersion: 9.03 Platform: - Windows.Desktop FileExtensions: - ijs InstallModes: - silent Installers: - Architecture: x64 InstallerType: nullsoft Scope: user InstallerUrl: https://www.jsoftware.com/download/j903/install/j903_win64.exe InstallerSha256: DFEA3F769B13581447D5C7AE183754AD4952235581BD5C5D189A7D86197ED541 InstallerSwitches: Custom: /currentuser ReleaseDate: Dec 2021 - Architecture: x64 InstallerType: nullsoft Scope: machine InstallerUrl: https://www.jsoftware.com/download/j903/install/j903_win64.exe InstallerSha256: DFEA3F769B13581447D5C7AE183754AD4952235581BD5C5D189A7D86197ED541 InstallerSwitches: Custom: /allusers ReleaseDate: Dec 2021 ManifestType: installer ManifestVersion: 1.2.0 On Sun, Jan 1, 2023 at 10:36 AM Eric Iverson <eric.b.iver...@gmail.com> wrote: > winget sounds interesting and I encourage you to explore further. > > My reservation is that it bypasses all attempts we make on the wiki pages > to inform users as to what they are getting and how to make use of it. But > that may be a lost cause. And winget would certainly be easier for those > who know exactly what they are doing. > > Ideally it would handle beta releases as well as stable. > > On Sat, Dec 31, 2022 at 12:28 AM Ric Sherlock <tikk...@gmail.com> wrote: > > > Is there any interest from JSoftware in making J available for > installation > > via the Windows Package Manager? > > > > I've been using the Windows Package Manager > > <https://learn.microsoft.com/en-us/windows/package-manager/> (via the > > command line tool winget) to install applications on Windows for a year > or > > so. It is a welcome improvement on the traditional (for Windows) > > time-consuming procedure (navigate-to-website, find-download-page, > > download-software-installer, run-software-installer, configure-software). > > > > The number, quality and variety of available Packages > > <https://github.com/microsoft/winget-pkgs/tree/master/manifests> is > > compelling. Other programming languages represented are Julia, Python, > > Scala, Golang, Erlang, Racket, Groovy. > > > > From what I can see making a J package available would just involve > > creating > > an appropriate manifest (Yaml file describing the current *.exe > installer), > > and submitting that manifest to the winget-pkgs GitHub repo > > <https://github.com/microsoft/winget-pkgs>. > > > > Once the PR is accepted, it would be possible to install J on Windows by > > simply running `winget Jsoftware.Jlang.9.03` (or similar) from a cmd or > > Powershell session. > > > > If there is any interest (or at least no opposition :-) ), I'd be happy > to > > investigate further. I'm equally happy to leave it for JSoftware to > action > > if preferred. > > > > Wishing you all a happy New Year! > > Ric > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
