Ticket #538 (closed task: wontfix)
Document the autodebathenification process in the wiki
Reported by: | jdreed | Owned by: | jdreed |
---|---|---|---|
Priority: | normal | Milestone: | Fall 2010 |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | ||
Upstream bug: |
Description
The process should be documented, including any control or flag files, and why, for example, it's trying to fetch things from http://localhost:9999
Change History
comment:1 in reply to: ↑ description Changed 15 years ago by andersk
comment:2 Changed 14 years ago by jdreed
- Owner set to jdreed
- Status changed from new to accepted
- Milestone changed from Summer 2010 (Lucid Deploy) to Fall 2010
comment:3 Changed 14 years ago by jdreed
- Status changed from accepted to closed
- Resolution set to wontfix
So, I guess what I really meant here was "Document the debathenification process". Specifically what steps are needed to start debathenifying a new package. But the answer seems to be "set some variables, and create a function called hack_package() that does unspeakable things". So we can probably close this.
Note: See
TracTickets for help on using
tickets.
Replying to jdreed:
The comments at the top of the script (trunk/debathena/scripts/build-server/autodebathenify) document it fairly well.
Nothing special about the autodebathenificator. localhost:9999 is an approx cache that is used for all builds (see trunk/debathena/NOTES).