search for: eapi

...ed document can be used for programmatically identifying what is currently considered part of the C API. The result so far is an experimental function tools:::funAPI(): > head(tools:::funAPI()) name loc apitype 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi 2 alloc3DArray WRE api 3 allocArray WRE api 4 allocLang WRE api 5 allocList WRE api 6 allocMatrix WRE api The '...

...he to use SSL. I came across the following resource: http://tud.at/programm/apache-ssl-win32-howto.php3 When I finally brought the application up, I encountered the following errors in the Apache log: [warn] Loaded DSO modules/mod_scgi.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) [warn] Loaded DSO C:/INSTAN~1/php/php4apache.dll uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) Although the explanation is fairly straightforward, I have no clue how to recompile those dll''s on a windo...

...tically identifying what is currently considered part of the C > API. The result so far is an experimental function tools:::funAPI(): > > > head(tools:::funAPI()) > name loc apitype > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > 2 alloc3DArray WRE api > 3 allocArray WRE api > 4 allocLang WRE api > 5 allocList WRE api > 6 allocMatrix...

...tically identifying what is currently considered part of the C > API. The result so far is an experimental function tools:::funAPI(): > > > head(tools:::funAPI()) > name loc apitype > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > 2 alloc3DArray WRE api > 3 allocArray WRE api > 4 allocLang WRE api > 5 allocList WRE api > 6 allocMatrix...

...tically identifying what is currently considered part of the C > API. The result so far is an experimental function tools:::funAPI(): > > > head(tools:::funAPI()) > name loc apitype > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > 2 alloc3DArray WRE api > 3 allocArray WRE api > 4 allocLang WRE api > 5 allocList WRE api > 6 allocMatrix...

...ed part > of the C > API. The result so far is an experimental function > tools:::funAPI(): > > ? ? ?> head(tools:::funAPI()) > ? ? ? ? ? ? ? ? ? ? ?name? ? ? ? ? ? ? ? ? ? loc apitype > ? ? ?1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h? ? eapi > ? ? ?2? ? ? ? alloc3DArray? ? ? ? ? ? ? ? ? ? WRE? ? ?api > ? ? ?3? ? ? ? ? allocArray? ? ? ? ? ? ? ? ? ? WRE? ? ?api > ? ? ?4? ? ? ? ? ?allocLang? ? ? ? ? ? ? ? ? ? WRE? ? ?api > ? ? ?5? ? ? ? ? ?allocList? ? ? ? ? ? ? ? ? ? WRE? ? ?api > ? ? ?6? ? ?...

...t; > API. The result so far is an experimental function > > tools:::funAPI(): > > > > > head(tools:::funAPI()) > > name loc apitype > > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > > 2 alloc3DArray WRE api > > 3 allocArray WRE api > > 4 allocLang WRE api > > 5 allocList WRE api &gt...

I have just upgraded my gentoo system to dovecot 2.0.11. The ebuild on http://wiki2.dovecot.org/Plugins/deleted-to-trash does not compile. I have modified this to a working version - see below. # cat dovecot_deleted_to_trash-0.3.ebuild EAPI="2" DESCRIPTION="Deleted to trash IMAP plugin for Dovecot" HOMEPAGE="http://wiki2.dovecot.org/Plugins/deleted-to-trash" RESTRICT="nomirror" SRC_URI="http://wiki2.dovecot.org/Plugins/deleted-to-trash?action=AttachFile&do=get&target=deleted-to-tra...

Hello, I built apache+openssl+mod_ssl. It is working fine, and I have been starting the server with: apachectl startssl Recently, however, I have decided that I will not be doing anything over https (for a while, at least) with this web server, so for security reasons, I want to only run on port 80. So now I start the server with: apachectl start And it runs without SSL. My question is, is