Opened 14 years ago

Closed 14 years ago

#2436 closed enhancement (fixed)

packaging of doc-files into RPM

Reported by: dummy@… Owned by: Adrian Holovaty
Component: contrib.admin Version: master
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no



I regulary build a RPM from the trunk via command 'python bdist_rpm'.
I always missed the doc-files in the RPM and have no a simple solution for this.

Add a setup.cfg with a [bdist_rpm] section and tell the build-system where the doc-files are.


Attachments (1)

setup.cfg (47 bytes) - added by dummy@… 14 years ago.
setup.cfg with [bdist_rpm] section

Download all attachments as: .zip

Change History (6)

Changed 14 years ago by dummy@…

Attachment: setup.cfg added

setup.cfg with [bdist_rpm] section

comment:1 Changed 14 years ago by Adrian Holovaty

What does the release=1 do?

comment:2 Changed 14 years ago by dummy@…

RPM packages are named like <name>-<version>-<release>.<arch>.rpm

<name> and <version> are defined in
<release> is just a fix number - like a patch-level of the RPM
<arch> is noarch

You can replace 'release=1' by 'release=$Revision$' (see ) if you like this, or set it fix to 1.

comment:3 Changed 14 years ago by dummy@…

You can leave 'release=1' away. This is the default value.

comment:4 Changed 14 years ago by anonymous

Are there offical RPM's for Django?

comment:5 Changed 14 years ago by Adrian Holovaty

Resolution: fixed
Status: newclosed

Fixed in [3693].

Note: See TracTickets for help on using tickets.
Back to Top