<rekado_>would it be acceptable for the CUPS package to create symlinks to the files created by the cups-filters package?
<rekado_>it's not only filters that the cups-filters package adds but also backends, configurations and so on.
<rekado_>filters are called dependent on the mime configuration (if the provided path is absolute), so I can avoid some of the trouble, but it seems that I have to actually link a few files across packages.
<rekado_>(the CUPS package depends on cups-filters)
<rekado_>is it at all possible for a package to read files from any of its input packages?
<rekado_>I want CUPS to create a symlink from out/backend/name to /gnu/store/xxx-cups-filters/backend/name
<taylanub>rekado_: yes, that's pretty standard .. gimme a sec
<rekado_>so far it's failing for me, saying that the file cannot be found.
<taylanub>in a phase procedure, if it takes a keyword argument 'inputs', then it gets an alist of the inputs, where you can assoc-ref "cups-filters" to get /gnu/store/xxx-cups-filters
<rekado_>I have that already. I do get the path to the filter. But when I pass that to (symlink oldpath newpath) it fails, saying that the file at oldpath does not exist.
<taylanub>creating a symlink doesn't require the target to exist ... maybe the parent directory of the symlink doesn't exist?
<rekado_>ah, good point. I guess this may be it. Will check again.
<taylanub>are you sure about the argument order? ln(1) has it reverse: ln symlink-path original-file-path