Tarek Ziadé wrote:
On Sun, Feb 15, 2009 at 11:56 PM, Gerry Reno wrote:
I've been looking at the spec file that 'bdist_rpm' generates and I do not
see a %config or %config(noreplace) section. Is there a way to generate a
%config section and specify a list of files? This is important so that
On Sun, Feb 15, 2009 at 11:56 PM, Gerry Reno wrote:
> I've been looking at the spec file that 'bdist_rpm' generates and I do not
> see a %config or %config(noreplace) section. Is there a way to generate a
> %config section and specify a list of files? This is important so that
> config files do
I've been looking at the spec file that 'bdist_rpm' generates and I do
not see a %config or %config(noreplace) section. Is there a way to
generate a %config section and specify a list of files? This is
important so that config files do not get overwritten when using 'rpm -U'.
___
2009/2/14 Tarek Ziadé :
> I really like the way setuptools wraps scripts depending on the platform.
>
> http://peak.telecommunity.com/DevCenter/setuptools#automatic-script-creation
>
> I am not talking about the entry_point feature, but the way it creates
> executables.
>
> What would people think
On Sun, Feb 15, 2009 at 10:39:48AM +0100, Tarek Ziadé wrote:
> 1. should the uninstall command be part of the Python interpreter
> itself ?
Don't think I like this. Seems a very big jump from how this normally
works. What I mean is that it feels like it's builtin interperter
functionality, while
I am going to start a new PEP defining a new, more sane EGG-INFO
directory format,
and clarifying the need to make metadata that we can put in setup.py match with
the ones in PKG-INFO file.
On Sun, Feb 8, 2009 at 11:31 AM, Lennart Regebro wrote:
> On Sun, Feb 8, 2009 at 11:05, Tarek Ziadé wrote
On Sat, Feb 14, 2009 at 11:23 PM, Robert Kern wrote:
> I have a couple of issues with this feature as implemented in setuptools. I
> think they should be addressed if the feature makes its way into the stdlib:
>
> 1. The pkg_resources import can make startup time quite large. For small
> command-l
Hi,
I started to write a detailed description of the uninstall feature
based on the previous threads we had, and there are two points I'd
like to
discuss:
1. should the uninstall command be part of the Python interpreter itself ?
for instance, be callable like this :
$ python
