-
Notifications
You must be signed in to change notification settings - Fork 440
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
repo: multi-arch build deps #1346
Conversation
@kalikiana please resolve the conflics. |
680d1a9
to
bf536d8
Compare
…ulti-arch-build-deps
bf536d8
to
0706476
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this one. There's a lot of effort dedicated to simply parsing build-dep
's output... are there really no alternatives? Specific questions inline.
The following information may help to resolve the situation: | ||
|
||
The following packages have unmet dependencies: | ||
builddeps:{}{} : {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I typically find that it's clearer to name these when used in a larger template like this. Otherwise changes become quite fragile.
return build_deps | ||
|
||
with tempfile.NamedTemporaryFile(suffix='.dsc') as fake_source: | ||
depends = 'Build-Depends: {}\n'.format(', '.join(package_names)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain how this has different results than using something like apt_pkg.parse_depends()?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems horrifically wrong. Parsing the Debian Source Control file directly should be unnecessary, as APT already has this information...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code generates the .dsc file based on build-packages and calls apt-get build-dep - there's nothing to parse here.
Figure out dependencies in a multi-arch compatible way using apt-get build-dep.
Follow-up on go plugin: Cross compile with CGo