Edgar Fuß <ef%math.uni-bonn.de@localhost> writes: > So what's the best way to go (apart from adding a poppler-cairo-utils package)? This is typically messy, and depends on how much pain is caused for who and what the socially optimal choice is. > -- Add the build dependency to print/poppler, let it install poppler-cairo.pc > and remove it from print/poppler-glib's PLIST? The question is how many people want to use poppler and not have cairo installed. If almost zero, this might be a good approach. > -- Add a poppler-cairo package (with a full dependency on cairo) that only > installs poppler-cairo.pc (removing it from print/poppler-glib)? That is probably optimal in terms of not forcing dependencies on people that they don't work, but adds a package. > -- Leave it as is and let the new poppler-cairo-utils package depend on > poppler and cairo directly? How would this work? Wouldn't poppler-cairo.pc not be installed? Or is this in poppler-glib, and that's depended on? If so, what's wrong now that would be fixed? (not challenging, just not clear) > Any better name than poppler-cairo-utils? Just pdftocairo? If that's what it provides, and that is likely to be stable, seems better to me.
Attachment:
signature.asc
Description: PGP signature