Matthias Saou wrote:

> I know, I know! Then one thing I could definitely do is help out
> documenting inside the rpm source tree *why* all of those "external"
> sources are included instead of being required. For instance, the
> reasons you give for zlib to be there seem more than okay, and most (if
> not all) people reading them from some file would understand them.
>
> Could it just be a matter of documenting it better? Writing it once to
> the source tree instead of once a year to a different mailing-list? :-)

I'm also interested in a little step-for-step or why-for-what,
as I am trying to put together a little "RPM From Scratch" doc
on how to go ahead building RPM from only humble surroundings -
say the Apple Developer Tools without the MacPorts handholding...

Eventually I want to end up with one single RPM framework,
that is easy to carry along bundled with a Mac application.
(for similar reasons as to why a static /bin/rpm is useful)
And while I'm at it, I'm building it as a Universal Binary.

But the docs would be a useful thing to have around, regardless.
--anders