Re: Interoperation between package managers

[Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>]

>
> Why not just say it is the responsibility of the package manager to
> let the user say which packages it is to make available and which
> packages it is to leave for another package manager?
With a properly structured API there would be no difference between a 
function provided by a package manager and something you just hacked 
together. As such this question would be left to the user. An advantage 
for having it on this level would be that you can do such configuration 
in a uniform way regardless of the package manager you use.

> Would this require a restructuring of how autoloading works in
> general?
Yes, seems like it would require restructuring autoloading, but the 
change would probably be backwards compatible.

> Another thing I worry about is whether this is the right abstraction
> for package managers that operate in different ways than package.el.
I don't see how it wouldn't be. We're asking "hey, can anyone load 
cool.el?" Package.el would answer no, since cool.el is not installed, 
straight.el would answer yes. And if it decides to download cool.el, 
it's entirely a decision left to it and how it's configured. This of 
course opens a possible attack angle of me having (require 
'malevolent-el) somewhere in my legit code.

-- 
Best Regards,
Nikolay Kudryavtsev