On Dec 09, Andreas Tille <andr...@an3as.eu> wrote:

> I would consider asking upstream about this for sure but the code is in
> maintenance mode and there is no Git repository to step back in history.
> The only way to go would be to take configure.ac from a later version
> and find out how it can be tweaked to create some working configure
> file from it.  I do not consider my time well spent in doing so except
> if there is some consensus here on the list that configure files without
> configure.ac are "missing source".
If there is no surviving configure.ac which can generate the current 
configure file then it is quite obvious that this is not a DFSG issue, 
because no such source exists.

But if your package contains a manually edited configure file then this
is a bad practice, and experience shows that sooner or later you will 
have to deal with the resulting bugs.

Clearly, the severity of these bugs is different, at least as long as 
your package builds.

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature

Reply via email to