[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [elpa] chess.el: Req. for comment/review: Info manual

From: Eli Zaretskii
Subject: Re: [elpa] chess.el: Req. for comment/review: Info manual
Date: Wed, 18 Jun 2014 21:36:59 +0300

> From: Mario Lang <address@hidden>
> Date: Wed, 18 Jun 2014 20:20:14 +0200
> >   -   git clone --reference .. --single-branch --branch externals/PACKAGE 
> > git://git.sv.gnu.org/srv/git/emacs/elpa PACKAGE
> >   +   git clone --reference .. --single-branch --branch externals/PACKAGE 
> > $(git config remote.origin.url) PACKAGE
> >
> > is not necessarily for better: now this command and "make externals"
> > will do subtly different things, which not everyone will realize.  If
> > we want to be sure people with write access use the URL with write
> > access (and don't want to rely on them to know that and use the
> > correct URL), we should make changes to admin/archive-contents.el to
> > do that when all the externals are checked out.
> Hmm, I changed just README since I tripped over this behaviour when
> using make externals.  I originally wanted to change the code run by
> make externals as well, but I was a bit too much chicken regarding me
> being new on ELPA :-).  Feel free to revert the one-liner in README if
> you think it is too confusing.  Or I will do that, if you feel strongly
> about it.

I'll let Stefan and Glenn do TRT, I no longer feel I understand what
is going on with elpa and the externals.  Why on earth did it have to
be so complicated?  Why did I need to read the Lisp source to figure
out how to checkout a single package from externals?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]