Re: Runtime package dependencies and compilation order

[Boris]

Hey Michael,

Thanks for your reply.

> Is this an exclusive "or"?  If not, why not just depend on B _and_ C?

It's not exclusive, it's disjunction. I don't want to depend on both of
them because they are huge. And some people would not like having orphan
package to be installed as dependency.

> ...is really the compilation order a problem, or the fact that A had
> been compiled without B being _loaded_?  Doesn't make much a difference
> from the end user's view, though.

Good question. And I am not sure. I'll look into it. Just out of curiosity.

> In the other case I cannot suggest anything better than what you already
> did.

Alright, then I'll just implement my solution. In any case, I like it. Just
wanted to hear others opinion.

Thanks again and best regards,
Boris

On Tue, May 31, 2016 at 5:47 PM Michael Heerdegen <michael_heerdegen@web.de>
wrote:

> Boris <d12frosted@gmail.com> writes:
>
> > Recently I've faced following problem. I have a package A that might
> > depend on package B or (disjunction) package C.
>
> Is this an exclusive "or"?  If not, why not just depend on B _and_ C?
>
> In the other case I cannot suggest anything better than what you already
> did.  Since AFACT, Emacs package management doesn't (yet?) allow
> dependencies of type "X or Y" (unlike some OS).  But I wonder...
>
> > The problem comes when someone wants to use the part of package A that
> > depends on package B - if package A is byte compiled before B, then some
> > functionality doesn't work and you have to manually recompile A.
>
> ...is really the compilation order a problem, or the fact that A had
> been compiled without B being _loaded_?  Doesn't make much a difference
> from the end user's view, though.
>
>
> Regards,
>
> Michael.
>