#11578 closed (wontfix)
Include init.d script in source for downstream packaging
| Reported by: | Sebastian Rahlf | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | dev |
| Severity: | Keywords: | init.d | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
There is a working init.d script in the wiki
http://code.djangoproject.com/wiki/InitdScriptForDebian
I may be a good idea to include this in the source to enable downstream package maintainers to include it, as well.
The debian maintainer is all up for it
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538863
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | django-init-d.patch added |
|---|
comment:1 by , 15 years ago
| Summary: | Include init.d script in source for ownstream packaging → Include init.d script in source for downstream packaging |
|---|
comment:2 by , 15 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:3 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I'm not convinced that the Django repository is the right place for this. init.d scripts are highly OS dependent, and can even be OS version dependent. If package maintainers want to include scripts like this, I encourage them to do so, but I don't see what having this code in the Django repository does to improve that process.
On top of the platform issue, there is also the issue that Django has historically treated deployment as a documentation issue. We have avoided providing Apache config files, wsgi scripts, or any other deployment artefact because local configuration of a webserver is something that always needs to be tuned to local needs.
Stupid typo!