You really don't want todo that because of the following reasons:Also, you can't destinguish them... as .so dependencies already existed.
If we would have called them ".fish" then you would know --> ".fish" is a
-devel dependency.
I don't think we need virtual provides at all, as we could resolve the dependancy at the build stage of the package to the package name.
- multiple packages can Provide the same thing. Which one are you going to choose?
- change in package name (or version) means that you need to rebuild everything that depends on it.
- breaks possible cross distribution dependencies;
if I think a bit longer, I could come up with more...
The requires script could check which package provides the requiredI wouldn't recommend this, sorry.
library and put that package name in the dependancy list.
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
