Re: [STUMP] Package management for StumpWM

[David Bjergaard]

For what its worth, and since I couldn't do it, its probably not worth
that much, your proposal doesn't seem that bad as long as there are some
conventions that are followed.

Run a "git clone" into a specified module directory in stump's path
(similar things are done with contrib now) and then load the module as
you would a contrib module now... 

I don't think there are enough modules floating around to warrant a
dedicated package management system. Emacs doesn't have a unified one
yet, and there is a plethora of elisp scattered all over the web.  I
think your best bet is to grow up your module on github, advertise it
here and the wiki, and when its stable get it added to contrib. 

I have no authority though, people higher up will probably give better
advice.

        Dave

Duncan Bayne <address@hidden> writes:

>> There's a comment in the load-module
>> function (in module.lisp) that suggests perhaps in the future load-module
>> should use asdf to load modules. If that was implemented (or even better if
>> it was made quicklisp aware) then package management could become much
>> easier. It shouldn't be a difficult task, if only someone had the time to do
>> it of course!
>
> Quicklisp is great, but there's no (documented) way of creating your own 
> dists:
>
> "You will be able to make your own private repositories of Quicklisp
> software (called dists), but it's not documented right now."
>
> Given that Quicklisp is curated, it doesn't seem like a great place to
> put (likely experimental) StumpWM add-ins.
>
> Taking the 'wishful thinking' approach, what I want to be able to do
> is put something like the following at the start of my .stumpwmrc:
>
> (load-module "stump-monitors"
> "git://github.com/duncan-bayne/stump-monitors.git")
>
> ... and have that Just Work (TM) as you'd expect.