www-apache/anyterm-1.1.25 was released on 2008-08-15.
Actually, anyterm 1.1.26 was released as well, and it no longer contains an apache module. I wrote a new ebuild, which I attach, following the instructions on the anyterm web page. It is installs anyterm as a standalone daemon, and the apache part as a webapp
Created attachment 170492 [details] new anyterm ebuild
Created attachment 170493 [details] files/init.d Init script for anyterm
Created attachment 170495 [details] files/conf.d conf.d file for anyterm
Created attachment 170496 [details] files/postinstall-en.txt post install instructions for the apache configuration (displayed by webapp-config)
this also needs metadata.xml updates and should be moved to www-apps
www-apps/anyterm-1.1.27 was released on 2008-10-26.
Thank you Arfrever for report and Moshe for contribution. Actually this new versions of anyterm provide only daemon which is the only piece which is required to make anyterm workable. Thus it's not web-app any more (in sense nothing need to be installed in htdocs). It's not have apache module... There are different ways to setup this thing: http://anyterm.org/1.1/install.html Taking into account that daemon works on it's own, I've decided not to put apache2 or stunnel USE flags in ebuild and not to depend on apache/stunnel as they are run time dependencies only and they are very setup dependent.
(In reply to comment #8) > Thank you Arfrever for report and Moshe for contribution. Actually this new > versions of anyterm provide only daemon which is the only piece which is > required to make anyterm workable. Thus it's not web-app any more (in sense > nothing need to be installed in htdocs). It's not have apache module... > > There are different ways to setup this thing: > http://anyterm.org/1.1/install.html > > Taking into account that daemon works on it's own, I've decided not to put > apache2 or stunnel USE flags in ebuild and not to depend on apache/stunnel as > they are run time dependencies only and they are very setup dependent. > The main problem is that, as explain on the above web page, the anyterm daemon by itself is insecure. So if no mention is made, someone who just installs anyterm and doesn't look at the web page is left with an insecure system without even knowing it. The other point is that (as mentioned on the web page) the web-app module allows you to modify the properties of the terminal without recompiling anyterm. By the way, version 1.1.28 is out, and the build system has slightly changed. I attach a modified ebuild.
Created attachment 179557 [details] ebuild for anyterm-1.1.28
Moshe, probably I haven't made that clear, but I've bumped 1.1.28 version... Just emerge --sync to see that. And yes, by default anyterm is not secure, but those who have not read documentation deserve their systems to be cracked... That's said, any further suggestions (preferably in form of patches) on how to improve this package are welcome.
Can someone tell me how to make this thing work? I can't find any Gentoo specific instructions for anyterm. I have emerged anyterm 1.1.29 Now what? :( Ken - vk4akp@gmail.com .-.-.
Ken, you have better change if you ask on forums.gentoo.org or gentoo-user mailing list. As I wrote you I've used it very long time ago and while it worked fine at that time I don't have working installation right now and so I don't have configs at hand. WBR.
