git
#emerge git gitosis-gentoo
gitosis被masked 需要在/etc/portage/package.keyworlds 添加
dev-util/gitosis-gentoo （這種方法不行！要用下面的方法）
如果此時遇到下面這樣的錯誤：
core2 ~ # emerge redmine
* Last emerge --sync was 194d 14m 49s ago.
Calculating dependencies... done!
!!! All ebuilds that could satisfy "redmine" have been masked.
!!! One of the following masked packages is required to complete your
request:
- www-apps/redmine-1.1.1 (masked by: ~amd64 keyword)
- www-apps/redmine-1.1.0 (masked by: ~amd64 keyword)
- www-apps/redmine-1.0.5 (masked by: ~amd64 keyword)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
解決辦法：
vim /etc/portage/package.keywords
在此文件裏添加“www-apps/redmine”這麼一句即可。（也可以這樣做：
echo "www-apps/redmine" >> /etc/portage/package.keywords）
redmine
1. emerge redmine
：（ 也被masked，同上處理下
2.
* Execute the following command to initlize environment:
*
* # cd /var/lib/redmine
* # cp config/database.yml.example config/database.yml
* # ${EDITOR} config/database.yml
* # emerge --config =www-apps/redmine-0.9.2
3. Create an empty database and accompanying user named redmine for example.
For MySQL:
create database redmine character set utf8;
create user 'redmine'@'localhost' identified by 'my_password';
grant all privileges on redmine.* to 'redmine'@'localhost';
4. Copy config/database.yml.example to config/database.yml and edit this file in order to configure your database settings for "production" environment.
Example for a MySQL database:
production:
adapter: mysql
database: redmine
host: localhost
username: redmine
password: my_password
If your server is not running on the standard port (3306), use this configuration instead:
production:
adapter: mysql
database: redmine
host: localhost
port: 3307
username: redmine
password: my_password
5. Generate a session store secret. This is required on the trunk version of Redmine at r2493 or above and the released 0.8.7 version or above.
Redmine stores session data in cookies by default, which requires a secret to be generated. This can be done by running:
RAILS_ENV=production rake config/initializers/session_store.rb
If you're using an SVN version of Redmine post r3055, the above file will no longer exist; it was deprecated as of r3054. On these versions, run
rake generate_session_store
6. Create the database structure, by running the following command under the application root directory:
RAILS_ENV=production rake db:migrate
It will create tables and an administrator account.
7. Insert default configuration data in database, by running the following command:
RAILS_ENV=production rake redmine:load_default_data
This step is optional but highly recommended,as you can define your own configuration from scratch. It will loaddefault roles, trackers, statuses, workflows and enumerations.
8. Setting up permissions
NB: Windows users have to skip this section.
The user who runs Redmine must have write permission on the following subdirectories: files, log, tmp (create the last one if not present).
Assuming you run Redmine with a redmine user:
mkdir tmp public/plugin_assets
sudo chown -R redmine:redmine files log tmp public/plugin_assets
sudo chmod -R 755 files log tmp public/plugin_assets
9. Test the installation by running WEBrick web server:
ruby script/server webrick -e production
Once WEBrick has started, point your browser to http://localhost:3000/. You should now see the application welcome page.
10. Use default administrator account to log in: