From 94d54537e585ddbb86c6a8482e586af791e44d31 Mon Sep 17 00:00:00 2001 From: Andrew Ruthven Date: Wed, 15 May 2024 22:16:42 +1200 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, create the local overlay directory: - $ mkdir -p local/static/css/ + $ mkdir -p /usr/local/share/request-tracker5/static/css/ And place your F file in it. Finally, adjust your C<@CSSFiles> in your F: @@ -145,14 +145,13 @@ this case, you'll want to create your own CSS directory. As shown above, the C directory is the place to put local modifications to RT. Run the following commands in your -C directory (or wherever your RT is installed) to get -started: +C 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 9f4ef1ec..92d7af02 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. +F. 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 +Create a new file F with the content: <%ARGS> diff --git a/docs/initialdata.pod b/docs/initialdata.pod index 72ccda96..c2d383a0 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 72b7ade8..5393d854 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 that defines +Create a Mason template in C 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, then extend the SelfService -interface to call it. Copy C to -C, then edit it to add: +C, then extend the SelfService +interface to call it. Copy C to +C, then edit it to add: <& /SelfService/Elements/MyPortlet &>