Browse Source

Moving code from github to own gitea instance

Alois Mahdal 5 years ago
parent
commit
6ca68e91cf
2 changed files with 8 additions and 8 deletions
  1. 7
    7
      README.md
  2. 1
    1
      mkit.ini

+ 7
- 7
README.md View File

23
 All of the above have their own dependencies, so if you want to install everything
23
 All of the above have their own dependencies, so if you want to install everything
24
 manually, follow instructions on their pages.
24
 manually, follow instructions on their pages.
25
 
25
 
26
-  [sbj]: https://github.com/AloisMahdal/shellfu-bash-jat
27
-  [sbx]: https://github.com/AloisMahdal/shellfu-bash-xcase
28
-  [jt]: https://github.com/AloisMahdal/jattool
29
-  [jd]: https://github.com/AloisMahdal/jats-demo
26
+  [sbj]: https://gitea.vornet.cz/jats/shellfu-bash-jat
27
+  [sbx]: https://gitea.vornet.cz/jats/shellfu-bash-xcase
28
+  [jt]: https://gitea.vornet.cz/jats/jattool
29
+  [jd]: https://gitea.vornet.cz/jats/jats-demo
30
 
30
 
31
 
31
 
32
 Installation
32
 Installation
62
 you will need to add repositories manually.  There's a [script][jel6]
62
 you will need to add repositories manually.  There's a [script][jel6]
63
 in GitHb Gist to help you with this step on CentOS-6 & RHEL-6.
63
 in GitHb Gist to help you with this step on CentOS-6 & RHEL-6.
64
 
64
 
65
-  [jel6]: https://gist.github.com/AloisMahdal/89e422b4af54f5f65b87f70f7e339594
65
+  [jel6]: https://netvor.info/scripts/jats-repos-el6
66
 
66
 
67
 Also note that in order to minimize dependencies on testing machine,
67
 Also note that in order to minimize dependencies on testing machine,
68
 install just *jattool-minimal* package, which contains only the bare
68
 install just *jattool-minimal* package, which contains only the bare
157
 
157
 
158
  1. Before you start, **contact maintainer** and inform them that you
158
  1. Before you start, **contact maintainer** and inform them that you
159
     are planning to write a test.  You can do this by filing an issue
159
     are planning to write a test.  You can do this by filing an issue
160
-    in Github repo or by contacting the maintainer directly.
160
+    in Gitea repo or by contacting the maintainer directly.
161
 
161
 
162
  2. Read [Shellfu coding style][sfcs]; tests need to follow this.
162
  2. Read [Shellfu coding style][sfcs]; tests need to follow this.
163
 
163
 
166
     written down.  A more consistent documentation is expected to arrive
166
     written down.  A more consistent documentation is expected to arrive
167
     before `v0.1.0`.
167
     before `v0.1.0`.
168
 
168
 
169
-  [sfcs]: https://github.com/AloisMahdal/shellfu/blob/last/notes/style.md
169
+  [sfcs]: https://gitea.vornet.cz/shellfu/shellfu/src/last/notes/style.md

+ 1
- 1
mkit.ini View File

4
     pkgname    = jats-demo
4
     pkgname    = jats-demo
5
     version    = 0.0.1
5
     version    = 0.0.1
6
     maintainer = Joe Maintainer <joe@example.org>
6
     maintainer = Joe Maintainer <joe@example.org>
7
-    vcs-browser = https://github.com/AloisMahdal/jats-demo
7
+    vcs-browser = https://gitea.vornet.cz/jats/jats-demo
8
 
8
 
9
 [macros]
9
 [macros]
10
     __JATS_SUITENAME__ = demo
10
     __JATS_SUITENAME__ = demo