A recent emerge --update world seemed to break cvsweb for me. When trying to fix this I stumbled across the fact that the cvs version that is in portage is no longer being maintained at that the freebsd people are now maintaining it. The highest version in portage is 1.93 (1.112 seems to be the latest non masked version), however the latest release is actually 3.0.0 (happened late last month). Reproducible: Always Steps to Reproduce: 1. 2. 3. See http://www.freebsd.org/projects/cvsweb.html for more info about cvsweb updates. I have created an ebuild for cvsweb but havn't done much ebuild writing before so I am not sure what the official procedure is for getting it included. Also cvsweb now requires the perl module IPC::Run which isn't in portage yet.
Created attachment 26741 [details] Initial ebuild, still needs perl module installed manually.
I will have to do more research on the matter..sorry for the delay
Hows the additional research going ?
According to INSTALL shipped with cvsweb-3.0.1, the following Perl modules are required (or optional). To enable addition of cvsweb-3.0.1 to portage, I've added all of these modules. Module Version Ships with Perl Type ---------------------------------------------------------- File::Temp 5.8.0 required IPC::Run N/A required MIME::Types N/A optional String::Ediff N/A optional URI N/A required At this point we just need somebody with webapp experience to do the cvsweb magic.
reassigning per agriffis
Created attachment 36843 [details] cvsweb-3.0.1.ebuild webapp.eclass magic. it's 3am here, so somebody please review and commit
Created attachment 36844 [details] files/postinstall-en.txt
In CVS, please test
rl03, thanks for working on this! :-) The postinstall message says to edit /etc/cvsweb/cvsweb.conf, but that file (and that directory) doesn't seem to exist... (reopening)
Ok, it appears the conf is in /var/www/localhost ... is that the right place for it? It also appears that the cgi installs as rwxr-xr-- ... is that correct? I had to chmod o+x to make it work
Bah, I knew I was going to forget to change postinstall instructions. Yes, it is the right place for it, as config files are per vhost, and if it is placed in /etc, then all vhost installations will share one config, which is clearly not we want. I've updated the instructions. As regards chmodding the cgi - we need -r9 of webapp-config, which should be out today.
Ok, then taking a look at viewcvs (the sister prog to cvsweb), it looks like viewcvs's conf files are installed in /etc. Should that be fixed? I don't mind filing a separate bug if you would prefer, but my understanding of webapps stuff is so limited that I'm not sure yet that it is a bug...
Yes, please file a separate bug. Also, webapp-config -r9 is out, please test and close the bug if the cgi is installed with correct permissions.
Yes, it installed correctly this time, thanks.
I filed bug 60893 for the viewcvs problem
It actually didn't. -r9 installs into ${D} correctly, but apparently Portage changes perms somewhere during the install process. Stuart will be testing more filing a bug shortly, and will block this one. Reopening for now.
ok, my apologies to the Portage gods, it was a bug in webapp-config. get -r10, and it should work
