blob: f6f91f9c0dc05204c8a14b0bd471ed548c454ab6 (
plain)
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
|
How to get a script added.
==========================
File a bug report assigned to the qa team. The qa team will add the script to
the repo or give you access to the repo.
By default all Gentoo developers should have full write access so just ask if
you can add your script in.
How to get output on the webpage added.
=======================================
Once your script is in the repo, infra needs to run the script and someone needs
to add the appropriate link to the webpage.
Important details:
- How often to run your script, normally daily is good enough.
- Any arguments needed for the script? (OR how to run it)
- Output is normally text but can be html too, must be static.
- Must not link outside of gentoo.org for integrity purposes. It is ideal to
maintain a closed system, output generated on the web host, etc.
Current runtimes:
================
(As of 201-11-28)
- emerge --sync: hourly. Assume PORTDIR=/usr/portage (may change in future)
- check_eclasses_eapis.sh: 4x daily
- eapi_usage.sh: 2x daily
- filesdir-usage.sh: daily
- find-binary-files.pl: daily
- genrdeps, run-genrdeps-index.sh: hourly
- mask_check.py: daily
- packages-inheriting-eclasses.py: daily
- gen-dev-wot.sh: weekly
|