Suggested packaging guideline: avoid running autoreconf

Braden McDaniel braden at endoframe.com
Mon Oct 13 04:41:43 UTC 2008


On Sun, 2008-10-12 at 17:59 +0000, Kevin Kofler wrote:

[snip]

> What you're missing is that Fedora _already_ has guidelines requiring to build 
> everything from source (which are enforced for Java and Mono stuff, for 
> example),

What you mean is that there are guidelines applicable to Java and Mono,
right?  If you're really saying that there's a guideline that applies
more generally, link please.

>  it's just that the autotools files are still considered "source",

That's right.  They *are* considered that.  So, again, if you want to
change that, you should propose an appropriate guideline.
 
> which they really aren't.

Maybe.  But they aren't delivered with the binary RPM; so how this
matters (or is the least bit similar to the Java/Mono situation) is not
clear.

Do you also want to use doxygen to regenerate API documentation included
in a tarball, despite the fact that a different doxygen version's subtle
stylesheet and markup changes could totally mangle the docs? How are you
going to catch *that* breakage?

-- 
Braden McDaniel                           e-mail: <braden at endoframe.com>
<http://endoframe.com>                    Jabber: <braden at jabber.org>





More information about the fedora-devel-list mailing list