a sensitive topic, this. the question is: why is it so difficult to install a new gtk? the answer from most linux developers would be, "it WASN'T difficult for me." which follows a long-standing linux tradition of insulting someone for asking a question, instead of answering the question. so, I don't want those kind of responses, please. I am an experienced software developer, and I have spent long hours creating installation scripts. I have been using Linux since 1998, and have had significant experience with SuSe, REdHat, and now, Mandrake distros. the Linux community is beginning to change its attitude towards many issues involving end-user competence/incompetence, but software installation is still a big problem. I think this needs to change. maybe you agree. Consider the JDK...also, like the GTK, a "toolkit", which, ostensibly, contains all the "tools" you'll need to start developing Java/Gnome apps; and that is the goal, after all, isn't it? - to get developers right to the task of developing. The goal really isn't to instruct them, through trial-by-fire, in the ins and outs of software installation. At first, the jdk install was troublesome. But, nowadays, it's just download, run their installer (regardless of the platform), set you PATH (if you feel like it, for convenience), and there you go...start programming in Java. I'd like that to be available for the GTK, as well. Of course, the main problem is freedom - freedom to configure my personal set up like I want. And, no unessecary libraries - if i already have glib at the right level, i don't want some other installation to install it again, over my existing installation. This is a good thing - to the extent that it is managable. Ultimately, I'd like to see the gtk install simply check for the correct level of dependant software during configure, prompt me when it finds a too-low level, and then prompt me to download, install, link, and set paths in the gtk config, so that the installation of gtk is sort of a contiguous, and successful, process. Alternatively, the gtk tarball could simply contain all the dependant libraries, and install them to the installation root of gtk. This solves the problem of the various Linux distros NOT using standardised paths for the standard libraries. Hope this is taken in the best sense - an effort to inspire Gnome development by making the tool kit as easily accessible as possible. -- Kameron Cole IBM Senior Edcation Specialist/Systems Programmer 515.283.2955 _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
