Re: [Bug-pyconfigure] Broken Link on savannah

[Brandon Invergo]

Hi Arne,

Arne Babenhauserheide <address@hidden> writes:
>
> I now grabbed your README, and I would rephrase the “later” part. Something 
> like the following:

Thanks! I agree with your changes so I've applied them (with some slight
modifications). 

-brandon


> diff --git a/README b/README
> --- a/README
> +++ b/README
> @@ -12,12 +12,11 @@ installation procedure:
>  Of course, since Python programs usually do not need to be compiled,
>  the second step can be eliminated.
>  
> -Currently, pyconfigure is designed to live alongside the
> -traditional Python distutils (`setup.py') method, providing a wrapper
> -around it. Later, it will expand to allow developers to bypass
> -distutils altogether.
> +Currently, pyconfigure is designed to live alongside the traditional
> +Python distutils (`setup.py') method, providing a wrapper around
> +it. Future releases might work independent of distutils.
>  
> -To use pyconfigure, you may simply drop the files from the src/
> +To use pyconfigure, you can simply drop the files from the src/
>  directory into your Python project. Without modification, they provide
>  a basic wrapper around setup.py that allows one to install to the
>  chosen prefix. It allows one optionally to install the application to
> @@ -27,11 +26,11 @@ your project's name and then run:
>  
>      $ autoreconf -fvi
>  
> -Several Autoconf macros are provided in the m4 directory which may be
> +Several Autoconf macros are provided in the m4 directory which can be
>  used to perform a variety of tests during the configuration stage,
>  from verifying a minimum Python version to running test programs. See
>  the included documentation for more info and browse through the
> -provided `configure.ac' sample Autoconf script for well-commented
> +provided sample Autoconf script (`configure.ac') for well-commented
>  examples.
>  
>  pyconfigure is official GNU software and is released under the aegis
>
>
> Claiming that it “will” do something without having code ready for that is 
> quite dangerous, because your plans might change when you actually tackle the 
> problem.
> (I’m one of the writers of the Quarter of the Hurd, and saying “it will” 
> without providing a patch with which it already does that is banned there - 
> but the Hurd is a special case when it comes to claims looking like 
> vaporware, 
> so this might not be that much of an issue for pyconfigure)