Hi Jack and Alex, I'd like to sincerely apologize about the tone of my previous message. It was a bit unprofessional and I'm deeply sorry for that. I really didn't mean or allude to anything negative about fink which has been working very well for me over the last number of years... It is just recently there have been a number of bugs related to various outside packages preventing from doing successful selfupdates.
In any case, as mentioned since those runs are quite long spitting out lots of compilation and other info, do you need a copy of the entire log file or just certain part of it? Would you accept the file as an attachment or would you rather I do a cut-&-paste and send as a text message? ... Thanks, and again, my sincere apologies. Many thanks for a great job maintaining and keeping fink up to date. Cheers, Saleh On May 11, 2015, at 7:57 AM, Jack Howarth wrote: > Saleh, > I doubt you will find MacPorts as a panacea for your problems. I > maintain a number of packages there as well. The absence of strict > enforcement of build dependencies coupled with the rampant use of > variants in port builds is its own form of torment. For example, pymol > requires... > > require_active_variants tcl "" corefoundation > require_active_variants tk "" quartz > > to provide the correct variants of tcl/tk for running pymol but port > lacks any real enforcement of this requirement so the end users have > to handle it themselves by manually installing the required > dependencies. > Jack > > On Mon, May 11, 2015 at 10:28 AM, Alexander Hansen > <alexanderk.han...@gmail.com> wrote: >> >>> On May 11, 2015, at 04:13, Saleh Elmohamed <m.a.saleh.elmoha...@gmail.com> >>> wrote: >>> >>> That will take quite a while and it will be too big... Not sure will >>> have any time soon to do so. If you guys can't fix these problems >>> then I think I'll just call it quit on fink and move to something else. >>> I just don't have much time for this constant reporting on bugs... >>> >>> -Saleh >>> >> >> Here’s the deal: in general, our developers put packages out after they’ve >> tested them on their own machines. Since build systems can get quite >> complex, it is essentially impossible for a packager to cover every possible >> failure that can occur with every possible interaction with other Fink >> packages. It’s even harder for the case of interactions with packages from >> outside of Fink. That’s why we rely on user reports to help us try to >> mitigate problems as much as we can. Another issue is that not all >> maintainers have access to all OS X versions and sometimes upstreams make >> subtle changes which break builds on some but not all OS X versions, >> particularly on older ones. >> >> If you don’t want to have to report _build_ bugs, then pre-built binaries >> are what you need. Other build systems will have their own build-time >> issues. >> >> -- >> Alexander Hansen, Ph.D. >> Fink User Liaison >> ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ 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
