You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by Mo DeJong <md...@cygnus.com> on 2000/12/14 02:18:15 UTC

Could buildconf be renamed to autogen.sh?

I agree with RTFM! as much the next guy, but it seems
like users might be better off if we renamed
the buildconf file to autogen.sh. Lots of
other projects use a script named autogen.sh.
I am not sure it is a "standard", but why
be different for no reason?

If this is done, the following patch
would also need to be added.

Index: README.dev
===================================================================
RCS file: /home/cvspublic/apr/README.dev,v
retrieving revision 1.1
diff -u -r1.1 README.dev
--- README.dev  2000/12/02 14:45:28     1.1
+++ README.dev  2000/12/14 01:16:13
@@ -5,9 +5,10 @@
 developer.  If you are building it as a standalone package, however,
 this means using a slightly non-standard build process.  
 
-1) ./buildconf
+1) ./autogen.sh
 2) ./configure
 3) make
 
 Currently, there is no make install step, as APR is not yet
-installable.  
\ No newline at end of file
+installable.  
+


cheers
Mo DeJong
Red Hat Inc


Re: Could buildconf be renamed to autogen.sh?

Posted by Sascha Schumann <sa...@schumann.cx>.
> > > I agree with RTFM! as much the next guy, but it seems
> > > like users might be better off if we renamed
> > > the buildconf file to autogen.sh. Lots of
> > > other projects use a script named autogen.sh.
> > > I am not sure it is a "standard", but why
> > > be different for no reason?
[..]
> I guess I don't follow your logic there. So, since someone
> else does it incorrectly, the whole concept must be flawed
> from the get go?

    You accused us of "[being] different for no reason".

    All I'm saying is that there is no standard, thus we simply
    cannot be different, because there is no objective standard
    to measure us with.

> Why exactly is it "better" for apr to use a custom name for the
> bootstrap scrip?

    Why exactly is it "better" for apr to use another custom name
    for the bootstrap strip?

> I suggest you go download the source code to gcc and take
> a look at the toplevel configure.in file. Does it change
> your mind about using a configure.in in apr?

    What relevance does that have here? While you bring up GCC,
    it is really beyond me why they still have autoconf-generated
    in CVS.

> Lets face it, people do not read the README.

    That is their problem. I also don't complain to the GCC
    or newlib maintainers that I cannot build their stuff from
    CVS without reading the documentation.

    Let's face it, developers who benefit Apache or APR are able
    to read READMEs. The rest can download a tarball.

    - Sascha


Re: Could buildconf be renamed to autogen.sh?

Posted by Mo DeJong <md...@cygnus.com>.
> > I agree with RTFM! as much the next guy, but it seems
> > like users might be better off if we renamed
> > the buildconf file to autogen.sh. Lots of
> > other projects use a script named autogen.sh.
> > I am not sure it is a "standard", but why
> > be different for no reason?
>
>     And as you point out in a later email, the behaviour of the
>     various autogen.sh is different in each project.
>
>     It is not a standard, hence your proposal is flawed.
>
>     - Sascha

I guess I don't follow your logic there. So, since someone
else does it incorrectly, the whole concept must be flawed
from the get go? Why exactly is it "better" for apr
to use a custom name for the bootstrap scrip?

I suggest you go download the source code to gcc and take
a look at the toplevel configure.in file. Does it change
your mind about using a configure.in in apr?

>     May I answer this with a quote of the famous Greg Stein:
>
>         "There is a README.dev in the top level of APR. That is
>          enough.
>
>         "Not our fault if people don't read the README.
>
>     - Sascha

Lets face it, people do not read the README.

Mo DeJong
Red Hat Inc

Re: Could buildconf be renamed to autogen.sh?

Posted by Sascha Schumann <sa...@schumann.cx>.
> Besides, as I said: the .sh extension is more for the user to know "oh, this
> is a shell script that I can run." Those other scripts you mention are all
> "internal" so who cares how they're named? Heck, let's call them script1,
> script2, and script3. :-)

    May I answer this with a quote of the famous Greg Stein:

        "There is a README.dev in the top level of APR. That is
         enough.

        "Not our fault if people don't read the README.

    - Sascha


Re: Could buildconf be renamed to autogen.sh?

Posted by Greg Stein <gs...@lyra.org>.
On Thu, Dec 14, 2000 at 02:34:44PM +0100, Sascha Schumann wrote:
> On Wed, 13 Dec 2000, Greg Stein wrote:
> > *) Subversion uses autogen.sh
> > *) APR and Apache uses buildconf
> > *) APRUTIL uses buildconf.sh (I stayed with the buildconf name, but felt
> >    that adding the .sh was much more declarative about what is going on)
> >
> > I'm +1 on changing APR and Apache to buildconf.sh.
> 
>     And PrintPath, TestCompile, GuessOS, GuessCodeset, CutRule,
>     MakeEtags, fp2rp, mfhead as well?
> 
>     What it is the point of starting a mass orgy of renaming
>     files?

Who said that I was going to start renaming those? :-) Or anything for that
matter?

Besides, as I said: the .sh extension is more for the user to know "oh, this
is a shell script that I can run." Those other scripts you mention are all
"internal" so who cares how they're named? Heck, let's call them script1,
script2, and script3. :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Re: Could buildconf be renamed to autogen.sh?

Posted by Sascha Schumann <sa...@schumann.cx>.
On Wed, 13 Dec 2000, Greg Stein wrote:

> *) Subversion uses autogen.sh
> *) APR and Apache uses buildconf
> *) APRUTIL uses buildconf.sh (I stayed with the buildconf name, but felt
>    that adding the .sh was much more declarative about what is going on)
>
> I'm +1 on changing APR and Apache to buildconf.sh.

    And PrintPath, TestCompile, GuessOS, GuessCodeset, CutRule,
    MakeEtags, fp2rp, mfhead as well?

    What it is the point of starting a mass orgy of renaming
    files?

    - Sascha


Re: Could buildconf be renamed to autogen.sh?

Posted by Mo DeJong <md...@cygnus.com>.
On Wed, 13 Dec 2000, Greg Stein wrote:

> *) Subversion uses autogen.sh
> *) APR and Apache uses buildconf
> *) APRUTIL uses buildconf.sh (I stayed with the buildconf name, but felt
>    that adding the .sh was much more declarative about what is going on)
> 
> I'm +1 on changing APR and Apache to buildconf.sh.
> 
> I'd like to hear about more projects that use the "autogen.sh" style to get
> a feel for how common/standard that name is.

Well, here are a few quick links for programs like gnome, gnucash,
galde, evolution, and some other projects.

http://www.cse.ogi.edu/~omega/gnome/gnometut/gnometut/autogen.sh.html
http://www.mail-archive.com/gnucash-devel%40gnucash.org/msg06320.html
http://rpmfind.net/tools/glade/messages/1172.html
http://lists.helixcode.com/archives/public/evolution-hackers/2000-August/000351.html

Note that there is one fatal error that a lot of folks make
when creating an autogen.sh file. One should never actually
run ./configure at the end of an autogen.sh file. This is
a big pain if you want to build in a directory other than the
srcdir.

APR does not currently work when building outside the src
dir, that is something else I would like to fix.

Mo DeJong
Red Hat Inc

Re: Could buildconf be renamed to autogen.sh?

Posted by Greg Stein <gs...@lyra.org>.
*) Subversion uses autogen.sh
*) APR and Apache uses buildconf
*) APRUTIL uses buildconf.sh (I stayed with the buildconf name, but felt
   that adding the .sh was much more declarative about what is going on)

I'm +1 on changing APR and Apache to buildconf.sh.

I'd like to hear about more projects that use the "autogen.sh" style to get
a feel for how common/standard that name is.

Cheers,
-g

On Wed, Dec 13, 2000 at 05:18:15PM -0800, Mo DeJong wrote:
> I agree with RTFM! as much the next guy, but it seems
> like users might be better off if we renamed
> the buildconf file to autogen.sh. Lots of
> other projects use a script named autogen.sh.
> I am not sure it is a "standard", but why
> be different for no reason?
> 
> If this is done, the following patch
> would also need to be added.
> 
> Index: README.dev
> ===================================================================
> RCS file: /home/cvspublic/apr/README.dev,v
> retrieving revision 1.1
> diff -u -r1.1 README.dev
> --- README.dev  2000/12/02 14:45:28     1.1
> +++ README.dev  2000/12/14 01:16:13
> @@ -5,9 +5,10 @@
>  developer.  If you are building it as a standalone package, however,
>  this means using a slightly non-standard build process.  
>  
> -1) ./buildconf
> +1) ./autogen.sh
>  2) ./configure
>  3) make
>  
>  Currently, there is no make install step, as APR is not yet
> -installable.  
> \ No newline at end of file
> +installable.  
> +
> 
> 
> cheers
> Mo DeJong
> Red Hat Inc

-- 
Greg Stein, http://www.lyra.org/

Re: Could buildconf be renamed to autogen.sh?

Posted by Sascha Schumann <sa...@schumann.cx>.
On Wed, 13 Dec 2000, Mo DeJong wrote:

> I agree with RTFM! as much the next guy, but it seems
> like users might be better off if we renamed
> the buildconf file to autogen.sh. Lots of
> other projects use a script named autogen.sh.
> I am not sure it is a "standard", but why
> be different for no reason?

    And as you point out in a later email, the behaviour of the
    various autogen.sh is different in each project.

    It is not a standard, hence your proposal is flawed.

    - Sascha