SquirrelMail has ./configure script in its root directory and config/conf.pl script. Both of these has 644 permissions in squirrelmail-1.4.2-r1.ebuild (maybe in earlier versions, too), so one must fix those manually or run the configuration program with "perl config/conf.pl" command. Here is my suggestion how to fix the SM ebuild, so the configuration programs would be executable right away after emerging SM. --- squirrelmail-1.4.2-r1.ebuild.old 2003-11-14 19:04:20.000000000 +0200 +++ squirrelmail-1.4.2-r1.ebuild 2003-11-14 19:11:22.000000000 +0200 @@ -50,0 +51,3 @@ + # Make SquirrelMail configure scripts executable + chmod 700 ${D}${destdir}/configure + chmod 700 ${D}${destdir}/config/conf.pl
One might also consider 750 or 755 permissions instead of 700.
src_compile() { #we need to have this empty function ... default compile hangs echo "Nothing to compile" } portage never runs configure
If you meant that SM's configure script shouldn't be changed to 700/750/755 permissions, please rethink one more time. :-) The configure script in question is not a traditional GNU ./configure thing, but a shortcut to SM's conf.pl, which is a shell-driven administration interface to SquirrelMail, looking like this: --- SquirrelMail Configuration : Read: config_default.php (1.4.0) --------------------------------------------------------- Main Menu -- 1. Organization Preferences 2. Server Settings 3. Folder Defaults 4. General Options 5. Themes 6. Address Books (LDAP) 7. Message of the Day (MOTD) 8. Plugins 9. Database D. Set pre-defined settings for specific IMAP servers C. Turn color on S Save data Q Quit Command >> ---
the bug is still there, someone should correct it...
Yeah. Leaving this one as is means broken SquirrelMail ebuild. The configure script + config/conf.pl in SquirrelMail should have executable rights per default, since the SquirrelMail sysadmin needs them right after Portage has finished SM installation. This has absolutely nothing to do with src_compile() or ebuild phase in general, this matters afterwards the installation. Please take another look to my suggestion in my initial post, because, I repeat, currently SquirrelMail ebuild is not working as expected. Steps to reproduce the bug in question: 1) emerge squirrelmail 2) cd /var/www/localhost/htdocs/squirrelmail/ 3) ./configure 4) *boom* 5) cd config 6) ./conf.pl 7) *boom* So, situation is the same than if xmms would want you to manually +x before it would run...
Grrrr.... This is also a documentation error.. the Desktop Configuration guide no longer applies.. .and I'm stuck without webmail... that I thought was working! also, about those permissions... 544 or 540 or 500 are much saner 550 if you have multiple admins the ./configure file points to the wrong directory anyway!
The documentation in the desktop configuration guide is outdated. ... and the permissions are all goofy for squirrelmail now... after remerging the squirrelmail.. i saw a hidden note of things to try to make it work... they didn't.. I'm posting that hidden note at the bottom of this message... there will have to be some chmod or chowining of squirrelmail in the rehash of the desktop guide... and or that happening in the ebuild.. (I unemerged it and reemerged it... if I copied it wrong earlier, the permissions should have been corrected by running the ebuild) ******************** Hidden info ****************** Now copy these following configuration files to their destinations and * edit them to configure your settings. This is not done automatically so * that your old settings are not disturbed. For readibility, all files * are relative to /var/www/localhost/htdocs//squirrelmail. * * config/config_default.php -> config/config.php * plugins/retrieveuserdata/config_default.php -> plugins/retrieveuserdata/config.php virus-scan * plugins/virus_scan/config_default.php -> plugins/virus_scan/config.php crypt * plugins/gpg/gpg_local_prefs_default.txt -> plugins/gpg/gpg_local_prefs.txt ldap * plugins/ldapuserdata/config_sample.php -> plugins/ldapuserdata/config.php ssl * plugins/show_ssl_link/config.php.sample -> plugins/show_ssl_link/config.php ssl * plugins/secure_login/config.php.sample -> plugins/secure_login/config.php * * You should also create the file '/var/www/localhost/htdocs//squirrelmail/config/admins' * containing the users who should have access to administrative options. * Put each login on its own line, and be sure to leave a newline at the end of the file. * * You can use the console based configuration tool by executing: * cd /var/www/localhost/htdocs//squirrelmail/config; perl conf.pl * Caching service dependencies... * Service 'metalog' already provide 'logger'!; * Not adding service 'sysklogd'..
i actually don't like the idea of it being executable, i like the idea of running perl configure.pl I think I ended up getting it working... we should only be able to login via ssl over the net.. I found a tutorial that said how to do it with a .htaccess file, maybe that should be taken care of by the squirrelmail installer too?
fixed in ebuilds
