- Notifications
You must be signed in to change notification settings - Fork7
an experimental package manager for operating systems
License
lodosgroup/lpm
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is the main source code repository for Lod Package Manager.
For a comprehensive understanding of the project, refer to this blog postAn Experimental Package Manager For Operating Systems: LPM
Please refer to the documentation atlpm.lodosgroup.org/docs for more information.
If you'd like to add/update or propose packages for the lpm repositories, please visitgithub.com/lodosgroup/package-builds.
To report bugs, suggest improvements, or request new features, kindlyopen a GitHub issue.
For security-related concerns, pleaseopen a private security vulnerability report. We kindly ask you not to create a public issue on GitHub for security matters.
To explore the packages available in the official lpm repositories, visitlpm.lodosgroup.org/explore-packages.
For guidance on contributing, readlpm.lodosgroup.org/docs/contributing/contribution-guidelines/ andlpm.lodosgroup.org/docs/contributing/code-of-conduct/.
Get the latest news and updates about lpmlpm.lodosgroup.org/news.
To install LPM from a specific branch, run the following command:
cargo install --git https://github.com/lodosgroup/lpm --branch main
Alternatively, you can install it from tags:
cargo install --git https://github.com/lodosgroup/lpm --branch<tag>
To confirm a successful LPM installation, simply execute thelpm -v
orlpm --version
command.
If you prefer building LPM from its source code (usually preferred for development), follow these steps:
Clone the lpm repository from GitHub:
git clone https://github.com/lodosgroup/lpm
Change into the cloned repository directory:
cd lpm
Build the lpm executable:
cargo build --release# exclude the `--release` flag for debugging
After the building, you will be able to use the lpm executable undertarget/{debug/release}
directory.
You don't need to install LPM on your host system just to play with it. You can use the docker image instead:
docker run -it ozkanonur/lpm:alpha
If you want to do some benchmarking withperf
tool, you may need to add--privileged
flag:
docker run -it --privileged ozkanonur/lpm:alpha
Now, you can play with LPM as you like in the container without touching your host system.
Migrate LPM database:
The first step is to migrate the LPM database. This process initializes the core database files required for LPM to function effectively.
sudo lpm --update --db
Add repository:
Adding a repository is essential for LPM to access and manage packages. A repository acts as the source of packages for your system. Let's add the
linux-amd64-default
repository as an example.# args: <repository-name> <repository-url>sudo lpm --repository --add linux-amd64-default linux-amd64-default.lpm.lodosgroup.org
Once you've added the repository, LPM will synchronize with the package indexes sourced from the added repository. This indicates that you are all set to install packages.
Install a package:
Installing packages using LPM is straightforward. Simply use the following command, replacing with the name of the package you want to install.
# args: <package-name>sudo lpm --install lzip
To confirm the successful completion of the installation, you can check by running the command
lzip --version
.Delete the installed package:
If you want to delete a package from your system, use the delete command followed by the package name.
# args: <package-name>sudo lpm --delete lzip
These steps cover the basic operations to quickly start using the LOD Package Manager. You can explore the advanced features of LPM from the docs athttps://lpm.lodosgroup.org.
About
an experimental package manager for operating systems
Topics
Resources
License
Code of conduct
Security policy
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Contributors3
Uh oh!
There was an error while loading.Please reload this page.