[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: elpa.git and `new-master`
From: |
Stefan Monnier |
Subject: |
Re: elpa.git and `new-master` |
Date: |
Tue, 15 Dec 2020 16:33:14 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
>> > Can you explain what does this mean in practice for those who, like
>> > me, just maintain the Git repository without installing the packages
>> > via package.el?
>> Could you clarify what you mean by "maintain the Git repository"?
> It's just the result of cloning the ELPA repository.
Cloning is a pretty small part of "maintaining" and is usually useless
on its own. So give an example of what you want to do. It would start
with
git clone .../elpa.git
presumably, but the interesting part is what you want to do after that.
>> A normal clone of the elpa.git repository will include all the packages,
>> as before, none of them in `master` or `new-master`, tho: all of them in
>> externals/[PKGNAME] branches.
>>
>> make packages/[PKGNAME]
>>
>> will bring a specific package into its `packages/[PKGNAME]` subdirectory
>> (by way of `git worktree`).
>
> So I will have to use 'make' to get every single package?
No: `make externals` works as before to populate `packages` with all the
packages, if that's what you're after. In that case, nothing has
changed from before, mostly (except that if you want to commit changes
to a particular package, you have to do so from the
`packages/[PKGNAME]` subdirectory).
Stefan
Re: elpa.git and `new-master`, Stephen Leake, 2020/12/15
Re: elpa.git and `new-master`, Stephen Leake, 2020/12/15
Re: elpa.git and `new-master`, Jonas Bernoulli, 2020/12/15