apkg (package management)

[alexcoder04]

Discussion about package management after switching to apkg as default package manager.

The roadmap for apkg is described here: lcpluginmaker/apkg#3

The idea is to have similar package management like most Linux distros:

1. Switch to *.lcpkg packages, which are just zip files containing all the files of the corresponding package as well as the metadata.
2. These files can be saved on a http server (own or raw.githubusercontent.com/...) or a local/network folder inside what called a repository. It also contains some metadata about the packages etc (no more need for PackageList.txt).
3. You can enable/disable different repositories with apkg.
4. The *.lcpkg files are built with an external script, because I'm not so good at C# -_-. However, it will be integrated into the apkg command (subcommand calls the external script).

[alexcoder04]

Pre-release of apkg v1.0.0 was released just now, but it still needs a lot of testing, refactoring, error handling implementing etc., so it's not ready for interation quite yet, however, we are on a good way

[alexcoder04]

I guess it's time to decide which repositories we will have. I would suggest something like this:

1. Main repository with official plugins. Enabled by default. Contains plugins from LC developers themselves and "trusted users". Plugin repositories can have Github Actions set up, so they push their latest version to the repo automatically on every release.
2. "contrib"/unofficial repository. Disabled by default. Moderated by LC devs, contains plugins from other users. Similar to the AUR.
3. User repositories, created and managed by third parties. Can be enabled manually.