Dear Tuomo, Dear Joerg Yes, may I just express exactly the same. Over the past few months I have installed ion3 without even the slightest of minimal hassles on quite a number of mac os x's using macports. Now, it's gone and I already am having trouble, having to go through dependencies etc.
Ion is an extremely useful tool, and me and several in my lab now use it effectively. However, we don't want to have to spend a day or more every time we want to reinstall it on some new machine, hunting for dependencies etc. In particular, that'll make sure we *NEVER* update to a newer version if we have a working one... in fact, that's what happened to me before... I stuck with ion1 for ages just because I got all kinds of silly problems compiling it. Thus, from my view and people like me, ion not being available on repositories like macports will just make sure we stick with an even older version than what we would if we were to stick with the ones on the repositories... so seems very counterproductive... Best wishes, Quentin PS: and as we're here: This is what I get when trying to compile: ql:~/Desktop/ion-3rc-20071130% make set -e; for i in libtu libextl libmainloop mod_tiling mod_query mod_menu mod_dock mod_sp mod_sm mod_statusbar de ioncore ion pwm etc utils man po ; do make -C $i; done gcc -Os -W -Wimplicit -Wreturn-type -Wswitch -Wcomment -Wtrigraphs -Wformat -Wchar-subscripts -Wparentheses -pedantic -Wuninitialized -DCF_XFREE86_TEXTPROP_BUG_WORKAROUND -DHAVE_SNPRINTF -c output.c -o output.o In file included from output.c:23: private.h:15:21: error: libintl.h: No such file or directory output.c: In function 'fallback_warn': output.c:116: warning: implicit declaration of function 'dgettext' output.c:116: warning: incompatible implicit declaration of built-in function 'dgettext' make[1]: *** [output.o] Error 1 make: *** [subdirs] Error 2 ... Thank you for any help... On Dec 17, 2007 11:04 AM, Joerg van den Hoff <[EMAIL PROTECTED]> wrote: > tuomo, > > I today learned 2 things: > > a) ion3 has been removed from `macports' which is the MacOSX > package management system. in terms of installed base, if > one can believe available statistics, macos x is _much_ > larger than all the other *ixes and *uxes together -- > actually the only OS besides windows with a significant > number of installations (sure, how many mac users actually > install x11-wms - or other open source software for that > matter - is a different question). it's in this respect not > a peripheral platform. > > b) debian seems to distribute now ion3 under some nonsense > name (particelMan?) in order to adhere to your licence (I > was'nt aware of this naming aspect, actually). > > you sure, that that's what you want for `ion3'. some kind of > name aliasing tricks for the only reason that your license > calls for such things? which does prevent exactly what? > which does have exactly what benfits? > > I think it really would be a wise and nice thing to do and > draw a line at demanding some unambigous info in the package > that it's none of your buiseness if an old version does not > work as expected. enforcing "under cover" names is > ridiculous. > > otherwise this seems a sure strategy to finish `ion3' off > outside of a _very_ small group. I'm sure you would'nt care > but need you enforce such a thing? > > joerg > >
