1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
From 38b34eb851d362ca4ae5a8a960d76229dafe1ea8 Mon Sep 17 00:00:00 2001
From: Dominic Hargreaves <dom@earth.li>
Date: Wed, 27 Mar 2013 23:42:04 +0000
Subject: Reference correct local directory for Debian
Forwarded: not-needed
Patch-Name: debianize_docs_local.diff
---
docs/customizing/styling_rt.pod | 13 ++++++-------
docs/extending/clickable_links.pod | 4 ++--
docs/initialdata.pod | 2 +-
docs/writing_portlets.pod | 8 ++++----
4 files changed, 13 insertions(+), 14 deletions(-)
diff --git a/docs/customizing/styling_rt.pod b/docs/customizing/styling_rt.pod
index ac8eb5dd..d0941efe 100644
--- a/docs/customizing/styling_rt.pod
+++ b/docs/customizing/styling_rt.pod
@@ -85,7 +85,7 @@ default CSS styles, via the C<@CSSFiles> configuration option. To add
an extra CSS file, for example F<my-site.css>, create the local overlay
directory:
- $ mkdir -p local/static/css/
+ $ mkdir -p /usr/local/share/request-tracker5/static/css/
And place your F<my-site.css> file in it. Finally, adjust your
C<@CSSFiles> in your F<RT_SiteConfig.pm>:
@@ -145,14 +145,13 @@ this case, you'll want to create your own CSS directory.
As shown above, the C<local> directory is the place to put
local modifications to RT. Run the following commands in your
-C</opt/rt5> directory (or wherever your RT is installed) to get
-started:
+C</usr/local/share/request-tracker5> directory to get started:
- $ mkdir -p local/static/css/localstyle
- $ cp -R share/static/css/elevator-light/* local/static/css/localstyle/
+ $ mkdir -p static/css/localstyle
+ $ cp -R /usr/share/request-tracker5/static/css/elevator-light/* static/css/localstyle/
- $ mkdir -p local/html/NoAuth/css/localstyle
- $ cp -R share/html/NoAuth/css/elevator-light/* local/html/NoAuth/css/localstyle/
+ $ mkdir -p html/NoAuth/css/localstyle
+ $ cp -R /usr/share/request-tracker5/html/NoAuth/css/elevator-light/* html/NoAuth/css/localstyle/
You can call your "localstyle" directory whatever you want and you don't
have to copy the elevator-light theme to start from, but it's a good place
diff --git a/docs/extending/clickable_links.pod b/docs/extending/clickable_links.pod
index 15fefb5e..073f8558 100644
--- a/docs/extending/clickable_links.pod
+++ b/docs/extending/clickable_links.pod
@@ -54,7 +54,7 @@ arbitrary HTML.
To extend the list of actions with your own types of data, use the
provided callback. Specifically, create the file
-F<local/html/Callbacks/MyCallbacks/Elements/MakeClicky/Default>.
+F</usr/local/share/request-tracker4/html/Callbacks/MyCallbacks/Elements/MakeClicky/Default>.
It will be called with the following arguments:
@@ -130,7 +130,7 @@ groups of your regexps are passed to action.
=head2 Custom MakeClicky action example
-Create a new file F</opt/rt5/local/html/Callbacks/MyCallbacks/Elements/MakeClicky/Default>
+Create a new file F</usr/local/share/request-tracker5/html/Callbacks/MyCallbacks/Elements/MakeClicky/Default>
with the content:
<%ARGS>
diff --git a/docs/initialdata.pod b/docs/initialdata.pod
index d2343349..bd711e12 100644
--- a/docs/initialdata.pod
+++ b/docs/initialdata.pod
@@ -24,7 +24,7 @@ of one another while the top level initialdata file is for fresh RT installs.
Extensions may also ship with database changes in such files. You may find
some in your install with:
- find local/plugins -name initialdata -or -name content
+ find /usr/local/share/request-tracker5/plugins -name initialdata -or -name content
=head1 What can be in an initialdata file?
diff --git a/docs/writing_portlets.pod b/docs/writing_portlets.pod
index e82e008d..c27f94d4 100644
--- a/docs/writing_portlets.pod
+++ b/docs/writing_portlets.pod
@@ -13,7 +13,7 @@ There are at least two things you have to do to create a portlet:
=item Create the template
-Create a Mason template in C</opt/rt5/local/html/Elements> that defines
+Create a Mason template in C</usr/local/share/request-tracker5/html/Elements> that defines
your portlet's behaviour.
=item Set C<$HomepageComponents> config
@@ -37,9 +37,9 @@ the "body" (left) or "summary" (right) columns of the home page.
They can also appear on the Self-Service interface, but have to be
hard-coded, because Self-Service users don't have the same preferences
available to them. You will have to create your element in
-C</opt/rt5/local/html/SelfService/Elements>, then exend the SelfService
-interface to call it. Copy C</opt/rt5/share/html/SelfService/index.html> to
-C</opt/rt5/local/html/SelfService/index.html>, then edit it to add:
+C</usr/local/share/request-tracker5/html/SelfService/Elements>, then exend the SelfService
+interface to call it. Copy C</usr/share/request-tracker5/html/SelfService/index.html> to
+C</usr/local/share/request-tracker5/html/SelfService/index.html>, then edit it to add:
<& /SelfService/Elements/MyPortlet &>
|
