#52259: w3m doesn't show images -------------------------------+-------------------------------- Reporter: bschack-pchome@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: w3m | -------------------------------+-------------------------------- Comment (by ken.cunningham.webuse@…): You sound like a person who might be ready for "MacPorts Grade 2"! Let Macports do most of the work for you - download, sandbox, cover dependencies. But you can modify what happens if you like. Of course, you're in Grade 2 now, so you'll need to cover a certain degree of your own messes, should you make them. If you get stuck, you can usually backtrack out of the situation with "sudo port uninstall w3m" (or whatever you're working on. Try something like this {{{ sudo vi `port file w3m` }}} or perhaps {{{ bbedit `port file w3m` }}} up comes the w3m portfile, and here you see what the person who wrote the original portfile was thinking about the configuration... {{{ configure.args --with-gc=${prefix} \ --with-ssl=${prefix} \ --enable-keymap=w3m \ --with-termlib=ncurses \ --with-libiconv-prefix=${prefix} \ --with-libintl-prefix=${prefix} \ --disable-image \ --mandir=${prefix}/share/man }}} hmmm -- you don't like "--disable-image"? Edit it in the portfile {{{ configure.args --with-gc=${prefix} \ --with-ssl=${prefix} \ --enable-keymap=w3m \ --with-termlib=ncurses \ --with-libiconv-prefix=${prefix} \ --with-libintl-prefix=${prefix} \ --enable-image \ --mandir=${prefix}/share/man }}} and then give it a try. See if it builds. Maybe it does -- on 10.11. But what about 10.9? Hmm.. find a friend, or use another machine. See what happens there. And there are a few variants in the portfile as well, that modify these configure settings. Best try those out as well, to make sure it all still works. You don't want to fix it for yourself and break it for everyone else, after all. You can also let macports do some of the work for you {{{ sudo port extract w3m }}} and then go into the working directory {{{ cd `port work w3m` }}} and look around at what is in there. Maybe there are other configuration options that the original portfile writer wasn't interested in, but you are... If you think your portfile ultimately works better, after you've tested it out sufficiently, OK! You can upload a patch to the portfile (show you how when you get to that point if you need help). Share it with everyone -- that is the whole point of macports, after all! If you like it for your own use, but you really don't think it has 'public consumption' quality -- set up your own local repository (instructions are here on this website), and just leave it there for your own use. It will "shadow" (hide) the macports version of w3m as long as it's in your local repository, and even if macports updates theirs, well then you still are using yours.... Of course that might cause you problems two years from now when many things update and yours is too far out of date now ... so you have to keep an eye on what you're doing if you go down this road, and be responsible for at least trying to figure out some of your own issues, should they arise. Good luck!! Ken -- Ticket URL: <https://trac.macports.org/ticket/52259#comment:2> MacPorts <https://www.macports.org/> Ports system for macOS