gentoo-utils/gentoo-utils-gitea
2
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Releases Activity

WIP: impl profile evaluation #7

Draft
jturnerusa wants to merge 10 commits from feature/profiles into master
pull from: feature/profiles
merge into: gentoo-utils:master
Conversation 2 Commits 10 Files Changed 49 +9
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 18b7a468b2 - Show all commits

9
src/repo/profile/mod.rs
View File

@@ -52,6 +52,7 @@ pub struct Profile {
#[get(kind = "deref")]
path: PathBuf,
eapi: Option<Eapi>,
deprecated: Option<String>,
#[get(kind = "deref")]
parents: Vec<Profile>,
make_defaults: HashMap<String, String>,
@@ -100,6 +101,13 @@ impl Profile {
Err(e) => return Err(Error::Io(eapi_path, e)),
};
let deprecated_path = path.as_ref().join("deprecated");
let deprecated = match fs::read_to_string(&deprecated_path) {
Ok(string) => Some(string),
Err(e) if matches!(e.kind(), io::ErrorKind::NotFound) => None,
Err(e) => return Err(Error::Io(deprecated_path, e)),
};
let make_defaults = make_defaults::evaluate(&parents, &path)?;
jturnerusa marked this conversation as resolved Outdated
penguin commented 2025-12-11 12:49:41 -06:00
Outdated
Review
Copy Link

I think the default behavior for no eapi file per the spec is to treat it as eapi 0. Do we do that here, or are we erroring out if there's no eapi file?

Maybe it should assign eapi 0 on failure to parse (no eapi file), then later during evaluation of the parsed profile you throw an error saying you don't support eapi 0. That way eapi 0 (or other versions) could be supported later without having to change parsing logic.

I think the default behavior for no eapi file per the spec is to treat it as eapi 0. Do we do that here, or are we erroring out if there's no eapi file? Maybe it should assign eapi 0 on failure to parse (no eapi file), then later during evaluation of the parsed profile you throw an error saying you don't support eapi 0. That way eapi 0 (or other versions) could be supported later without having to change parsing logic.
👍 1
let packages = packages::evaluate(&parents, &path)?;
@@ -124,6 +132,7 @@ impl Profile {
path: path.as_ref().to_path_buf(),
parents,
eapi,
deprecated,
make_defaults,
packages,
package_mask,