on Nostr: Nekobit >deps and metadata The Pkgfiles have a "depends" field that accepts ...
Nekobit (npub1csc…kqq2) (npub1ajw…aj8d)
>deps and metadata
The Pkgfiles have a "depends" field that accepts packet dependencies.
Prt-get has a "depinst" switch to install the dependencies first.
It's just that the selection of packages nicely configured with dependencies are those in the official repos and the selection is nowhere as big as gentoo.
But the packaging system is made in a way that it makes it *very* easy to create your own packages.
The only other metadata are some md5 hashes, a .footprint file that documents all the files in the package so as to avoid conflicts/overwrites, and a package db at /var/lib/pkg/db with the ground truth of all the packages and their files installed in the system with prt-get.
The first time you install it that it will take some time to configure those packages not in the official repos.
For me it's easier to maintain than any other system I've used because I know exactly how it's built.
>deps and metadata
The Pkgfiles have a "depends" field that accepts packet dependencies.
Prt-get has a "depinst" switch to install the dependencies first.
It's just that the selection of packages nicely configured with dependencies are those in the official repos and the selection is nowhere as big as gentoo.
But the packaging system is made in a way that it makes it *very* easy to create your own packages.
The only other metadata are some md5 hashes, a .footprint file that documents all the files in the package so as to avoid conflicts/overwrites, and a package db at /var/lib/pkg/db with the ground truth of all the packages and their files installed in the system with prt-get.
The first time you install it that it will take some time to configure those packages not in the official repos.
For me it's easier to maintain than any other system I've used because I know exactly how it's built.