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

x11-terms/terminology unbundle lz4 and fix efl dependencies on 1.2.1 #9636

Closed
wants to merge 2 commits into from
Closed

x11-terms/terminology unbundle lz4 and fix efl dependencies on 1.2.1 #9636

wants to merge 2 commits into from

Conversation

juippis
Copy link
Member

@juippis juippis commented Aug 20, 2018

This change probably doesn't need a revbump, but to be sure I decided to do it. Terminology compiles in 30 seconds so no huge harm there (+ the USE-flag change probably makes everyone re-compile anyway).

@gentoo-bot
Copy link

Pull Request assignment

Areas affected: ebuilds
Packages affected: x11-terms/terminology

x11-terms/terminology: @juippis, @gentoo/proxy-maint

Bugs linked: 648834

In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

@gentoo-bot gentoo-bot added self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else) assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. labels Aug 20, 2018
default
xdg_environment_reset

if use system-lz4 ; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the patch is really tiny, apply it unconditionally

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and always use system-provided lz4 rather than bundled one? What if the build fails with system one? I wanted to apply it unconditionally but couldn't answer this question myself, so decided to make it a USE flag.

Copy link
Contributor

@Zlogene Zlogene Aug 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but is there a reason to use bundled lz4? By standards and security reasons we try not to use bundled libs at all if possible. So it is better to just make sure it works and leave it with the system one.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By standards and security reasons we try not to use bundled libs at all if possible.

I'm aware :)
My logic was, that it was probably bundled due to system lz4 causing breakages, and I didn't wish for that to happen. I'll gladly apply it unconditionally.

And I talked about this with the author in IRC, and he's getting rid of it with terminology-1.3 (https://phab.enlightenment.org/T7328)

Anyway I'll remove the USE-case and rebase this PR in a minute.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

- Add patch to use system liblz4 instead of bundled one,
- More accurate dependencies on dev-libs/efl to use with wayland.

Closes: https://bugs.gentoo.org/648834

Package-Manager: Portage[mgorny]-2.3.43.3
Package-Manager: Portage[mgorny]-2.3.43.3
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2018-08-20 13:00 UTC
Newest commit scanned: 8d11fcf
Status: ✅ good

No issues found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else)
Projects
None yet
4 participants