[bug #16236] po file update conflicts with autoconf conventions

[Shaddy Baddah]

URL:
  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=16236>

                 Summary: po file update conflicts with autoconf conventions
                 Project: make
            Submitted by: shaddybaddah
            Submitted on: Fri 03/31/06 at 11:09
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
       Component Version: CVS
        Platform Version: Any
           Fixed Release: None

    _______________________________________________________

Details:

As I know it, the convention for autoconf/automake builds is to follow these
steps at command line:

- make a build directory out of the $(srcdir)
- change directory to that build directory
- run the configure script by entering the correct path to it
- run make out of the build directory to build
- run make install out of the build directory to install

I understand that when using CVS, there are some additional bootstrapping
tasks before getting to this stage, and README.cvs indicates running
autoreconf -i in $(srcdir) to produce the configure script.

However, there is a further bootstrapping task after this, which is make
update, that updates the po files. This task, and the configure task in
between it are the subject of this report.

As per the "conventional" steps I specified about, I expect to do my
configure outside of $(srcdir). But there is no doubt for bootstrapping, a
configure "at least" needs to be done in $(srcdir) or else you cannot
bootstrap.

This isn't necessarily a bug... but IMO, it is a break with convention that
should be acknowledge somewhere, if not enhanced at some point.




    _______________________________________________________

Carbon-Copy List:

CC Address                          | Comment
------------------------------------+-----------------------------
shaddybaddah                        | 




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=16236>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/