Changes between Version 49 and Version 50 of TracOnGentoo
- Timestamp:
- Jan 26, 2015, 9:12:11 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracOnGentoo
v49 v50 1 = Installing and Running Trac on Gentoo = 2 '''WARNING''' 3 This page seems very out of date. Have a look at this first: [http://en.gentoo-wiki.com/wiki/Trac Trac - Gentoo Wiki page] 1 = Installing and Running Trac on Gentoo 4 2 5 6 '''Warning: be sure to read the generic TracInstall instructions about the recommended versions of the dependent packages. In particular, pysqlite-1.1.6 is ''no longer'' the recommended version. Use 2.3.2 instead.''' 7 8 Trac is included in portage as of 2004/04/29. Installing is as simple as: 3 Trac is included in [http://packages.gentoo.org/package/www-apps/trac Gentoo portage] as of 2004/04/29. Installing is as simple as: 9 4 10 5 {{{ … … 13 8 14 9 Past that, normal Trac configuration should apply. 10 For the instructions below, read the generic TracInstall instructions about the recommended versions of the dependent packages. 15 11 16 Someone's put together a really nice guide to setting up trac on gentoo [http://home.dju.elegiac.net/wiki/MultipleTracInstancesOnGentoohere].12 A nice guide to setting up Trac on gentoo [http://www.gentoo-wiki.info/Trac here]. 17 13 18 There were a couple of littlethings that were required to make Trac on Gentoo work.14 There were a couple of things that were required to make Trac on Gentoo work. 19 15 20 16 * Make sure your berkdb and python use flags are set! … … 22 18 * '''If you have any trouble, go down to the bottom and start emerging components this is how I figured out that the svn bindings for Python weren't building, etc..''' Be sure to run the python update script if needed. 23 19 24 * Once built, your alias for /trac will be different from the TracInstall doc. It 'll look something like this:20 * Once built, your alias for /trac will be different from the TracInstall doc. It will look something like this: 25 21 26 22 {{{ … … 30 26 This makes Trac all pretty, like you're used to seeing! Otherwise it's got essentially no layout. 31 27 32 == Install Trac from Source ==28 == Install Trac from Source 33 29 34 Attached is the ebuild to build trac from it 's source:trunk.35 To use it save and extract it to your '''PORTDIR_OVERLAY''', normally 30 Attached is the ebuild to build trac from its source:trunk. 31 To use it save and extract it to your '''PORTDIR_OVERLAY''', normally: 36 32 {{{ 37 33 /usr/local/portage/www-apps … … 52 48 mkdir /usr/local/portage/dev-python 53 49 cd /usr/local/portage/dev-python 54 wget http://projects.edgewall.com/trac/attachment/wiki/TracOnGentoo/pysqlite- 1.1.6.tar55 tar xvf pysqlite- 1.1.6.tar56 rm pysqlite- 1.1.6.tar50 wget http://projects.edgewall.com/trac/attachment/wiki/TracOnGentoo/pysqlite-2.3.2.tar 51 tar xvf pysqlite-2.3.2.tar 52 rm pysqlite-2.3.2.tar 57 53 }}} 58 54 To build from what Gentoo provides, although I havent tested like this, simply do: … … 69 65 echo =dev-util/subversion-1.2.1 ~x86 >> /etc/portage/package.keywords 70 66 }}} 71 And you'll probably will also need to (portage will complain):67 And you'll probably will also need to do the following: 72 68 {{{ 73 69 echo =net-www/apache-2.0.54-r13 ~x86 >> /etc/portage/package.keywords … … 77 73 }}} 78 74 79 '''Note:''' portage will complain because this is NOT the right way to do it! You need to use the newer method to unmask masked packages.Please see http://gentoo-wiki.com/Masked for the right way to do this.75 '''Note:''' portage will complain because this is NOT the right way to do it! You need to use the newer method to unmask masked packages. Please see http://gentoo-wiki.com/Masked for the right way to do this. 80 76 81 These are the ebuilds I'm using:77 These are the ebuilds you can use: 82 78 {{{ 83 79 dev-lang/python-2.3.5 … … 85 81 dev-util/subversion-1.2.1 86 82 dev-db/sqlite-3.2.1-r3 87 dev-python/pysqlite- 1.1.6[cutom ebuild - see attached]83 dev-python/pysqlite-2.3.2 [cutom ebuild - see attached] 88 84 dev-libs/clearsilver-0.9.7 89 85 dev-python/docutils-0.3.5 … … 91 87 }}} 92 88 93 == My two cents, 2006-02-24 ==89 == My two cents, 2006-02-24 94 90 95 91 (I'm fairly good with Gentoo). 96 92 97 I'm not sure berkdb needs to be set as mentioned above by another user. You do need to choose between sqlite and postgresql though. Newer ebuilds don't assume sqlite. It may be a good idea to set this in /etc/portage/package.use. This is what I put in there:93 I'm not sure berkdb needs to be set as mentioned above by another user. You do need to choose between SQLite and Postgresql though. Newer ebuilds don't assume SQLite. It may be a good idea to set this in /etc/portage/package.use, such as: 98 94 99 95 {{{ 100 www-apps/trac 96 www-apps/trac enscript silvercity sqlite vhosts 101 97 }}} 102 98 103 There may be some instructions in the output from the ebuilds along the way. Pay attention to these.For instance, you may get this while emerging webapp-config:99 There may be some instructions in the output from the ebuilds along the way. For instance, you may get this while emerging webapp-config: 104 100 105 101 {{{ … … 109 105 }}} 110 106 111 And later, while emerging trac itself, I got this message because I enabled the vhosts USE flag:107 And later, while emerging Trac itself, I got this message because I enabled the vhosts USE flag: 112 108 113 109 {{{ … … 123 119 }}} 124 120 125 If you do '''not''' want trac installed into a virtual host, you can remove the 'vhosts' USE flag, and the installation will continue through installing it at /trac on the default host:121 If you do '''not''' want Trac installed into a virtual host, you can remove the 'vhosts' USE flag, and the installation will continue through installing it at /trac on the default host: 126 122 127 123 {{{ … … 140 136 }}} 141 137 142 == 2010/08, personal use == 143 trac-0.12 no postgres/mysql, sqlite used. 138 == Personal use, 2010/08 139 140 For Trac-0.12 no Postgres/MySQL, SQLite used: 141 144 142 {{{ 145 143 # emerge -vu apache mod_python trac