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

[FR] Binary flag #1000

Closed
oparoz opened this issue Sep 5, 2014 · 3 comments
Closed

[FR] Binary flag #1000

oparoz opened this issue Sep 5, 2014 · 3 comments

Comments

@oparoz
Copy link

oparoz commented Sep 5, 2014

When using a mix of binary packages and ports compiled with portmaster, there are conflicts in terms of package management as both pkgng and portmaster want to update the same ports.

I can give you the example of LibreOffice, which we did not want to compile. It has a dependency on libGL 7.6, but the source tree has 9.1.
pkgng does not need to update it, but portmaster wants to and wants to install all the dependencies which go with it and which we didn't want to compile in the first place. Same problem with gtk2, etc.

pkg info -f shows no binary flag, there is only an annotation section where you can see that the package was pre-built, so there really isn't an easy to be able to quickly filter out binary packages.

Could we have a binary flag?

@bdrewery
Copy link
Member

IMHO the better approach here is to have packages built from ports annotate themselves in a way such that pkg upgrade will prefer to not replace them by default if the options did not match the default when it was built.

As for portmaster/portupgrade/ports, these need to be smarter such that they can use remote packages if possible, checking for correct arch/options/version. If all of those match then the remote package can be used, otherwise use the port. This would help, but it require ports/portmaster/portupgrade be the driver on a system. Portmaster could annotate the ports it installs such that it will not touch ports it did not install, but I think it would be better to have it just use a remote package if it matches what the user wants. Currently the remote packages features of portmaster are all disabled. I'm working on fixing that now (at the least the dumb version). A smarter options-checking one will come later.

@bdrewery
Copy link
Member

My first point is related to repo binding. Ports needs to be "just another repository" to Pkg. It should have a way to strongly prefer Pkgs from a specific repo and never from another. Perhaps ports needs a way to set this annotation by default.

@bapt
Copy link
Member

bapt commented Nov 12, 2016

There is now an annotation repository_type: binary

@bapt bapt closed this as completed Nov 12, 2016
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

No branches or pull requests

3 participants