-
Notifications
You must be signed in to change notification settings - Fork 281
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
Comments
IMHO the better approach here is to have packages built from ports annotate themselves in a way such that 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. |
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. |
There is now an annotation repository_type: binary |
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?
The text was updated successfully, but these errors were encountered: