Closed p5pRT closed 10 years ago
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
On Tue\, 03 Nov 2009 13:08:09 -0800\, Jesse (via RT) \perlbug\-followup@​perl\.org wrote:
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
In defense ...
http://perl5.git.perl.org/metaconfig.git/ http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README is already up-to-date and mentions
$ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using & porting perl 5.6.2\, 5.8.x\, 5.10.x\, 5.11.x on HP-UX 10.20\, 11.00\, 11.11\, 11.23\, and 11.31\, OpenSuSE 10.3\, 11.0\, and 11.1\, AIX 5.2 and 5.3. http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
The RT System itself - Status changed from 'new' to 'open'
On Tue 3.Nov'09 at 23:41:59 -0800\, H. Merijn Brand via RT wrote:
On Tue\, 03 Nov 2009 13:08:09 -0800\, Jesse (via RT) \perlbug\-followup@​perl\.org wrote:
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
In defense ...
http://perl5.git.perl.org/metaconfig.git/ http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README is already up-to-date and mentions
$ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
Apologies! My statement was about:
# Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.sourceforge.net/svnroot/dist/trunk/dist # # # Though this script was generated by metaconfig\, it is OK to send # patches against it. It's up to the Configure pumpkin to backport # the patch to the metaunits if it is accepted. # See Porting/pumpkin.pod for more information on metaconfig.
in blead's "Configure"
On Wed\, 4 Nov 2009 16:29:08 -0500\, Jesse Vincent \jesse@​fsck\.com wrote:
On Tue 3.Nov'09 at 23:41:59 -0800\, H. Merijn Brand via RT wrote:
On Tue\, 03 Nov 2009 13:08:09 -0800\, Jesse (via RT) \perlbug\-followup@​perl\.org wrote:
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
In defense ...
http://perl5.git.perl.org/metaconfig.git/ http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README is already up-to-date and mentions
$ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
Apologies! My statement was about:
# Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.sourceforge.net/svnroot/dist/trunk/dist # # # Though this script was generated by metaconfig\, it is OK to send # patches against it. It's up to the Configure pumpkin to backport # the patch to the metaunits if it is accepted. # See Porting/pumpkin.pod for more information on metaconfig.
in blead's "Configure"
Ah\, correct. I will address that shortly!
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using & porting perl 5.6.2\, 5.8.x\, 5.10.x\, 5.11.x on HP-UX 10.20\, 11.00\, 11.11\, 11.23\, and 11.31\, OpenSuSE 10.3\, 11.0\, and 11.1\, AIX 5.2 and 5.3. http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
On Wed Nov 04 23:51:57 2009\, hmbrand wrote:
On Wed\, 4 Nov 2009 16:29:08 -0500\, Jesse Vincent \jesse@​fsck\.com wrote:
On Tue 3.Nov'09 at 23:41:59 -0800\, H. Merijn Brand via RT wrote:
On Tue\, 03 Nov 2009 13:08:09 -0800\, Jesse (via RT) \perlbug\-followup@​perl\.org wrote:
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
In defense ...
http://perl5.git.perl.org/metaconfig.git/ http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README is already up-to-date and mentions
$ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
Apologies! My statement was about:
# Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.sourceforge.net/svnroot/dist/trunk/dist # # # Though this script was generated by metaconfig\, it is OK to send # patches against it. It's up to the Configure pumpkin to backport # the patch to the metaunits if it is accepted. # See Porting/pumpkin.pod for more information on metaconfig.
in blead's "Configure"
Ah\, correct. I will address that shortly!
Has this question about how/where we say changes to Configure need to be committed been addressed?
Thank you very much. Jim Keenan
On Sat\, 03 Aug 2013 10:07:04 -0700\, "James E Keenan via RT" \perlbug\-followup@​perl\.org wrote:
On Wed Nov 04 23:51:57 2009\, hmbrand wrote:
On Wed\, 4 Nov 2009 16:29:08 -0500\, Jesse Vincent \jesse@​fsck\.com wrote:
On Tue 3.Nov'09 at 23:41:59 -0800\, H. Merijn Brand via RT wrote:
On Tue\, 03 Nov 2009 13:08:09 -0800\, Jesse (via RT) \perlbug\-followup@​perl\.org wrote:
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
In defense ...
http://perl5.git.perl.org/metaconfig.git/ http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README is already up-to-date and mentions
$ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
Apologies! My statement was about:
# Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.sourceforge.net/svnroot/dist/trunk/dist # # # Though this script was generated by metaconfig\, it is OK to send # patches against it. It's up to the Configure pumpkin to backport # the patch to the metaunits if it is accepted. # See Porting/pumpkin.pod for more information on metaconfig.
in blead's "Configure"
Ah\, correct. I will address that shortly!
Has this question about how/where we say changes to Configure need to be committed been addressed?
I changed that to --8\<--- # Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.code.sf.net/p/dist/code/trunk/dist # # Though this script was generated by metaconfig from metaunits\, it is # OK to send patches against Configure itself. It's up to the Configure # pumpkin to backport the patch to the metaunits if it is accepted. # For more information on patching Configure\, see pod/perlhack.pod # # The metaunits are also available from the public git repository: # http://perl5.git.perl.org/metaconfig.git/ or # $ git clone git://perl5.git.perl.org/metaconfig.git metaconfig # # See Porting/pumpkin.pod for more information on metaconfig. -->8---
back in
commit 7f5516d11013641bb723aba27b6cb26c845b096c Author: H.Merijn Brand \merijn@​nb09\.procura\.nl Date: Thu Nov 5 15:32:11 2009 +0100
Mention git repo in Configure's header
I think that the *middle* section is enough\, right?
Thank you very much. Jim Keenan
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.19 porting perl5 on HP-UX\, AIX\, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
On Sat Sep 07 09:18:41 2013\, hmbrand wrote:
On Sat\, 03 Aug 2013 10:07:04 -0700\, "James E Keenan via RT" \perlbug\-followup@​perl\.org wrote:
On Wed Nov 04 23:51:57 2009\, hmbrand wrote:
On Wed\, 4 Nov 2009 16:29:08 -0500\, Jesse Vincent \jesse@​fsck\.com wrote:
On Tue 3.Nov'09 at 23:41:59 -0800\, H. Merijn Brand via RT wrote:
On Tue\, 03 Nov 2009 13:08:09 -0800\, Jesse (via RT) \perlbug\-followup@​perl\.org wrote:
We should clarify that any change _committed_ to Configure needs to be extracted into metaconfig. also that metaconfig lives in git\, not sourceforge.
In defense ...
http://perl5.git.perl.org/metaconfig.git/ http://perl5.git.perl.org/metaconfig.git/blob/HEAD:/README is already up-to-date and mentions
$ git clone git://perl5.git.perl.org/metaconfig.git metaconfig
Apologies! My statement was about:
# Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.sourceforge.net/svnroot/dist/trunk/dist # # # Though this script was generated by metaconfig\, it is OK to send # patches against it. It's up to the Configure pumpkin to backport # the patch to the metaunits if it is accepted. # See Porting/pumpkin.pod for more information on metaconfig.
in blead's "Configure"
Ah\, correct. I will address that shortly!
Has this question about how/where we say changes to Configure need to be committed been addressed?
I changed that to --8\<--- # Note: this Configure script was generated automatically. Rather than # working with this copy of Configure\, you may wish to get metaconfig. # The dist package (which contains metaconfig) is available via SVN: # svn co https://svn.code.sf.net/p/dist/code/trunk/dist # # Though this script was generated by metaconfig from metaunits\, it is # OK to send patches against Configure itself. It's up to the Configure # pumpkin to backport the patch to the metaunits if it is accepted. # For more information on patching Configure\, see pod/perlhack.pod # # The metaunits are also available from the public git repository: # http://perl5.git.perl.org/metaconfig.git/ or # $ git clone git://perl5.git.perl.org/metaconfig.git metaconfig # # See Porting/pumpkin.pod for more information on metaconfig. -->8---
back in
commit 7f5516d11013641bb723aba27b6cb26c845b096c Author: H.Merijn Brand \merijn@​nb09\.procura\.nl Date: Thu Nov 5 15:32:11 2009 +0100
Mention git repo in Configure's header
I think that the *middle* section is enough\, right?
Yes. Thanks for the response. Marking ticket resolved.
Thank you very much. Jim Keenan
@jkeenan - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#70203 (status was 'resolved')
Searchable as RT70203$