cargo-ebuild
PDM
Our great sponsors
cargo-ebuild | PDM | |
---|---|---|
6 | 47 | |
79 | 6,553 | |
- | 5.2% | |
0.9 | 9.6 | |
over 2 years ago | 4 days ago | |
Rust | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-ebuild
-
diziet | Debian’s approach to Rust
In Gentoo, Rust crates are just normal files to be downloaded in order to build a given package. The package pins (and checks the hashes of) the crate deps, and builds using cargo --offline. There is no serde/clap/etc packages, just ripgrep/librsvg/etc packages. There is no need to patch all packages to use the same serde crate version. Packaging a Rust program in gentoo is pretty much automatic.
-
How do I adjust fan curves on AMDGPU?
Then, I went through like 3 different pages on gentoo and learned how to make my own rebuild using this... But after setting up my custom repo and making sure it had the right permissions, manifest, etc. the ebuild failed on account of not being able to find the Config.yoml file it needed, which exists in the directory I built the ebuild from. I think I am just SOL on this, and will have to probably find a different approach
-
Cooperative Package Management for Python
FWIW it's worth for portage (Gentoo) there is g-sorcery[0], which can create ebuilds for Emacs (m/elpa) and python packages automatically. Similarly there is also cargo-ebuild[1] which can create ebuilds for rust programs/libraries, including a list of all dependencies with hashes.
I've successfully used cargo-ebuild in the past to create ebuilds automatically, it's a breeze. I'd be surprised if similar tools didn't exist for deb/rpm based distros.
[0]:https://github.com/jauhien/g-sorcery
[1]: https://github.com/cardoe/cargo-ebuild
-
Can Anybody Help Me With My Custom Ebuild for xplr?
I'm working on a custom repository where I intend to write ebuild files for packages that's not supported by Gentoo's repository. Right now, I'm trying to write an ebuild file for xplr, which is a Rust project that uses the Cargo build system. Initially, I used the cargo-ebuild tool, which generated the file xplr-0.14.3.ebuild.
-
Wrote my first ebuild and created an overlay
Maybe you already know, but specifically for making Rust ebuilds and filling the CRATES variable there's a tool cargo-ebuild to automatically extract that from Cargo.toml.
-
In the full retrospect what are some pros and cons on converting to gentoo from the blue distro?
I have zero issues with Gentoo's Rust and Rust-using packages. I use rustup's Rust and cargo install for development, and maintain a gentoo package using cargo ebuild.
PDM
-
Implementing Quality Checks In Your Git Workflow With Hooks and pre-commit
# See https://pre-commit.com for more information # See https://pre-commit.com/hooks.html for more hooks repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v3.2.0 hooks: - id: trailing-whitespace - id: end-of-file-fixer - id: check-yaml - id: check-toml - id: check-added-large-files - repo: local hooks: - id: tox lint name: tox-validation entry: pdm run tox -e test,lint language: system files: ^src\/.+py$|pyproject.toml|^tests\/.+py$ types_or: [python, toml] pass_filenames: false - id: tox docs name: tox-docs language: system entry: pdm run tox -e docs types_or: [python, rst, toml] files: ^src\/.+py$|pyproject.toml|^docs\/ pass_filenames: false - repo: https://github.com/pdm-project/pdm rev: 2.10.4 # a PDM release exposing the hook hooks: - id: pdm-lock-check - repo: https://github.com/jumanjihouse/pre-commit-hooks rev: 3.0.0 hooks: - id: markdownlint
-
Beginning Python: Project Management With PDM
PDM is a solution that allows for easy creation and management of python projects. Some of the key features that will improve the management of python projects include:
-
A question about good practice when using docker.
You'd need a proper dependencies management tool like PDM or Poetry to exhaustively resolve and lock down all the transitive dependencies if you want to have anything closed to reproducible build.
-
pdm-dotenv: Simplify Your Project's Environment Variable Management
Are you working on a Python project that uses pdm for dependency management and dotenv for local environment variable and secrets management? Do you find it frustrating when CLI tools like pgcli don't automatically pick up your .env file, forcing you to resort to npm install -g dotenv-cli? I've got a more convenient solution for you!
-
PEP 582 rejected - consensus among the community needed
I first learned about PDM from a blog post written by one of the PDM contributers. The post was about OOPifying argparse to allow for easy creation/modification of subcommands that exist as their own classes/files, and to avoid maintaining a single long script with an endless number of subparser.add_argument(...) lines.
-
PEP 704 – Require virtual environments by default for package installers
That's more or less what PEP 582 plans to do, but it's been stalled and mired in discussions for years. The PDM tool went ahead and implemented it though if you want to use it: https://github.com/pdm-project/pdm
-
This Week In Python
pdm – A modern Python package and dependency manager
- Pdm: A modern Python dependency manager supporting the latest PEP standards
-
How does a virtual environment work?
pdm and PEP 582 enter the chat
-
Boring Python: Code Quality
I'm liking PDM for a while now. Quicker than Poetry and built according to the Python package spec in mind and not as an afterthought. While it was originally meant to work with PEP 582, it works with virtual environments too (now default).
https://github.com/pdm-project/pdm
What are some alternatives?
cargo-bitbake - cargo extension that can generate BitBake recipes utilizing the classes from meta-rust
Poetry - Python packaging and dependency management made easy
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
conda - A system-level, binary package and environment manager running on all major operating systems and platforms.
cargo-update - A cargo subcommand for checking and applying updates to installed executables
pip-tools - A set of tools to keep your pinned Python dependencies fresh.
cargo-make - Rust task runner and build tool.
pip - The Python package installer
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml
Pipenv - Python Development Workflow for Humans.
cargo-benchcmp - A small utility to compare Rust micro-benchmarks.
PyFlow - Visual scripting framework for python - https://wonderworks-software.github.io/PyFlow