-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency Types #7
Comments
Addition: This allows packagers to maintain more dependency types, for example optional X11 support (for example for vim) would get the dependency type |
Addition: Packages of course know what dependency types they're installed with, kawa will maintain a |
to keep compatibility, all dependencies that are not prefixed are marked as required. |
now that the only things really missing (apart from this of course) are patch pkgs and errno handling, I'll probably start work on this very soon |
To make things exponentially easier, I'll just say that dependency type tags MUST be 3 chars long. This can change in a future kawa version, so don't rely on 3 char dependency types being a requirement. |
or wait, how about we make it 1-4 chars, yeah, that sounds good |
checklist:
|
kawa should support required/optional/recommended dependencies.
Many package managers accomplish this by creating multiple fields for certain requirement levels.
kawa will implement a way that is more like Gentoo's USE-Flags:
DEPENDS=req:glibc req:libcurl rec:tar rec:xz rec:gzip opt:bash
Every package name in
DEPENDS
has a preceding requirement type + :Required is req, Recommended is rec, Optional is opt and for building Documentation is doc. (Or maybe not, we'll see if we'll add separate *-doc packages (probably))
Kawa's
config.h
will include a list of dependency types that will be selected by default. These settings can be changed by the--no-type
,-Ntype
,--use-type
and-Utype
command-line options.The text was updated successfully, but these errors were encountered: