Skip to content
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

Closed
wants to merge 16 commits into from

Conversation

kalikiana
Copy link
Contributor

Figure out dependencies in a multi-arch compatible way using apt-get build-dep.

Follow-up on go plugin: Cross compile with CGo

@come-maiz
Copy link
Contributor

@kalikiana please resolve the conflics.

@kalikiana kalikiana force-pushed the multi-arch-build-deps branch 2 times, most recently from 680d1a9 to bf536d8 Compare June 16, 2017 13:21
@kyrofa kyrofa added this to the 2.32 milestone Jun 17, 2017
Copy link
Contributor

@kyrofa kyrofa left a 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:{}{} : {}
Copy link
Contributor

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))
Copy link
Contributor

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()?

Copy link
Contributor

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...

Copy link
Contributor Author

@kalikiana kalikiana Jul 10, 2017

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.

@kyrofa kyrofa removed this from the 2.32 milestone Jun 22, 2017
@kalikiana kalikiana changed the title Multi arch build deps repo: multi-arch build deps Aug 8, 2017
@sergiusens sergiusens added this to the 2.35 milestone Aug 10, 2017
@kalikiana kalikiana closed this Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants