[zpkg] Packaging a standalone zope3 package

[Lennart Regebro]

On 10/24/05, Fred Drake <fred at zope.com> wrote:
> In this case, yes, the wildcard only saves a few lines.  In other cases, it
> can save more.  The savings of lines is a fairly minor point, I think, and is
> mostly interesting when additional packages are being added to a tree on an
> obgoing basis (as for the Zope 3 tree), because it avoids needing to update
> the map every time a package is added.

Right.

>  > Actually, my main recommendation would be to get rid of all the
>  > different config files, and put everything into one, with a
>  > standardized name. That would make everything MUCH easier.
>
> I've thought about that, and there's some serious appeal to that.  Jim has
> objected to the idea because he wants the dependencies information separate
> from the other packaging information because it's also part of the package's
> contract: it should be a considered design decision to change a released
> package to require packages it did not require before the change.

I'm not sure I understand that reasoning, but by allowing file
inclusion you could still have separate dependencies files if you
want. Maybe I'm missing the point?

--
Lennart Regebro, Nuxeo     http://www.nuxeo.com/
CPS Content Management     http://www.cps-project.org/