Re: package.el, auto-installation, and auto-removal

[Nic Ferrier]

Achim Gratz <address@hidden> writes:

> Nic Ferrier writes:
>> One thing about elpakit's solution is that elpakit does this by making a
>> package with the right dependencies.
>>
>> Elpakit's solution is in fact just a package depend builder. Choose X, Y
>> and Z packages and then make a new package depending on those.
>
> So I'd have an (empty) package named "user-packages" and it depends on
> exactly those packages I named, possibly with their version specified?
> And I could maybe have a number of additional packages to create
> something of a hierarchy of such things?  Like a "system-packages"
> package that my "user-packages" package can depend on (or not if I don't
> want to)?

Yes.

Elpakit let's you do that. Stefan is asking for something simpler than
that. And I agree, something simpler than that is a good thing.


>> Maybe the current package installed by user state could be constantly
>> regenerated as a package.
>
> Or maybe just skip the actual packaging step and really only deal with
> the dependencies.

Sure. But packages are a useful encapsulation of dependencies.


Nic