On 11/25/05, Donovan Baarda <abo@minkirri.apana.org.au> wrote:
> Sorry... that's what I meant; don't deb an egg... install it as an egg,
> outside of the Debian package management system. As an egg, it is under
> development and not ready for release as a deb. When the software is
> ready for release, strip the egg package management layer and create a
> proper deb out of it.
Again, this is something I picked up from previous discussions of this
nature, but you can't "strip the egg package management layer" without
also stripping out the other features of eggs, such as plugin support,
metadata introspection, etc, which are useful whether or not you care
about package management.
So, as a package developer, if I want to use egg metadata or plugin
support, I have to buy into the whole egg experience, including the
installation stuff.
I'd argue that the different features should be separated, so that
people can choose the ones they want to use (and as a consequence, the
"egg package management layer" could be stripped out independently).
But that doesn't seem to be the direction the development is going.
Apologies if this is incorrect. I'm still researching...