546614 – Clarify the proper way to fix configure.in -> configure.ac migration

Bug 546614 - Clarify the proper way to fix configure.in -> configure.ac migration

Summary: Clarify the proper way to fix configure.in -> configure.ac migration

Status:	RESOLVED DUPLICATE of bug 426262

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Quality Assurance Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-04-14 18:19 UTC by Pacho Ramos
Modified:	2022-01-24 23:36 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Pacho Ramos gentoo-dev

2015-04-14 18:19:36 UTC

Hi!

I get many reports because of the QA check added for bug 426262... but looks like nobody is really fixing them. Then, I wonder what is the way to go. Are we allowed to simply make "mv configure.in configure.ac" (in the case it doesn't break of course)? Is there any other way that could prevent us from needing to add this magic to tons of ebuilds?

Thanks a lot for your help :)

Comment 1 SpanKY gentoo-dev

2015-07-13 03:59:32 UTC

you should report the issue upstream and once there's a bug there, put the `mv` into the ebuild with a comment linking to the upstream report

 # See http://xxxx
 mv configure.{in,ac} || die

Comment 2 Michael 'veremitz' Everitt 2016-09-08 15:41:40 UTC

Any updates on this? Noticed there's still a few occurrences on packages I'm using.

Comment 3 Sam James archtester

2022-01-24 23:36:27 UTC

Renaming added in other bug.

*** This bug has been marked as a duplicate of bug 426262 ***