pushed to staging as
~~~
commit 0471360de028b3981596bb4688952a49bfb300b1
Author:     Jonas Hahnfeld <hah...@hahnjo.de>
AuthorDate: Tue Dec 24 15:15:10 2019 +0100
Commit:     Jonas Hahnfeld <hah...@hahnjo.de>
CommitDate: Tue Jan 21 18:23:03 2020 +0100

    Issue 5654/4: Remove passing of package variables

commit 90e0a31201464bf6bbe0dc5ae93d555f16e6cd75
Author:     Jonas Hahnfeld <hah...@hahnjo.de>
AuthorDate: Wed Jan 8 21:34:50 2020 +0100
Commit:     Jonas Hahnfeld <hah...@hahnjo.de>
CommitDate: Tue Jan 21 18:22:26 2020 +0100

    Issue 5654/3: Call AC_INIT correctly with all parameters
    
    Version information via m4_esyscmd_s() by David K.
    The additional SRCDIR variable is needed for read-only source
    directories. It is used during autoconf and MUST NOT be read
    in the generated configure script itself.

commit 2db727328de836028421ef9d418ed854942f6622
Author:     Jonas Hahnfeld <hah...@hahnjo.de>
AuthorDate: Tue Dec 24 14:37:07 2019 +0100
Commit:     Jonas Hahnfeld <hah...@hahnjo.de>
CommitDate: Tue Jan 21 18:21:45 2020 +0100

    Issue 5654/2: Drop unused MICRO_VERSION

commit 194a0001cd0d16a9681c5b53fdab0d4e416a20ce
Author:     Jonas Hahnfeld <hah...@hahnjo.de>
AuthorDate: Mon Dec 23 14:50:58 2019 +0100
Commit:     Jonas Hahnfeld <hah...@hahnjo.de>
CommitDate: Tue Jan 21 18:21:45 2020 +0100

    Issue 5654/1: Cleanup directory handling in STEPMAKE_INIT
    
     * Get rid of code which configures the Stepmake package, that hasn't
       been supported for a long time.
     * Replace $ugh_ugh_autoconf250_builddir by $ac_pwd and @abs_builddi@.
       I think the latter is actually more correct, but $ac_abs_builddir
       not available when executing configure.
     * Replace hacks around $srcdir and @srcdir@ by predefined variables.
~~~


---

** [issues:#5654] Cleanup initialization of configure process**

**Status:** Started
**Created:** Wed Jan 08, 2020 03:06 PM UTC by Jonas Hahnfeld
**Last Updated:** Tue Jan 21, 2020 04:33 PM UTC
**Owner:** Jonas Hahnfeld


Cleanup initialization of configure process

Individual changes:
1. Cleanup directory handling in STEPMAKE_INIT

Get rid of code which configures the Stepmake package, that hasn't been 
supported for a long time.
Replace $ugh_ugh_autoconf250_builddir by $ac_pwd and @abs_builddi@. I think the 
latter is actually more correct, but $ac_abs_builddir not available when 
executing configure.
Replace hacks around $srcdir and @srcdir@ by predefined variables.

2. Drop unused MICRO_VERSION

3. Call AC_INIT correctly with all parameters

Version information via m4_esyscmd() by David K.

4. Remove passing of package variables

http://codereview.appspot.com/549350043


---

Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to