[Distutils] pypi and easy_install

[Giampaolo Rodola']

> after having run setup.py sdist the installation hangs
> on when arrives to run the tar.exe utility.

Sorry, obviously I meant "setup.py sdist --formats=gztar" (instead of
"setup.py sdist") that's what I did actually .



2008/1/16, Giampaolo Rodola' <billiejoex at gmail.com>:
> I'm sorry, just one more question (hopefully).
> I work from Windows and I'd like to generate a gzipped tar file (.tar.gz).
> On documentation I see that:
>
> "It requires external utilities: tar and possibly one of gzip, bzip2,
> or compress"
>
> I installed:
> http://gnuwin32.sourceforge.net/packages/gtar.htm
> ...and:
> http://gnuwin32.sourceforge.net/packages/gzip.htm
>
> Since apparently there's no way to provide cmd line arguments to tell
> distutils where to find gtar and gzip executables I created two .bat
> files in the setup.py directory pointing to original utility
> executables but after having run setup.py sdist the installation hangs
> on when arrives to run the tar.exe utility.
> Is there an easier way for doing what I want?
> I know that maybe this is more a Windows issue than a distutils issue
> but I find very uncomfortable the way distutils manage such things.
>
> PS - I've never used it but by reading the documentation it seems that
> the tarfile module would be able to read and write those kind of
> archives. If that is true it would be much easier using that instead
> of relying on third party packages like those ones I've tried.
>
> 2008/1/16, Giampaolo Rodola' <billiejoex at gmail.com>:
> > Thanks for the useful information I wasn't aware of.
> > I'll use MANIFEST file.
> >
> > 2008/1/16, Phillip J. Eby <pje at telecommunity.com>:
> > > At 02:00 AM 1/16/2008 +0100, Giampaolo Rodola' wrote:
> > > >2008/1/14, Phillip J. Eby <pje at telecommunity.com>:
> > > > > At 02:14 AM 1/14/2008 +0100, Giampaolo Rodola' wrote:
> > > > > > > (This is a distutils feature and doesn't require setuptools, although
> > > > > > > the distutils are a bit trickier to get the tarball to include
> > > > > > > everything, as you have to explicitly list in MANIFEST.in anything
> > > > > > > that distutils doesn't automatically pick up.
> > > > > >
> > > > > >Sorry for replying so late.
> > > > > >Gently, I would be interested in knowing how can I have distutils to
> > > > > >include everything.
> > > > > >Currently I've tried to use setup.py sdist but CREDITS, HISTORY,
> > > > > >INSTALL and LICENSE files aren't included in the tarball.
> > > > >
> > > > > http://python.org/doc/2.4.1/dist/manifest.html
> > > >
> > > >Is there a way to specify that in setup.py?
> > >
> > > Not that I'm aware of, no.  You just put the MANIFEST.in next to setup.py.
> > >
> > > The alternative is to use setuptools + source control: setuptools
> > > natively picks the files up from SVN or CVS, and there are plugins
> > > for several other source control systems including Bazaar, Git,
> > > Monotone, and Mercurial, if I recall correctly.  (Search PyPI for
> > > "setuptools" and the appropriate tool to find the plugin.)
> > >
> > > (Note that these revision control plugins do NOT require users of
> > > your package to have the revision control tool OR the plugin -- it
> > > only affects *building* the source distribution, not using it.  In
> > > fact, it's even possible to make it so your users don't have to have
> > > setuptools, although that's not the default setup.)
> > >
> > >
> >
>