I must admit that I'm more than a little surprised at the overall consensus here, but it's a very clear one.
As you can imagine I'm in favour of the idea for obvious reasons... but I'd be a fool if I asked for advice on what people thought and then ignored it. For now, I'll say that this idea... from Kamaelia import RandomStuffYouHaveNoIdeaWhereFrom ... is dead in the water for now. But I think the idea can be reworked in a way that works. FWIW, where I'm coming from is here: ~> echo $PATH /opt/kde3/bin:/home/zathras/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/opt/gnome/bin:/usr/lib/qt3/bin ~> which ls /bin/ls Or an example of something that's a pain: $ echo $PATH /bin:/sbin:/usr/bin:/usr/sbin $ which enable /usr/bin/enable $ enable enable . enable : enable [ enable alias enable bg enable bind enable break enable builtin enable cd enable command enable compgen ... (this output of enable is not the declared one by which, but the shell builtin "enable") Essentially I'm wondering how to best implement the equivalent of $PATH for KamaeliaComponents. However, FWIW, it won't be thrown *in* without more discussion, and not in the form I suggested, given various reactions :-) Cheers :-) Michael. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en -~----------~----~----~----~------~----~------~--~---
