When I emerge issue-tracker, the next message view: ---------------------------------------------- >>> md5 src_uri ;-) issue-tracker-4.0.3.tar.bz2 * Ebuilds (like this one) that use the webapp-apache.eclass need to * be converted to use the new webapp.eclass, to be compatible with * webapp-config. * * Please file a bug on http://bugs.gentoo.org/, stating that this * ebuild needs converting to use the new approach. * Installing for Apache v2 i not have problem to running or using issue-tracker ! i only follow indication message Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" emerge issue-tracker 2. 3. Actual Results: Calculating dependencies ...done! >>> emerge (1 of 1) net-www/issue-tracker-4.0.3 to / >>> Downloading http://128.213.5.34/gentoo/distfiles/issue-tracker-4.0.3.tar.bz2 --14:07:25-- http://128.213.5.34/gentoo/distfiles/issue-tracker-4.0.3.tar.bz2 => `/usr/portage/distfiles/issue-tracker-4.0.3.tar.bz2' Connecting to 128.213.5.34:80... connected. HTTP request sent, awaiting response... 200 OK Length: 191,396 [application/x-tar] 100%[====================================>] 191,396 50.26K/s ETA 00:00 14:07:30 (48.30 KB/s) - `/usr/portage/distfiles/issue-tracker-4.0.3.tar.bz2' saved [191396/191396] >>> md5 src_uri ;-) issue-tracker-4.0.3.tar.bz2 * Ebuilds (like this one) that use the webapp-apache.eclass need to * be converted to use the new webapp.eclass, to be compatible with * webapp-config. * * Please file a bug on http://bugs.gentoo.org/, stating that this * ebuild needs converting to use the new approach. * Installing for Apache v2 >>> Unpacking source... Portage 2.0.50-r7 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 i686 Unknown CPU Type Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://128.213.5.34/gentoo/ ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://gentoo.ccccom.com http://gentoo.binarycompass.org" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X apm arts avi berkdb bonobo cdr crypt cups encode esd foomaticdb gdbm gif gpm gtk2 gtkhtml guile imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline sdl slang spell ssl tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib"
Created attachment 35944 [details] issue-tracker-4.0.3-r1.ebuild Updated ebuild with webapp.eclass
Created attachment 35945 [details] files/reconfig
Created attachment 35946 [details] files/postinstall-en.txt
The new ebuild mentions creating a new mysql user & database for issuetracker, however the steps provided do not explain how to create a new user and set a password, only to add a new database with an existing user.
Adding database users is beyond the scope of this ebuild. Please consult the relevant documentation, e.g. http://dev.mysql.com/doc/mysql/en/Adding_users.html
<@rl03> karltk: if you tell me exactly what you want it to do, i'll be happy to give it a shot and show you how things work with wbapp.eclass now <@karltk> rl03: basically, I want it look like this: <@karltk> rl03: emerge issue-tracker <@karltk> rl03: then in in postinstall-en.txt is says "To configure, run ebuild ${path-to-ebuild} config" <@karltk> rl03: when the user does that, the pkg_config() is invoked inside the ebuild, and the reconfig script is run
Adding a pkg_config() goes against our vhost support. Users use the webapp-config script to install multiple copies of an app - not Portage. It's webapp-config that runs the hook script. That's how it's designed to work. Why do you want to make people run pkg_config(), when all of this is already automated? Best regards, Stu
I suppose you could move the db stuff into pkg_config(), and instruct the users to edit the config file with appropriate values. This could be a middle-ground between having it in the reconfig script and not providing any db configuration.
To run properly, mod_php has to be compiled with USE="session", otherwise there is a "Call to undefined function session_save_path()" (same with phpmyadmin) Is it possible to handle this in the ebuild?
issue-tracker-4.0.3-r1.ebuild in the tree
