You are not logged in.
I am going to make a custom build of MPlayer because I want it patched to take advantage of the Compiz Video plugin. I think I might enable a couple other options that are disabled as well. The thing I'm not sure of is how pacman will react to my package. I know I can install it with pacman, but when a new official MPlayer package is released in the repos, will it update it and override my custom package? If so, I thought it might help if I changed the package name, but then I thought that might mess up dependency tracking. For instance, if I make a custom package of which other packages rely on, will those other packages be able to see mine and list the dependency as fulfilled?
Basically I want a way for my system to see my custom package as something that can fulfill dependencies for other official packages that might rely on that particular program. But at the same time I don't want it overridden when a new official package comes out since it likely won't contain the options I want enabled. If it would give a message indicating a new version is available but not install it, that would really help. Is this possible, and what would be the best way to handle this?
Last edited by nLEyETn (2008-10-06 06:44:47)
Offline
Use the provides= parameter. man PKGBUILD for full details.
Offline
Thanks, that seems to be just what I was looking for ![]()
Last edited by nLEyETn (2008-10-06 06:45:11)
Offline