On 4/9/14, 3:15 PM, Posternak Michel wrote: > Dear Dr. Hansen, > > Thank you very much for your prompt reply, and for having pointed out > the origin > of the problem when compiling the inkscape package. My next question is > now how > will this bug be practically corrected. Is somebody in your staff > allowed to modify > the code in order to get rid of this mistake, or is it the > responsibility of inkscape > developers ? And also, how will the fink users community be informed > that the > mistake has been corrected ? > > Thank you again for your answer, and best regards, > > Michel Posternak >
Somebody from Fink (probably the maintainer, possibly someone else) will need to put in a patch for our builds which addresses the problem. The inkscape developers are aware of the problem: https://bugs.launchpad.net/inkscape/+bug/1293169 In general, the easiest way to look for packages that have been updated is via the Recent Package updates item on http://www.finkproject.org, because this includes fixes where the package version doesn't change. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
