Re: Git version of ELPA

[Achim Gratz <Stromeko@nexgo.de>]

Dmitry Gutov writes:
> Probably not, but Melpa does this okay. Aside from not having to pull
> from hundreds of external repositories, I think ELPA should work the
> same way (but also retain and use the Version header values).
>
> If implementing it is going to be a lot of work, are we willing to
> take package-build.el from the Melpa project and adapt it, or reuse
> some of its pieces? If maybe, do we care about copyright assignments
> for its code?

Melpa in its current form doesn't work with packages needing a build
system or more generally auto-generated files other than *.elc.  Since
this screws over everyone using their VCS The Right Way(TM), I don't
think this is a particularly good model to follow.  ELPA needs to
distribute _releases_ of packages, which necessarily means to add or
even alter files from the development tree.  I'll read the whole thread
again, but it seems that the structure envisioned for ELPA so far has
not directly considered the consequences of that fact.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html