Why bundling lua?

[Ralf Corsepius]

On Tue, 2006-04-25 at 18:18 +0200, Matthias Saou wrote:
> Panu Matilainen wrote :
> 
> > On Tue, 2006-04-25 at 17:40 +0200, Ralf Corsepius wrote:
> > > Hi,
> > > 
> > > Question: Why does apt-rpm have a copy of lua bundled with it and can't
> > > use an external lua instead?
> > > 
> > > I see apt-pkg/luaiface.h is accessing some private lua header files, but
> > > I know too little about lua to be able to understand it.
> > 
> > Because it's not just an arbitrarily selected script interpreter to run
> > external commands at certain points, it's *embedded* in libapt so that
> > it can affect update/downgrade etc decisions, alter configuration at
> > runtime and such. It simply wouldn't be possible to do those things from
> > an external process.
> 
> I think Ralf was just asking why apt couldn't link against a separate
> static lua library.
Exactly.

>  AFAIK, lua is only provided as a static library when
> build from the original sources, never as a DSO.
Right.

> Maybe lua could be removed from the apt tarball, but still embedded at
> build time by using the static library provided by the lua-devel package.
That's what I am referring to.

I want to slimdown to tarball and get rid of code, such it doesn't have
to be maintained as part of apt-rpm.

Ralf