qico FTN mailer / Bugs / #11 Incorrect bug reporting reference in generated file 'configure'

Robert James Clay - 2013-05-27

Reference seems to be in the generated configure script rather than in the configure.in script.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1,5 +1,5 @@
 The following is part of what is currently displayed when running configure:

-> Report bugs to <r45c at mail dot ru>.
+> Report bugs to <r45c at mail dot ru\>.

 All instances of that should be updated to reference the Qico SourceForge project.

summary: Bug reporting does not reference the SourceForge project --> Generated file 'configure' is in the source archive.
Description has changed:

Diff:

--- old
+++ new
@@ -1,5 +1,2 @@
-The following is part of what is currently displayed when running configure:
-
-> Report bugs to <r45c at mail dot ru\>.
-
-All instances of that should be updated to reference the Qico SourceForge project.
+Since the 'configure' file is generated from configure.in by autoconf during the initial configure step when using automake/autoconf, why is the file in the code
+repository? Just left over from the xe version or other imports?

Robert James Clay - 2013-05-27

The following is part of what is currently displayed when running configure:

Report bugs to <r45c at mail dot ru>.

All instances of that should be updated to reference the Qico SourceForge project.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Description has changed:

Diff:

--- old
+++ new
@@ -1,2 +1 @@
-Since the 'configure' file is generated from configure.in by autoconf during the initial configure step when using automake/autoconf, why is the file in the code
-repository? Just left over from the xe version or other imports?
+Since the 'configure' file is generated from configure.in by autoconf during the initial configure step when using automake/autoconf, why is the file in the code repository? Just left over from the xe version or other imports?

Robert James Clay - 2013-05-27

Remove the autoconf generated file 'configure' from the code repository. [ddadf2]

Related

Commit: [ddadf2]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2013-05-27

status: accepted --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2014-04-24

summary: Generated file 'configure' is in the source archive. --> Remove automake related files after cmake build available

Description has changed:

Diff:

--- old +++ new @@ -1 +1 @@ -Since the 'configure' file is generated from configure.in by autoconf during the initial configure step when using automake/autoconf, why is the file in the code repository? Just left over from the xe version or other imports? +Remove automake related files after a cmake build system is available.

status: closed-fixed --> accepted

Group: v0.58 --> None

Priority: 5 --> 7
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2014-04-24

Had started removing the automake related files by removing the configure script but a basic set of cmake files are not ready, so put it back in.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2014-11-22

summary: Remove automake related files after cmake build available --> Generated file 'configure' is in the source archive.

Description has changed:

Diff:

--- old +++ new @@ -1 +1 @@ -Remove automake related files after a cmake build system is available. +Since the 'configure' file is generated from configure.in by autoconf during the initial configure step when using automake/autoconf, why is the file in the code repository? Just left over from the xe version or other imports?

Group: None --> v0.59
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2014-11-22

Putting this bug back to original issue.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

summary: Generated file 'configure' is in the source archive. --> Incorrect bug reporting reference in generated file 'configure'
Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,5 @@
-Since the 'configure' file is generated from configure.in by autoconf during the initial configure step when using automake/autoconf, why is the file in the code repository? Just left over from the xe version or other imports?
+The following is part of what is currently displayed when running configure:
+
+> Report bugs to <r45c at mail dot ru\>.
+

+ All instances of that should be updated to reference the Qico SourceForge project, at https://sourceforge.net/p/qico/bugs.

Robert James Clay - 2014-11-27

This was corrected in the source file configure.in with [cbcef6].

The generated file configure, like some other such generated files, is still in version control; from back when it added to the orginal CVS repository. It has been getting updated over time but the question now is if such generated files should kept in version control at all.

Related

Commit: [cbcef6]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2014-11-27

This was corrected in the sourcefile configure.in with [cbcef6].

Related

Commit: [cbcef6]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robert James Clay - 2015-05-13

Group: v0.59 --> v0.60
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Incorrect bug reporting reference in generated file 'configure'

Group

Searches

Help

#11 Incorrect bug reporting reference in generated file 'configure'

Discussion

Related

Related

Related