#2 DistUtils-ification

closed-fixed
None
5
2002-04-23
2002-02-15
Jon Nelson
No

I DistUtils-ified pylibpcap-0.2
Now, instead of wiggling the Makefile to suit the
installed software, just:

./setup.py build
(or for RPMs)
./setup.py bdist_rpm
(or to distribute in a tarball)
./setup.py bdist
and so on.

DistUtils is a wonderful thing.
Try ./setup.py --help to find out what commands are
available, and ./setup.py <command> --help to find out
how to alter that particular command to suit your
needs.

To make this work, I had to rename pcap.c to
pcap_interface.c.

While DistUtils does not use the Makefile anymore, I
also altered it.

Included is a tarball. Its contents are:

pylibpcap-2.1/
pylibpcap-2.1/COPYING
pylibpcap-2.1/MANIFEST.in
pylibpcap-2.1/README
pylibpcap-2.1/error.c
pylibpcap-2.1/exception.c
pylibpcap-2.1/pcap.i
pylibpcap-2.1/pcap.py
pylibpcap-2.1/pcap_interface.c
pylibpcap-2.1/pypcap.h
pylibpcap-2.1/setup.cfg
pylibpcap-2.1/setup.py
pylibpcap-2.1/PKG-INFO

I did not alter error.c, exception.c, pcap.i, pcap.py,
pcap_interface.c, COPYING, README

(pcap.c -> pcap_interface.c)
I altered pypcap.h to change an include line from
<pcap/pcap.h> to <pcap.h> due to setup.py and/or -I
lines automatically pre-pending the pcap/ portion if
necessary. Look in setup.py for the line
"include_dirs".

The setup.cfg, setup.py, and MANIFEST.in are distutils
files. PKG-INFO contains some meta-data that is
automatically generated by the distutils software.

Discussion

  • Jon Nelson
    Jon Nelson
    2002-02-15

    A tarball that contains everthing.

     
    Attachments
  • David Margrave
    David Margrave
    2002-04-17

    • assigned_to: nobody --> davidma
     
  • David Margrave
    David Margrave
    2002-04-23

    • status: open --> open-fixed
     
  • David Margrave
    David Margrave
    2002-04-23

    • status: open-fixed --> closed-fixed