lodosgroup/lpm

an experimental package manager for operating systems

lpm's Issues

rewrite 3rd party dependencies

Lpm must able to build/run without any 3rd party dependency due to design choices, maintainability reasons and security concerns.

Current 3rd party dependencies:

• [ ] ar (we will no longer need this after #41)
• tar
• xz2 (upgraded lz4)
• serde (replaced)
• serde_json (replaced)

pkg protection

Provide a protective feature that can prevent the packages from deleting or updating.

provide lpm sdk with C ABI

• implement logger for sdk
• implement all package functionality of lpm in sdk
• compatible error handling from Rust to C ABI
• provide unified C header for sdk

update-upgrade operations

Since #7 is done, now delete & update-upgrade operations could be implemented to the lpm.

cross tests

implement cross testing for official modules on CI

benchmark json deserializer and optimize duplicated code

json works fine without any problem as it replaced serde and serde_json. It just needs some refactoring on duplicated blocks.

json was made for replacing 3rd party json deserializer dependencies, so I didn't put much effort on performance in order to have extra time on focusing other tasks. Since json crate successfully replaced serde and finished it's first goal, now, optimizing and benchmarking it's performance is the next important goal.

dev guide in repository and doc comments in rust sources

Creating development related documentations in repository level, and writing doc comments all around the rust source code.

execute db operations on pkg installation

When a package is installed, save the relevant information on the package into the database. Right now, package update/delete operations can not be implemented to lpm since program can not find the necessary informations to update/delete packages.

dump snapshot

Dump all lpm context from database, which can be used to recover all packages/states on fresh/newly installed systems.

table versioning mechanism

Create table versioning mechanism using PRAGMA user_version.

provide virtual playground environment

Provide virtual playground environment in some container so people can experience lpm in there without needing distro or lpm installation on their system.

pkg installation flow

The package specification have been updated. So package installation in lpm has to be updated as well. The updated specification is all about checksum validations. meta/checksums.json is renamed to meta/files.json. And the schema of the file is entirely changed as well. Sample data can be found here.

TODOs:

• Checksum related names/data-types should be updated into something related with File.
• Files(in program directory) should not be directly copied into system no longer. Instead, read the meta/files.json and do the checksum validation(for each file) before copying them into system.

implement user prompts

Require user confirmation on operations like install, delete, update, etc.

sql builder

Create SQL builder to avoid using raw statements in codebase. This will reduce the maintainability difficulty of the project and prevent potential bugs that could be hard to debug and detect.

implement dynamic module handling

• remove config file (no longer needed)
• add module
• remove module
• list modules

consider using single extraction algorithm

On extraction process, currently both ar and tar are involved. Consider removing ar and extract everything from the package in single time. This requires changes in build files.

module infrastructure

Create dynamic module infrastructure that are loadable at runtime.

cli module needed

Create cli module to deal with command line arguments.

backup functionality on pkg upgrade/delete operations

Provide backup(snapshot the current version of the pkg) functionality that gets triggered from the cmd arg.

Add new field enable_backup or enable_backup_snapshot (cmd arg overrides this value, so this should only work in case if cmd arg isn't provided) to pkg metadata.

[install] temporary packages

Enhance LPM to support the installation of packages in a temporary form that gets purged on system poweroff and reboots.

Example usage: lpm --install(or -i) --tmp(or -t) $pkg_name

openssl implementation

Implement and use openssl bindings for tls transports and package sign verification(assuming they are signed from the builder server).

Continuous Development using github actions

CD pipeline needed with following actions:

• fmt
• clippy
• test
• build

app context

create app context that get's initialized on lpm execution

for the start context will include:

• args, flags, etc
• db connection

rollback on pkg operation error

Rollback all performed package operations when an error occurs during the package operations.

repository implementetion and dependency resolver

Implement package handling from linked repository and dependency resolver.

Blocked by not having any repository deployed and that is also blocked by not having builder plugin.

install multiple packages at once

Currently, we can only install one package at a time. Improve core::install to make lpm capable of installing multiple packages (e.g., lpm -i lzip gc ed).

P.S.: parser already reads all values

lpm/lpm/cli_parser/src/install.rs

Lines 2 to 3 in 848b7b4

	pub struct InstallArgs {
	pub packages: Vec<String>,

update to lz4 algorithm

requires changes on build files

gracefully exit on installing already installed pkg

Instead of returning an error, print an info msg and gracefully exit the program.

allow installing external packages

Allow installing external packages from 3rd party repository or filesystem rather than official/signed repositories via enabling a flag.

build and install from source

lpm should be capable of installing packages by building them from source.

e.g., usage: lpm --install --from-source(or --compile maybe?) lzip

tracking issue for permission required lpm functions

Following functions must require permissions from cmd or configuration file.

• entry point execution
• plugins
• packages sources (repositories, local package file installation, etc)
• pkg version upgrades (with dependencies, without dependencies)

handle package scripts

Support stage1 scripts that supposed to be executed before or after the package operations.

(first provide sample of the specifications in assets about this feature)

https://github.com/foss-lodpm/assets/tree/main/packaging/ripgrep/stage1

simulation tests

simulate and test package install, delete and update operations

configuration file

A configuration file needed for managing lpm features/options such as package protection, plugin management, repositories, etc.

new log type for success messages

implement new log type for printing success messages with green color

allow running concurrent lpm instances

If the package lists of running operations aren't the same, user should able to run multiple lpm instances at a time.