On Oct 12, 2009, at 2:46 AM, Tom G. Christensen wrote:
This is still just a workaround for an issue that RPMforge should have dealt with instead of putting this burden on the user.
eh? how would you suggest that RPMforge address this particular issue? i can see essentially three options:
1) don't package Log::Dispatch 2.24 (and too bad for anybody who needs it) 2) package Sys::Syslog 0.16 without a man page, or with man page in some nonstandard location (thus "hiding" the fact that we're replacing a system package) 3) package Log::Dispatch 2.24 with incorrect dependency information (which means it installs, but potentially doesn't work)
i don't particularly like any of those options better than the current situation. can you suggest another fix?
-steve --If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es/
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
