Re: [elpa] main 8f4cb59: * elpa-packages (counsel, ivy, swiper): Auto-sync.

[Basil L. Contovounesios]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> The packages ivy-avy and ivy-hydra are considered optional integrations
>> with the separate packages avy and hydra, respectively, so they seem
>> like the best candidates for splitting into separate packages (or
>> merging with the avy and hydra packages, I think).
>
> `ivy-hydra` seems to be "extra `ivy` functionality, using a hydra",
> rather than "`ivy` support for hydras", so I don't think it belongs with
> `hydra.el`.
>
> OTOH, I think it should be included into `ivy`.  IIUC this is currently
> not done because it would require adding `hydra` as a dependency to
> `ivy`, but my counter argument would be that the better option is to add
> to `hydra` a new *function* to replace/complement the `defhydra`
> *macro*, so that `ivy-hydra.el` can be included into `ivy` (and compiled
> correctly) without needing to add a dependency on `hydra`.

Right.

> For `ivy-avy` I think the argument is almost the same, except I don't
> see any reason why it isn't done yet (there doesn't seem to be any need
> for `avy` to be around to compile correctly `ivy-avy`).
>
> So, let's start with this: Could we merge `ivy-avy` into `ivy`?

That's where it was until last year:

https://git.savannah.gnu.org/cgit/emacs/elpa.git/commit/?id=6a576cba564ab8860142f9ec343b13ec89cc2440

Thanks,

-- 
Basil