CPAN functionality for python

Sean Reifschneider jafo at
Tue Feb 27 09:38:32 CET 2001

On Tue, Feb 27, 2001 at 01:22:34AM -0700, Bruce Sass wrote:
>Hmmm, so RPM based systems don't have a way to automatically generate
>a .spec file from a source tree... that would be a must.

RPMs include pieces of information such as:

   Description of package
   Summary of the package
   Source URL
   Type of package (network daemons, console tools, etc)
   What is needed to install it.
   What is needed to build it.
   Scripts used for adding and removing a package
      (probably less necessary for most modules packages, but is used
      for software for doing things like adding user IDs, inittab entries,
      and the like)
   What files are "documentation".
   Where to install files and what their permissions are.
   Which installed files are config files.

Some of it is obviously superfluous, but much of it is not, and little of
it can be automaticly pulled from an arbitrary tar file.

Now, at the minimum, an RPM file consists of the files that make it up
and the permissions, so you can fake a minimal RPM file if you need to.

 Brooks's Law of Prototypes: Plan to throw one away, you will anyhow.
Sean Reifschneider, Inimitably Superfluous <jafo at> - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python

More information about the Python-list mailing list